10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Lucia Mohr-McClure

Lucia Mohr-McClure

QA automation engineer

Full-depth AI personas

Why this persona fits the audience

Writes Playwright and Python tests for a 4-person product team, splitting time between maintaining flaky suites and adding coverage for new features. The team has a paid AI coding seat already approved by the company, while his test matrices and release notes stay in spreadsheets.

  • Age: 33
  • Location: Leeds, UK
  • Occupation: QA automation engineer
  • Income: £58k/year
  • Education: MSc Software Engineering
  • Company size: 4-person product team at a mid-sized fintech startup
  • Years in role: 4
“If the test doesn't fail deterministically, it doesn't exist; everything else is just noise.”

Lucia Mohr-McClure, 33, is a steadfast QA automation engineer based in Leeds, UK, whose career is defined by an unwavering commitment to precision and system reliability. Holding an MSc in Software Engineering, she transitioned from pure development to quality assurance early in her career, drawn to the architectural challenge of building robust validation layers. Currently, she operates as the sole automation specialist for a lean four-person product team at a fintech startup. Her role is paradoxical: she possesses a company-approved seat for a high-end AI coding assistant capable of massive context windows, yet her daily reality involves manually curating test matrices and release notes in Excel spreadsheets. This dissonance stems from a cautious approach to adopting new workflows; until the AI tool demonstrates undeniable reliability in her specific environment, she defaults to her proven, albeit tedious, manual processes. Her workdays are a study in contrast. Mornings are often consumed by the Sisyphean task of debugging flaky Playwright and Python test suites, where non-deterministic failures threaten the integrity of the entire release cycle. Afternoons are reserved for expanding coverage for new features, a task she approaches with military-like discipline. Despite her technical prowess, she feels constrained by the team's resource allocation, which prioritizes new feature delivery over infrastructure stability. Financially, she is secure on £58k annually, allowing her to live comfortably in a renovated loft in Chapel Allerton, though she remains fiscally conservative, viewing money as a tool for security rather than status. Socially, she is reserved, finding solace in the predictable rhythms of baking and the narrative structures of true crime podcasts. Her personality, characterized by high conscientiousness and moderate openness, makes her a reliable anchor for her team, even if she sometimes struggles to articulate the value of her preventative work to more aggressive stakeholders.

Background & daily life

A day in their life

Lucia wakes at 6:15 AM, brewing coffee with a calibrated pour-over method before her morning yoga session. By 8:30 AM, she is logging into her workstation, immediately checking the CI/CD pipeline logs for overnight failures. Her morning is consumed by triaging flaky tests, often spending hours isolating race conditions in Playwright scripts. Lunch is a quick, solitary affair where she listens to a true crime episode, using the break to mentally reset. Afternoons are dedicated to writing new integration tests for the latest feature branch, meticulously documenting edge cases. At 4:30 PM, she updates her master Excel sheet with daily build statuses and release notes, a ritual she refuses to automate despite having the AI tool available. She leaves work by 5:30 PM sharp, ensuring she never brings work stress home, spending her evening baking or reading historical texts before bed.

Lifestyle

Lucia resides in a quiet, sun-drenched loft in Chapel Allerton, Leeds, where she maintains a strict separation between work and home life. Her evenings are ritualistic: after cooking precise, measured batches of sourdough or intricate pastries, she settles in with a true crime podcast, often replaying episodes until the details are memorized. She is financially prudent, prioritizing savings over luxury, and manages her budget with spreadsheets that rival corporate dashboards. Socially, she prefers small gatherings with close friends rather than large parties, finding energy in deep one-on-one conversations about philosophy or code rather than networking events. Her health routine involves morning yoga and long walks along the River Aire, essential for clearing the static of debugging sessions.

Work life

