Tell me about a game or game feature you built. What was the hardest problem and how did you solve it?

What the interviewer wants to hear

• Clear description of the game or feature and your role
• A specific technical problem
• How you investigated it, for example profiling or debugging
• The solution and trade-offs
• What you learned or would do differently

Model answer

In a game jam, our team of three built a 2D platformer in Unity in 48 hours, and I wrote the player controller. The hardest problem was that the character sometimes got stuck on the edges between tiles. Using debug drawing, I saw the box collider was catching on the small seams between separate tile colliders. I switched the tilemap to a composite collider, so the ground became one smooth shape, and changed the player to a capsule collider with a small edge radius. I also added coyote time and jump buffering, so jumps felt fair. Movement became smooth, and players said the controls felt good. I learned to use visual debugging early and to test game feel with real players often.

More easy Game Developer questions

• What is a game loop, and why is delta time important?
• In Unity, what is the difference between Awake, Start, Update, FixedUpdate and LateUpdate?
• How do you use vectors, dot product and cross product in game development?
• How does collision detection work in a game engine, and what is the difference between a collider and a trigger?
• Why do game engines like Unity and Unreal favour components over deep inheritance trees for game objects?
• How would you set up version control for a small game team with programmers and artists?
• What do you do as a programmer to make a game "feel" good to play?
• What are coroutines in Unity, and when would you use them instead of Update or async/await?
• How do you use prefabs, nested prefabs and prefab variants to keep a Unity project organised?