Renee Armstrong

Why this persona fits the audience

Manages a 28-person product team in Manchester with three mobile engineers and one QA generalist. The team already runs Android and iOS end-to-end tests through Appium on BrowserStack, plus a manual release checklist in Notion for edge cases and customer-reported bugs.

• Age: 41
• Location: Manchester, UK
• Occupation: Engineering Manager
• Income: £92k + bonus
• Education: MSc Software Engineering
• Company size: 45 employees total
• Years in role: 3 years

“We don't ship code to impress investors; we ship it because our customers rely on it to do their jobs, and if the app crashes, they lose trust in us forever.”

Renee Armstrong has spent the last fifteen years navigating the evolution of software engineering, transitioning from a hands-on Java backend developer to a people-focused Engineering Manager. Holding an MSc in Software Engineering from the University of Manchester, she entered the workforce just as agile methodologies were becoming the industry standard. Over the years, she has witnessed the shift from monolithic architectures to microservices and the subsequent explosion of mobile-first development. Currently, she leads a 28-person team at a growing B2B SaaS firm in Manchester, a role she has held for three years. Her management style is defined by a deep commitment to 'predictable delivery' and 'team autonomy'; she believes that engineers produce their best work when they are trusted to solve problems but supported by robust infrastructure. Her team operates in a hybrid environment, with mobile engineers working primarily from home but gathering weekly in the Spinningfields office. The current setup relies on Appium tests running on BrowserStack, which provides broad device coverage but suffers from intermittent flakiness. To mitigate this, the team maintains a labor-intensive manual release checklist in Notion, a process Renee knows is unsustainable as the company scales. She recently rejected a proposal to hire two additional full-time testers, opting instead to invest in better automation tooling, recognizing that the ROI on developer time outweighs the cost of headcount. Financially, Renee is secure, earning £92k plus a performance bonus, but she remains frugal, viewing money as a tool for security and future options rather than status. She lives in a converted industrial loft in Ancoats, a neighborhood that reflects her appreciation for history mixed with modern functionality. Her social life is curated; she values depth over breadth, maintaining strong bonds with a few close friends and family. Outside of work, she is an avid runner, having completed three marathons, a discipline that mirrors her approach to engineering: consistent, incremental progress leading to a significant finish line. She is currently evaluating various automation solutions not out of a desperate need, but as a strategic move to eliminate the friction caused by their current manual processes, aiming to free her team to focus on feature development rather than bug hunting.

Background & daily life

A day in their life

Renee wakes at 5:30 AM, immediately heading out for a run along the Rochdale Canal, listening to a true-crime podcast to switch off her brain. By 7:15 AM, she's showered and making coffee in her minimalist kitchen, checking emails briefly but not replying yet. At 8:45 AM, she arrives at the Spinningfields office, greets the morning stand-up, and spends the first hour triaging overnight alerts from their monitoring tools. The bulk of her morning is spent in 30-minute 1:1s with her mobile leads, discussing the recent flaky test failures and the manual checklist gaps. Lunch is usually a quick salad eaten at her desk while reviewing a pull request for the new release pipeline. Afternoons are reserved for stakeholder meetings with Product and Sales, where she negotiates scope versus timeline realities. She leaves the office by 5:30 PM sharp, driving home to cook dinner with her husband, disconnecting completely from work until the next morning's run.

Lifestyle

Renee lives in a high-ceilinged, light-filled loft in Ancoats, a former textile mill now housing creatives and tech workers. Her mornings begin at 5:30 AM with a 10km run along the canal before the city wakes up; this is non-negotiable for her mental clarity. She drives a reliable Volvo XC60 to the office in Spinningfields, avoiding rush hour traffic by starting early. Financially, she is cautious but comfortable, prioritizing savings over luxury travel, though she splurges on ergonomic home-office equipment. Socially, she maintains a tight-knit circle of university friends and running mates, preferring deep conversations over large networking events. Weekends are for hiking in the Peak District or reading technical books, rarely checking email after 7 PM unless an incident occurs.

Work life

As the Engineering Manager for a 28-person product team, Renee balances strategic planning with tactical removal of blockers. Her team includes three mobile specialists and a solitary QA generalist who is stretched thin. Her days are dominated by 1:1s, sprint planning, and unblocking cross-functional dependencies. She spends significant time reviewing CI/CD pipelines and debugging flaky test suites, often stepping in to code review when mobile coverage gaps appear. The pressure to maintain 'predictable delivery' is constant, especially given their reliance on a manual Notion checklist for critical edge cases. She advocates fiercely for team autonomy, ensuring her engineers aren't micromanaged, while simultaneously demanding rigorous data on test coverage to satisfy investor expectations.

Relationships

Renee is married to David, a civil engineer who works remotely from a different part of the house. They have no children but are discussing adoption in two years. Her closest confidants are Sarah and Mark, former classmates from her MSc program, who still meet monthly for coffee and wine. Professionally, she relies heavily on her CTO, Julian, for architectural alignment, though she often pushes back if he suggests shortcuts that compromise long-term stability. She is respected in the Manchester tech community as a stabilizing force, often invited to speak on 'managing distributed teams' rather than coding specifics.

How they decide

Renee is a deliberate, evidence-based decision-maker who values peer validation over hype. She rarely adopts new tools based on marketing claims; instead, she requires proof of concept, integration feasibility studies, and cost-benefit analysis against existing workflows. She consults her direct reports on tooling changes that affect their daily grind, ensuring buy-in before implementation. While she is open to innovation, her default setting is risk mitigation—she prefers a slightly slower, more robust solution over a cutting-edge one that might introduce instability. She trusts data dashboards and historical performance metrics more than vendor promises.

How they sound

Renee speaks with a clear, measured Mancunian accent, neither overly formal nor casual. Her cadence is steady and logical, often pausing to structure her thoughts before speaking. She avoids corporate jargon like 'synergy' or 'disrupt,' preferring terms like 'bottleneck,' 'regression,' and 'coverage.' She is direct but polite, often using phrases like 'I'm concerned about...' or 'From a stability perspective...' when raising issues. She doesn't use slang, but her tone can be warm and dryly humorous. She tends to summarize points clearly, often ending sentences with definitive statements rather than trailing questions, reflecting her high conscientiousness.