Why this persona fits the audience
Works as a QA analyst in Bristol and spends weekends building tiny 2D platformer prototypes with a friend, using free tools, a color spreadsheet, and hand-tuned tile and sprite sheets. He treats AI art tools as experimental references rather than part of his usual workflow.
- Age: 27
- Location: Bristol, UK
- Occupation: QA analyst
- Income: GBP 34k salary
- Education: BSc in computer games technology
- Company size: Mid-sized (100-500 employees)
- Years in role: 4
“There's a certain satisfaction in wrestling a feature into submission with nothing but logic and a bit of code – it feels earned.”
Born and raised in a smaller town outside Bristol, Leon developed an early fascination with computers and games, spending countless hours dissecting how they worked. His university degree in computer games technology provided a solid theoretical foundation, but it was his own drive for practical application that truly shaped his skills. He landed his current QA analyst role four years ago, drawn by the stability and the opportunity to work within the games industry, even if not in a direct development capacity. Leon views his salary as a means to an end: covering living expenses, enabling his hobbies, and providing a buffer, rather than a primary measure of success. He's deeply invested in the 'maker' culture, finding immense satisfaction in creating functional systems from scratch. His approach to tools is pragmatic; he’ll leverage anything that works, but he’s wary of solutions that promise magic without tangible understanding. Recently, he and his friend Alex have been experimenting with procedural generation techniques for their prototype, a decision driven by a desire to push their technical boundaries and reduce manual asset creation time, though Leon remains committed to hand-crafted pixel art for core elements. He meticulously budgets his time, treating his game jam projects as vital outlets for his creativity and technical curiosity, often sacrificing some leisure activities to make progress. He views money as a resource to be managed efficiently, ensuring it serves his goals without becoming an end in itself. This mindset extends to his tools and software, where he prioritizes free or low-cost options that offer robust functionality and learning potential, reflecting his value for self-reliance and minimal overhead.
Background & daily life
A day in their life
Leon's weekday begins around 7:00 AM with a quick breakfast and checking the news on his phone. He cycles for 30 minutes to his office, arriving by 8:30 AM. The workday is a cycle of testing builds, logging bugs in Jira, attending brief stand-up meetings, and collaborating with developers on specific issues. Lunch is usually a packed sandwich eaten at his desk while browsing a technical forum. After finishing his shift around 5:00 PM, he cycles home, perhaps stopping at the supermarket. Evenings are split between unwinding with a short gaming session, preparing dinner, and then dedicating 2-3 hours to his personal game projects, often focusing on refining mechanics or troubleshooting code with Alex via Discord. He aims to be in bed by 11:00 PM.
Lifestyle
Leon lives in a rented two-bedroom flat in a slightly more affordable area of Bristol, sharing with a flatmate to keep costs down. His evenings and weekends are a careful balance between mandatory relaxation and dedicated hobby time. He cycles to work daily, rain or shine, to save money and get some exercise. Meals are often simple, home-cooked affairs, with a focus on efficiency. Socially, he's not one for big nights out, preferring smaller gatherings with close friends or focused evenings spent on his projects. He meticulously tracks his spending to ensure he can afford his modest lifestyle and still put a little aside.
Work life
Leon's days are consumed by the meticulous, often repetitive, process of quality assurance. He navigates bug tracking software, executes test plans, and meticulously documents every anomaly he finds in the studio's latest AAA title. The pressure is on to catch critical issues before release, often leading to long hours during crunch periods, though he's managed to largely avoid those in his current role. He collaborates closely with a small team of testers and developers, engaging in detailed technical discussions about reproducible steps and edge cases. His desk is a picture of organised chaos, with multiple monitors displaying code, bug reports, and performance metrics.
Relationships
Leon is closest to his childhood friend, Alex, with whom he develops games. They've been collaborating on and off for years, their shared passion for game creation forming the bedrock of their friendship. He has a good rapport with his immediate colleagues at work, sharing a pragmatic, problem-solving dynamic. His extended family lives scattered across the country, and contact is usually limited to calls and occasional visits.
How they decide
Leon is a highly analytical and research-driven decision-maker, especially concerning tools or anything that impacts his workflow or budget. He'll meticulously compare options, read documentation, and often try out free versions or experiments before committing to anything. Peer recommendations from trusted sources carry weight, but he ultimately trusts his own testing and understanding of his specific needs.
How they sound
Speaks in a clear, measured tone with a slight West Country lilt that emerges when he's relaxed or excited. He tends to use precise language, especially when discussing technical topics. He avoids hyperbole and is quite direct, but not blunt. His slang is minimal and usually limited to common gaming or tech terms.
Personality traits
- Methodical
- Resourceful
- Detail-oriented
- Patient
- Pragmatic
- Analytically minded
- Quietly ambitious
- Skeptical of hype
- Prefers tangible progress
Goals
- To complete and release a small, polished 2D platformer with his friend.
- To improve his understanding of shader programming.
- To build a robust personal portfolio of game prototypes.
- To eventually transition into a game design or technical lead role.
- To maintain a stable work-life balance.
Problems & frictions
- Limited free time due to work demands and personal projects.
- Finding genuinely innovative game mechanics that haven't been done to death.
- The steep learning curve for advanced game engine features.
- Balancing the desire for creative freedom with the need for efficient prototyping.
- The sheer volume of unfinished personal projects.
Values
- curiosity
- self-reliance
- low overhead
- craftsmanship
- efficiency
Interests
- game jams
- free tools
- platformers
- retro pixel art
- indie game development
- algorithm efficiency
Media habits
- Watches indie game dev streams on Twitch
- Listens to game design podcasts during commutes
- Follows niche game development blogs
- Scours Reddit for useful free software and tutorials
- Reads technical documentation extensively