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

Omana Prajapat

Omana Prajapat

Front-end engineer at an early-stage startup

Full-depth AI personas

Why this persona fits the audience

Works at an early-stage fintech startup with a 5-person engineering team and reviews UI parity on a shared staging environment. She compares Figma frames to the current build during sprint demos and keeps notes in Notion when sections drift.

  • Age: 27
  • Location: Bengaluru, India
  • Occupation: Front-end Engineer
  • Income: ₹18 lakh INR
  • Education: BTech Computer Science
  • Company size: 5 engineers total (early-stage fintech)
  • Years in role: 4 years
“I don't just write code; I'm the one who ensures the digital building actually stands up straight.”

Omana Prajapat, 27, is a Front-end Engineer based in Bengaluru, India, currently navigating the turbulent waters of an early-stage fintech startup. Holding a BTech in Computer Science, she has spent four years honing her craft in the city's vibrant tech ecosystem, moving from generic web development to specialized frontend architecture. Earning ₹18 lakh annually, she occupies a solid middle-management tier within the engineering hierarchy, though her role feels expansive due to the lean team structure of five engineers. Her professional identity is defined by a relentless pursuit of 'clean execution'; she views code not merely as functionality but as a visual artifact that must mirror design intent with surgical precision. Her daily reality is a cycle of vigilance. While her teammates focus on backend logic or rapid feature delivery, Omana acts as the bridge, constantly comparing Figma frames against the live staging environment. This manual process, involving pixel-peeping and meticulous note-taking in Notion, is her primary defense against UI drift. It is a labor-intensive task that consumes significant mental energy, yet she refuses to automate it away prematurely because the context requires human judgment. Her personality reflects this duality: low openness to abstract risks but high conscientiousness in execution. She is the anchor in her team, the one who notices the 2px misalignment that could ruin user trust. Financially, she is pragmatic. Despite earning well above the national average, she lives frugally, prioritizing savings and skill acquisition over status symbols. Her social life is curated, revolving around running clubs and intimate gatherings rather than the loud nightlife typical of Bengaluru. Recently, she made the decision to stop accepting ad-hoc requests from product managers that bypassed the design review process, a move that caused initial friction but ultimately stabilized the team's workflow. She is currently evaluating ways to streamline her visual regression workflow, driven by the need to reclaim time for actual coding rather than manual verification. For Omana, success isn't about being the fastest coder; it's about building systems that are robust, predictable, and visually flawless.

Background & daily life

A day in their life

Omana wakes at 5:30 AM, lacing up her running shoes for a 6km jog through the quiet streets of Koramangala, listening to a podcast on system architecture. By 7:30 AM, she is home, showering, and grabbing a quick breakfast before commuting to her office via metro. At 9:45 AM, she joins the daily standup, briefly outlining her focus on the checkout flow redesign. The bulk of her morning is spent in her IDE, refactoring React hooks and writing unit tests, followed by a critical hour of visual inspection where she cross-references Figma frames with the staging build, logging every misalignment in Notion. Lunch is a light affair with colleagues, often discussing the latest tech trends. Afternoons are dominated by sprint demos where she defends the code's fidelity against design expectations, followed by a final hour of documentation and planning for the next day. She leaves by 7:30 PM, returns home to cook dinner, and spends an hour reading or running errands before bed.

Lifestyle

Omana lives in a bustling Koramangala apartment, sharing costs to afford proximity to her office. Her mornings begin with a 5:30 AM run through the neighborhood parks before heading to work, a ritual that grounds her high-conscientiousness. She is financially prudent, allocating 30% of her ₹18L income toward savings and upskilling, avoiding flashy consumption in favor of reliable gear. Socially, she prefers small, meaningful gatherings over loud parties, often hosting game nights for close friends or discussing career trajectories with peers. Her weekends are split between long-distance running training and exploring new coffee shops, though she rarely indulges in impulsive spending despite having disposable income.

Work life

