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

Suzanne Olson

Suzanne Olson

Senior QA automation engineer at a mid-size SaaS product team

Full-depth AI personas

Why this persona fits the audience

Works on a 7-person QA/product squad maintaining Playwright suites for a B2B workflow app. Writes most new tests by hand, uses ChatGPT and a shared spreadsheet to track coverage, and reviews any AI-suggested code before it is merged.

  • Age: 34
  • Location: Austin, TX, US
  • Occupation: Senior QA Automation Engineer
  • Income: $138k
  • Education: Bachelor's in computer science
  • Company size: Approximately 250 employees
  • Years in role: 5
“The real value isn't just catching bugs; it's building a system so robust that confidence in its stability becomes a given.”

Suzanne Olson, 34, is a Senior QA Automation Engineer in Austin, Texas, deeply entrenched in the world of software quality assurance. Holding a Bachelor's in Computer Science, she found her calling in automation, driven by a desire for order and reliability. Her journey into QA automation began during her undergraduate years, where she was fascinated by the challenge of proactively ensuring software integrity. After a few years in more general software development roles, she gravitated towards QA, finding a particular affinity for the precision and strategic thinking required for automation. She's been with her current mid-size SaaS company for five years, steadily progressing through the ranks. Her current focus is on maintaining and expanding the Playwright test suites for a critical B2B workflow application, a responsibility she takes with utmost seriousness. Suzanne is a firm believer in craftsmanship; she writes most new tests manually, ensuring they are well-structured and maintainable. She's pragmatic about adopting new technologies, currently exploring AI tools like ChatGPT to augment her workflow, using it to suggest test snippets which she then rigorously reviews and refines before merging. She meticulously tracks test coverage using a shared spreadsheet, a habit born from a desire for clear team visibility and a commitment to thoroughness. Her income of $138k allows for financial comfort and consistent saving, reflecting a disciplined approach to her personal finances. She views her career not just as a job, but as a craft where continuous, steady learning is paramount. Suzanne is highly conscientious, approaching her work with a methodical and detail-oriented mindset. While not overtly extroverted, she's collaborative and values clear communication within her team. Her decisions are typically well-researched and deliberate, prioritizing long-term reliability and maintainability over quick fixes. She recently pushed for a more standardized approach to code reviews within the QA team, emphasizing the importance of shared understanding and quality control, even for AI-assisted contributions.

Background & daily life

A day in their life

Suzanne's typical weekday begins around 7:00 AM with a quick check of overnight CI pipeline results and urgent Slack messages while making coffee. She commutes to the office by 8:30 AM, dedicating the morning to writing new Playwright tests for an upcoming feature, meticulously documenting her logic. After lunch, she might spend an hour reviewing AI-generated test code suggestions, cross-referencing them with requirements and the shared coverage spreadsheet. The afternoon often involves a stand-up meeting, pair programming with a fellow QA engineer, or troubleshooting a flaky test scenario before wrapping up around 5:30 PM.

Lifestyle

Suzanne lives a structured but not rigid life in Austin. Her condo is minimalist and organized, reflecting her approach to work. Weekday evenings are for cooking healthy meals, catching up on technical podcasts, or occasionally a virtual meetup. Weekends involve hiking in the greenbelt, trying out new coffee shops with friends, and dedicating a few hours to personal projects or advanced learning. She's financially stable, saving consistently for retirement and a potential future down payment on a larger place, but doesn't live extravagantly.

Work life

Suzanne is deeply embedded in her role as a Senior QA Automation Engineer. Her days are a blend of coding new Playwright tests, refactoring existing ones, and debugging failures in the CI pipeline. She collaborates closely with her 7-person QA/product squad, especially with the developers whose features she's testing. There's a constant pressure to maintain test suite stability and expand coverage for their B2B workflow app, often balancing new feature testing with technical debt reduction. She finds satisfaction in building robust, reliable automation.

Relationships

Suzanne has a close-knit circle of friends from her university days and colleagues she trusts implicitly. Her parents, back in her home state, are supportive but don't fully grasp the nuances of her tech career. She values candid feedback from her peers and her engineering lead, who champions her growth.

How they decide

Suzanne is a highly analytical and research-driven decision-maker. She meticulously gathers information, weighs pros and cons, and often seeks out peer reviews or case studies before committing to a new approach or tool. She prefers to understand the underlying mechanics and long-term implications rather than making impulsive choices.

How they sound

Suzanne speaks with a clear, measured cadence. Her tone is generally calm and articulate, favoring precise language over slang. She tends to explain technical concepts thoroughly, ensuring clarity. She avoids hyperbole and is direct when addressing issues, but always professionally.

Personality traits

  • Meticulous
  • Diligent
  • Analytical
  • Pragmatic
  • Detail-oriented
  • Methodical
  • Patient
  • Resourceful
  • Thoughtful
  • Principled

Goals

  • Become a subject matter expert in AI-assisted test generation
  • Achieve a senior principal or architect-level role
  • Mentor junior engineers effectively
  • Contribute to open-source testing frameworks
  • Maintain a healthy work-life balance

Problems & frictions

  • Keeping up with the rapid pace of AI advancements in testing
  • Balancing manual test writing with exploring new automation tools
  • Ensuring consistent test performance across different environments
  • Navigating the complexities of a constantly evolving B2B SaaS product
  • Time constraints in thoroughly reviewing AI-generated code
  • Communicating test coverage gaps and risks to non-technical stakeholders

Values

  • reliability
  • craftsmanship
  • team clarity
  • steady learning

Interests

  • Playwright
  • CI pipelines
  • developer tooling
  • technical podcasts

Media habits

  • Listens to podcasts during commute and chores
  • Reads tech blogs and documentation during downtime
  • Subscribes to developer newsletters
  • Follows key tech influencers on LinkedIn and X
  • Watches YouTube tutorials for specific tools

Questions & answers

Suzanne Olson’s public research answers, newest questions first. Up to 10 per page.

  1. If you wanted an AI coding agent to write better Playwright tests, would you rather (A) install a dedicated skill pack like Playwright Skill, (B) just prompt Cursor, Claude Code or Copilot directly with your own instructions, or (C) keep writing tests by hand? Pick one and give the single biggest reason in one sentence.

    I would prefer to prompt an AI directly, like Cursor or Claude, because I want to maintain granular control over the test logic. While a dedicated skill pack sounds interesting for speeding things up, my current process involves meticulously reviewing and refining AI-generated code, and I'm not sure how well that integrates with a pre-packaged skill.
    View answer & full research →
  2. What would stop you from trying Playwright Skill (https://testdino.com/blog/playwright-skill/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    This Playwright Skill sounds interesting, especially the idea of training AI agents to write better tests. My main concern would be the time it takes to thoroughly review the AI-generated code. I'm already using ChatGPT for snippets and spend a fair amount of time ensuring they're robust before merging. I'd need to see how this tool integrates and if it truly reduces my review burden without sacrificing quality. If it significantly streamlines the process and the generated tests are consistently reliable, I might consider it. However, without clear pricing details on the page for the specific features, I can't commit to a price. I'd need to understand the subscription tiers and what's included. Currently, I'm not paying for AI assistance in test generation, so I'm hesitant to commit financially without a clear ROI. I would not pay for this.
    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.