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

Jerry Boehm-Johns

Jerry Boehm-Johns

Frontend engineer owning test automation at a small startup

Full-depth AI personas

Why this persona fits the audience

At a 4-person startup, he owns most Playwright coverage for the web app while also shipping UI features. He already pays for a general AI coding assistant in his editor and keeps test scenarios in a spreadsheet before turning them into code.

  • Age: 29
  • Location: Manchester, UK
  • Occupation: Frontend Engineer
  • Income: £78k
  • Education: Bachelor's in software engineering
  • Company size: 4 (including founders)
  • Years in role: 3 years
“I don't write code to impress anyone; I write it so the machine stops lying to me.”

Jerry Boehm-Johns is a 29-year-old Frontend Engineer based in Manchester, UK, navigating the chaotic yet exhilarating waters of a four-person startup. With a Bachelor's in Software Engineering and three years of experience in the industry, Jerry has carved out a unique niche where he is simultaneously the primary architect of user interfaces and the sole guardian of their reliability. His daily reality is a delicate balancing act: he spends mornings crafting responsive React components that delight users and afternoons wrestling with Playwright tests to ensure those components don't regress when the world changes. Unlike larger organizations with dedicated QA teams, Jerry operates with a 'full-stack' mentality regarding quality, managing everything from scenario definition in a clunky Google Sheet to the final execution of automated tests. He is a pragmatist at heart, driven by a desire for speed and code quality, often finding himself in the awkward position of having to justify the time spent on testing to founders focused on rapid feature deployment. Jerry is technically confident but acutely aware of his limitations; he knows that while he can build almost anything, the maintenance burden of a growing test suite is a ticking clock. He recently invested in a premium AI coding assistant for his editor, hoping to bridge the gap between his spreadsheet notes and actual code generation, but remains skeptical of tools that promise to replace human judgment entirely. Living in a shared loft in the creative hub of Ancoats, Jerry's life outside work is a mix of disciplined routine and creative exploration. He is deeply protective of his mental space, often working late into the night not because he wants to, but because the nature of his role demands it. His income of £78k provides a comfortable middle-class life, allowing him to invest in high-quality hardware and occasional travel, but he remains financially cautious, prioritizing savings over status symbols. Jerry is a man defined by ownership; he takes pride in the systems he builds, even when they are imperfect, and views every bug fixed as a small victory in a war against entropy.

Background & daily life

A day in their life

Jerry's day typically begins at 7:30 AM with a double-shot espresso and a quick scan of GitHub notifications before commuting via tram to the city center. By 9:00 AM, he's in his ergonomic chair, diving into Jira tickets for the morning stand-up, where he quietly advocates for adding more time to the current sprint for refactoring. The bulk of his morning is spent writing Playwright scripts, often pausing to debug a flaky assertion that took three hours to fix yesterday. Lunch is a rushed sandwich eaten at his desk while reading a Substack article on AI-assisted coding. Afternoons involve pair programming with the CTO on a new dashboard feature, followed by a frantic hour of updating his test spreadsheet with new scenarios discovered during user testing. He leaves the office around 6:30 PM, usually stopping at a local gym to decompress before heading home to cook dinner and occasionally tinkering with a side project on an old Raspberry Pi.

Lifestyle

Jerry lives in a high-ceilinged, exposed-brick loft in Ancoats, sharing rent with a graphic designer and a musician. His apartment is a minimalist sanctuary dominated by dual monitors and a custom-built mechanical keyboard that sounds like rain. He wakes early, often brewing pour-over coffee before checking emails, preferring a quiet start to the day. On weekends, he disconnects from screens to hike the Peak District or tinker with retro computing hardware. Financially, he is pragmatic; he invests heavily in high-quality gear that lasts but avoids luxury cars or dining out frequently. He maintains a tight-knit circle of university friends who are now scattered across London and Berlin, meeting up quarterly for pub dinners where the conversation inevitably turns to career trajectories and housing markets.

Work life

As the de facto QA lead in a four-person team, Jerry splits his time between building new React components and maintaining the integration test suite. The pressure is constant: if a feature breaks production, it's on him. He currently manages test scenarios in a messy Google Sheet, manually converting them into Playwright scripts when he has the bandwidth, which is rarely enough. His day is fragmented by urgent Slack messages and the need to context-switch between feature development and bug hunting. He feels the weight of being the only one who truly understands the system's edge cases. While he loves the ownership, the lack of dedicated QA resources means he often works late to ensure the next sprint starts without a fire drill.