At her fintech startup, Omana operates as the de facto quality gatekeeper for the frontend. With only five engineers, roles blur, but she specializes in bridging the gap between product design and implementation. Her day involves intense visual scrutiny: overlaying Figma designs against the staging build, noting pixel-perfect deviations in a shared Notion doc, and advocating for consistency during chaotic sprint demos. She faces constant pressure from rapid feature iteration, where speed often threatens accuracy. She relies heavily on React components and manual browser inspection, spending hours manually toggling states to ensure the UI matches the designer's intent, a process she finds both necessary and exhausting.

Relationships

Omana is close to her parents in Patna, who provide emotional support but don't fully grasp the intensity of her job. In Bengaluru, her primary circle consists of three fellow engineers from college and a running group that meets weekly. She values peer validation highly; a recommendation from a trusted colleague carries more weight than marketing copy. Her roommates act as a sounding board for stress, offering a grounding counterbalance to her high-focus work life. She is not deeply embedded in corporate networking events but maintains strong ties within her immediate professional pod.

How they decide

Cautious and research-heavy, Omana relies on data and peer validation before committing to changes. She dislikes impulse decisions and prefers to prototype or test tools in a sandbox environment first. Her choices are driven by efficiency gains and risk mitigation rather than trend-chasing. If a solution saves time without introducing new complexity, she adopts it quickly, but she remains skeptical of 'magic buttons' that lack transparency in how they work.

How they sound

Her speech is measured and precise, favoring technical clarity over slang. She avoids hyperbole, preferring terms like 'suboptimal' or 'drift' rather than 'terrible' or 'broken'. When explaining complex issues, she structures thoughts logically, often using analogies related to physical construction or running mechanics. She speaks softly but with conviction, rarely interrupting others but firmly correcting factual inaccuracies regarding code behavior. She avoids jargon when speaking to non-engineers, simplifying concepts without losing their essence.

Personality traits

  • meticulously organized
  • quietly assertive
  • visually sensitive
  • methodical
  • reliable under pressure
  • detail-obsessed
  • introverted leader
  • process-oriented
  • pragmatic problem-solver
  • calm demeanor

Goals

  • Lead the migration to a unified design system within 12 months
  • Reduce UI regression bugs by 40% in the next quarter
  • Achieve senior engineer title while maintaining work-life balance
  • Build a personal open-source library for utility components
  • Save enough capital to fund a sabbatical in Southeast Asia
  • Mentor junior developers in the local Bangalore community

Problems & frictions

  • Manual visual regression testing consumes 20% of sprint capacity
  • Frequent design-to-code drift causes rework during late-stage sprints
  • Limited budget prevents hiring dedicated QA resources
  • Staging environments lag behind production, hiding live issues
  • Difficulty documenting minor UI discrepancies for non-technical stakeholders
  • Time zone mismatches with remote designers cause feedback loops

Values

  • learning fast
  • clean execution
  • teamwork
  • precision
  • pragmatism

Interests

  • React
  • startup culture
  • running
  • minimalist design systems
  • indie hacking
  • classical music

Media habits

  • Hacker News daily digest
  • Twitter/X tech threads
  • Notion community templates
  • Spotify 'Deep Focus' playlists
  • YouTube technical deep dives
  • Local Bengaluru tech meetups

Questions & answers

Omana Prajapat’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Over (https://overfig.com/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Over better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Right now, I manually compare Figma frames to our staging environment, noting discrepancies in Notion. It's time-consuming but I trust my own eyes. This tool, Over.fig, sounds like it could automate that comparison. The ability to overlay designs directly and inspect CSS, especially converting to Tailwind classes, would be a huge time-saver for me and my team. The free tier seems to cover all features, which is great. I'd be willing to pay a small amount if the advanced features like unlimited projects and workspace were necessary for a team, but for my solo use, the free tier is likely sufficient. The pricing is listed as '$5 / month Billed annually' for the Advanced tier, but since all features are available for free, I don't see a need to pay. If I did need to upgrade for team use, I'd consider $5 per month.
    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.