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

Thirza Visser

Thirza Visser

QA automation engineer supporting a small remote team

Full-depth AI personas

Why this persona fits the audience

She supports a remote 5-person engineering team in the Netherlands that merges through GitHub PRs and relies on automated tests plus manual review for release decisions. She keeps a lightweight spreadsheet of recurring review issues and often checks whether changes came from AI-assisted coding or from hand-written patches.

  • Age: 33
  • Location: Utrecht, Netherlands
  • Occupation: QA Automation Engineer
  • Income: €68,000 gross
  • Education: BSc Software Engineering
  • Company size: Small (approx. 20 people total)
  • Years in role: 5
“The goal isn't just to find bugs, it's to build confidence that the code we ship is robust and reliable, no matter how it was written.”

Thirza Visser, 33, has been a dedicated QA Automation Engineer based in Utrecht for the past five years, holding a BSc in Software Engineering. Her career path has been a steady progression, driven by a deep-seated need for order and a fascination with how systems work and can be improved. She joined her current company, a small tech firm with a global remote engineering team, shortly after graduating, drawn by the opportunity to build testing frameworks from the ground up. Her role is pivotal, supporting a lean, five-person engineering team that relies heavily on GitHub for collaboration. Thirza's primary responsibility is ensuring the quality and reliability of their software releases through robust automated testing. She meticulously crafts and maintains these test suites, always striving for maximum code coverage. A significant part of her daily routine involves scrutinizing GitHub pull requests, not just for functional correctness but also for adherence to best practices and potential vulnerabilities. She maintains a lightweight, yet crucial, spreadsheet where she logs recurring issues identified during reviews, a practice born from her conscientious nature and desire for systemic improvement. Recently, she's been dedicating extra attention to discerning the origin of code changes, differentiating between human-written patches and code generated with AI assistance, a growing concern for maintaining code integrity. This analytical approach extends to her personal life; she approaches financial planning with similar diligence, saving consistently for future goals like travel and property. While not overtly ambitious in terms of climbing a corporate ladder, Thirza is driven by a desire for mastery in her field and contributing meaningfully to her team's success. She values her autonomy and the intellectual challenge her role provides, finding satisfaction in solving complex problems and optimizing processes. Her decision-making is typically data-driven and well-researched, reflecting her methodical personality.

Background & daily life

A day in their life

Thirza's typical weekday starts around 7:30 AM with coffee and a quick scan of overnight test results. By 9:00 AM, she's logged into Slack and Jira, checking for urgent requests or PRs needing review. Her morning is often dedicated to writing new automated tests or refactoring existing ones, aiming to increase coverage for a recently deployed feature. After a brief lunch break, she dives into reviewing GitHub PRs, meticulously checking for adherence to coding standards, potential bugs, and, increasingly, signs of AI-generated code. She maintains her spreadsheet of recurring issues, noting any patterns. The afternoon might involve a short sync with a developer to discuss a complex bug or a planning session for upcoming sprint testing.

Lifestyle

Thirza lives in a comfortable apartment in Utrecht with her partner, a graphic designer. Their routines are fairly balanced, with Thirza enjoying early mornings for focused work and a quiet cup of meticulously brewed pour-over coffee before her workday officially begins. Evenings are often spent cycling through the city, cooking together, or unwinding with a book. She's financially responsible, saving consistently for future travel and home improvements, but enjoys small luxuries like high-quality coffee beans. Socially, she prefers smaller gatherings with close friends over large parties.

Work life

As a QA Automation Engineer for a small, fully remote team, Thirza's days are a blend of proactive test development and reactive code review support. She spends a significant portion of her time writing and maintaining automated test suites, ensuring comprehensive coverage across their web application. Her current focus is on refining the CI/CD pipeline to catch regressions earlier. She collaborates closely with the 5 engineers, primarily through GitHub pull requests and asynchronous communication channels. The pressure is on to maintain high code quality with limited resources, making her role critical for timely releases.

Relationships

Thirza is in a stable, long-term relationship with her partner, who provides a supportive and creative counterbalance to her technical world. Her immediate family lives in a different province, and they connect via video calls weekly. Her closest work relationships are with the engineers she supports, built on mutual respect for each other's contributions and a shared goal of product quality.

How they decide

Thirza is a research-heavy decision-maker, especially for tools or processes that impact her workflow. She values evidence, peer recommendations within trusted technical communities, and thorough evaluation of alternatives before committing. She's not impulsive and prefers to understand the long-term implications of any change.

How they sound

Speaks clearly and precisely, with a moderate pace. Her tone is generally calm and professional, avoiding overly casual slang or jargon unless in a very familiar technical context. She tends to use complete sentences and articulate her thoughts thoroughly. She avoids hyperbole and focuses on factual descriptions. When discussing technical issues, she's direct but polite.

Personality traits

  • meticulous
  • analytical
  • detail-oriented
  • methodical
  • patient
  • collaborative
  • pragmatic
  • observant
  • organized

Goals

  • Achieve a senior QA Automation Engineer position within the next three years.
  • Contribute to a significant open-source testing framework.
  • Become proficient in a new programming language (e.g., Rust) for performance-critical testing.
  • Maintain a healthy work-life balance without sacrificing career growth.
  • Save enough for a down payment on a small house.

Problems & frictions

  • Keeping up with the rapid pace of new AI coding tools and their potential impact on code quality.
  • Ensuring consistent test coverage across a growing codebase with limited development resources.
  • Managing the overhead of manual review processes alongside automated checks.
  • The challenge of distinguishing between genuinely novel code and AI-generated patterns that might introduce subtle bugs.
  • Occasional communication friction in a fully remote team setting.

Values

  • reliability
  • coverage
  • team coordination
  • code quality
  • efficiency

Interests

  • test automation
  • open-source tools
  • home coffee brewing
  • exploring new programming languages
  • cycling

Media habits

  • Reads tech blogs (e.g., Martin Fowler's site, Hacker News)
  • Listens to podcasts during commute (e.g., Software Engineering Daily, The Changelog)
  • Follows key figures in QA and dev tools on Twitter/X
  • Watches YouTube tutorials for new tools or techniques
  • Participates in Slack communities for specific open-source projects

Questions & answers

Thirza Visser’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Detect AI-generated code in any GitHub PR in 15 seconds. the product gives every codebase a VibeCode score and blocks risky merges with PR Guardian. Try it free. 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.

    The biggest problem for me is the uncertainty around AI-generated code. It's becoming increasingly difficult to reliably distinguish between human authorship and AI assistance, and I worry about subtle bugs or security vulnerabilities slipping through. This means I spend extra time manually scrutinizing PRs, which adds to the review overhead and potentially delays releases. We've already tried having developers self-report if they used AI tools, but that's not a foolproof solution. I'm not sure how a 'VibeCode score' would work in practice or if it could accurately detect these nuances in 15 seconds. What are the false positive rates?
    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.