5 exercises — choose the best-structured answer to common game development interview questions. Focus on technical vocabulary, architectural concepts, and performance thinking.
Structure for game development concept questions
Define: state what the concept is in one precise sentence
Mechanism: explain how it works technically
Why it matters: connect to performance, correctness, or player experience
Concrete example: numbers, engine-specific API, or scenario
0 / 5 completed
1 / 5
The interviewer asks: "Can you explain what the game loop is?" Which answer demonstrates the clearest technical understanding?
Option B is the strongest: it defines the game loop precisely, names the three operations in order with technical labels (process input, update game state, render), explains the variable-framerate concern, and mentions the important engineering pattern of decoupling update from render. Option C is technically reasonable and mentions 60fps — a useful concrete detail — but doesn't mention decoupled update/render or explain why this matters. Option A is correct but very brief. Option D is vague and focuses on what happens if it breaks rather than how it works. Structure: define → list operations in order → add the non-obvious engineering consideration.
2 / 5
The interviewer asks: "What is a component-based architecture and why does Unity use it?" Choose the most professional answer.
Option B is the best: it defines the pattern formally (composed of reusable, single-purpose behaviour components), contrasts it with the alternative (rather than inheriting from deep class hierarchies), explains the communication model (via messages or direct references), and names the design principle (composition over inheritance) and the problem it solves (fragile base class). Option A is accurate and includes a concrete example — a real strength — but doesn't explain the architectural principle. Option C also gives a concrete example, which is excellent for interviews. Option D incorrectly equates Unity's classic architecture with ECS — a different, newer pattern. Tip: name the design principle and the alternative it replaces.
3 / 5
The interviewer asks: "What is frustum culling and why is it important?" Which answer is most accurate and complete?
Option A is the strongest: precise definition (pyramidal volume defining what the camera can see), explains what is saved (draw calls and GPU workload), and gives a concrete scenario to make the benefit tangible (open-world scene while in a small room). Option D is also excellent — mentioning bounding box intersection, the six frustum planes, and the CPU-before-GPU order shows implementation-level knowledge. Option C is valuable because it contextualises frustum culling within the broader culling family, but doesn't fully explain frustum culling itself. Option B is correct but lacks technical depth. For systems-level questions, describe the mechanism and give a concrete cost/benefit example.
4 / 5
The interviewer asks: "How do you approach performance optimisation in a game?" Choose the most structured and professional answer.
Option A is the best answer: it starts with the correct methodology (profiling first, not guessing), names the two categories of bottleneck (CPU-bound vs GPU-bound), gives specific examples of each type of problem, and lists five concrete optimisation techniques. "Profile first" is a professional principle that candidates who have actually shipped games know — it signals experience. Option C is also strong and more detailed on the CPU/GPU split. Option B lists techniques without the profiling methodology — acceptable but less structured. Option D describes a naive workflow ("when something feels slow") and makes premature changes (reducing polygons before profiling). Key rule: always lead with profiling, then fix the measured bottleneck.
5 / 5
The interviewer asks: "What is a delta time and why is it used?" Choose the clearest explanation.
Option B is the strongest: it provides a precise definition (elapsed time between current and previous frame, in seconds), explains the application (frame-rate independent), gives a concrete numerical example (100 units/second at 30fps vs 120fps), and states the consequence of not using it (runs faster on higher-performance hardware). Option A has an excellent concrete example (5 units/frame → speed doubles) but doesn't give the full definition or the general formula. Option C mentions the Unity API (Time.deltaTime) — a useful specific detail — but doesn't explain the numerical relationship. Option D is accurate but informal and lacks a concrete example. Tip: for "what is X and why is it used" questions, give the definition, the formula, and a numeric example.