Casey Waelchi

Why this persona fits the audience

Leads QA for a healthtech product with 5 testers and 2 automation engineers in Manchester. Tracks API contract changes across staging and release branches with Postman collections, spreadsheets, and release notes, while coordinating with developers on what changed between versions.

• Age: 40
• Location: Manchester, UK
• Occupation: QA lead
• Income: GBP 68k
• Education: Bachelor's in Information Systems
• Company size: Mid-sized healthtech startup (approx. 120 employees)
• Years in role: 3

“You can't automate your way out of a lack of clear requirements; the machine will just tell you faster that you're wrong.”

Casey Waelchi is a 40-year-old QA Lead based in Manchester, operating at the intersection of rigorous software engineering and the high-stakes world of health technology. With a Bachelor's in Information Systems earned over two decades ago, she has spent her entire career navigating the evolution of quality assurance from manual checklist execution to sophisticated, code-heavy automation strategies. Currently leading a team of seven in a mid-sized healthtech firm, she is responsible for the integrity of APIs that power patient management systems, where a single error can have real-world consequences. Her professional philosophy is built on an unyielding commitment to consistency and accountability. Unlike many peers who chase the newest shiny frameworks, Casey prefers tools that offer stability and traceability. She currently manages her team's verification efforts through a fragmented ecosystem of Postman collections, legacy Excel trackers, and disparate release notes. This manual patchwork is her biggest source of friction; she frequently finds herself spending valuable hours manually correlating API contract changes between staging and release branches, a process prone to human error and exhaustion. Casey is married to a primary school teacher, and together they navigate the demands of raising a young daughter in a city with a thriving but competitive tech scene. Financially secure on a £68k salary, she prioritizes long-term security over short-term indulgences, investing heavily in her home garden and her daughter's future. Her personality reflects this balance: she is highly conscientious and organized, yet grounded enough to appreciate the quiet satisfaction of a well-tended tomato patch. She is a skeptic by nature, requiring evidence before adopting new methodologies, but remains deeply collaborative, often acting as the bridge between aggressive developers and meticulous compliance officers. Recently, she has been advocating for better documentation standards within her company, arguing that the current reliance on verbal handovers is unsustainable as the product scales.

Background & daily life

A day in their life

Casey wakes at 6:00 AM to the sound of her daughter getting ready for school. After a quick breakfast and checking the weather forecast for her garden, she drives into Manchester, listening to a true crime episode to mentally transition into 'problem-solving mode.' At 9:00 AM, she joins the daily stand-up, immediately flagging a discrepancy in the latest API payload schema. The morning is consumed by reviewing Pull Requests, debugging a failing automation suite, and reconciling three different spreadsheets to map version changes. Lunch is a solitary affair, often spent reading industry updates. Afternoon meetings involve negotiating deadlines with product managers and coaching a junior tester on a complex integration scenario. By 5:30 PM, she closes her laptop, ensuring no open tickets are left ambiguous, before heading home to prepare dinner and engage with her family's evening routine.

Lifestyle

Casey lives in a renovated Victorian terrace in Didsbury with her husband and seven-year-old daughter. Her weekends are a careful balance of domestic duty and personal restoration; Saturday mornings are dedicated to tending her extensive vegetable garden, where she experiments with heirloom tomatoes despite the damp English climate. Evenings are often reserved for cooking elaborate meals from scratch, a meditative counterpoint to her high-stress work week. Financially, she is prudent but not frugal, prioritizing savings for her daughter's education and occasional family trips over luxury goods. Socially, she maintains a tight circle of close friends and colleagues, preferring deep conversations over large gatherings.

Work life

As the QA Lead, Casey manages a hybrid team of five manual testers and two automation engineers. Her days revolve around the chaotic rhythm of API contract changes; she spends hours cross-referencing Postman collections against release notes to ensure staging environments mirror production integrity. She coordinates closely with senior developers to interpret version control diffs, translating technical jargon into actionable test cases. The pressure is constant: a missed regression could mean patient data errors, so her office is a fortress of spreadsheets and tracked tickets. She fiercely protects her team from scope creep, acting as the gatekeeper who ensures nothing ships without a signed-off verification.

Relationships

Casey relies heavily on her husband for logistical support, allowing her to focus on career growth without neglecting home life. Her relationship with her development leads is professional but strained; she views them as necessary collaborators rather than friends. In the community, she is known as the reliable neighbor who always has a spare plant or a homemade loaf of bread. She values peer advice from other QA leads in the Greater Manchester tech scene, often meeting for coffee to vent about tooling limitations.

How they decide

Casey employs a cautious, evidence-based decision style. She rarely commits to a new workflow or tool without seeing concrete proof of its reliability in a sandbox environment. She weighs the long-term maintenance cost against immediate benefits, often favoring solutions that require less ongoing administrative overhead. Peer validation is crucial; if a trusted colleague has successfully implemented a process, she is more likely to adopt it quickly. She avoids impulsive choices, preferring to sit on a decision until the data aligns with her core values of consistency and clarity.

How they sound

Her speech is precise and measured, devoid of unnecessary filler words. She speaks with a soft Mancunian accent, using clear, professional terminology but avoiding overly academic jargon unless explaining a concept to non-technical stakeholders. She tends to pause before answering complex questions, gathering her thoughts rather than improvising. She avoids hyperbole, rarely saying something is 'amazing' or 'terrible,' preferring descriptors like 'inefficient' or 'robust.' In casual conversation, she shifts to a warmer, more storytelling tone, particularly when discussing gardening or the plots of her favorite podcasts.