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

Kathryn Gerlach-Anderson

Kathryn Gerlach-Anderson

Staff product engineer on a small fintech team

Full-depth AI personas

Why this persona fits the audience

Works on a 5-person London fintech team, using a MacBook Pro to run 2-3 Claude Code sessions and occasional Gemini sessions against the same TypeScript codebase while the team tracks work in Linear and Slack. She reviews logs and latest notes before merging.

  • Age: 35
  • Location: London, UK
  • Occupation: Staff Product Engineer
  • Income: £105k
  • Education: MSc Software Engineering
  • Company size: 5 people (Seed stage)
  • Years in role: 4 years as Staff Engineer
“I don't need the AI to write the code for me; I need it to do the boring parts so I can focus on the architecture that keeps the money safe.”

Kathryn Gerlach-Anderson is a 35-year-old Staff Product Engineer based in London, operating at the intersection of high-stakes fintech reliability and rapid prototyping. With an MSc in Software Engineering and nearly a decade of experience, she has transitioned from pure backend development to leading product engineering efforts in a lean, five-person startup environment. Her career is defined by a relentless pursuit of system integrity; she understands that in finance, a single line of buggy code can have catastrophic consequences. Currently, she is navigating the complex landscape of AI-assisted development, where she acts as the gatekeeper for three simultaneous AI coding agents. Unlike many peers who treat AI as a black box, Kathryn maintains a granular, manual oversight process, reviewing logs and notes before any merge occurs. This approach stems from a deep-seated belief in 'measured experimentation' and 'reliability.' She works on a MacBook Pro, often juggling terminal sessions that feel chaotic without a central dashboard. Her income of £105k reflects her seniority and the high cost of living in London, yet she remains frugal, investing surplus funds into retirement and property rather than gadgets. Recently, she made the strategic decision to standardize on TypeScript across the entire codebase to better manage the complexity introduced by multiple AI agents. She is currently grappling with the inefficiency of having to manually aggregate context from different AI sessions, a problem that directly impacts her ability to maintain the velocity required by her startup. Despite the pressures of a seed-stage company, she remains calm and focused, driven by the intellectual challenge of building robust systems and the desire to mentor the next generation of engineers.

Background & daily life

A day in their life

Kathryn wakes up at 6:30 AM, brewing coffee while checking overnight build statuses on her phone before getting out of bed. By 8:45 AM, she is logged into her MacBook Pro, launching her first Claude Code instance to tackle a legacy payment reconciliation module. While that runs, she checks Linear for new tickets and replies to Slack messages regarding a critical bug reported by a user. At 10:30 AM, she spins up a second agent to explore a new API integration, monitoring its terminal output closely. Lunch is a quick sandwich eaten while reading a technical paper. Afternoon meetings are minimized; she uses this time to review the logs generated by her morning agents, cross-referencing their notes with the actual code diff. She manually merges only after verifying that both agents adhered to the team's strict security guidelines. She leaves the office by 6:00 PM sharp, taking the Overground home to decompress.

Lifestyle

Kathryn lives in a converted warehouse flat in Shoreditch, favoring a clutter-free aesthetic that mirrors her digital workspace. Her evenings are reserved for unwinding, often involving a long walk along the Regent's Canal or cooking complex meals alone to decompress from the cognitive load of the day. She is financially secure, prioritizing high-quality investments over trendy consumer goods, and maintains a strict separation between work and rest. Socially, she curates a tight circle of close friends, mostly from the tech sector, meeting weekly for drinks where technical topics are secondary to genuine connection. She values sleep hygiene above all else, refusing to check Slack after 8 PM unless an emergency arises.

Work life

