Design a real-time multiplayer game backend
Match players into game sessions and keep everyone’s game state in sync with very low latency, like Fortnite.
Functional requirements
- Matchmaking by skill and location
- Real-time gameplay for up to 100 players per match
- Store results, rankings and rewards
Non-functional requirements
- Under 50 ms round trip for gameplay
- Cheating is hard
- Players can reconnect into a running match
Scale
- 10M concurrent players
- 100K matches running at once
- 30 to 60 state updates per second per match
How you’ll be scored
10 checks covering your diagram and your notes, and any valid approach counts. Hints appear for anything you miss. Common mistakes, such as single points of failure or components you never explain, cost points. How grading works
What interviewers look for
- Clarify before you draw. State what is in and out of scope. For “Design a real-time multiplayer game backend”, that starts with: Matchmaking by skill and location; Real-time gameplay for up to 100 players per match; Store results, rankings and rewards. Interviewers notice candidates who pin the requirements down first.
- Turn the scale into numbers. The scale (10M concurrent players; 100K matches running at once; 30 to 60 state updates per second per match) should become requests per second, storage and bandwidth, and those figures should drive your choices. Estimates with units carry more weight than adjectives.
- Show how each quality is met. Your design should visibly deliver: Under 50 ms round trip for gameplay; Cheating is hard; Players can reconnect into a running match. Saying that it does isn’t enough; point to the part of the design that makes it true.
- Expect follow-ups on the hard parts. Interviewers usually probe real-time, netcode and matchmaking here. This is a hard problem, so interviewers expect depth: what breaks first at this scale, how each failure is contained, and which trade-offs you accepted on purpose.
- Explain failure and trade-offs. Say what happens when a component fails, where a single point of failure would hurt, and what you chose not to build. Naming a trade-off is a stronger answer than claiming there isn’t one.