The scenario
Picture an early-stage search with no target studio picked yet. The AI interviewer opens with what almost every studio asks before anything role-specific: why games development over another engineering path, how you handle a stretch of unplanned overtime near a release, and a behavioral question about disagreeing with a teammate over a technical direction.
None of it depends on a specific engine, codebase, or shipped title, which is exactly why it works before a target studio exists.
What gets covered
Expect background and motivation questions about why games specifically, a work-style question about handling deadline pressure or crunch, and at least one behavioral scenario about a disagreement with a teammate or a lead.
Team-fit questions round it out too, how you'd describe your ideal team size and communication style, since that varies enormously between a ten-person indie studio and a two-hundred-person AAA team.
A question about how you keep learning outside of work, a hobby project, a game jam, or a new engine you picked up on your own, is common as well, since the field moves fast enough that ongoing curiosity gets tested directly.
The session doesn't touch a specific coding exercise or a portfolio walkthrough, since those depend on the technical or resume-based practice types instead, and it won't reference a specific engine or shipped title since neither exists yet without a document supplied.
Scoring
How scoring applies here
All five dimensions get scored, but the candidate-questions penalty is the one worth watching in a general session for this role. Interviewers at most studios expect a closing question about the team's crunch culture or their current project's stage, and a candidate who never asks anything back reads as not having thought seriously about what the job actually involves day to day.
Ending the session without asking something costs points under the same penalty system that applies across every Intervieux interview.
Communication and Behavioral both carry real weight here too, since a deadline-pressure answer that stays vague scores lower than one that describes a specific decision made under time constraint, and calibration floors and caps keep an upbeat tone from covering for an answer that never actually names a decision.
Frequently asked questions
Do I need a target studio picked before running this session?
No. The general interview type runs with no job posting or resume required, which makes it the right session before a specific studio has come up.
Will this include a coding exercise?
No. Coding and debugging exercises are covered by the technical practice type, which for this role can involve real code execution.
What should I ask the interviewer at the end?
Something that shows you're thinking about the actual working conditions, like the team's crunch history or what stage the current project is at, since ending without a question costs points.
How is this different from practicing against a specific job description?
This session covers ground common to almost any studio, while a job-description session builds questions from one specific posting's requirements.
Related pages
Start a general game developer interview
Practice the standard opening round, motivation, deadline pressure, and team fit, before you've narrowed in on a specific studio to target.