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

Jimmy Romaguera

Jimmy Romaguera

UK Junior QA Engineer

Full-depth AI personas

Why this persona fits the audience

Working remotely from London for a fintech startup. Daily workflow involves reproducing bugs on macOS and submitting reports to developers. Currently uses the built-in OS screenshot tool and manual spreadsheets to track issues, often struggling with consistent annotation standards across the team.

  • Age: 26
  • Location: London, UK
  • Occupation: Junior QA Engineer
  • Income: £32,000 - £42,000
  • Education: Bachelor's Degree
  • Company size: Startup (approx. 40 employees)
  • Years in role: 2
“It's frustrating when you know there's a better way to do something, but you're stuck with the old routine.”

Born and raised in a suburb of Manchester, Jimmy showed an early aptitude for logical thinking and problem-solving, often taking apart electronics to see how they worked. He pursued a Bachelor's degree in Computer Science at a reputable university in the North of England, where he discovered a keen interest in software quality assurance. The meticulous nature of testing appealed to his detail-oriented personality. Upon graduating, he landed his first role as a Junior QA Engineer at a small but ambitious fintech startup, attracted by the prospect of working remotely and the fast-paced environment. He moved to London shortly after, drawn by the city's cultural vibrancy and career opportunities, settling into a flatshare to manage his living costs. Jimmy is diligent in his role, driven by a desire for accuracy and efficiency, which sometimes clashes with the limitations of his current tooling. He recently spent a significant chunk of his discretionary income on a high-resolution monitor, aiming to improve his ability to spot subtle visual bugs. He’s always looking for ways to optimize his workflow, whether through keyboard shortcuts or exploring new software, seeing it as a continuous learning process essential for career growth. He views his current role as a stepping stone, eager to deepen his expertise in automated testing and contribute more significantly to the development lifecycle. He’s conscious of his financial future, saving diligently from his salary, but also allows himself small indulgences in tech gadgets and books that align with his professional development goals.

Background & daily life

A day in their life

Jimmy's typical weekday begins around 8:30 AM with a strong cup of coffee and a quick scan of overnight bug reports and team Slack channels from his London flat. By 9:00 AM, he's logged into the company's VPN, ready to tackle his assigned tasks. This usually involves picking up new bug tickets, attempting to reproduce them on his macOS machine by following precise steps, and documenting each finding. He'll spend a good hour or two wrestling with a particularly tricky bug, capturing screenshots, annotating them with basic arrows and text using the built-in tool, and then meticulously filling out the shared spreadsheet. Lunch is a quick affair, often a sandwich at his desk while catching up on a tech blog. The afternoon might involve a stand-up meeting, collaborating with a developer on a bug fix, or testing a new feature. He usually wraps up around 5:30 PM, feeling a sense of accomplishment but also aware of the backlog he’s built.

Lifestyle

Jimmy lives in a bustling but affordable area of East London, sharing a three-bedroom flat with two friends who work in marketing and graphic design. His evenings are often a mix of unwinding with a video game or diving into a coding tutorial, aiming to upskill. He's conscious of his budget, favouring cooking at home over eating out frequently, and enjoys exploring London's free museums and parks on weekends. While not a big spender, he occasionally treats himself to new tech gadgets or books related to his interests.

Work life

As a Junior QA Engineer at a rapidly growing fintech startup, Jimmy's days are consumed by the intricate dance of bug hunting. He spends a significant portion of his time meticulously reproducing issues reported by users or spotted internally, often on his personal MacBook Pro, as the company is Mac-first. His current workflow involves taking screenshots with the built-in macOS tool and then painstakingly logging them into a shared Google Sheet, alongside detailed reproduction steps and expected outcomes. This manual process feels increasingly cumbersome, especially when trying to convey complex UI glitches or user flow problems to the development team, who are spread across different time zones.

Relationships

Jimmy maintains strong ties with his university friends, often meeting up for pub nights or gaming sessions. His family lives a few hours away, and he calls them weekly. Within the company, he has a good working relationship with his direct manager and the developers he interacts with, who appreciate his thoroughness, though he sometimes feels hesitant to interrupt them with 'minor' issues.

How they decide

Jimmy tends to research thoroughly before making any significant decision, whether it's a personal purchase or a work-related tool. He values consensus and seeks input from colleagues he trusts, cross-referencing information from multiple sources before committing. He is not impulsive and prefers a structured approach to evaluation.

How they sound

Speaks with a clear, articulate London accent, generally polite and measured. Uses common British colloquialisms occasionally, like 'brilliant' or 'a bit much'. Avoids overly technical jargon when speaking to non-technical people, but is precise and uses standard QA terminology with developers. His tone is earnest and slightly formal in professional settings.

Personality traits

  • Meticulous
  • Diligent
  • Cooperative
  • Curious
  • Methodical
  • Detail-oriented
  • Slightly Reserved
  • Adaptable

Goals

  • Become a Senior QA Engineer within the next three years.
  • Contribute to open-source testing frameworks.
  • Achieve financial independence to travel more.
  • Develop a personal project, perhaps a small mobile app.
  • Master a new programming language like Python for automation.

Problems & frictions

  • The current bug tracking system is inefficient and prone to human error.
  • Difficulty in standardising annotation quality across the QA team.
  • Balancing learning new testing techniques with daily task demands.
  • Feeling siloed by remote work and missing informal team problem-solving.
  • The constant pressure to release new features quickly can lead to rushed testing cycles.

Values

  • Accuracy
  • Team Collaboration
  • Continuous Learning
  • Efficiency
  • Problem Solving

Interests

  • Software Testing
  • Agile Methodologies
  • Productivity Hacks
  • Open Source Software
  • Indie Game Development

Media habits

  • Follows tech blogs like Hacker News and The Verge
  • Listens to podcasts on software development and productivity during commutes
  • Uses YouTube for tutorials and tech reviews
  • Active on LinkedIn for professional networking
  • Occasional Reddit browsing in r/qualityassurance and r/learnprogramming

Questions & answers

Jimmy Romaguera’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying ScreenSnap Pro (https://www.screensnap.pro/) 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 stopping me this month is our current workflow. I meticulously document bugs using the built-in macOS tool and then manually log everything into a shared spreadsheet. It’s a bit clunky, especially getting the annotations consistent across the team. While ScreenSnap Pro looks brilliant for that, I'd need to see how it integrates with our existing process and maybe get a quick consensus from my manager, as I'm also trying to save up for a new keyboard. I'm not really keen on subscriptions; I'd prefer a one-off purchase, but if I had to, I'd consider paying around $5 per 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.