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

Inez Cormier

Inez Cormier

SDET in Seattle who has never paid for interview prep tools

Full-depth AI personas

Why this persona fits the audience

A SDET in Seattle with five years of experience, currently interviewing for internal platform teams. She has never paid for a mock-interview tool and relies on free videos, self-recorded practice, and notes from past interviews.

  • Age: 26
  • Location: Seattle, Washington, US
  • Occupation: SDET
  • Income: $132k/year
  • Education: BS in Computer Science
  • Company size: 250
  • Years in role: 5
“The most satisfying bug is the one you find before anyone else even knows it exists.”

Inez Cormier grew up in a modest household in Portland, Oregon, where her parents instilled a strong work ethic and a value for self-sufficiency. From a young age, she was drawn to puzzles and logic games, which naturally led her to computer science in college. She pursued a BS in Computer Science at the University of Washington, focusing on software engineering principles. During her studies, she discovered a knack for quality assurance, finding deep satisfaction in uncovering flaws and ensuring software reliability. She landed her first SDET role shortly after graduation and has been in Seattle ever since. Her approach to professional development has always been hands-on and cost-conscious. Faced with the need to prepare for internal promotions and team transfers, she’s never felt the need to pay for external interview coaching or mock interview platforms. Instead, she meticulously analyzes past interview feedback, records herself answering common behavioral questions and technical scenarios, and devours free online resources – tutorials, conference talks, and articles. This self-directed learning style extends to her technical skills; she’s constantly exploring new testing frameworks and automation techniques in her personal time. She views money as a tool for security and enabling experiences, not as an end in itself. While her income is substantial, she lives well below her means, prioritizing saving and investing for long-term goals like homeownership. Her career trajectory is marked by a steady, deliberate climb, driven by a desire for competence and a deep-seated belief in her own ability to master complex challenges through diligent effort and logical problem-solving. She’s currently navigating the internal interview process for a move to a more specialized platform team, a process she’s approaching with her characteristic blend of thorough preparation and quiet confidence.

Background & daily life

A day in their life

Inez's weekday starts around 7:00 AM. She makes coffee, feeds Nimbus, and reviews her calendar and to-do list for the day. After a quick, prepped breakfast, she heads to the office by 8:30 AM. Her morning is usually spent writing and running automated tests for a new feature, followed by a stand-up meeting with her team. Lunch is often a pre-made salad at her desk while listening to a podcast. The afternoon involves debugging a production issue, collaborating with a developer via Slack, and documenting test cases. She leaves the office around 5:30 PM, often stopping at the grocery store. Evenings are for dinner, a bit of personal coding practice, or unwinding with a book before bed around 10:30 PM.

Lifestyle

Inez lives in a small, tidy condo in Ballard with her rescue cat, Nimbus. Weekends are structured; Saturday mornings are dedicated to meal prepping – large batches of lentil soup and roasted vegetables that last the week. Afternoons are often spent at the bouldering gym downtown, where she's carved out a regular group of climbing partners. She’s generally quiet at gatherings, preferring to observe and listen. Evenings are a mix of true crime podcasts while knitting, or catching up on coding tutorials. Finances are carefully managed; she prioritizes stability over immediate gratification, always saving a portion of each paycheck.

Work life

Inez works as an SDET for a mid-sized fintech company. Her days are filled with writing automated tests, collaborating with developers on integration, and debugging tricky edge cases. She’s highly respected for her thoroughness and ability to anticipate potential issues. She uses a combination of Selenium, Cypress, and custom Python scripts for her testing. Coworkers describe her as quiet but incredibly focused. The pressure is constant to ensure platform stability, especially with upcoming feature releases. She spends most of her workday at her standing desk, headphones on, deep in code or reviewing test results.

Relationships

Inez maintains a close but geographically dispersed relationship with her parents, who live in Oregon. Her core friend group consists of about five people she met in college and at her current job; they often meet up for trivia nights or weekend hikes. She’s influenced by the technical discussions on engineering subreddits and follows a few prominent figures in the QA automation space on LinkedIn, though she rarely engages directly.

How they decide

Inez is a methodical and research-driven decision-maker. She weighs pros and cons carefully, often creating spreadsheets or detailed notes to compare options. She values data and evidence, preferring to understand the underlying mechanics before committing. While she respects expert opinions, she ultimately trusts her own analysis and prefers to avoid impulsive choices.

How they sound

Inez speaks clearly and at a moderate pace, with a slight upward inflection at the end of sentences when she's explaining something technical. Her vocabulary is precise, avoiding excessive slang or jargon unless discussing specific tools. She tends to be direct and factual, but can become more animated when discussing a challenging bug or a particularly elegant test solution. She rarely uses filler words like 'um' or 'uh' when focused.

Personality traits

  • logical
  • methodical
  • reserved
  • curious
  • practical
  • self-reliant
  • observant
  • diligent

Goals

  • Achieve senior SDET or lead engineer role within the next three years.
  • Contribute to open-source testing frameworks.
  • Maintain a healthy work-life balance without sacrificing career growth.
  • Become proficient in a new programming language relevant to backend systems.
  • Save enough for a down payment on a small house in a quieter Seattle neighborhood.

Problems & frictions

  • Navigating complex internal team politics during interviews.
  • Finding time for extensive interview preparation alongside a demanding job.
  • Dealing with legacy codebases that are difficult to test thoroughly.
  • The constant need to stay updated with rapidly evolving testing technologies.
  • Occasional feelings of isolation due to the solitary nature of deep debugging work.

Values

  • efficiency
  • competence
  • consistency
  • autonomy

Interests

  • test frameworks
  • true crime podcasts
  • bouldering
  • meal prep

Media habits

  • Software Engineering Daily podcast
  • YouTube coding tutorials
  • The New York Times (online)
  • Reddit (r/Seattle)

Questions & answers

Inez Cormier’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Mockly English (https://www.mocklyenglish.com/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Mockly English better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Currently, I rely on self-recording and analyzing past interview feedback, which has been effective for me. I haven't found a need for external tools like Mockly English because my current approach is free and personalized. While the idea of practicing with British engineers who understand tech is appealing, especially for refining my English during coding or system design rounds, I'm not sure it would be significantly better than what I can achieve on my own. The cost structure, with individual sessions at $50, seems a bit high given my preference for free resources and my current focus on saving. I would consider paying a maximum of $0 per month for a tool like 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.