Relationships

Jerry is the 'go-to' guy for technical troubleshooting among his flatmates, though they know better than to interrupt during deep work sessions. He has a supportive relationship with his parents in Cheshire, who worry about his long hours but respect his independence. His professional network is mostly peer-based, consisting of other engineers he met at conferences or online communities. He values honesty over politeness in relationships and finds himself drawn to people who can challenge his ideas intellectually. He doesn't have a partner yet, viewing dating as a low-priority activity until he stabilizes his career trajectory further.

How they decide

Jerry approaches decisions with a 'measure twice, cut once' philosophy. He rarely makes impulsive purchases, preferring to research thoroughly, read documentation, and look for community consensus before committing. However, when faced with a bottleneck, he will quickly adopt a solution if it demonstrably saves time, provided it doesn't compromise code quality. He is influenced heavily by peer reviews and technical benchmarks rather than marketing hype. If a tool requires a steep learning curve, he will only adopt it if the ROI is clear and immediate.

How they sound

His speech is precise and measured, often using technical analogies to explain everyday concepts. He speaks with a distinct Mancunian accent but moderates it in professional settings to ensure clarity. He tends to avoid hyperbole, preferring phrases like 'it's a bit brittle' rather than 'it's broken.' He rarely uses corporate buzzwords unless quoting leadership, instead opting for direct, functional language. When frustrated, his tone drops an octave, becoming quieter but sharper. He values brevity in communication and often interrupts to clarify ambiguity rather than letting a misunderstanding fester.

Personality traits

  • methodically paranoid about regression bugs
  • efficiently verbose in documentation
  • prone to over-engineering solutions
  • deeply skeptical of 'magic' tools
  • relentlessly curious about tooling
  • protective of team velocity
  • wears his fatigue like a badge of honor
  • prefers direct feedback over sugar-coating
  • meticulously organized digital workspace
  • socially adaptable but mentally reserved

Goals

  • Achieve 90% automated test coverage on critical user flows within six months
  • Reduce manual testing time by half to focus on complex architectural problems
  • Mentor junior developers on best practices for UI testing
  • Transition into a Staff Engineer role with more strategic influence
  • Build a personal open-source tool that solves a specific Playwright pain point
  • Secure a sustainable work-life balance where evenings are screen-free

Problems & frictions

  • The friction of translating abstract requirements from spreadsheets into reliable code
  • Maintaining flaky tests as the product API and UI evolve rapidly
  • Lack of time to refactor legacy test suites due to feature delivery deadlines
  • The cognitive load of remembering every edge case without a structured knowledge base
  • Difficulty justifying the time cost of writing perfect tests to non-technical stakeholders
  • Feeling isolated as the sole guardian of test quality in a tiny team

Values

  • pragmatism
  • speed
  • code quality
  • ownership
  • technical autonomy
  • transparency

Interests

  • React
  • Playwright
  • editor extensions
  • startups
  • mechanical keyboards
  • indie game design

Media habits

  • Weekly deep-dive podcasts on software architecture
  • Hacker News and specific GitHub repositories
  • Twitter/X for niche React ecosystem updates
  • Local Manchester tech meetups
  • Reddit r/webdev and r/programming
  • Substack newsletters from indie hackers

Questions & answers

Jerry Boehm-Johns’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’d rather install a dedicated Playwright Skill pack because my AI coding assistant is decent, but Playwright tests often fail on real-world sites, and I'm drowning in test maintenance. Having structured guides and production-tested skills sounds like it could seriously cut down on the time I spend debugging flaky tests and manually converting spreadsheet scenarios into code, which is the biggest time sink right now.
    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).

    My current AI coding assistant already helps me generate test code, and I'm skeptical of tools that claim to replace human judgment entirely. I manage my test scenarios in a spreadsheet, which is a manual process, but at least I know exactly what's being tested. The idea of training AI agents to write better Playwright tests is interesting, but I'd need to see concrete proof that it solves the 'flaky CI runs' and 'wrong selectors' issues without adding its own layer of complexity or cost. Since I'm the only one handling Playwright coverage, anything new has to be a significant improvement to justify the learning curve and potential integration headaches. I'm not willing to pay for this this month.
    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.