From the game development course.

Files

  1. The Game Dev Round — the dot product and what it’s for, fixed timestep, diagnosing 30 fps, pooling, collision phases, lag compensation, ECS, and the portfolio conversation

The scope note — read this first

INTERVIEW.md states a principle this bank sits awkwardly against: “an interview bank for a subject you haven’t practised would be memorisation, not preparation.”

That principle still holds, and this bank exists anyway — added on request, and honestly labelled. The material here is derived from the course, not from having sat these interviews. Treat it as a map of what the round asks, not as preparation you can substitute for reps.

What actually prepares you for this round is a finished game. Games hiring weights the portfolio more heavily than most software hiring — a shipped jam entry with twenty ratings outperforms a perfect answer to Q1 → getting started.

What this round is testing

Three things, and the weighting surprises people:

  1. Concrete maths — vectors and transforms, on a whiteboard, without a library. Cheap to prepare, and candidates routinely fumble it
  2. Performance reasoning under a hard budget — “is this CPU- or GPU-bound, and how would you find out?” is the shape of most technical follow-ups
  3. Evidence you finish things — the largest single factor, and the one you cannot revise for

Specialisation matters more than in general software. Gameplay, engine, graphics, tools, AI and network programming are genuinely different roles with different rounds — this bank covers the shared core → kinds of software engineering.

↑ Back to Game Development