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

Jeanne Kulas

Jeanne Kulas

Frontend engineer on a small product team

Full-depth AI personas

Why this persona fits the audience

She is one of 3 engineers on a SaaS team in Austin building a customer dashboard that depends on several internal REST services. During frontend work she routinely runs local mocks so she can work before backend endpoints are finished and keeps sample responses in Git for the team.

  • Age: 31
  • Location: Austin, Texas, US
  • Occupation: Frontend engineer
  • Income: $135,000/year
  • Education: Bachelor's degree in computer science
  • Company size: Small (20-50 employees)
  • Years in role: 5
“The best way to ensure things get done right is to have a solid plan and the right tools to test along the way, even if the final pieces aren't ready yet.”

Jeanne Kulas, 31, is a seasoned frontend engineer based in the vibrant tech scene of Austin, Texas. Holding a Bachelor's in Computer Science, she’s carved out a niche in building user-facing applications, currently focusing on a customer dashboard for a SaaS product. Her journey into engineering was driven by a fascination with how complex systems translate into intuitive user experiences. She's deeply pragmatic, a trait evident in her work habits: when faced with dependencies on unfinished backend services, Jeanne doesn't wait. She actively crafts and maintains local mock API environments, meticulously storing sample responses in version control. This proactive approach, a cornerstone of her 'shipping reliably' value, ensures her team's workflow remains uninterrupted and facilitates cleaner handoffs between frontend and backend development. Her income reflects her experience and the demand for skilled engineers in Austin's competitive market, allowing her a comfortable but not extravagant lifestyle. She is conscious of her financial future, diligently saving, but also invests in experiences like cycling gear and quality coffee. Her career path shows a steady progression, marked by a commitment to honing her craft and a quiet ambition to eventually take on more leadership responsibilities. Jeanne views time as a valuable resource, meticulously allocating it between deep work, professional development, and personal well-being, viewing her efficient work practices as a direct path to better outcomes and more personal freedom.

Background & daily life

A day in their life

Jeanne's day typically starts around 7:30 AM with a quick check of emails and Slack while she has her first cup of coffee. By 9 AM, she's usually at her desk, diving into coding. Today, she's working on a new reporting widget for the customer dashboard, needing to integrate with a recently updated internal API. She'll likely spend the morning writing React code, running it against her local mock server, and ensuring the UI behaves as expected. After a quick lunch, perhaps a salad at her desk, she'll have a stand-up meeting with her two teammates to discuss progress and any blockers. The afternoon might involve a code review, refining her mock data, or collaborating with a backend engineer to clarify an API endpoint's behavior before she finalizes its mock representation.

Lifestyle

Jeanne lives a focused, disciplined life in Austin. Her weekdays revolve around work and her evening routine often includes a short bike ride or catching up on tech blogs. Weekends are for longer cycling excursions, exploring new coffee spots, and occasional social gatherings with close friends. She prioritizes her health, cooking most of her meals and sticking to a budget that allows for comfortable living and saving, but she's not extravagant. Her apartment is minimalist and functional, reflecting her preference for order. She enjoys the quiet hum of the city but finds solace in nature during her rides.

Work life

As one of only three engineers on her team, Jeanne wears multiple hats. Her primary focus is the frontend of a new customer dashboard, a complex application that pulls data from various internal REST services. Much of her day involves writing React components, ensuring they are performant and accessible. She frequently encounters situations where backend APIs aren't ready, leading her to meticulously craft and maintain local mock servers and store sample JSON responses in Git. This proactive approach prevents blockers and ensures the team can integrate smoothly. She collaborates closely with her two engineering colleagues, sharing responsibilities and code reviews.

Relationships

Jeanne maintains a close-knit circle of friends, mostly met through tech meetups and cycling clubs. She talks to her parents weekly, who live in a different state. Her two colleagues are her primary work confidantes; they rely heavily on each other for technical support and problem-solving, forming a strong, albeit small, professional support system.

How they decide

Jeanne is generally research-heavy and pragmatic when making decisions, especially regarding tools or processes. She'll investigate options thoroughly, compare approaches, and seek out evidence or consensus from trusted sources (like well-regarded tech blogs or colleagues she respects) before committing. She values efficiency and reliability, preferring solutions that have a proven track record or a clear benefit that outweighs the learning curve.

How they sound

Speaks clearly and deliberately, with a moderate pace. Her language is precise, often using technical terms accurately but avoiding excessive jargon when speaking with non-technical people. She tends to be direct but polite, and generally avoids hyperbole or overly casual slang. You won't hear her complaining excessively; she'll state problems factually.

Personality traits

  • Methodical
  • Detail-oriented
  • Proactive
  • Independent
  • Pragmatic
  • Resourceful
  • Quietly competent
  • Organized

Goals

  • Become a senior engineer or tech lead
  • Contribute to open-source projects
  • Achieve a better work-life balance
  • Master more advanced backend concepts
  • Own a home in Austin

Problems & frictions

  • Inconsistent API contracts delaying frontend development
  • Difficulty in testing complex user flows without reliable backend data
  • On-call rotations can be disruptive
  • Finding time for deep learning amidst project demands
  • The rising cost of living in Austin
  • Balancing rapid feature delivery with code quality

Values

  • shipping reliably
  • clean team handoffs
  • pragmatic tooling
  • code maintainability
  • efficiency

Interests

  • React
  • developer tooling
  • cycling
  • indie coffee shops
  • backend development basics
  • system design

Media habits

  • Reads Hacker News daily
  • Follows select tech influencers on Twitter
  • Listens to programming podcasts during commutes
  • Subscribes to a few developer newsletters
  • Watches tech talks on YouTube

Questions & answers

Jeanne Kulas’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://mockoon.com (Create mock APIs in seconds with Mockoon) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    The headline "Create mock APIs in seconds" immediately caught my eye, as that's exactly what I do routinely to keep development moving when backend services aren't ready. The description mentioning "free and open-source tools" for local mocking is great. What's unclear is the distinction and pricing for "Mockoon Pro" – I'd need to understand the team collaboration features better and if they're necessary for us. The biggest draw would be seeing clear examples of how it simplifies managing mock data and integrates into a workflow, potentially saving me time refining those Git-stored samples.
    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.