At her fintech startup, Lucia is the gatekeeper of quality for a tiny four-person engineering squad. Her day is a constant negotiation between building new test coverage for rapid feature releases and the relentless task of stabilizing a legacy Playwright suite that suffers from intermittent flakiness. Despite having an approved seat for a paid AI coding assistant, she finds herself still relying heavily on manual verification and Excel matrices to track test results and release notes, as the team's current documentation process remains stubbornly analog. The pressure is internal; she feels the weight of being the only safety net before production, leading to late nights spent refactoring brittle selectors rather than innovating new testing strategies.

Relationships

Lucia is deeply connected to her immediate circle, particularly her older brother who works in civil engineering and offers a grounded perspective on structural integrity. She has a tight-knit group of three university friends from Manchester whom she sees once a month for dinner. While she participates in a local knitting group, she keeps her professional network strictly limited to peers she trusts implicitly. She does not seek influence from industry influencers, preferring the advice of colleagues who have demonstrated practical competence over theoretical knowledge.

How they decide

Her decision-making process is slow, deliberate, and heavily reliant on empirical evidence. She rarely adopts a new tool or methodology without seeing peer-reviewed case studies, proof of concept demonstrations, and a detailed breakdown of integration costs. She avoids hype-driven purchases, preferring incremental improvements that offer immediate, measurable returns on time invested. Trust is built through consistency and transparency rather than persuasive marketing.

How they sound

She speaks with a calm, clipped Yorkshire accent, favoring precise terminology over colloquialisms. Her sentences are structured logically, often starting with a premise followed by supporting evidence. She avoids absolute statements like 'always' or 'never', preferring qualifiers such as 'typically' or 'under current constraints'. She rarely raises her voice, even when discussing critical bugs, and tends to pause thoughtfully before responding to questions, valuing accuracy over speed in conversation.

Personality traits

  • meticulously organized
  • quietly persistent
  • risk-averse in deployment
  • methodical problem solver
  • protective of data integrity
  • reserved in meetings
  • highly self-reliant
  • pragmatic about tools
  • detail-oriented observer
  • structured thinker

Goals

  • Achieve 100% deterministic test execution rates across all critical paths
  • Lead the migration of all manual release tracking to a centralized, automated dashboard
  • Obtain certification in a specialized cloud security testing framework
  • Reduce technical debt in the test infrastructure by 40% within 18 months
  • Establish a mentorship program for junior QA engineers in the Leeds tech community

Problems & frictions

  • Spending 60% of her week debugging flaky tests instead of writing new ones
  • The disconnect between the approved AI tool and her actual workflow efficiency
  • Maintaining accurate release notes in spreadsheets while developers move fast
  • Lack of clear ownership when test failures occur due to upstream code changes
  • Difficulty convincing stakeholders to invest time in infrastructure over new features
  • The mental fatigue of context-switching between complex Python logic and spreadsheet maintenance

Values

  • accuracy
  • consistency
  • traceability
  • efficiency
  • intellectual honesty

Interests

  • test automation architecture
  • artisanal baking
  • true crime podcasts
  • analog photography
  • historical linguistics

Media habits

  • Listens to 'The Daily' and 'Serial' during commutes
  • Reads 'IEEE Spectrum' and 'The Register'
  • Follows niche subreddits on Python best practices
  • Watches YouTube tutorials on CI/CD pipelines
  • Scrolls through LinkedIn for industry trends but rarely comments

Questions & answers

Lucia Mohr-McClure’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Show HN launch (163 pts, 2024-02-22): the product, the first code completion tool with 300k token context. Site shows pricing/signup. What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    A 300k token context window sounds impressive, but my biggest problem right now is actually integrating and trusting the AI tools we already have. We have a paid seat for an AI coding assistant, yet I'm still manually managing test matrices in spreadsheets. The real cost is the time lost on flaky tests and the potential for errors slipping through because I can't reliably offload tasks. I'd need to see clear, repeatable success cases specific to debugging and maintaining complex Playwright suites before considering anything new, regardless of its context window size.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.