Skip to content
RED SAGSkills
hardGame Developer interview question

How would you design the backend for an online game with matchmaking and dedicated servers?

What the interviewer wants to hear

  • Separate services: accounts, matchmaking, game server fleet, persistence
  • Matchmaker groups players by skill, latency and region, relaxing rules over time
  • Fleet manager allocates dedicated servers and autoscales by demand
  • Authoritative game servers report results; player data stored server-side
  • Security, anti-cheat, rate limits, and handling outages gracefully
  • Use platforms like Agones, GameLift or vendor services where it saves effort

Model answer

I would separate the backend into services. An account and identity service handles login through platforms like Steam or console networks. The matchmaker takes tickets with skill rating, party size and ping to each region, groups compatible players, and relaxes rules the longer people wait so queues stay short. When a match forms, a fleet manager allocates a dedicated game server in the best region; I would use something like Agones on Kubernetes or Amazon GameLift so servers autoscale with demand and scale down at night. The game server is authoritative, validates gameplay, and reports results to a stats service that updates ratings and inventory, which only the backend can change. I would add rate limiting, anti-cheat checks, health monitoring, and degrade gracefully, for example letting players stay in menus if matchmaking is down.

Can you answer it under time pressure?

Take a timed hard round and get scored on every answer.

Start mock interview

More hard Game Developer questions