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

Wesley Ritchie

Wesley Ritchie

Frontend engineer on a small product squad

Full-depth AI personas

Why this persona fits the audience

Works on a six-person B2B SaaS product squad in Chicago. He wires Storybook snapshots and Cypress screenshots into CI, then tracks expected UI diffs in a spreadsheet and Slack thread before release. He also helps maintain the review checklist for one other squad that shares the same staging app.

  • Age: 31
  • Location: Chicago, Illinois, USA
  • Occupation: Frontend engineer
  • Income: $135k
  • Education: B.S. in Computer Science
  • Company size: Mid-sized tech company (approx. 250 employees)
  • Years in role: 5
“Consistency is key; if we can automate the checks that ensure it, we free ourselves up to build better things.”

Wesley Ritchie, 31, is a dedicated frontend engineer based in Chicago, holding a B.S. in Computer Science. He has spent the last five years honing his skills within small product squads, currently contributing to a six-person team developing B2B SaaS solutions. His professional life is characterized by a deep commitment to quality and efficiency, particularly evident in his current workflow. Wesley is instrumental in integrating Storybook snapshots and Cypress screenshots directly into their Continuous Integration (CI) pipeline. This process involves meticulously tracking expected UI differences, a task he manages through a combination of spreadsheets and dedicated Slack threads, ensuring that visual regressions are identified and addressed before each release. His conscientiousness (0.84) shines through in this detailed approach, aiming for maximum release confidence. Beyond his immediate squad, Wesley also dedicates time to maintaining the review checklist for another team that shares their staging application, demonstrating a sense of shared responsibility and a desire for standardized quality across the product. His income of $135k allows for a comfortable lifestyle, but he remains pragmatic and focused on long-term financial security, saving diligently. Wesley's interest in developer tooling, design systems, and practical automation stems from a genuine desire to improve the development process and build more reliable software. He values clear ownership and seeks to automate repetitive tasks, viewing it as essential for maintaining high standards without burnout. His reserved nature (extraversion 0.38) means he often expresses his ideas through well-reasoned code and documentation rather than extensive verbal debate, but his contributions are highly valued by his colleagues and management.

Background & daily life

A day in their life

Wesley's typical weekday begins around 7:00 AM with a quick breakfast and checking personal emails. He commutes to the office by 8:30 AM, often listening to a tech podcast. His workday starts with reviewing overnight CI runs and addressing any critical issues. The bulk of his morning is spent coding new features or fixing bugs, collaborating with his team via Slack and occasional stand-ups. After lunch, he dedicates time to setting up Storybook snapshots for new components or refining Cypress tests. He also spends about an hour helping the other squad with their review checklist. He leaves the office around 5:30 PM, heads to the gym, and then goes home to cook dinner and unwind.

Lifestyle

Wesley lives a structured, relatively quiet life in Chicago. He rents a modern one-bedroom apartment in Lincoln Park, which he keeps meticulously organized. His evenings often involve cooking a healthy meal, followed by either diving into a personal coding project, reading tech blogs, or catching up on a sci-fi series. He prioritizes his health, hitting the gym three times a week and enjoying long walks along the lakefront on weekends. Socially, he's not one for large parties, preferring smaller gatherings with close friends or quiet nights in. His financial habits are conservative; he saves diligently, aiming for long-term stability rather than immediate gratification.

Work life

As a frontend engineer on a small B2B SaaS product squad, Wesley's days are focused on ensuring UI stability and consistency. His primary responsibility involves integrating Storybook snapshots and Cypress screenshots into their CI pipeline. He meticulously tracks expected UI diffs, often in a shared spreadsheet and a dedicated Slack thread, to catch regressions before they reach production. He also dedicates a portion of his week to maintaining the review checklist for another squad that shares their staging environment, a task he approaches with his characteristic thoroughness. The pressure is on to maintain high quality with limited resources, making his role critical for release confidence.

Relationships

Wesley maintains a small but strong circle of friends, mostly met through university or previous jobs. He communicates with his parents weekly via phone calls. Within his team, he's respected for his reliability and technical contributions, though he's not the most vocal member in meetings. His direct manager, Sarah, values his consistent output and attention to detail.

How they decide

Wesley is a cautious and research-heavy decision-maker, especially concerning technical tools. He thoroughly investigates options, weighs pros and cons systematically, and often seeks out documentation and community consensus before committing. He values practical, proven solutions over trendy, unverified ones.

How they sound

Speaks in a clear, measured tone. Tends to be precise and avoids hyperbole or overly casual slang. Uses technical jargon naturally within a work context but is capable of explaining complex topics in simpler terms when needed. He's not prone to complaining but will state facts about challenges directly. Avoids definitive pronouncements unless he's fully confident in the data.

Personality traits

  • meticulous
  • detail-oriented
  • methodical
  • reliable
  • analytical
  • reserved
  • pragmatic
  • systematic
  • patient

Goals

  • Achieve senior engineer status within the next two years
  • Contribute to an open-source project related to UI testing or design systems
  • Develop a more robust and automated UI testing strategy for his team
  • Maintain a healthy work-life balance without sacrificing career progression
  • Save enough for a down payment on a condo in the next five years

Problems & frictions

  • The manual tracking of UI diffs is becoming increasingly time-consuming and prone to human error
  • Limited bandwidth to fully explore and implement more advanced visual regression testing tools
  • Balancing the needs of his immediate squad with the shared responsibilities for the staging app
  • Occasional friction with designers over the perceived subjectivity of UI changes
  • Keeping up with the rapid pace of frontend framework and tooling updates

Values

  • release confidence
  • practical automation
  • clear ownership
  • code quality
  • efficiency

Interests

  • Storybook
  • Cypress
  • CI/CD
  • design systems
  • frontend performance
  • developer tooling

Media habits

  • Reads Hacker News daily
  • Follows key figures on Twitter for tech news
  • Listens to tech podcasts during commute (e.g., Syntax.fm, Frontend Masters)
  • Watches YouTube tutorials for specific libraries/frameworks
  • Occasionally browses Reddit's r/frontend

Questions & answers

Wesley Ritchie’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: The batteries-included platform for visually testing and reviewing your UI; it's even self-hostable! Connect your codebase with our many integrations and dramatically increase your test coverage in minutes. 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 we face is the sheer manual effort involved in tracking UI diffs across Storybook snapshots and Cypress screenshots. We're currently managing this with a spreadsheet and a Slack thread, which is time-consuming and, frankly, prone to human error. It costs us valuable engineering hours that could be spent on feature development or improving our core testing. I've already tried standardizing our checklist and automating initial snapshot generation, but the diff review itself remains a bottleneck. I'm curious how your platform handles the 'batteries-included' aspect – does it integrate directly with Storybook, and how does it manage the review process for expected changes?
    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.