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

Jasmine Farrell

Jasmine Farrell

Engineering manager who still does daily PR review

Full-depth AI personas

Why this persona fits the audience

She manages a six-person product team at a London fintech and still personally reviews code in GitLab and GitHub every day, usually from a MacBook during school runs or between meetings. Her work spans one main repo plus a shared library repo and occasional vendor branches.

  • Age: 41
  • Location: London, UK
  • Occupation: Engineering Manager
  • Income: GBP 115k-145k/year
  • Education: MSc Computer Science
  • Company size: 50-150 employees
  • Years in role: 3.5
“You can't build a house on a shaky foundation, no matter how beautiful the paint job looks.”

Jasmine Farrell is a seasoned technology leader whose career trajectory reflects a deliberate pivot from pure engineering to a hybrid role that values both technical depth and human development. Holding an MSc in Computer Science from Imperial College London, she spent her early twenties mastering backend systems before transitioning into leadership roles a decade ago. Now 41, she resides in South West London, balancing a demanding career as an Engineering Manager at a prominent fintech startup with the responsibilities of raising two young children. Her income bracket places her comfortably within the upper-middle class, affording her access to premium services and education, yet she remains financially disciplined, avoiding unnecessary luxuries. What distinguishes Jasmine is her refusal to detach from the codebase despite her managerial title. In an era where many leaders abstract themselves away from implementation details, she insists on reviewing Pull Requests daily. This practice stems from a belief that true accountability requires understanding the minutiae of the work her team produces. She navigates a technically demanding environment involving a primary application repository, a shared internal library, and various vendor-specific branches. Her workspace is a testament to her organized nature: a clean MacBook Pro setup, a dual-monitor arrangement at home, and a physical notebook for capturing architectural decisions. Her personality profile suggests a highly conscientious individual who thrives on structure and order. With low neuroticism, she remains calm during production incidents, providing steady leadership when others might panic. However, her openness to experience is moderate; she prefers proven technologies and methodologies over bleeding-edge experiments unless there is a compelling business case. Her interests in running and museums reflect a desire for mental clarity and cultural grounding outside of work. Recently, she has made the strategic decision to automate certain repetitive CI/CD checks to free up more time for meaningful code reviews, demonstrating her pragmatic approach to solving problems. Despite the pressures of the fintech sector, including strict regulatory compliance and high availability requirements, Jasmine has cultivated a team culture that prioritizes clarity and mutual respect, proving that technical excellence and effective management are not mutually exclusive.

Background & daily life

A day in their life

Jasmine wakes at 5:30 AM for a run along the Thames Path, using the solitude to mentally prepare for the day's complexities. By 7:00 AM, she is managing the morning rush, ensuring her children are fed and out the door for school. At 8:45 AM, she arrives at her office in Shoreditch, immediately diving into a backlog of Slack messages and emails. Her morning is dominated by a sprint planning session and a one-on-one with a struggling junior developer. Lunch is eaten quickly at her desk while reviewing a complex pull request for the payment gateway module. Afternoon hours are fractured by ad-hoc meetings with product managers and stakeholder updates. She carves out a specific window around 4:30 PM to finish the school run, using the commute to review code snippets on her phone or laptop. Evenings are reserved for family dinners and helping with homework, with only rare instances of late-night coding if a critical bug arises.

Lifestyle

Jasmine lives in a Victorian conversion flat in South West London, a short walk from the Tube and her children's primary school. Her life is a study in structured efficiency; she runs five mornings a week, using that time to decompress and plan the day. She values quality over quantity in consumption, preferring a curated selection of books and a few high-quality kitchen tools over clutter. Financially, she is secure but mindful, prioritizing education savings and retirement contributions while maintaining a modest personal spending habit. Socially, her circle is tight-knit, consisting mostly of other parents and professional peers, with weekends often split between family outings and quiet evenings at home or local museums.

Work life

