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

Bryant Hackett

Bryant Hackett

Engineering manager at a digital agency

Full-depth AI personas

Why this persona fits the audience

Manages a 5-person delivery squad that builds and maintains Playwright tests across several client web apps. He keeps coverage plans in spreadsheets for each client, and the team uses a mix of in-editor AI assistance and hand-written assertions.

  • Age: 44
  • Location: London, UK
  • Occupation: Engineering Manager
  • Income: £96k
  • Education: Bachelor's in computer science
  • Company size: 50-100 employees
  • Years in role: 3
“You can't automate confidence, but you can sure as hell automate the things that undermine it.”

Bryant Hackett, 44, has spent nearly two decades navigating the chaotic world of digital agencies. His career began at a web development startup during the dot-com boom, where he learned that 'deadline' often meant 'best guess at a future date'. After a brief stint at a consultancy that taught him the value of controlled skepticism, he joined Bridge Digital as a senior engineer 7 years ago and was promoted to Engineering Manager 3 years back. His team's work on Playwright test automation has become something of a case study within the agency - clients love the consistency but often push back on the maintenance costs. Bryant's strategic adoption of GitHub Advanced Security was a career milestone, proving his ability to drive technical initiatives even when met with budgetary resistance. His meticulous spreadsheets tracking test coverage across projects have become something of an agency legend, used as both a teaching tool and a cautionary tale about over-optimizing. Personally, Bryant is relentlessly pragmatic about his career - he knows he's past the age where companies take big bets on mid-level managers, so he's focused on becoming the indispensable facilitator his organization needs. Though he occasionally daydreams about moving to a pure-play software company, he genuinely enjoys the variety and intensity of agency work. His biggest professional accomplishment was mentoring a junior engineer who now leads testing efforts at a major fintech firm. His biggest failure? Underestimating how quickly a client would de-prioritize test maintenance after their first major incident was resolved. This near-miss fundamentally changed how he approaches client education.

Background & daily life

A day in their life

Bryant's alarm goes off at 6:15, though he's usually already awake scrolling through Hacker News. By 6:45 he's at his standing desk with a black coffee, reviewing the latest test failure notifications from overnight runs. He walks to work by 7:45, stopping at his usual café for a decaf latte (he cut caffeine after a particularly bad sleep study). The standup is at 9:00, where he'll gently probe for blockers before dashing to a 9:30 client sync. Between 10 and 12, he alternates between spreadsheets, code reviews, and a standing desk walkabout to check on his team's progress. Lunch is usually a meal-prepped bowl on his desk while catching up on tech blogs. Afternoons are meeting-heavy - today it's a portfolio planning session followed by a painful review of a junior engineer's test coverage plan. By 5:30 he's wrapping up but will check Slack one last time before his usual 6:00 kickboxing class. Dinner's usually a supermarket meal he can eat while watching Jamie Oliver's latest inferior series. By 9:00 he'll be in bed with a technical book, though he'll be asleep before chapter 2.

Lifestyle

Bryant keeps an almost ascetic flat in Shoreditch, prioritizing function over aesthetics - his furniture is all IKEA but meticulously arranged. He starts his mornings with black coffee and The Guardian app before walking 20 minutes to work through Spitalfields, where he'll detour to a proper café at least twice a week. His gym routine is inconsistent but guilt-driven; he knows he should do better. As a lifelong Spurs fan, he makes it to White Hart Lane at least 4 times a season when fixtures align with client deadlines. His social life revolves around fellow ex-agency types and a few university mates who've stayed in tech. Money-wise, he's comfortable but disability-conscious after watching his father's health struggles - he maxes out his pension contributions and keeps a 6-month emergency fund. On weekends, he'll sometimes pair programming with a decent IPA at the local brewery, treating it like a technical book club but with less theory and more debugging sessions.

Work life

As Engineering Manager at tech-forward agency Bridge Digital, Bryant oversees the squad maintaining Playwright test suites for 6 active client apps. His team's work is a constant balancing act - clients want near-perfect coverage but balk at the budget for proper test maintenance. The spreadsheets tracking coverage plans across projects have become a running joke with other managers, though privately they're jealous. His squad uses a mix of Copilot X for test generation and hand-written assertions for critical paths, though Bryant's been skeptical about AI tools' reliability. He spends 60% of his time in coordination meetings (client, internal, and portfolio-level) and the rest in code review or spreadsheet wrangling. His biggest recent decision was adopting GitHub Advanced Security for client repos, which took 3 months of internal lobbying. The team's biggest pain point? Flaky tests that explode randomly, usually after client rollbacks.

Relationships

