Game developer intern interviews at studios and engine companies test programming fundamentals, usually in C++ or C#, the maths that moves objects through a 3D world, and a portfolio you can explain. Expect at least one coding interview, questions about the engine you used, and a deep dive into a game, mod or jam project in which you show exactly what you built and why. This page covers the rounds to expect, the questions that come up with what a strong answer contains, two sample answers, what interviewers expect from an intern, the mistakes that cost offers, and a two-week prep plan.
What the game developer intern interview looks like
| Round | What happens | How to prepare |
|---|---|---|
| Application and portfolio review | Résumé plus a portfolio or GitHub with playable builds or videos, sometimes a note on why this studio | Lead with one or two polished projects, not ten unfinished ones |
| Technical screen or test | A coding test, sometimes a take-home such as a small gameplay feature in Unity or Unreal | Timed C++ or C# problems and one small feature built from scratch |
| Technical interviews | Data structures, C++ memory and object questions, game maths and your engine experience | Explain memory ownership, vectors and transforms out loud |
| Team and portfolio round | Walk through your project, how you work with designers and artists, and why this studio | Know the studio's games and pick one design choice to discuss |
Questions that come up, and what strong answers contain
- What is the difference between the stack and the heap, and when would you use a smart pointer? Automatic versus dynamic lifetime; unique_ptr for single ownership, shared_ptr only when ownership is truly shared, and why studios watch allocations inside hot loops.
- How would you use the dot product in a game? To tell whether an enemy is in front of the player from the sign of the dot product between the facing vector and the direction to the enemy, to test a field-of-view cone, or in lighting. Normalize the vectors first.
- Explain the game loop. Process input, update the simulation, render, repeat. Cover fixed versus variable time steps, why physics usually runs on a fixed step, and using delta time so movement does not depend on frame rate.
- How would you detect a collision between two spheres, or two boxes? Spheres: compare the distance between centres with the sum of the radii, using squared values to skip the square root. Axis-aligned boxes: check for overlap on every axis. Then explain broad phase versus narrow phase.
- Unity or Unreal: what did you build, and how is the engine organized? Unity scripts are written in C# on components attached to GameObjects; Unreal uses C++ and its Blueprints visual scripting, with Actors and Components. Say what you built and one problem you hit, such as garbage-collection spikes in C# or slow Blueprint logic.
- Your game drops to 20 frames per second in one area. How do you find out why? Profile first: find out whether it is CPU or GPU bound, then which system is responsible (draw calls, physics, scripts or allocations). Fix the biggest cost, then measure again.
- Tell me about a disagreement with a designer or teammate on a game project. How you turned the disagreement into a prototype or playtest, and what the players or the team decided.
Two sample answers
How would you use the dot product?
Say I want to know whether an enemy can see the player. I take the enemy's forward vector and the vector from the enemy to the player, normalize both and take their dot product, which is the cosine of the angle between them. If the field of view is 90 degrees, the half-angle is 45, so anything with a dot product above about 0.707 is inside the cone. Then I'd raycast to check that nothing blocks the line of sight. The dot product avoids calling a trigonometric function every frame for every enemy.
Walk me through a project.
At a 48-hour game jam, our team of four made a puzzle platformer in Unity where the player rewinds time. I built the rewind system: every physics step it recorded each object's position, velocity and state in a ring buffer covering the last five seconds. My first version allocated a new list every frame and caused visible stutter, so I switched to a preallocated array of structs, which removed the garbage-collection spikes. If I rebuilt it, I'd record only objects that moved, because static objects wasted most of the buffer.
What interviewers expect from an intern
- Solid programming fundamentals in C++ or C#; our C++ interview questions cover the C++ side.
- Working game maths: vectors, dot and cross products, matrices and transforms.
- A portfolio with playable, finished work and a clear account of your own contribution.
- Collaboration: game teams mix programmers, designers, artists and producers.
For the full-time version of these questions, see game developer interview questions.
Mistakes that cost offers
- A portfolio made only of tutorial projects, with nothing original.
- Not being able to say which parts of a team project you wrote.
- Optimizing in an answer without saying you would profile first.
- Knowing the studio's games only as a player, with nothing to say about how they were built.
A two-week prep plan
- Days 1 to 3: C++ or C# refresh: memory, references and pointers, classes and virtual functions, and the standard containers.
- Days 4 to 5: game maths: vectors, dot and cross products, matrices, and two collision tests coded from scratch.
- Days 6 to 8: polish one portfolio project: a short video, a build that runs, and a page explaining your contribution and one technical problem you solved.
- Days 9 to 11: timed coding problems on arrays, grids and graphs, such as pathfinding on a tile map.
- Days 12 to 14: research the studio's games and technology, prepare questions and run two mock interviews; for engine makers, compare our Unity and Epic Games coding interview guides.
Timing matters as much as preparation: see our internship recruiting timeline, and once you are in, turning an internship into a return offer. Engineering candidates should also read software engineer intern interview questions.
Where CoPilot Interview fits
Intern interviews reward clear explanations of your own projects and coursework, and that takes practice out loud. CoPilot Interview is an AI interview assistant; its free AI mock interview builds game developer intern questions from your résumé and the job description, reads them aloud, scores each spoken answer out of ten and shows a model answer to compare. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included, with no card, which suits a student budget. For real interviews and online assessments, follow your employer's rules.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
Should I use Unity or Unreal for my portfolio?
Use the engine the studio uses if you know it; otherwise either is fine. Unity uses C#, and Unreal uses C++ alongside its Blueprints visual scripting, so an Unreal project can also show the C++ skill many studio programming roles ask for.
Do game developer interns get LeetCode-style questions?
Often at least one coding round, as candidates commonly report, though many studios favour practical problems such as grids, pathfinding or a small gameplay feature. Ask your recruiter which format to expect.
Do game jams count as experience?
Yes. A finished jam game shows that you can scope, ship and work in a team under time pressure. Explain what you built, what went wrong and what you would change.
Can I use AI tools during an internship interview?
Only where the instructions allow it. Online assessments and many live rounds forbid outside help. Use AI to practice beforehand, and follow your employer's rules.
Practice this interview before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview