Why pre-screen game user researchers before the studio interview
This role attracts a large number of applicants whose qualification is loving games, which is common and not the skill. The skill is designing a session that answers a specific development question, on a build that crashes, with participants who will tell you the game is great because they are being watched. Separating what a player did from what they said afterwards is most of the discipline. A short screen surfaces whether a candidate has actually done it.
What actually matters when screening Game User Researcher candidates
- 01
Method and rigour
Check how they design playtests: sample sizing for small n, counterbalancing builds, think-aloud versus RITE iterations, survey scales like SUS or PENS, and mixing telemetry with lab sessions.
- 02
Real casework
Probe actual studies run on shipped or in-development titles: genre, build stage (vertical slice, alpha, soft launch), participant recruitment, and which design decisions changed as a result.
- 03
Interpretation and judgement
Test how they separate tutorial comprehension failures from difficulty tuning or motivation drop-off, and how they read funnel drop, session length, and D1 or D7 retention signals.
- 04
Reporting and testimony
Assess how they deliver findings to designers and producers: highlight reels, severity-ranked issue lists, one-page readouts, and holding a position when a creative director pushes back.
Pre-screening questions to ask Game User Researcher candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
Method fits the question
3 questions01What experience do you have designing and running playtests?
Listen forSessions they designed with the development question stated first, and the method chosen to answer it rather than a standard format applied.
Playtest experience that turns out to be participating rather than running, or one format used for every question.
02How do you design surveys and questionnaires for player research?
Listen forAwareness that self-report is unreliable, with survey questions used for things observation cannot reach rather than as the primary method.
Relies on post-session surveys as the main evidence, or asks players to rate features they barely used.
03Have you run studies across several rounds or over an extended period?
Listen forIterative testing across builds with findings tracked between rounds, plus how they handle players becoming familiar with the content.
One-off sessions only, or no awareness that repeat participants stop behaving like new players.
Sessions on real builds
3 questions04What do you do when a build crashes or breaks during a session?
Listen forA practical recovery plan with the session salvaged where possible, and a clear record of what the failure invalidated.
No experience of a build failing mid-session, or data from a broken session reported as if it were clean.
05What experience do you have setting up test hardware and controllers for sessions?
Listen forPractical lab setup across platforms with recording of screen, face and inputs, and awareness of how the setup affects behaviour.
Assumes a lab is provided and configured, or no experience testing on the actual target hardware.
06Do you have any experience with game development or design?
Listen forEnough understanding of production to know what can still change and when, so findings arrive while they are still actionable.
No sense of production timelines, or findings delivered after the window in which they could be acted on.
Behaviour against opinion
3 questions07How do you distinguish what a player does from what they say about a game?
Listen forObservation treated as primary with self-report used carefully, and an example where the two directly contradicted each other.
Reports player opinions as findings, or no awareness that participants soften criticism when observed.
08How do you decide which aspects of a game to focus a study on?
Listen forScope agreed with the team against a development decision, with something explicitly excluded rather than everything examined at once.
Studies that cover the whole game, or focus chosen by the researcher's own interest rather than the team's question.
09Can you describe a time your research identified a specific problem in a game?
Listen forA concrete problem with the evidence behind it, such as completion rates or where players got stuck, rather than a preference.
Findings expressed as opinions about what would be better, with no behavioural evidence attached.
Findings developers used
3 questions10How do you recruit participants who represent the intended audience?
Listen forScreening against the target player profile, with awareness that easily recruited enthusiasts are not typical of the wider audience.
Recruits from friends, colleagues or the studio's own community, with no acknowledgement of the bias that creates.
11How does your familiarity with different genres inform how you design a study?
Listen forGenre conventions used to set fair tasks and distinguish genuine confusion from unfamiliarity with the genre's norms.
Genre knowledge offered as personal preference, or tasks that penalise players unfamiliar with a convention.
12How do you communicate findings so that developers act on them?
Listen forFindings prioritised by severity with clips shown rather than described, and a specific design change that followed.
Reports delivered as long documents late in production, or findings that never changed anything in the build.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Method and rigour
35%5Names specific method choices per question type, defends small-sample limits, and pairs behavioural telemetry with observed session data rather than relying on opinion polls.
Real casework
25%5Cites named titles or projects with study counts, recruitment criteria, and concrete features cut, retuned, or redesigned because of their findings.
Interpretation and judgement
25%5Distinguishes signal from participant noise, states confidence levels honestly, and resists overclaiming from six sessions or a single A/B cohort.
Reporting and testimony
15%5Delivers prioritised, actionable findings tied to design intent, uses clips as evidence, and negotiates scope with designers without softening uncomfortable results.
Loving games is common and is not the skill; running a fair session on a build that crashes is. A one-way video screen tells the two apart.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for a game user researcher take?
Fifteen minutes across eight to ten questions, answered async. Enough to test method thinking, establish whether they have run sessions on unfinished builds, and hear how findings reached the development team.
How much should games knowledge count?
Enough to design a fair test and speak credibly to developers, and no more. Genre familiarity helps with recruitment and task design. Enthusiasm for games is not a qualification, and this posting attracts a lot of it.
Evaluating answers
What is the strongest signal when screening a game user researcher?
Separating observed behaviour from stated opinion. Players routinely say a section was fine while the recording shows them lost for four minutes. Researchers who lead with what players did, and treat what they said as secondary, understand the job.
How do I test whether their findings landed?
Ask what changed in the game. Research that produced a deck and no build change is common, particularly late in production. A researcher who can name a specific design change and how they got it accepted has done the harder half of the work.
Go deeper on this role
Sanat has been hiring since 2012 and watching the recruitment industry change up close ever since, and turned that screening process into Hirevire's video screening platform. LinkedIn