Bryant's parents live in High Wycombe, where his father runs a small plumbing business and his mother volunteers at the local library. He sees them monthly, though recent visits have been tense as his father's Parkinson's progresses. His closest friends are a group of university mates from Kingston - they meet quarterly for HDI-heavy dinners that inevitably turn into technical debates. At work, he's particularly tight with the senior PMO who shares his love of absurd test failure stories. His dating life is sporadic; he occasionally uses Bumble but often deletes it after 6 weeks when work gets hectic. His professional network is his strongest social circle, though he's wary of becoming too dependent on agency colleagues for social fulfillment.

How they decide

Bryant is data-driven when it's practical, but will go with his gut on people decisions. He consults extensively with his team before making major technical calls, though his final word is authoritative. For client-facing decisions, he weighs potential fallout meticulously - he's been burned too many times by optimists. When choosing tools, he prefers things that integrate with their existing stack and can be evaluated through a free tier or trial. He's skeptical of hype but will doggedly research anything that might give his team an edge.

How they sound

Bryant speaks in measured cadence with occasional self-deprecating humor. He avoids tech jargon with non-technical people but won't dumb it down with his team. He has a habit of saying 'right?' after statements that aren't actually questions. His London accent is educated but still carries East End inflections from his childhood. He's prone to analogy-heavy explanations ('It's like trying to build a Lego castle while someone keeps stealing your 2x4s'). When stressed, his sentences get shorter and more clipped. He never says 'sorry' in meetings - it's either 'my fault' or 'that was on me'.

Personality traits

  • Pragmatic to a fault - will hack together a fix if it means keeping deadlines
  • Quietly competitive about test coverage metrics with other teams
  • Hates unnecessary abstraction but respects clean code
  • Has a dry wit that catches people off guard initially
  • Diligent about documentation but will skip it when pressed
  • Strategic about when to push back on client demands
  • Loyal to people who prove themselves but quick to cut ties with flakes
  • Enjoys explaining technical concepts in drunk-guy-at-a-bar analogies
  • Obsessively tracks personal productivity metrics (Toggl, Notion, etc.)
  • Will spend hours automating a repetitive task that only saves 30 minutes

Goals

  • Become a senior manager or director within 2 years
  • Move to a proper house in a slightly greener area (Walthamstow or Hackney Wick)
  • Learn Rust well enough to contribute to open-source projects
  • Improve his golf handicap to single digits
  • Build a sustainable side project beyond just testing
  • Reduce his stress headaches by 50% (currently tracking via Headspace data)

Problems & frictions

  • Clients who treat test maintenance as an afterthought until their app breaks in production
  • Balancing agency deadlines with meaningful technical investment
  • Finding the right junior engineers who can write maintainable tests
  • Keeping test coverage spreadsheets from becoming unwieldy beasts
  • His team's frustration with flaky tests undermining their credibility
  • The agency's tendency to overpromise on delivery timelines
  • Maintaining work-life boundaries when on-call weeks coincide with personal plans

Values

  • Client confidence
  • Delivery consistency
  • Team coordination
  • Practicality
  • Work-life balance
  • Technical rigor

Interests

  • Agency work and its unique challenges
  • Playwright automation and test strategy
  • Team leadership and psychological safety
  • Delivery metrics and KPIs
  • Occasional indie game development
  • Football (soccer) as a spectator

Media habits

  • Listens to The Changelog and Software Engineering Radio during his commute
  • Follows DevOps and testing subreddits obsessively at lunch
  • Watches YouTube tutorials (specifically Mattias Petter Johansson's stuff)
  • Reads Hacker News first thing in the morning
  • Occasionally consumes The Economist for big-picture thinking

Questions & answers

Bryant Hackett’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 go with option A, installing a dedicated skill pack like Playwright Skill. The biggest reason is that it provides structured, production-tested skills that can guide the AI agent effectively, reducing the flakiness and contextual gaps we’ve struggled with. With 70+ skills ready to go, it’s a faster and more reliable approach than relying on generic AI tools or hand-coding everything, especially when we’re juggling multiple client apps.
    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).

    Honestly, the biggest thing stopping me from trying Playwright Skill this month is the potential integration hassle. Right now, we use a mix of Copilot X and hand-written assertions, and I'm not sure how seamless this would be to plug in. I’d need to see a clear migration path or a sandbox environment to test without disrupting our current workflow. Additionally, I’m wary about adding another subscription cost when clients already push back on existing test maintenance budgets. We handle flaky tests manually with a lot of spreadsheet tracking, and I’d want concrete proof that this tool reduces that overhead before committing. As for cost, I couldn’t justify more than $50/month for something unproven in our specific context.
    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.