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

Felicia Kemmer

Felicia Kemmer

Engineering manager at a startup

Full-depth AI personas

Why this persona fits the audience

Manages an eight-person product engineering group split across two squads: frontend, backend, mobile, and QA. Uses Jira, Confluence, and GitHub Copilot in day-to-day work, while spending a lot of time translating roadmap items into executable tasks and keeping release coordination on track.

  • Age: 29
  • Location: Manchester, UK
  • Occupation: Engineering Manager
  • Income: £62k base + bonus
  • Education: BSc in Computing
  • Company size: 25-50 people
  • Years in role: 3
“«I don’t mind late nights when the code’s breaking, but I draw the line at late nights when it’s just people breaking their promises."”

Felicia Kemmer cut her teeth as a junior developer at a fintech startup, where she accidentally became the de facto project coordinator after the designated Scrum Master quit during a particularly messy AWS outage. That experience—combined with her undergraduate thesis on «cross-team communication in agile environments»—led her to pivot into management, landing her current role at a B2B SaaS startup building tools for clinical research. Her first year was chaos: she inherited a team where the backend squad joked their CI/CD pipeline was «held together with duct tape and swear words», and the frontend lead was convinced everyone else was «just not trying hard enough». Felicia’s first major intervention was instituting «docs before deploy» meetings, which initially met with eye-rolls but eventually became her team’s most efficient knowledge-sharing ritual. Her real breakthrough came when she convinced leadership to split the squads geographically, moving the backend to Manchester while keeping QA and frontend in London. The hybrid setup was rocky at first (she still has PTSD from the «cultural mismatch» Slack thread that went 47 messages deep), but it gave her engineers more ownership—and fewer 7 AM video calls. Her proudest accomplishment? Getting her team to adopt a «no-meeting Mondays» policy, which cut context-switching and gave her space to finally tackle her backlog of 1:1s. Now, she’s navigating the challenge of scaling her management style as the team grows, all while trying to convince her fiancé that their ‘weekend road trips’ are sabotaging her meal prep. She’s pragmatic about the tradeoffs: she’ll always fight for her team’s capacity, but she’s learned to stop apologizing for leaving before 6:00 PM.

Background & daily life

A day in their life

Felicia’s weekday starts at 6:45 AM with almond milk oatmeal while skimming yesterday’s GitHub issues. The 7:15 train from Chorlton is her sacred silent reading time (*The Pragmatic Programmer* on her Kindle, currently on the second read-through). At the office, she does a quick desk audit—if she sees more than 3 sticky notes, she knows she’ll need to schedule a team clean-up. By 11:30, she’s in a «tl;dr meeting» with product, where she’s mastered the art of listening while subtly prioritizing her to-do list in Notion. Lunch is either the same halloumi wrap from the café or her «emergency protein bars» if meetings overrun. Afternoons are her «thinking time», usually spent in a corner of the office café with a Mocha Java, reviewing her team’s velocity charts. She calls it quits at 5:45 PM sharp, unless a «migration emergency» requires her attention—then she’ll pull a «divide and conquer» strategy with the backend lead. Her evening routine is 6:15 PM guitar practice (Mark insists the soundproofing in the spare room is «for the neighbors, not you»), 7:30 PM home-cooked meal while watching *Taskmaster*, and 10:00 PM bedtime with her «no-screens» rule—though she often fails to resist 5 minutes of Reddit’s r/webdev.

Lifestyle

Felicia shares a renovated terrace house in Chorlton with her fiancé, Mark. Their weekends alternate between local hiking (she’s recently become obsessed with the Peak District) and band practice (she plays rhythm guitar in a GarageBand-esque indie outfit called The Overclockers). She’s diligent about her gym routine but cuts herself slack on weekends, binge-watching *The Great British Bake Off* while snacking on the biscuits Mark insists they don’t need. Financially, she’s comfortable but tight-lipped about spending: she maxes out her ISAs, splurges on a new guitar pedal every other year, and refuses to pay for coffee after 3:00 PM. Socially, her closest friends are former uni classmates who’ve all scattered across Europe, so she maintains relationships via a weekly Zoom «pub quiz» they host. Mark teases her for her «managerial bedtime routine»—that is, reviewing the next day’s calendar while eating a banana with peanut butter.

Work life

Felicia’s days are a relentless dance of coordination: 9:30 AM starts with a standup that she insists stays under 20 minutes, followed by a ritualistic Confluence audit of her backend squad’s documentation. By noon, she’s usually knee-deep in GitHub PR reviews, hunting for «technical debt smell» in commits. She loathes status meetings but has embraced a personal rule of «if it takes more than 3 emails to resolve something, we’re having a chat». Her biggest recent win was convincing leadership to adopt GitHub Copilot for the mobile squad, but she’s still dealing with the fallout from a botched Azure migration that left QA scratching their heads for two weeks. She’s constantly juggling her team’s capacity (especially her frontend lead, who’s about to go on parental leave) and the product manager’s «we need this yesterday» requests. Her secret weapon? A shared Trello board for her fiancé and herself where they track household chores—their version of agile retrospectives.

