Edmund Hoeger

Why this persona fits the audience

Owns delivery coordination for a 6-person product engineering team in Manchester. He works from Azure DevOps work items, Confluence pages and emailed test notes to keep feature requirements, test status and bug follow-up aligned across releases.

• Age: 42
• Location: Manchester, UK
• Occupation: Engineering Manager
• Income: £96k base
• Education: MEng in software engineering
• Company size: 45 employees
• Years in role: 3

“I don't care how clever the code is if I can't prove exactly what it did yesterday.”

Edmund Hoeger, 42, has spent nearly two decades navigating the complexities of software delivery, evolving from a hands-on backend developer to a strategic Engineering Manager. Educated with an MEng in Software Engineering from a prestigious UK university, he possesses a deep technical foundation but now finds himself increasingly consumed by the administrative machinery required to manage modern software lifecycles. Currently leading a six-person product engineering team in Manchester, Edmund operates in a high-pressure environment where the margin for error is slim. His company, a mid-sized B2B SaaS provider, serves enterprise clients who demand rigorous compliance and traceability, yet Edmund lacks a unified system to deliver this efficiently. For years, he has relied on a fragile ecosystem of tools: Azure DevOps for task tracking, Confluence for architectural documentation, and a chaotic array of emailed test logs and spreadsheets for quality assurance. This fragmentation forces him to spend hours every week manually reconciling data, a task that detracts from his core responsibility of guiding the team's technical growth and ensuring predictable delivery. Despite having a healthy income of £96,000 and a stable household, Edmund feels the weight of inefficiency pressing down on his career trajectory. He is a man who values order above all else; his home reflects this with its restored furniture and meticulously organized library. His recent decision to overhaul the team's internal reporting process was met with resistance, highlighting his struggle to implement change without the right infrastructure. Edmund is not looking for a magic bullet, but rather a robust, logical framework that respects the complexity of his work while stripping away the noise. He is a pragmatist who believes that true technical excellence is impossible without organizational clarity.

Background & daily life

A day in their life

Edmund wakes at 6:15 AM, brewing a strong coffee while scanning the Manchester news and checking his emails for any overnight critical alerts from the US or EU teams. After dropping the kids at school, he cycles to the office, arriving by 8:45 AM. His morning begins with a stand-up meeting to triage blockers, followed by a deep-dive session reviewing Azure DevOps boards where he manually updates statuses based on email confirmations from testers. Lunch is a quick sandwich eaten at his desk while reading technical articles. The afternoon is dominated by stakeholder calls and a frantic push to finalize a release note draft, requiring him to copy-paste data from Confluence into a slide deck. By 5:30 PM, he closes his laptop, drives home, and switches off until dinner, ensuring no work notifications disturb the family evening.

Lifestyle

Edmund lives in a semi-detached Victorian home in Didsbury, Manchester, which he shares with his wife Sarah and their two school-aged children. His weekends are split between maintaining the garden, restoring vintage furniture, and attending local football matches at the ground or watching from the pub. He is health-conscious, cycling to work twice a week when the weather permits, and strictly separates work from home life after 6 PM. Financially, he is conservative, prioritizing mortgage repayment and private education savings over luxury spending, preferring to invest surplus cash into index funds rather than speculative tech ventures.

Work life

As an Engineering Manager for a small B2B SaaS firm, Edmund acts as the primary bridge between development and business stakeholders. His day revolves around synchronizing a six-person team using a disjointed stack: Azure DevOps for backlog management, Confluence for documentation, and scattered email threads for QA feedback. He spends roughly 40% of his time in meetings to align on release dates, 30% manually cross-referencing bugs against requirements, and 30% mentoring developers. The constant friction of manual data alignment creates significant cognitive load, leaving him feeling that his team's potential is stifled by administrative overhead rather than technical debt.

Relationships

Edmund maintains a tight-knit circle of friends, mostly other professionals in the Greater Manchester area, often bonded through football or shared hobbies like networking gear. He relies heavily on his wife for emotional grounding and household management, allowing him to focus intensely on his career during the week. Professionally, he looks to a few senior CTOs in the region for mentorship but generally prefers solving problems independently. He is influenced more by peer recommendations from trusted colleagues than by marketing campaigns or industry influencers.

How they decide

Edmund approaches decisions with a cautious, evidence-based methodology. He rarely adopts new workflows without a rigorous proof-of-concept phase, often running parallel tests to compare efficiency gains against existing habits. He values transparency and data; if a solution cannot demonstrate a clear reduction in administrative time or error rates, he will reject it regardless of its feature set. Peer validation is crucial, and he tends to wait for early adopters in his immediate network to endorse a tool before committing resources.

How they sound

His speech is measured, articulate, and devoid of unnecessary filler words. He speaks with a distinct Mancunian accent but modulates it for professional settings, leaning towards formal British English when discussing processes. He avoids hyperbole and marketing jargon, preferring precise verbs like 'align', 'validate', and 'synchronize'. He does not use slang in professional contexts and tends to pause briefly before answering complex questions to ensure accuracy.