Games User Researcher

This archetype's distinct contribution is finding out, with real players and real evidence, whether a game is doing what its designers believe it is doing — something no one on a development team can reliably judge about their own work after hundreds of hours inside it. The primary pull is Discovery: the defining act is systematic, structured observation — watching someone play a build cold, without the accumulated assumptions a designer can no longer set aside, and finding out where the tutorial confuses them, where a boss fight reads as merely cheap rather than hard, or where a mechanic the whole level was built around goes completely unnoticed. This is different from Quality Assurance elsewhere in the industry, which exists to find things that are broken; a games user researcher exists to find things that work exactly as built and are still not fun, which is a harder and less visible problem to catch.

The daily texture is running structured sessions — think-aloud playtests, usability studies, surveys, sometimes biometric or eye-tracking data on larger productions — then turning what happened in the room into something a design team can act on. That second half is where Revelation and Connection come in: raw observations ("three of six players missed the exit") have to become a diagnosed cause ("the exit reads as scenery because it shares the wall's colour palette"), and then be delivered to a team that built the thing being critiqued, in a way that lands as useful rather than as an attack on their work.

The role is genuinely close in method to `uxd`'s UX Researcher elsewhere in this corpus — both run structured studies of real users encountering a real product cold — but the domain changes what "success" even means. A UX Researcher is usually optimising for a user completing a task efficiently; a games user researcher is optimising for an experience that is supposed to be hard, tense, or frustrating on purpose, and has to distinguish deliberately-designed friction (a boss fight that should feel unfair the first time) from unintended, unwanted friction (a menu nobody can find) — a judgement call that a general product-research background does not automatically prepare someone for.

Most players, and most people who want to work in games, have no idea this discipline exists as its own job separate from design, art, and QA — the assumption is that "is it fun" gets decided by designers alone, on instinct. In practice it remains a younger and smaller discipline than QA: dedicated games user research teams are standard at larger publishers and platform holders but far less common at small and mid-size studios, which often rely on designer instinct and vocal community feedback instead. UK pay averages around £54,300, with a typical range of roughly £39,600-£74,400 and senior specialists reaching £98,700 and above [from salary and job-posting data, UK games user research salary data — Glassdoor, 2026]. Studios draw from genuinely mixed academic backgrounds — psychology, human-computer interaction, and interaction or product design all lead to the role, with no single required degree or registration [UK games user research job listings — Player Research / PlayStation Studios, 2026].

No fixed credential. Common entry routes are a degree in psychology, human-computer interaction, or a design discipline, followed by a junior role at a specialist research studio (Player Research, based in Brighton, is one of the field's best-known independent agencies) or an in-house team at a larger publisher or platform holder. As with the rest of this field, self-directed proof of the skill helps — running structured playtests on a personal or student game project, and writing up findings the way a professional study would, is a credible way to demonstrate the discipline before a first paid role.