Relationships

Felicia’s parents, both teachers, still tease her about «getting a real job» despite her raising her salary early. Her best friend from uni, now in Berlin, is her «emotional Slack channel» for venting about startup culture. Mark’s the only one who’s seen her cry during a particularly stressful sprint review. She’s close with her QA lead, Priya, who’s become her co-conspirator in gently pushing back on unrealistic deadlines. Her band’s drummer, a physics postgrad, is the only person she’ll admit to being slightly intimidated by. She still hasn’t told her parents about the band.

How they decide

Research-heavy but timeboxed: for work decisions, she starts with her «3-2-1 rule» (consult 3 sources, get 2 opinions, make a choice in 1 hour). Social decisions follow the «Mark veto rule» (if he visibly winces at her suggesting another tapas night, she’ll relent and order curry instead). She’s stubborn about her no-meeting Wednesdays but will suddenly deviate from her routine if a problem smells like «foundation-level technical debt».

How they sound

Felicia speaks in measured, pragmatic sentences with a slight Mancunian lilt. She avoids jargon with newcomers («Just say ‘backend’ instead of ‘server-side’, mate») but defaults to technical shorthand with her team. Her «tell» is a sharp intake of breath when she hears an unrealistic deadline. She often says «I’ll gentle push back on that» or «We should put a pin in that». She laughs self-deprecatingly when caught mid-air guitaring in the kitchen but bristles if her band’s soundcheck is interrupted.

Personality traits

  • The kindly but unshakably organized project wrangler
  • Pragmatic collaborator who values clarity over verbosity
  • Hates ambiguity in sprint planning but thrives in 1:1 mentoring
  • Tactical optimist who defaults to
  • If it's working, let's not break it
  • Secretly competitive about her guitar skills in the band's practice sessions
  • Ruthless about protecting personal downtime after work
  • Tends to eat the same three lunches on rotation (avocado toast, halloumi wrap, sushi bento)
  • Struggles to say no to volunteering for mentorship programs
  • Keeps a meticulously color-coded calendar but loathes filling out timesheets

Goals

  • Hit Senior Engineering Manager by 35 to offset the gender gap in leadership
  • Get The Overclockers signed to a local venue for monthly gigs (despite Mark’s insistence they’re «not ready»)
  • Finish the Coursera cybersecurity specialization before the industry certification expires
  • Learn enough Spanish to understand Mark’s family at their next visit to Barcelona
  • Stop checking Slack after 7:15 PM (currently at 22% success rate)

Problems & frictions

  • Her backend squad’s habit of silently fixing critical bugs in production (they argue it’s «just how things get done»)
  • The office’s lack of natural light makes her default to 2:30 PM espresso runs to the café
  • Her fiancé’s insistence on «spontaneous weekend drives» interferes with her batch-cooked Sunday meal prep
  • She’s been meaning to write a blogpost about «agile fatigue in startups» for 18 months
  • Her bandmate Simon keeps cancelling practices because his girlfriend’s cat keeps knocking over his pedals
  • She’s 80% sure her product manager is using AI to rewrite her emails (but can’t prove it)

Values

  • predictability
  • collaboration
  • focus
  • work-life balance
  • continuous learning

Interests

  • people management
  • agile coaching
  • guitar
  • hiking
  • urban planning

Media habits

  • Tech YouTubers (Fireship, Computerphile)
  • GitHub discussions
  • BBC News
  • Spotify playlists for focus
  • Indie game dev blogs

Questions & answers

Felicia Kemmer’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Klyve (https://klyve.online): 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).

    As an Engineering Manager, I’m constantly juggling between high-level planning and ensuring my team’s execution stays on track. Tools like GitHub Copilot have been helpful, but they’re still tactical. Klyve’s promise of full-lifecycle engineering is intriguing—being able to offload 90% of the non-coding work (specs, testing, documentation) could be transformative for my team. However, given my experience with integrations like Azure, I’d need to ensure Klyve plays well with our existing stack (Jira, Confluence, and GitHub). The local-first approach is a big plus for security and compliance, which aligns with my priorities. But the beta phase raises questions about stability and support. If Klyve can handle end-to-end project orchestration with minimal oversight, I’d consider it a game-changer. I’d likely pay up to $99 per month, per license, but only if it significantly reduces our cycle time and technical debt.
    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.