Why this persona fits the audience
Works on an 8-person London fintech team that keeps one shared production repo on a Mac build machine. She uses Cursor daily, helps answer implementation questions from the coding agent, and reviews terminal output and git diffs between commuting, meetings, and on-call rotations.
- Age: 29
- Location: London, UK
- Occupation: Backend engineer
- Income: £105k base + bonus
- Education: MSc Software Engineering
- Company size: 8 people
- Years in role: 4
“The most dangerous thing in software isn't the bug you can't find; it's the feature you ship because you didn't have the time to think about how it would break tomorrow.”
Terri Paucek, 29, is a Backend Engineer based in London, operating at the intersection of high-stakes fintech delivery and emerging AI-assisted development methodologies. Holding an MSc in Software Engineering, she joined her current eight-person startup four years ago, rising from a junior developer to a critical pillar of their engineering culture. The company operates with a lean structure, relying on a single shared production repository hosted on a Mac build machine, a setup that demands absolute precision from every team member. Terri has become the de facto guardian of code quality, particularly in the context of generative AI tools like Cursor. She does not merely write code; she curates it, spending a significant portion of her day answering implementation queries posed by the coding agent and rigorously reviewing terminal outputs and git diffs. Her workflow is uniquely adapted to a hybrid reality: she works from a laptop in the office but maintains operational control from her phone during commutes and on-call shifts. This necessity has forced her to develop a mental model of the codebase that transcends physical screen real estate. She values predictability above all else, having seen too many startups fail due to technical debt accumulated in the name of speed. While she embraces the efficiency of AI, she remains skeptical of its autonomy, insisting on human oversight for any change touching production financial data. Outside of work, Terri channels her discipline into running, targeting a sub-2-hour half-marathon, and curating extensive collections of board games that require strategic planning. She is financially secure with a £105k salary plus bonuses, yet her spending habits reflect a long-term mindset, prioritizing savings and experiences over material goods. Her life is a study in balance: she navigates the chaos of a startup with a structured, almost algorithmic approach to personal time, believing that order in the private sphere is essential for managing the inherent unpredictability of software development.
Background & daily life
A day in their life
Terri wakes at 5:30 AM for a run along the canal, returning by 7:00 AM to prepare for the tube. By 8:45 AM, she is on the train, reviewing pending PRs and reading through terminal logs generated overnight by the CI pipeline, using her phone to spot-check git diffs. At 9:30 AM, she joins a stand-up, quickly clarifying blockers for the team. Her morning is spent debugging a race condition in the payment gateway, frequently invoking Cursor to generate boilerplate but manually auditing every suggestion. Lunch is a quick sandwich eaten while sketching a new API endpoint design. Afternoon meetings with stakeholders consume two hours, after which she dives back into code. During her evening commute, she checks on-call alerts, approving minor changes via a mobile interface before heading home to dinner and a board game night with housemates.
Lifestyle
Terri lives in a converted warehouse flat in Islington with two fellow engineers, fostering a low-maintenance, high-efficiency household. Her routine is rigid: 5:30 AM runs along the Regent's Canal are non-negotiable, followed by a strict breakfast of oats and black coffee. She manages her finances with spreadsheets, prioritizing savings over luxury, though she splurges occasionally on board games or tech hardware. Socially, she prefers deep conversations over large parties, often gathering friends for strategy nights at local pubs rather than loud clubs. Health is paramount; she tracks sleep and running metrics religiously, viewing physical stamina as directly linked to cognitive endurance.
Work life
As one of only eight people at her London fintech startup, Terri wears multiple hats, primarily focusing on backend architecture within a single shared production repository hosted on a Mac build machine. Her day is fragmented by on-call rotations and stand-ups, yet she maintains a relentless focus on code quality. She spends significant time reviewing terminal outputs and git diffs generated by AI agents like Cursor, acting as the human-in-the-loop validator. Between meetings and commuting, she meticulously audits implementation suggestions, ensuring the team's rapid delivery doesn't compromise stability. The pressure is constant; with no dedicated QA team, she feels personally accountable for every line of code merging into production.
Relationships
Terri is close with her parents in Manchester, calling them every Sunday, though they struggle to grasp the nuances of her job. In London, her social circle is tightly knit with colleagues from the startup, blurring the lines between work and play. She has a mentor, a CTO from a previous role, who guides her career trajectory. She avoids superficial networking, preferring one-on-one interactions where she can discuss specific technical challenges or share insights on design systems.
How they decide
Terri is a cautious researcher who relies heavily on peer validation and concrete evidence before adopting new workflows. She rarely makes impulsive decisions, especially regarding financial or professional tools. Instead, she gathers data, reads documentation thoroughly, and seeks opinions from trusted technical peers. She values predictability and will stick to a known system until a new option demonstrably solves a specific, recurring friction point with measurable efficiency gains.
How they sound
Her speech is precise, measured, and devoid of filler words. She tends to use British English idioms sparingly, preferring technical jargon that conveys exact meaning. She avoids hyperbole, often qualifying statements with 'likely' or 'potentially' rather than absolutes. When explaining complex logic, she structures thoughts linearly, often pausing to ensure clarity. She rarely raises her voice, even in disagreements, opting for calm, reasoned rebuttals backed by data.
Personality traits
- methodical
- quietly authoritative
- highly organized
- pragmatic
- meticulous about documentation
- strategic about time management
- calm under pressure
- collaborative but independent
- curious about efficiency tools
- disciplined
Goals
- Achieve principal engineer status within three years
- Refactor the legacy payment processing module to improve latency by 20%
- Publish a technical article on optimizing AI-assisted development workflows
- Complete a half-marathon in under 2 hours
- Build a sustainable, automated home lab environment
- Mentor two junior developers to seniority
Problems & frictions
- Fragmented context switching while reviewing AI-generated code on public transport
- Lack of immediate access to full terminal logs when away from the office desk
- Difficulty maintaining deep focus due to frequent on-call interruptions
- Managing the cognitive load of validating complex git diffs without proper mobile tools
- Balancing the speed of AI generation with the need for rigorous manual review
- Limited bandwidth for learning new architectural patterns amidst delivery pressure
Values
- code quality
- predictability
- team accountability
- learning
Interests
- running
- design systems
- board games
- tech meetups
Media habits
- Listening to technical podcasts during runs
- Skimming GitHub trend pages
- Reading engineering blogs on commute
- Following niche Discord channels for AI tooling