Design real-time multiplayer game state sync
PremiumReal-timeHard
- Authoritative server
- Client side prediction
- Lag compensation
Quick answer
This real-time interview question asks you to design real-time multiplayer game state sync. Aim for a design that delivers updates to many users with low delay, then explain connections, fan-out, ordering and trade-offs. Interviewers want to see how you keep latency low, handle reconnects and stay correct under load.
The problem
Design real-time state sync (netcode) for a competitive multiplayer game with 64 players per match, like Battlefield. The server is the authority so no client can cheat, yet each player's own movement must feel instant, other players must move smoothly, and a hit must register the way the shooter saw it.
Each player moves, shoots and interacts many times per second. Matchmaking, voice chat, the game engine itself and anti-cheat beyond server authority are out of scope.
What must the system do?
- Authority: The server simulates the world and decides every outcome; clients render what the server says.
- Responsiveness: A player's own movement and shooting respond immediately on their screen.
How well must it do it?
- Latency: Target round trip under 60 ms within a region; playable up to 150 ms.
- Tick rate: Server simulates and sends at 60 ticks per second for competitive modes.
What scale should you design for?
Use these numbers in your estimates.
The scale numbers unlock with this questionUnlock
Key concepts
- Authoritative server
- Client side prediction
- Lag compensation
- Tick rate
- UDP
- Delta snapshots
How you’ll practise
- Requirements
- Estimate
- Connections
- Message flow
- Delivery guarantees
- Wrap-up
Lala, personalized to you, gives a hint when you ask and reviews your design when you are ready.
What do interviewers look for?
In any real-time design round.
- Clarifies latency, ordering and delivery guarantees
- Chooses a connection model with reasons
- Explains fan-out to many receivers
- Handles reconnects, missed messages and duplicates
- Plans for hot spots and sudden traffic spikes
- States trade-offs between consistency and speed
Questions people ask about this interview question
- Which design type is this question?
- It is a real-time question. You design real-time multiplayer game state sync and explain your choices the way you would in an interview.
- Is this question asked at entry level?
- It is marked Hard. It suits engineers preparing for senior interviews, where you are expected to drive the discussion and go deep on trade-offs.
- What should I cover first?
- Start with who sends and receives updates, how fast they must arrive and what order matters. Agree on scope with the interviewer before you design anything.
- Can I practise it for free?
- It is a premium question. Sign up and unlock it once for 10 credits; it then stays unlocked. When you finish, Lala, your personalized AI mentor, can review your design for 30 credits.
Related questions
Updated · Written by the SevyDevy team