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

Frank Howe

Frank Howe

QA automation engineer at a SaaS startup

Full-depth AI personas

Why this persona fits the audience

Works on a 5-person product engineering team in Austin, maintaining end-to-end tests that trigger SMS OTP flows on staging and pre-production. Keeps a small pool of rented test numbers and API credentials for repeated verification runs across US and UK routes, and already uses 5sim for some checks.

  • Age: 31
  • Location: Austin, TX, US
  • Occupation: QA Automation Engineer
  • Income: $118k
  • Education: B.S. Computer Science
  • Company size: Startup (under 50 employees)
  • Years in role: 4
“The real test of automation isn't just that it passes; it's that it passes reliably, consistently, and without creating more work down the line.”

Frank Howe, a 31-year-old QA Automation Engineer, has carved out a niche in the demanding world of SaaS startups. Hailing from a solid academic background with a B.S. in Computer Science, he found his calling not in direct development, but in the critical art of ensuring software quality through automation. His journey into QA automation began during an internship at a larger tech firm, where he witnessed firsthand the chaos that poorly tested releases could unleash. This experience cemented his belief in the foundational importance of robust testing, especially in fast-paced startup environments. He landed in Austin, drawn by its burgeoning tech scene and vibrant cycling culture, and has been with his current company, a growing SaaS provider, for four years. Here, he operates within a lean, five-person product engineering team. His primary responsibility revolves around the intricate SMS OTP (One-Time Password) flows, essential for user onboarding and verification within the platform. Frank meticulously maintains and enhances the end-to-end test suites that run on staging and pre-production environments, ensuring these critical pathways are solid before code hits live users. Frank's approach is highly systematic. He manages a small, curated pool of rented test phone numbers and API credentials, strategically cycling through them for repeated verification runs. Recognizing the limitations and costs associated with managing this infrastructure, he's integrated services like 5sim into his workflow to optimize coverage and efficiency for both US and UK routes. He's deeply invested in the principles of clean automation, viewing it as a direct investment in the company's ability to ship on schedule without sacrificing quality. He champions low-friction coordination within the team, believing that clear, automated processes prevent misunderstandings and speed up development cycles. His income of $118k allows for a comfortable, though not extravagant, lifestyle, which he further enhances through diligent saving and a focus on value over impulse purchases, reflecting his inherent conscientiousness.

Background & daily life

A day in their life

Frank's weekday begins with a 6:30 AM alarm, followed by a quick check of overnight test reports and Slack messages. After a meticulously prepared breakfast, he's at his desk by 8:00 AM. The morning is dedicated to writing new automated tests for upcoming features, focusing on the SMS OTP workflows. This involves configuring test data, updating API credentials, and ensuring coverage for US and UK routes. Lunch is a packed meal he eats at his desk while skimming tech news. The afternoon is often spent debugging failing tests, coordinating with developers on bug fixes, and refining existing test scripts for better performance and reliability. He might spend an hour exploring new automation libraries or reading documentation for potential improvements. His workday typically wraps up around 5:30 PM.

Lifestyle

Frank lives a fairly structured life, prioritizing efficiency and order. His Austin apartment is minimalist and organized, reflecting his tendency towards clean systems. Evenings are often spent tuning his mechanical keyboard or researching new automation tools. Weekends involve long cycling routes through the Greenbelt, followed by quiet nights catching up on tech news or indie SaaS development blogs. He's disciplined about his health, packing his own lunches and sticking to a regular sleep schedule. Financially, he’s saving diligently, aiming for long-term security over extravagant spending.

Work life

Frank is deeply immersed in ensuring the stability of his company's SaaS platform. His days are a cycle of writing, maintaining, and debugging end-to-end test suites, focusing heavily on the SMS OTP flows critical for user onboarding and verification. He juggles tasks with the small product engineering team, often acting as the gatekeeper for releases, ensuring tests pass reliably across staging and pre-production environments. The pressure to ship on schedule is constant, pushing him to optimize his test runs and manage his pool of rented test numbers efficiently, integrating services like 5sim where it makes sense to maintain coverage.

Relationships

Frank maintains a small, close-knit circle of friends, mostly colleagues from previous tech jobs and fellow cyclists. He talks to his parents weekly, who live in a different state and appreciate his stable career. His primary professional influence comes from online communities and a few respected figures in the test automation space he follows on LinkedIn and Hacker News.

How they decide

Frank is highly analytical and research-driven. Before committing to a new tool or process, he meticulously evaluates its technical merits, potential long-term maintenance overhead, and alignment with his team's existing infrastructure. He favors solutions that offer proven reliability and clear documentation, and is willing to invest time in understanding the underlying mechanics rather than adopting trends superficially. Peer recommendations from trusted technical sources carry weight, but the final decision is always based on his own rigorous assessment.

How they sound

Frank speaks with a measured, deliberate cadence. His language is precise and technically accurate, often employing specific automation terminology. He avoids hyperbole and unnecessary slang, preferring clear, factual statements. When discussing technical challenges, he’s direct but not confrontational, focusing on root causes and logical solutions. His tone is generally calm and even, reflecting his methodical approach.

Personality traits

  • meticulous
  • analytical
  • detail-oriented
  • methodical
  • patient
  • introverted
  • focused
  • observant
  • principled

Goals

  • Achieve a senior or lead QA automation engineer position
  • Contribute to open-source automation frameworks
  • Build a side project related to developer tooling
  • Complete a challenging century cycling race
  • Maintain a high level of technical proficiency

Problems & frictions

  • Inconsistent test environments causing flaky test runs
  • Managing the lifecycle and cost of rented test phone numbers
  • Balancing comprehensive test coverage with tight release deadlines
  • Lack of standardized processes for cross-team coordination on testing
  • Keeping up with the rapid pace of new testing technologies and methodologies

Values

  • reliability
  • clean automation
  • shipping on schedule
  • low-friction coordination
  • efficiency

Interests

  • test automation
  • indie SaaS
  • cycling
  • mechanical keyboards
  • performance tuning

Media habits

  • Reads tech blogs (e.g., Hacker News, The Register)
  • Listens to tech podcasts during commutes
  • Follows specific QA and automation influencers on LinkedIn
  • Watches YouTube tutorials for coding and tool tips
  • Checks Reddit for niche tech discussions

Questions & answers

Frank Howe’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying DogeSMS (https://dogesms.com/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    The main thing that would stop me from trying DogeSMS this month is the need to evaluate its reliability for our specific OTP flows, especially for US and UK routes. Currently, I manage a pool of rented numbers and use 5sim for some checks. I'd need to see if DogeSMS can consistently deliver codes without introducing flakiness into our end-to-end tests, which are critical for our staging and pre-production environments. The pay-as-you-go model is interesting, but I'd need to understand the actual costs incurred for successful verifications. I'd be willing to pay up to $50 per month for this service, but only if it proves more stable and cost-effective than my current setup.
    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.