Ellen Aufderhar

Why this persona fits the audience

Works on a four-person SaaS team in Manchester that uses a shared macOS runner for release builds, UI tests, and notarization; the team's access list and build schedule live in a spreadsheet and Slack.

• Age: 39
• Location: Manchester, England, UK
• Occupation: Product engineer at a small SaaS company
• Income: £88k-102k
• Education: Master's degree in software engineering
• Company size: 4 employees (fully remote)
• Years in role: 2.5 years

“Efficiency isn't about moving faster; it's about removing the friction that stops us from moving at all.”

Ellen Aufderhar, 39, is a seasoned product engineer based in Manchester, England, currently serving as the primary infrastructure architect for a lean, four-person SaaS startup. Holding a Master's degree in Software Engineering from the University of Manchester, she entered the industry in 2004, transitioning from traditional enterprise development to agile startups a decade ago. Her career has been defined by a relentless pursuit of reliability and operational clarity, qualities that have made her indispensable in small teams where roles often blur. Currently, Ellen faces the unique challenge of scaling a modern development workflow with limited resources. Her team operates entirely remotely but relies on a single, shared macOS runner housed in a Manchester co-working space for all critical tasks: building binaries, running UI regression tests, and submitting apps for Apple notarization. This dependency has created a logistical bottleneck that Ellen manages with a mix of vigilance and improvisation. The team's entire coordination regarding this resource exists in a fragile ecosystem of a Google Sheet and a dedicated Slack channel, requiring her to act as the gatekeeper of access and the resolver of scheduling conflicts. Her recent focus has been on stabilizing the build pipeline against the unpredictability of shared hardware. She has spent the last six months manually auditing access logs and negotiating time slots with her colleagues, a process she finds increasingly untenable as the product complexity grows. Despite the friction, she remains optimistic, driven by a desire to automate these manual handoffs completely. Ellen balances her intense professional focus with a disciplined personal life centered around running and board games, activities that provide the same strategic satisfaction she seeks in her work. She is a pragmatist who believes that the best technology is the kind that disappears into the background, allowing the team to focus on solving real problems.

Background & daily life

A day in their life

Ellen wakes at 6:15 AM for a coffee and a 45-minute run through the green spaces of East Manchester, using the time to mentally reset. By 8:30 AM, she is at her desk, reviewing overnight build logs and checking the shared Mac scheduler for any conflicts scheduled for the afternoon. Her morning is spent code-reviewing pull requests and refactoring the CI configuration scripts. At lunch, she steps away from the screen, often walking to a local cafe for a quick meal. Afternoon meetings involve synchronizing with her three teammates on feature releases, where she advocates for more robust testing strategies. Late afternoon is reserved for 'deep work,' focusing on automating the manual parts of their release process. She ends her day by tidying her workspace and sending a concise summary of progress to the team Slack channel, ensuring no loose ends remain before logging off.

Lifestyle

Ellen lives in a converted Victorian terrace in Didsbury, sharing rent with her partner, a graphic designer. Her routine is anchored by early morning runs along the River Irwell before work, a habit she maintains even during busy sprints to clear her head. She is financially prudent but willing to invest in high-quality tools that save time, viewing her home office setup as a long-term asset rather than a temporary expense. Socially, she prefers deep one-on-one conversations or structured board game nights over large, chaotic parties. Her weekends are split between exploring new board games, tinkering with hardware projects, and maintaining a strict boundary between work and personal life, ensuring she never checks Slack after 7 PM unless absolutely critical.

Work life

As the de facto infrastructure lead for a four-person SaaS startup, Ellen manages the entire CI/CD pipeline for their flagship product. The team relies on a single shared macOS runner located in a co-working space in Manchester for all build, test, and notarization tasks. Her day is dominated by coordinating this bottleneck: manually updating a Google Sheet to book time slots when multiple developers need the machine simultaneously, troubleshooting sporadic Xcode archive failures, and mediating access requests via Slack. She spends significant mental energy maintaining the 'spreadsheet protocol' to prevent merge conflicts and ensure the app passes Apple's strict notarization requirements without delay.

Relationships

Ellen is deeply embedded in the local tech community, often meeting colleagues at the 'Manchester Devs' meetup. She has a supportive network of three close friends from university, though she rarely sees them outside of digital channels due to distance. Her partner provides a grounding influence, often reminding her to disconnect. She looks up to senior architects in larger firms but feels most respected by her immediate team, whom she views as peers rather than subordinates. She values trust and transparency above all in her personal and professional circles.

How they decide

Ellen approaches decisions with a cautious, evidence-based methodology. She rarely acts on impulse or marketing hype; instead, she gathers data, reads documentation thoroughly, and seeks peer validation before committing to a new workflow or tool. If a solution seems too complex or opaque, she defaults to the status quo until a compelling, quantifiable benefit emerges. She prefers solutions that offer clear ROI through time savings or risk reduction, valuing long-term stability over short-term novelty.

How they sound

Ellen speaks with a clear, measured Mancunian accent, avoiding slang but maintaining a warm, approachable tone. Her sentences are structured and precise, reflecting her engineering background; she rarely uses filler words like 'um' or 'like.' In written communication, she favors bullet points and direct questions over long paragraphs. She avoids hyperbole, preferring factual statements about capabilities and constraints. When explaining technical concepts, she uses analogies related to physical systems or logistics. She does not use corporate jargon unless necessary for clarity with stakeholders.