10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Navin Dhawan

Navin Dhawan

UI developer at a services firm

Full-depth AI personas

Why this persona fits the audience

UI developer at a 12-person product-services firm in Pune; converts Figma mockups into HTML/CSS for three active client projects, and often swaps icons between libraries to match spacing, export format, and color requirements in the handoff.

  • Age: 24
  • Location: Pune, India
  • Occupation: UI Developer
  • Income: ₹12 LPA
  • Education: Bachelor's degree
  • Company size: 12
  • Years in role: 3
“It’s about getting every pixel just right, making sure the client’s vision translates perfectly, and that the final code is as clean as the design itself.”

Navin Dhawan grew up in a middle-class family in a smaller city near Pune, where his father worked as an accountant and his mother was a homemaker. From an early age, he showed a knack for logical thinking and problem-solving, which naturally led him to pursue a Bachelor's degree in Computer Science. During his studies, he discovered a passion for web development, particularly the tangible results of turning designs into functional interfaces. He excelled in his coursework, always driven by a desire for precision and a deep satisfaction in creating order from complexity. Upon graduating, he was eager to enter the professional world and joined his current firm, a compact product-services company in Pune, specifically because of its diverse client projects and the opportunity to learn quickly. He's been with them for three years, steadily building his expertise. Navin is highly conscientious, meticulously organizing his work and double-checking every detail. This is evident in how he approaches his current role, converting intricate Figma mockups into robust HTML/CSS. He’s currently working on three major client projects, a common scenario in his firm, which often means context-switching and maintaining high standards across different codebases. A recurring challenge, and a point of significant focus for him, is managing icon assets; he frequently finds himself hunting for specific icons across various libraries, painstakingly adjusting their size, color, and export format to perfectly match design specifications for a 'precise handoff'. This meticulousness, while time-consuming, ensures the final product is polished and meets client expectations. He views his income of ₹12 LPA as a solid foundation, allowing him to live comfortably while saving diligently, with aspirations for future financial independence. His professional life is his primary focus, but he finds satisfaction in the efficient execution of tasks and the positive feedback from clients.

Background & daily life

A day in their life

Navin's weekday begins around 7:30 AM with a quick breakfast before cycling to the office. His workday starts at 9:30 AM, immediately diving into code. He typically spends the morning refining HTML structures and CSS for one client project, then switches gears to implement interactive elements or fix bugs on another. Lunch is usually a packed meal from home, eaten at his desk while scanning industry news. Afternoons involve more coding, attending brief stand-up meetings, and often troubleshooting icon inconsistencies for an upcoming feature. He leaves the office around 6:30 PM, cycles home, has dinner, and might spend an hour or two on a personal coding exploration or watching a tutorial before winding down for the night.

Lifestyle

Navin lives in a modest rented apartment in Kothrud, sharing with two college friends. His evenings are often spent after dinner, either catching up on personal coding projects or watching tech review videos on YouTube. He prioritizes saving a portion of his salary, aiming to eventually buy his own place, but also enjoys occasional outings with friends to local eateries. He cycles to work to save money and stay fit, usually packing his lunch from home to further control expenses. Socially, he’s part of a WhatsApp group for his engineering alumni and stays in touch with family weekly.

Work life

As a UI Developer at a small, agile product-services firm, Navin's days are consumed by translating complex Figma designs into pixel-perfect HTML and CSS. He juggles three client projects simultaneously, each with its own brand guidelines and technical constraints. A significant part of his work involves meticulously managing icon sets, often spending time to find the exact right icon from different libraries, ensuring consistent spacing, correct export formats, and precise color matching for seamless client handoffs. He collaborates closely with a senior developer and the project manager, who are his main points of contact for technical queries and project timelines.

Relationships

Navin is close with his parents and younger sister back in their hometown, calling them every Sunday. His immediate circle consists of his two roommates and a few colleagues from college who now work in similar roles. He trusts the advice of his senior developer at work for technical decisions and values the pragmatic guidance of his project manager for client-facing issues.

How they decide

Navin approaches decisions methodically. For work-related tools and processes, he prioritizes proven solutions and efficiency, often researching best practices and seeking input from his senior colleague. For personal purchases, he tends to compare options, read reviews, and consider the long-term value and cost-effectiveness before committing.

How they sound

Navin speaks with a measured pace, clear enunciation, and a generally polite tone. His English is proficient, with a slight Pune accent. He tends to use technical jargon naturally when discussing work but keeps his language accessible otherwise. He avoids overly casual slang and prefers precise phrasing, especially when explaining technical concepts. When stressed, his speech might become slightly more rapid, but he generally maintains composure.

Personality traits

  • meticulous
  • reliable
  • methodical
  • patient
  • observant
  • practical
  • diligent
  • detail-oriented

Goals

  • Achieve senior developer status within five years
  • Contribute to an open-source front-end project
  • Develop expertise in a specific JavaScript framework (e.g., React)
  • Save enough for a down payment on an apartment in Pune
  • Maintain a good work-life balance without sacrificing career growth

Problems & frictions

  • Inconsistent asset delivery from design teams
  • Tight project deadlines that sometimes compromise thoroughness
  • Managing multiple client requests with limited resources
  • Keeping up with the rapid evolution of front-end tools and best practices
  • Finding high-quality, consistently styled icon sets for diverse projects

Values

  • precise handoff
  • efficiency
  • attention to detail
  • client satisfaction
  • clean code

Interests

  • front-end HTML/CSS
  • component libraries
  • client project delivery
  • performance optimization
  • web accessibility

Media habits

  • Stack Overflow for quick fixes
  • YouTube tutorials on new CSS techniques
  • following design and front-end blogs (e.g., Smashing Magazine)
  • occasional Reddit threads on development tools
  • WhatsApp for team communication

Questions & answers

Navin Dhawan’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Icon Stash (iconstash.io): a searchable icon library for designers and builders who need icons that fit their product, design system, or codebase. Thinking about how you actually pick and use icons today (Figma libraries, Lucide, Heroicons, Font Awesome, SVGs in the repo, design-system tokens, VS Code / IDE plugins, Storybook, etc.): 1. Which ONE integration would most make you start using Icon Stash (instead of sticking with what you have)? Be specific — e.g. Figma plugin, design-system sync, VS Code / Cursor extension, Storybook, npm package, Slack/Notion, CMS, or something else. 2. Why that integration over the others? 3. What would still stop you from switching even if that integration existed?

    A Figma plugin would be the most impactful integration for me. I spend so much time ensuring icons match Figma specs, so having that seamless link would save a ton of effort. It's the core of my workflow. Other integrations like Storybook or an npm package are useful, but if the icons aren't right in the design tool first, it creates extra work downstream. What would stop me is if the icon library's style wasn't consistent enough with what my clients expect, or if it didn't offer the specific variety I need for different projects.
    View answer & full research →
  2. What would stop you from trying Icon Stash (https://iconstash.io) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    The main thing that would stop me from trying Icon Stash this month is the potential time investment. My current workflow involves pulling icons from various libraries, and I'm very meticulous about matching spacing, export format, and color requirements. While Icon Stash promises to unify this, I'd need to see how efficiently I can actually find and customize icons to my exact needs without spending more time than I already do. Today, I'm manually hunting and downloading them one by one, often comparing them side-by-side in Figma. I wouldn't pay more than $5 per month for this tool.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.