Game Developer
Interview Questions.
15 practice questions across 13 skills — each with what the interviewer is really listening for. Prepare with intent, not guesswork.
Free · No signup · Grouped by skill
How to use this page
Don't memorise answers. For each question, read what the interviewer is looking for, then practise answering out loud in your own words with a real example. The notes describe strong answers and common red flags — they are for your prep, not a script.
C++
1 questionWhy is C++ still dominant in game engines, and what memory concerns matter for games?
AdvancedWhat the interviewer is looking for: Strong answers cite performance and control over memory, cache-friendliness, and avoiding per-frame allocations. Not understanding why allocations in the game loop hurt is a red flag.
Unity
1 questionHow does Unity's component/GameObject model shape how you structure a game?
IntermediateWhat the interviewer is looking for: Look for composition over deep inheritance, using components and prefabs, and separating data from behaviour. Giant monolithic scripts on one object are a red flag.
Game Physics
1 questionWhy should gameplay logic that affects physics run in FixedUpdate rather than Update?
AdvancedWhat the interviewer is looking for: Strong candidates explain fixed timestep for deterministic, frame-rate-independent physics, and applying forces there. Doing physics in Update tied to frame rate is a red flag.
C#
1 questionIn C#, how do you avoid garbage collection spikes that cause frame hitches?
AdvancedWhat the interviewer is looking for: Look for minimising per-frame allocations, pooling objects, and avoiding boxing and LINQ in hot paths. Ignoring GC pressure in the game loop is a red flag.
3D Math
1 questionHow do you use vectors and dot/cross products for something like aiming or field-of-view checks?
AdvancedWhat the interviewer is looking for: Strong answers apply dot product for angles/facing and cross product for perpendiculars, with normalisation. Shaky vector math fundamentals are a red flag for gameplay work.
Performance Optimization
1 questionThe game runs at 30fps when it should hit 60. How do you find the bottleneck?
AdvancedWhat the interviewer is looking for: Look for profiling to find whether it is CPU or GPU bound, checking draw calls, physics, and GC, before optimising. Guessing and optimising randomly is a red flag.
Gameplay Programming
1 questionHow do you implement a game mechanic so it is fun and easy to iterate on?
IntermediateWhat the interviewer is looking for: Strong candidates expose tunable parameters, prototype quickly, and playtest, valuing feel over premature optimisation. Hardcoding everything and shipping without playtesting are red flags.
Unreal Engine
1 questionHow do you decide between Unity and Unreal for a project?
IntermediateWhat the interviewer is looking for: Look for weighing team skills, project type, visuals, and tooling rather than dogma. Insisting one engine is always best is a red flag.
Git
1 questionHow do you use Git effectively on a game project with large binary assets?
IntermediateWhat the interviewer is looking for: Strong answers use LFS for binaries, sensible branching, and lock large assets that cannot merge. Committing huge binaries directly and blowing up the repo is a red flag.
Iteration Mindset
1 questionGame development is highly iterative. How do you approach prototyping a new idea?
IntermediateWhat the interviewer is looking for: Look for building rough, playtesting fast, and being willing to throw away work that is not fun. Over-engineering an unproven idea is a red flag.
Receiving Feedback
1 questionA mechanic you love is not fun in playtests. How do you respond?
BasicWhat the interviewer is looking for: Strong candidates trust playtest evidence over ego and iterate or cut. Insisting players are wrong is a red flag.
Collaboration
1 questionHow do you collaborate with artists and designers as a programmer?
BasicWhat the interviewer is looking for: Look for building tools and tunable systems that empower designers and artists, and clear communication. Building rigid systems only you can change is a red flag.
Problem Solving
1 questionHow do you solve a tricky gameplay bug that only reproduces intermittently?
AdvancedWhat the interviewer is looking for: Look for reproducing reliably, adding logging, and isolating timing or state issues methodically. Random changes hoping it goes away are a red flag.
Behavioural & role-general
2 questionsTell me about a game or feature you built. What was the hardest technical problem?
BasicWhat the interviewer is looking for: Strong answers show a real challenge, the solution, and lessons, with clear ownership. Vague descriptions with no depth are a red flag.
How do you keep learning in a field with constantly evolving engines and hardware?
BasicWhat the interviewer is looking for: Look for building side projects, following the community, and hands-on experimentation. Vague 'I keep up' with no specifics is a red flag.