Engineering IC interview prep.

A senior engineering IC at a games studio is judged on real-time systems depth (engine loop, memory, threading, frame budget), domain craft (graphics / gameplay / network / AI / tools depending on seat), and shipping discipline (multi-platform certification, performance debugging, art + design +...

What interviewers look for

  • Can the candidate think in frame budget - 16.6ms at 60fps / 8.3ms at 120fps - and allocate it across sim, render, physics, animation, audio, network - not 'add a thread'?
  • Do they pick data layout + memory pattern to cache locality (SoA, ECS, contiguous allocators) and name the tradeoff vs OOP, not 'use ECS because Unity does'?
  • Can they profile before optimising - flame graph, GPU profiler, frame capture - and locate the bottleneck (CPU bound / GPU bound / draw-call bound / fill-rate bound) - not 'I think it's slow'?
  • Do they distinguish determinism (same inputs -> same state on every machine) from synchronisation (state shipped over wire) - and pick netcode model to the genre (lockstep RTS, rollback fighter, client-server FPS)?
  • Can they partner with art + design + production - explain a tradeoff to a non-engineer (poly count vs frame rate; physics tick vs determinism) - not retreat into 'engineering knows best'?
  • Are they cert + multi-platform aware - the slowest target dictates the budget, certification is a hard wall, not a polish phase?

Behavioural questions to expect

  1. Walk me through your CV.

    What it tests: Story coherence + genuine fit for a games engineering seat. Teams want evidence of shipped title work (or strong demoscene / engine side-project), real-time / perf orientation, and craft progression (feature -> system -> subsystem ownership) - not pure CS coursework or generic SWE.

  2. Tell me about your most impactful technical project.

    What it tests: Depth + ownership + ability to articulate the technical tradeoff. Tests whether the candidate frames problem -> approach (alternatives + tradeoffs) -> result (quantified) -> lesson, not 'I worked on the renderer'.

  3. Tell me about a weakness, a failure, or feedback you've received and worked on.

    What it tests: Self-awareness + shipping discipline. Cross-role canonical. Games-engineering mistakes (shipped without profiling, over-engineered an engine layer, missed a cert blocker, broke determinism live) shape teams + titles.

  4. Why games engineering - and why this firm / genre vs other tech roles or studios?

    What it tests: Authentic fit for the real-time + multi-platform + creative-partnership seat. Tests whether the candidate has a real reason to choose games over higher-pay SaaS / FAANG-equivalent - and a real reason to choose this studio.

  5. Which engineering area would you want to work on, and why?

    What it tests: Genuine fit + grasp of how games engineering sub-specialties differ (gameplay / engine / graphics / network / tools / AI / audio). Tests whether the candidate has a reasoned preference grounded in past work.

  6. Why this firm?

    What it tests: Whether the candidate has done the homework. Bar: specific evidence from the firm's titles, engine, eng culture, tech talks, postmortems - not generic 'great studio'.

  7. How would you describe this firm's engineering organisation + tech stack in your own words?

    What it tests: Whether the candidate has internalised HOW the firm engineers + ships games - engine choice, genre, target platforms, cross-functional shape.

  8. How does engineering actually drive value at a games studio like this firm?

    What it tests: Whether the candidate understands games-engineering economics: engineering enables the design vision (frame budget = what's possible), perf + stability = retention + reviews + cert, tools investment = team velocity, live-ops engineering = LTV.

Technical concepts to master

Game loop + ECS + data-oriented design

Fixed timestep sim + variable render
Game loop runs sim at fixed Hz (e.g. 60) regardless of frame rate; render interpolates between sim ticks for smoothness.
ECS (Entity Component System)
Data-first architecture: entities = IDs, components = pure data, systems = logic iterating over component arrays.
AoS vs SoA + cache lines
Array-of-structs groups by entity (OOP feel); struct-of-arrays groups by field (SoA - hot loops touch only what they need; cache-friendly).
Memory allocators - pool / stack / frame
Custom allocators for predictable + fast alloc: pools (fixed-size), stack (LIFO), frame / arena (reset per frame); avoid heap in hot path.

Rendering pipeline + GPU optimisation

Forward+ vs deferred shading
Forward+: tile / cluster cull lights per screen tile; shade in forward pass. Deferred: G-buffer all material data, shade in screen-space lighting pass.
Draw call cost + batching + instancing
Each draw call = CPU + driver + GPU state-change cost; batch (combine meshes) + instance (one call, many transforms) to amortise.
GPU bottleneck classification
Vertex bound (geometry-heavy), pixel / fill-rate bound (overdraw + shader cost), bandwidth bound (texture reads), or sync / barrier bound.
LOD + culling + occlusion
Don't render what player can't see / care about: frustum cull, occlusion cull, distance LOD, mesh LOD, shader LOD.

Gameplay + AI patterns

State machine (FSM) + hierarchical FSM
Discrete states + transitions; hierarchical adds sub-state-machines for shared behavior (e.g. 'in combat' parent with 'attack / dodge / reload' children).
Behavior tree + utility AI + GOAP
Behavior tree: hierarchical decision tree for AI (selector / sequence / decorator). Utility: score-based reactive. GOAP: planner with action preconditions.
Physics + collision (broadphase / narrowphase / CCD)
Broadphase prunes pairs (AABB / spatial hash / BVH); narrowphase computes contacts (GJK / SAT); CCD prevents fast objects tunnelling.
Animation - blend trees + IK + ragdoll
Blend trees combine clips by parameters (speed, direction); IK adjusts bones to fit world (foot placement); ragdoll for death + impact.

Networking + multiplayer architecture

Authority + sync models
Client-server (server-authoritative, cheat-resistant), peer-to-peer (small + trusted), lockstep (RTS, deterministic sim), rollback (fighter, deterministic + state rewind).
Client prediction + reconciliation + interpolation
Prediction: simulate local player's inputs immediately, reconcile to server state on response. Interpolation: render remote entities ~100ms behind for smoothness.
Lag compensation + hit registration
Server rewinds hit detection to the shooter's timestamp so 'what I saw' counts; balances fairness vs the 'shot behind cover' frustration.
Determinism + rollback netcode
Deterministic sim: same inputs -> same state on every machine; enables lockstep + rollback. Rollback: predict remote inputs, roll state back on mismatch.

Practical drills

  • A 60fps target on the slowest platform (8-core CPU, mid-tier GPU). Sim runs at 60Hz fixed, render at variable. (a) Frame budget in ms. (b) Plausible ms allocation across sim + animation + physics + AI + render + audio + UI + networking. (c) If physics tick is 120Hz instead of 60Hz, what changes? (d) GPU is at 14ms of the budget under load - is the system GPU bound, and what's the first action?
  • Design an ECS for 10K active entities in a top-down action game; each entity has transform + render + AI + physics components; budget 4ms per frame for ECS update. Walk me through it.
  • A title that runs at solid 60fps starts hitching to 30fps every few seconds on the slowest target platform; QA reports it after the latest gameplay build. Walk me through how you'd diagnose + fix.

Smart-question anchors

  • Engine + stack - proprietary vs Unreal vs Unity, C++ standard, scripting layer, tools chain
  • Perf target + platform - 30/60/120fps, target platforms, the slowest-target discipline
  • Cross-functional - art + design + audio + production + cert partnership, decision-making process
  • Engineering culture - code review, design-doc / RFC discipline, ownership, perf-budget governance
  • Live-ops + post-launch - on-call rotation, patch cadence, live perf monitoring, postmortem culture

Related roles

Sourced from

Ready to Generate Your Own Prep?

Drop your CV and a job description on the home page. A couple of minutes later you get a report with everything you need to land the job.

Generate my first prep