Engineering Ic interview prep.

Behavioural questions to expect

1. Walk me through your CV.
2. Tell me about your most impactful technical project.
3. Tell me about a weakness, a failure, or feedback you've received and worked on.
4. Why games engineering - and why this firm / genre vs other tech roles or studios?
5. Which engineering area would you want to work on, and why?
6. Why the firm?
7. How would you describe the firm's engineering organisation + tech stack in your own words?
8. How does engineering actually drive value at a games studio like the firm?

Technical concepts to master

• Game loop + ECS + data-oriented design

  Fixed timestep sim + variable render · ECS (Entity Component System) · AoS vs SoA + cache lines · Memory allocators - pool / stack / frame

• Rendering pipeline + GPU optimisation

  Forward+ vs deferred shading · Draw call cost + batching + instancing · GPU bottleneck classification · LOD + culling + occlusion

• Gameplay + AI patterns

  State machine (FSM) + hierarchical FSM · Behavior tree + utility AI + GOAP · Physics + collision (broadphase / narrowphase / CCD) · Animation - blend trees + IK + ragdoll

• Networking + multiplayer architecture

  Authority + sync models · Client prediction + reconciliation + interpolation · Lag compensation + hit registration · Determinism + rollback netcode

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

Sourced from

Game Engine Architecture (Jason Gregory, 3rd ed) · Real-Time Rendering (Akenine-Moller et al, 4th ed) · Gaffer On Games — Networked Physics + Glenn Fiedler series · Data-Oriented Design (Richard Fabian) + ECS canon · GDC Vault — programming track talks (engine, gameplay, network, graphics) · Glassdoor + levels.fyi + Reddit r/gamedev interview reports