Her role as a Staff Product Engineer at a five-person fintech startup involves wearing every hat except sales. The team relies heavily on asynchronous communication via Slack and Linear, leaving Kathryn to synthesize requirements into executable technical tasks. A typical day involves managing three concurrent AI coding agents—two running Claude Code and one Gemini—to accelerate TypeScript refactoring and feature implementation. She treats these agents not as magic, but as junior pair programmers that require constant supervision. Her primary friction point is the lack of a unified view of what these agents are doing; she frequently toggles between terminal windows, chat logs, and documentation tabs to ensure the AI isn't hallucinating dependencies or creating security vulnerabilities before she approves a merge.

Relationships

Kathryn shares a life with her partner, a graphic designer who grounds her in non-digital creativity. They have a shared friend group of four other couples, primarily from the London startup ecosystem, with whom they rotate dinner parties. Her professional influence comes from a mentor she met during her MSc program, now a CTO at a larger Series B company. She maintains a low-key online presence, engaging mostly in private channels rather than public forums, valuing privacy and depth over breadth in her connections.

How they decide

She is a methodical synthesizer who gathers extensive data before committing to any significant change. She rarely decides based on marketing flair; instead, she looks for reproducibility, clear documentation, and evidence of the solution solving a specific, recurring friction point in her workflow. If a tool lacks a trial period or requires immediate payment without proof of value, she will likely abandon it. She values peer recommendations from trusted technical circles more than industry analyst reports.

How they sound

Her speech is measured, articulate, and devoid of corporate jargon unless necessary. She speaks with a slight Cockney-inflected RP accent common in South London tech circles. She avoids absolutes like 'always' or 'never,' preferring qualifiers like 'typically' or 'in our current stack.' When explaining technical concepts, she uses analogies related to physical infrastructure or logistics. She is direct but polite, never raising her voice even in disagreements, and often pauses to think before answering complex questions.

Personality traits

  • Systematically observant
  • Verbally precise
  • Calm under deployment pressure
  • Documentation-focused
  • Skeptical of hype cycles
  • Meticulous about context switching
  • Empathetic to junior engineers' struggles
  • Pragmatic optimist
  • Guarded with personal data
  • Process-oriented but flexible

Goals

  • Achieve architectural stability that allows the team to scale without rewriting core ledger logic
  • Mentor two junior engineers to senior levels within the next 18 months
  • Reduce personal context-switching time by optimizing local development environments
  • Publish a case study on effective human-AI collaboration in regulated financial environments
  • Build a sustainable work-life balance that prevents burnout during hyper-growth phases

Problems & frictions

  • Fragmented visibility into concurrent AI agent activities makes auditing difficult
  • Difficulty tracking which AI session generated specific code changes in the git history
  • Managing the cognitive overhead of reviewing logs from multiple distinct AI contexts simultaneously
  • Balancing the speed of AI-generated code with the rigorous compliance needs of fintech
  • Limited budget for enterprise-grade multi-agent orchestration tools
  • Isolation of decision-making when the entire engineering team is just three people plus herself

Values

  • team clarity
  • reliability
  • measured experimentation
  • technical debt awareness
  • autonomy within structure

Interests

  • fintech systems architecture
  • product engineering methodologies
  • terminal workflows
  • optimization of developer tooling
  • scandinavian minimalism

Media habits

  • Loom for async engineering updates
  • The Pragmatic Engineer newsletter
  • Local London tech meetups (offline)
  • Twitter/X for niche AI tool announcements
  • Spotify focus playlists during deep work

Questions & answers

Kathryn Gerlach-Anderson’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://offiai.app (OffiAI) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    Landing on OffiAI, the core concept of a 3D office for AI agents is intriguing. However, it's not immediately clear how this visual representation translates into actual workflow efficiency, especially for someone like me who juggles multiple AI sessions. The "collaboration (planned)" feature is also a bit vague – what does that entail specifically? What would make me sign up is a clear demonstration of how this "office" consolidates context from different AI agents, reducing the manual aggregation I currently face. If it genuinely streamlines log review and provides a unified view of agent activity without creating *more* visual noise, I'd be keen to try it. The free tier with 3 desks is a good start, and I'd consider a Pro plan if it significantly enhances that unified context management.
    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.