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

Ivan Connelly

Ivan Connelly

QA lead at a fast-growing startup

Full-depth AI personas

Why this persona fits the audience

Coordinates a 3-person QA team and collects short recordings of regressions, flaky flows, and browser-only bugs for engineering tickets. He already pays for a desktop capture tool on his own machine, while the team often shares notes through spreadsheets and issue comments.

  • Age: 35
  • Location: Denver, Colorado, US
  • Occupation: QA Lead
  • Income: $128k
  • Education: BS in computer science
  • Company size: Startup (approx. 80 employees, growing rapidly)
  • Years in role: 4
“It's not just about finding bugs; it's about ensuring that when we find them, we can clearly communicate their impact so they get fixed right the first time.”

Ivan Connelly has been a QA Lead at his current fast-growing startup for four years, navigating the exhilarating but often chaotic pace of rapid development. Holding a BS in Computer Science from a state university, his career path was a natural progression from developer to tester, then into leadership. He chose QA because of his inherent drive for order and his fascination with how systems function—and fail. Denver has been his home for over a decade, drawn by its outdoor lifestyle and growing tech scene. He and his wife, Sarah, have built a stable life there, prioritizing financial prudence with a keen eye on long-term goals like homeownership. Ivan’s work ethic is deeply rooted in conscientiousness; he believes that thoroughness and attention to detail are non-negotiable for building reliable software. He actively invests in his own professional development, recently purchasing a desktop capture tool to personally demonstrate superior bug reporting methods to his team. This personal investment stems from a deep-seated frustration with the current manual processes his team relies on, which involve clunky spreadsheets and scattered issue comments for sharing critical visual evidence of regressions. He's keenly aware of the startup's budget sensitivities but is constantly evaluating tools and workflows that could provide better traceability and efficiency without breaking the bank. His focus is on building repeatable processes that ensure product quality doesn't become a casualty of rapid scaling. He views his role as a guardian of the user experience, and his decisions are guided by the principles of consistency, quality, and complete traceability of issues from discovery to resolution.

Background & daily life

A day in their life

Ivan's day typically starts around 6:30 AM with a run. After breakfast and getting ready, he's at his desk by 8:00 AM. The first hour is spent catching up on emails and reviewing overnight automated test results. From 9:00 to 11:00 AM, he holds a daily stand-up with his QA team, discussing blockers and assigning tasks. The rest of the morning involves digging into complex bugs, reviewing pull requests from his team, and collaborating with engineers on ticket details. After a quick lunch, he dedicates time to process improvement, currently focusing on better ways to capture and share regression videos, perhaps exploring new tools or refining existing workflows. He often ends the day by preparing for the next day's sprint planning or release testing.

Lifestyle

Ivan lives in a well-maintained townhouse in a Denver suburb with his wife, Sarah, a graphic designer. They're saving for a down payment on a house but haven't rushed the decision. His routine is structured: wake early for a quick run or gym session, commute listening to a podcast, and then dive into work. Evenings are a mix of cooking healthy meals, watching documentaries, or occasionally meeting friends for trivia night. They prioritize experiences over material possessions, planning a trip to national parks next summer. Money is managed carefully, with a focus on long-term financial security.

Work life

As QA Lead, Ivan's days are a constant balancing act. He juggles coordinating his three-person team, reviewing bug reports, and ensuring the quality gates for upcoming releases are met. The rapid growth of the startup means frequent new features and a constant influx of changes, often leading to regressions or flaky tests. He's committed to improving the bug reporting process, recognizing the limitations of their current spreadsheet-based system for sharing critical regression videos. He recently invested in a personal desktop capture tool to demonstrate better bug documentation to his team and engineering, hoping to standardize it.

Relationships

Ivan is married to Sarah, who grounds him and provides a creative counterpoint to his technical world. He maintains a small, close-knit group of friends from college, with whom he shares technical and life updates. His direct reports respect his methodical approach and clear direction, though they sometimes wish for more flexibility in reporting tools.

How they decide

Ivan is a highly analytical and research-driven decision-maker. He weighs evidence carefully, considers long-term implications, and seeks data to support his choices. He prefers to understand the 'why' behind a proposed solution and will often prototype or test options before committing. Peer consensus isn't his primary driver, but he values input from trusted colleagues and his team.

How they sound

Speaks in a measured, calm tone. He tends to use precise language and avoids hyperbole or overly casual slang. His cadence is steady, punctuated by thoughtful pauses. He's direct but polite, and his sentences are well-structured. He's unlikely to use buzzwords unless they are technically relevant and clearly understood. He might say things like, 'We need to establish a more consistent method for documenting these visual anomalies.'

Personality traits

  • Meticulous
  • Process-oriented
  • Analytical
  • Patient
  • Detail-focused
  • Reliable
  • Systematic
  • Pragmatic
  • Calm under pressure

Goals

  • Establish a robust, centralized system for capturing and sharing visual bug evidence
  • Automate more regression test cases to free up QA team bandwidth
  • Achieve Senior QA Engineer certification
  • Contribute to the company's stability and reputation for quality
  • Maintain a healthy work-life balance despite company growth

Problems & frictions

  • Inconsistent quality of bug reports from his team due to tool limitations
  • Wasting time manually digging for context on reported bugs
  • Engineering team's occasional difficulty reproducing reported issues without clear visual aids
  • Pressure to scale QA processes quickly without significant budget increases
  • The overhead of maintaining and organizing bug documentation manually
  • Balancing proactive quality assurance with reactive bug fixing

Values

  • consistency
  • quality
  • traceability
  • efficiency
  • clarity

Interests

  • release testing
  • bug tracking
  • dev workflows
  • automation strategies
  • performance metrics

Media habits

  • Listens to tech podcasts during his commute
  • Reads industry blogs and Stack Overflow daily
  • Follows engineering and QA thought leaders on LinkedIn
  • Subscribes to newsletters on software development trends
  • Uses Reddit for niche technical discussions

Questions & answers

Ivan Connelly’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Screen Awesome (https://screenawesome.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).

    My team and I currently rely on a combination of spreadsheets and issue comments for documenting bugs, which is inefficient for visual evidence. I've personally invested in a desktop capture tool to demonstrate better reporting methods. What would stop me from trying Screen Awesome is the lack of team-wide deployment or management features. I need a way to standardize usage across my three-person team, ensuring consistency and easy access to recordings for engineering tickets. If it offered centralized management or a simple way for my team to use it and contribute recordings uniformly, I might consider it. I would be willing to pay up to $15 per month for a solution that addresses our team's specific needs for bug reporting, though the current offer seems to be free for individual use.
    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.