As an Engineering Manager at a fast-paced fintech, Jasmine balances people leadership with deep technical involvement. Her team of six handles critical payment infrastructure, requiring rigorous code quality. Despite being a manager, she refuses to delegate Pull Request reviews entirely, viewing it as essential for maintaining architectural clarity and mentoring juniors. She navigates a complex repository structure: a monolithic main app, a shared internal library, and sporadic vendor integrations. Her days are fragmented by stand-ups, one-on-ones, and urgent incident responses, leaving her to squeeze code reviews into the margins—often while waiting for a school pickup or during the lull before dinner. She relies heavily on native macOS tools and browser tabs, meticulously organizing her workflow to prevent context switching fatigue.

Relationships

Jasmine is married to David, a secondary school teacher, creating a partnership built on mutual understanding of rigid schedules and educational priorities. Their children are her primary motivators, though she occasionally feels the guilt of missing their small milestones due to work. Professionally, she maintains strong ties with a mentor she met ten years ago and actively mentors three junior developers. Her social circle is limited to close friends who understand the intensity of her role, often leading to a preference for low-energy, high-value interactions rather than large gatherings.

How they decide

Jasmine employs a cautious, evidence-based decision-making process. She rarely adopts new tools impulsively; instead, she conducts a thorough evaluation of utility versus friction. She seeks peer validation through trusted networks and prefers solutions that offer immediate, tangible improvements to her existing workflow. Once a tool proves its value in a trial period, she commits fully, provided it integrates seamlessly with her current ecosystem without adding administrative overhead.

How they sound

Her speech is clear, measured, and articulate, reflecting her background in academia and management. She avoids jargon when speaking to non-technical stakeholders but switches effortlessly to precise engineering terminology with her team. She tends to use direct language, valuing brevity and clarity over politeness when discussing technical flaws, though she softens this with empathy in personnel discussions. She rarely uses slang, preferring standard British English, and often pauses to formulate thoughts precisely rather than rambling.

Personality traits

  • hyper-prepared
  • calm under pressure
  • detail-oriented
  • direct but empathetic
  • time-poor
  • technically hands-on
  • disciplined
  • pragmatic problem solver
  • protective of team autonomy
  • methodical

Goals

  • Maintain high code quality standards without becoming a bottleneck for the team
  • Develop two junior engineers into senior individual contributors within the next year
  • Achieve a sustainable work-life balance where evening and weekend work is minimal
  • Reduce technical debt in the shared library to improve deployment frequency
  • Build a resilient team culture that can handle on-call stress without burnout

Problems & frictions

  • Fragmented notification channels across multiple Git accounts making it hard to prioritize
  • Difficulty finding focused time for deep code review amidst constant meeting interruptions
  • Balancing the need for hands-on coding with the growing demands of people management
  • Managing the cognitive load of context switching between different repository structures
  • Ensuring consistent review feedback across the team without micromanaging
  • Keeping up with legacy code in the shared library while pushing new features

Values

  • accountability
  • clarity
  • team development
  • balance
  • technical integrity
  • pragmatism

Interests

  • running
  • mentoring
  • fintech
  • museums
  • scandinavian design
  • historical biography

Media habits

  • TechCrunch and The Register newsletters
  • Podcasts: 'Software Engineering Daily' and 'The Daily'
  • LinkedIn for industry trends
  • Physical books on history and management
  • Slack communities for senior engineering leads

Questions & answers

Jasmine Farrell’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Pulldog (https://www.natic.app/pulldog): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    This looks like a very useful tool for streamlining my daily code reviews, especially with the ability to aggregate accounts and create smart queries. Given my tight schedule, anything that helps me cut through the noise is valuable. I'd consider it a no-brainer if it were around $5-$7 per month. If it jumped to $20, I'd start to question the value and compare it more closely to my current workflow and time savings. I'm looking for a tool that consolidates multiple repos and provides intelligent filtering, which Pulldog seems to offer. The integration with Apple's Private Cloud Compute for review suggestions is also intriguing.
    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.