Emily Boyer

Why this persona fits the audience

Manages a six-developer team at a UK fintech scaleup and still joins hands-on code sessions when blockers come up. Their routine is live pairing in Cursor or VS Code Live Share, plus short Zoom check-ins and Jira tickets.

• Age: 41
• Location: Manchester, UK
• Occupation: Engineering manager
• Income: £110k salary + bonus
• Education: M.Eng. Software Engineering
• Company size: 45-60 employees
• Years in role: 3.5

“You can't fix what you can't see, and you certainly can't ship what isn't documented properly.”

Emily Boyer has been navigating the complexities of software engineering since the early 2000s, starting her career as a C++ developer in London's high-frequency trading sector before transitioning to fintech in Manchester. At 41, she commands significant respect as an Engineering Manager at a Series B scaleup, where she balances the dual pressures of rapid growth and regulatory compliance. Unlike many managers who retreat from the keyboard, Emily remains a hands-on practitioner, believing that empathy for the code is essential for effective leadership. Her M.Eng in Software Engineering from the University of Manchester laid the foundation for her methodical approach to system design. Currently, she oversees a six-person squad responsible for the company's core payment infrastructure. Her recent decisions have centred on stabilising the team's delivery pipeline after a period of chaotic scaling. She spearheaded the migration from monolithic microservices to a more modular architecture, a move that required extensive refactoring and retraining. Emily is known for her rigorous documentation standards, insisting that every API endpoint be accompanied by clear usage examples and failure mode analysis. This habit has significantly reduced onboarding time for new hires, a metric she tracks obsessively. Despite her high income and senior title, Emily lives frugally, viewing money as a tool for security and future options rather than status. She drives a modest electric car and lives in a home she renovated herself, avoiding luxury spending. Her professional philosophy is built on the belief that predictable delivery is the only way to build trust with stakeholders. She is currently evaluating collaborative coding environments to streamline her remote pairing sessions, seeking tools that integrate seamlessly with their existing Cursor and VS Code workflows without introducing latency or friction. For Emily, technology is only valuable if it serves the human element of the team.

Background & daily life

A day in their life

Emily wakes at 5:45 AM, brews strong tea, and cycles 12 miles to her office in Spinningfields, arriving by 7:15 AM. Her morning is spent reviewing overnight logs and clearing emails before the team arrives. By 9:00 AM, she's in a daily stand-up, quickly identifying a blocker in the payment reconciliation service. Instead of delegating, she hops on a VS Code Live Share call with a senior dev, tracing a logic error together until 10:30 AM. The rest of the morning involves back-to-back 1:1s with direct reports, focusing on career development rather than task tracking. Lunch is a quick sandwich at her desk while reading about UK banking regulation changes. Afternoon hours are reserved for architectural reviews and writing design docs for the upcoming quarter. She leaves the office by 5:30 PM on most days, picking up her children and ensuring dinner is home-cooked, though she keeps her laptop open just in case a P0 incident hits during the evening.

Lifestyle

Emily lives in a converted Victorian terrace in Didsbury, a leafy suburb of Manchester, with her partner Mark and their two school-aged children. Her mornings are rigid: a 45-minute cycle to the city centre before dropping the kids off, followed by work. Evenings are a careful balance; she tries to leave by 6 PM on Tuesdays and Thursdays for family dinners, but often works late on Wednesdays if a deployment window opens. She prioritises health, running three times a week regardless of weather, and manages finances through a mix of automatic savings and a personal portfolio focused on low-risk index funds. Socially, she keeps a tight circle of university friends and colleagues, preferring deep one-on-one coffee chats over large networking events.

Work life

Her role sits at the intersection of people management and high-level architecture. She leads a team of six backend and full-stack engineers building payment orchestration layers for a rapidly scaling fintech. While she spends 40% of her time in Jira, hiring, and stakeholder alignment, she refuses to become disconnected from the codebase. When a critical blocker arises—usually a race condition in a transaction ledger or a confusing API contract—she immediately jumps into a pair programming session using VS Code Live Share. Her days are punctuated by 'stand-ups' that are actually 15-minute syncs to unblock, not status reports. The pressure comes from the UK financial regulations and the expectation of near-zero downtime for clients.

Relationships

Emily's primary support system is her partner, Mark, a civil engineer who understands the demands of project deadlines. They share domestic responsibilities equally. Her closest professional influence is a former mentor now working in Silicon Valley, whom she calls monthly for strategic advice. She is deeply embedded in the Manchester tech community, often volunteering as a judge for local hackathons, which keeps her connected to the grassroots developer culture while maintaining her executive perspective.

How they decide

Emily is a research-heavy, evidence-based decider. She rarely adopts a new workflow or tool based on hype alone; she requires data, peer validation, and a clear ROI calculation. If a tool promises efficiency, she will run a pilot with a small subset of her team before committing the whole group. She values transparency and is skeptical of sales pitches that lack technical depth, preferring to see how a solution integrates with existing CI/CD pipelines before making a choice.

How they sound

Emily speaks with a calm, measured Manchester accent, favouring precise terminology over corporate jargon. She uses 'we' frequently to denote team ownership and avoids hyperbolic language like 'revolutionary' or 'game-changing.' Her tone is supportive but firm when discussing deadlines or quality standards. She tends to ask clarifying questions before offering solutions, often saying, 'Let's walk through the constraints first.' She dislikes vague requests and prefers bullet points over paragraphs in written communication.