Gretchen Halvorson

Why this persona fits the audience

Manages 5 engineers at a UK B2B SaaS company and stays close to incident handling. She reviews alert threads, keeps bug status in spreadsheets and Jira, coordinates who investigates which service, and signs off when fixes are validated.

• Age: 39
• Location: London, UK
• Occupation: Engineering Manager
• Income: £118k
• Education: BEng Software Engineering
• Company size: 45 employees
• Years in role: 3

“I don't manage people; I manage the conditions that allow them to do their best work without burning out.”

Gretchen Halvorson is a 39-year-old Engineering Manager based in London, operating at the intersection of technical depth and operational stability. With a BEng in Software Engineering and nearly fifteen years of experience, she transitioned from individual contributor to leadership three years ago at a mid-sized B2B SaaS firm. Her current role involves managing a lean team of five engineers, a structure that demands she remain intimately involved in every incident response. Unlike larger organizations where specialized SRE teams handle the heavy lifting, Gretchen personally triages alerts, maps bugs to services, and validates fixes before they hit production. She relies on a hybrid system of Jira for ticketing and a custom Excel tracker for high-level status visibility, a workaround born of necessity due to budget constraints. This manual layering creates a constant cognitive load, particularly when coordinating multiple simultaneous incidents. Despite the chaos, she cultivates a culture of calm, believing that panic is the enemy of resolution. Outside of work, she channels her need for control into sailing and gardening, finding solace in the predictable mechanics of nature. She is financially comfortable, earning £118k, yet remains frugal, investing heavily in her future rather than her present consumption. Her recent decision to reject a complex enterprise tool in favor of simpler, integrated workflows reflects her pragmatic approach: tools must solve problems, not create new dependencies.

Background & daily life

A day in their life

Gretchen wakes at 5:30 AM for a quiet hour of reading and planning before the household stirs. By 7:15 AM, she is on the road, listening to a true crime podcast while navigating traffic toward Shoreditch. Her morning stand-up focuses on blocking issues, followed by a deep dive into the previous night's incident logs. At 11:00 AM, she spends an hour reviewing the bug tracking spreadsheet, reassigning tasks for engineers who are blocked. Lunch is a quick salad eaten at her desk while responding to Slack messages. Afternoon meetings are reserved for 1:1s with her direct reports and cross-functional syncs with Product. Late afternoons are for code review approvals and incident post-mortems. She leaves by 6:00 PM sharp to pick up her children, switching off notifications unless there is a P0 alert. Evenings are for family, cooking, and her garden, reserving late-night work only for genuine emergencies.

Lifestyle

Gretchen lives in a semi-detached Victorian home in Clapham, London, where she maintains a surprisingly lush vegetable garden despite her demanding schedule. Her weekends are split between early morning runs, tending to tomatoes and herbs, and sailing trips on the Thames with a local crew. She is financially secure, having maximized her pension contributions while maintaining a modest lifestyle; she prioritizes quality over quantity in purchases. Socially, she balances family time with a tight-knit group of friends from university and sailing, often gathering for dinner parties rather than loud nights out. Health is a priority, with regular yoga sessions and a strict sleep schedule that rarely breaks, even during crunch times.

Work life

As the sole Engineering Manager for a five-person team at a fast-growing London B2B SaaS startup, Gretchen operates as the bridge between technical execution and business stability. Her day revolves around incident response; she personally reviews PagerDuty alerts, triages them into Jira tickets, and assigns investigations based on engineer expertise. She maintains a master 'Bug Status' spreadsheet alongside Jira to track SLAs and validation cycles, ensuring nothing slips through the cracks. While she delegates coding, she retains final sign-off authority on all production fixes. The pressure is constant: with only five engineers, one sick day can cascade into a delayed release or an unresolved customer issue, requiring her to step in as a force multiplier.

Relationships

Gretchen is married to a civil engineer who grounds her with his practical approach to problem-solving. They share the domestic load, though she manages the emotional labor of their social calendar. Her parents live in Surrey and visit weekly for Sunday lunch, providing a crucial anchor. Professionally, she relies heavily on her CTO for strategic alignment but acts as the primary advocate for her team's mental health. She has no major mentors currently but actively seeks peer advice from other managers in the London tech scene via informal Slack groups.

How they decide

Gretchen is a cautious, evidence-based decider who prefers to validate assumptions through small-scale testing before full commitment. She dislikes high-pressure sales tactics and values transparency above all else. When evaluating options, she weighs long-term maintenance costs and team adoption friction more heavily than initial features. She tends to consult her immediate team and a trusted external advisor before making significant financial decisions, preferring a consensus-driven approach that minimizes risk.

How they sound

Her speech is clipped, precise, and devoid of filler words like 'um' or 'like'. She uses professional terminology but avoids corporate jargon, favoring direct, actionable language. She speaks with a calm, authoritative cadence that rarely rises in volume, even when discussing failures. She avoids hyperbole, preferring quantifiable metrics over subjective feelings. In casual settings, she remains engaging but maintains clear boundaries, rarely oversharing personal details. She listens intently, often pausing before responding to ensure accuracy.