Marilyn Towne

Why this persona fits the audience

Coordinates browser and mobile testing for a 4-person QA group at a B2B SaaS company, using a free tunnel plus a spreadsheet to rotate ephemeral HTTPS links for builds, bug repro steps, and vendor webhooks during test cycles.

• Age: 39
• Location: Manchester, UK
• Occupation: QA automation lead
• Income: £67,000
• Education: Bachelor of Science in Computer Science
• Company size: 18 employees
• Years in role: 5

“I don't need the most expensive tool; I need the one that doesn't make me guess what happened when it broke at 3 AM.”

Marilyn Towne is a 39-year-old QA Automation Lead based in Manchester, UK, operating at the intersection of rigorous process and pragmatic engineering. With a Bachelor's degree in Computer Science earned a decade ago, she has climbed the ranks from manual tester to the strategic lead of a four-person QA unit within a growing B2B SaaS firm. Her career is defined by a relentless pursuit of consistency; she believes that quality is not an accident but the result of a meticulously engineered process. Currently, she navigates the complexities of modern software delivery with a toolkit that is impressive in its frugality yet fragile in its dependency on human vigilance. Her team relies on a custom-built spreadsheet to manage the rotation of ephemeral HTTPS links generated by a free tunnel service, a workaround that saves the company money but consumes hours of cognitive load each week. This manual choreography of URLs for bug reproduction and vendor webhooks represents a persistent friction point in her professional life. Despite the budget constraints typical of smaller teams, Marilyn has demonstrated exceptional resourcefulness, leveraging open-source technologies like Go and Caddy to patch gaps in their infrastructure. She is currently evaluating whether to invest time in building a dedicated self-hosted solution or to adopt a managed alternative, driven by the need to eliminate the risk of link expiration during critical test cycles. Her reputation is built on her ability to translate chaotic development environments into stable, repeatable workflows. While she enjoys the technical challenge of coding, her true passion lies in the stability of the systems she oversees. She views herself as a guardian of the product's integrity, ensuring that the software delivered to clients functions flawlessly across a myriad of mobile devices and browsers.

Background & daily life

A day in their life

Marilyn wakes at 6:15 AM, brewing coffee and checking her emails before the house stirs. By 8:00 AM, she is on the Metrolink to the city center, reviewing the nightly build logs on her tablet. At 9:30 AM, she joins the daily stand-up, quickly identifying a bottleneck in the mobile testing pipeline. The morning is spent writing Go scripts to automate the extraction of logs from the ephemeral tunnel service, a task she finds deeply satisfying. Lunch is a quick salad eaten at her desk while reading a technical article on TLS handshakes. Afternoon meetings focus on aligning the team's testing strategy with upcoming product releases. She leaves the office at 5:30 PM sharp, avoiding overtime unless a critical deployment is happening. Evenings are for cooking, reading, or tinkering with a Raspberry Pi project, ensuring her mind remains engaged but not exhausted.

Lifestyle

Marilyn lives in a converted warehouse apartment in Ancoats, Manchester, sharing the space with her partner, a graphic designer. Her evenings are rarely 'off'; she dedicates two hours three nights a week to learning new scripting languages, often Go or Python, to solve local inefficiencies. She is financially prudent, having maxed out her pension contributions early, but spends generously on high-quality ergonomic office furniture and reliable hardware. Her social life is small but deep, centered around board game nights and hiking groups in the Peak District where she disconnects from screens. She maintains a strict separation between work and home, viewing her commute as a necessary mental buffer zone.

Work life

As the de facto architect of the QA stack for a tight-knit team of four, Marilyn's days are a mix of high-level strategy and gritty debugging. She manages the integration of mobile browser testing across iOS and Android simulators, a constant battle against flaky network conditions. Her primary tool is a complex Google Sheet that acts as a dynamic registry for ephemeral HTTPS links, manually rotating them every few minutes to ensure builds are fresh. She spends significant time troubleshooting why a vendor webhook failed to trigger during a regression cycle, often rewriting documentation to ensure reproducible steps are crystal clear. The pressure comes not from volume, but from the critical nature of the B2B product; one missed edge case can cost a client trust.

Relationships

Marilyn is the anchor of her immediate family, known for her reliability rather than her spontaneity. She has a close circle of three university friends who gather quarterly, usually for long walks. At work, she commands respect through competence rather than volume; she is the person colleagues go to when a process breaks. Her influence extends to her junior team members, whom she guides with patience and detailed feedback. She values privacy and rarely shares personal details about her finances or health, keeping those boundaries firm.

How they decide

Decisions are made slowly and with heavy reliance on data validation. Marilyn does not trust intuition over evidence; she will run a local simulation before committing to a workflow change. She is highly risk-averse regarding downtime but open to adopting new technology if it demonstrably reduces technical debt. Peer recommendations from trusted engineering leads weigh more heavily than marketing claims, and she requires a clear understanding of the underlying mechanics before adopting any new tool.

How they sound

Her speech is precise, clipped, and devoid of filler words like 'um' or 'like'. She uses industry jargon naturally but explains complex concepts simply when speaking to non-technical stakeholders. There is a calm, measured cadence to her voice; she never raises it, even when frustrated. She avoids hyperbole, preferring phrases like 'this seems inefficient' rather than 'this is terrible.' She values clarity above all, often pausing to rephrase a sentence if she senses ambiguity.