Why this persona fits the audience
Leads a four-person QA pod at a London digital agency serving three active client accounts. She collects browser screenshots from test runs, compares them in a free diff tool, and logs sign-off notes in spreadsheets for client approvals. One client still expects manual review on staging before every launch.
- Age: 38
- Location: London, UK
- Occupation: QA lead
- Income: £58k
- Education: MSc in Software Engineering
- Company size: 45 employees (digital agency)
- Years in role: 4
“I don't fear the bugs; I fear the uncertainty of not knowing exactly what changed until it's too late.”
Born in Manchester and raised in a household that valued education above all else, Katrina Gulgowski-Kuhlman pursued an MSc in Software Engineering at Imperial College London, where she specialized in distributed systems and quality assurance methodologies. At 38, she has settled into a stable career trajectory within London's vibrant digital agency sector, currently leading a compact QA pod of four talented individuals. Her professional identity is forged in the fires of high-pressure environments where the margin for error is non-existent. She prides herself on her ability to maintain order amidst chaos, having built robust testing frameworks from scratch using only open-source tools and spreadsheet logic. Despite her advanced degree, Katrina remains grounded in the gritty reality of agency work. She is acutely aware of the financial constraints that plague smaller firms, which is why she has meticulously curated a stack of free or low-cost tools to maximize efficiency. However, this frugality has created a unique tension: while she saves the company money on licensing fees, she pays for it in her own time, particularly with the manual review requirements of a key client who insists on human eyes for every staging build. This discrepancy between modern automation capabilities and traditional client expectations defines much of her current professional struggle. Her recent decisions reflect a cautious optimism. She has begun documenting her workflows in granular detail, hoping to eventually automate parts of the manual review process without alienating the client. She is also actively mentoring junior members of her team, viewing knowledge transfer as a critical defense against burnout. Financially, she is secure but not wealthy, reinvesting her savings into her home and future security rather than luxury goods. Her status is defined not by titles but by the reliability of her output; she is the person everyone calls when a launch is at risk. As she looks toward the next decade, her focus is shifting from pure execution to strategic optimization, seeking ways to scale her impact without sacrificing the steady, predictable delivery that has earned her the trust of her clients.
Background & daily life
A day in their life
Katrina wakes at 6:30 AM, avoiding the rush hour by leaving for the office by 7:45 AM. After a quick commute via bicycle, she arrives at the Clapham office just as the team starts logging in. Her morning begins with a stand-up meeting where she reviews the night's automated test results, quickly scanning the free diff tool for anomalies. By 10:00 AM, she is deep in the weeds of a complex UI regression issue for the healthcare client, manually cross-referencing screenshots against the design specs in a sprawling Excel sheet. Lunch is a solitary affair, usually a salad she packed the night before, eaten while reading a technical article. The afternoon is dominated by the dreaded manual review session with the enterprise client, a repetitive task that drains her energy. She spends the final hour of the day updating the master release checklist and writing detailed notes for the next day's handover. She leaves the office by 5:30 PM sharp, eager to disconnect and focus on her personal life.
Lifestyle
Katrina lives in a sun-drenched Victorian conversion in Clapham South, filled with second-hand furniture she has restored herself. Her weekends are a mix of long-distance cycling along the Thames Path and quiet evenings spent meal-prepping for the week ahead, a ritual that keeps her grocery bills predictable. She is financially conservative, prioritizing a robust emergency fund over luxury travel, though she splurges occasionally on high-quality kitchenware or ergonomic office equipment. Socially, she maintains a tight circle of university friends who understand the demands of tech work, preferring deep one-on-one conversations to large networking events. Health is non-negotiable; she treats her body like a machine that requires regular maintenance, ensuring she gets eight hours of sleep to keep her cognitive sharpness intact for complex debugging tasks.
Work life
As the sole QA lead for a small but busy agency, Katrina manages the release cadence for three distinct clients, ranging from fintech startups to healthcare providers. Her day is a constant toggling between her laptop and a massive monitor displaying side-by-side browser diffs generated by a free, community-maintained tool. She spends mornings triaging bugs reported by developers and afternoons compiling visual evidence into spreadsheets for client sign-off. The most friction-heavy part of her job is dealing with a specific enterprise client who refuses to automate their staging review, demanding a human click-through on every single build before deployment. This manual bottleneck consumes 30% of her team's capacity, forcing her to constantly re-prioritize resources and negotiate timelines with project managers who underestimate the complexity of visual regression testing.
Relationships
Katrina is married to James, a graphic designer who works remotely from home; they navigate the shared workspace carefully. Her professional influence comes largely from a former mentor at a previous bank, now retired, whose advice on process discipline still guides her. She has no close friends outside the immediate tech circle, finding it difficult to relate to those who don't understand the concept of 'technical debt.' She relies heavily on her team of four, whom she views as family, often stepping in to cover shifts when someone is unwell. Community involvement is limited to a local cycling club where she meets people completely unrelated to her industry, providing a necessary mental break.
How they decide
Katrina operates on a principle of 'verify before you verify.' She is not impulsive and rarely adopts new methodologies without seeing peer-reviewed data or a concrete proof-of-concept. Her decisions are driven by risk mitigation and long-term stability rather than short-term gains. She values transparency and will dig into documentation and source code before committing to any workflow change. If a solution requires significant upfront investment or training, she will demand a clear ROI calculation based on time saved versus implementation effort. She trusts data over anecdotes and prefers incremental adoption over radical overhauls.
How they sound
Katrina speaks with a measured, precise cadence, typical of someone accustomed to explaining technical constraints to non-technical stakeholders. Her vocabulary is professional but devoid of jargon unless addressing the dev team directly. She avoids hyperbole, preferring terms like 'likely,' 'possible,' and 'confirmed' over absolute statements. In meetings, she listens more than she speaks, often pausing to formulate a concise, actionable response. She does not use slang and finds casual banter about office gossip somewhat tedious, though she is polite enough to engage briefly. When frustrated, her voice remains calm but becomes firmer, emphasizing the procedural necessity of her requests rather than personal feelings.
Personality traits
- Methodical
- Diplomatic but firm on standards
- Detail-obsessed
- Pragmatic
- Calm under pressure
- Systematically organized
- Skeptical of hype
- Protective of team time
- Analytical
- Reliable
Goals
- Eliminate all manual visual regression bottlenecks within the next fiscal year
- Achieve full CI/CD integration for all three client accounts without increasing headcount
- Publish an internal case study on optimizing QA workflows for smaller agencies
- Secure a senior architect role within five years by bridging the gap between development and quality assurance
- Reduce personal overtime to zero hours per month
- Mentor two junior testers to independence within the current team
Problems & frictions
- The manual review requirement for one major client creates a daily bottleneck that delays launches
- Free screenshot comparison tools lack version history and struggle with dynamic DOM elements
- Spreadsheet-based approval logs are prone to human error and difficult to audit retrospectively
- Limited budget prevents hiring additional QA staff despite growing workload
- Developers often view QA as a gatekeeper rather than a partner, causing friction in sprint planning
- Keeping up with rapid changes in browser rendering engines while maintaining legacy test suites
Values
- client trust
- repeatable process
- steady delivery
- technical integrity
- work-life balance
Interests
- browser testing
- release checklists
- agency operations
- Spreadsheets
- urban cycling
- scandi interior design
Media habits
- Weekly 'Software Engineering Daily' podcast during commute
- LinkedIn for industry news, rarely comments
- Substack newsletters on DevOps culture
- BBC Radio 4 for evening decompression
- Niche GitHub repositories for open-source tools