System Design Interview Questionsas rounds you can run

Reading a system design answer is not the same as giving one. Here every question is a round: draw your design on a board, send the problem’s real traffic through it, and watch which box breaks. Then an AI interviewer reviews your board and asks the follow-ups, from fresher to senior.

rounds
8rounds
follow-up questions
32follow-up questions
load test, no sign-in
Freeload test, no sign-in
The load test on a one-server Tatkal designBreaks
  1. Users74k/s at 10:00
  2. Load balancer37% · 74k/s of 200k
  3. Booking serviceOverloaded · 79k/s of 5k
  4. PostgresOverloaded · 67k reads/s of 10k

What fixes it on the board: cache the availability, keep seat counts in Redis, and put a waiting room in front of booking.

How a round works

  1. 1Do the numbersRead the brief and estimate the load, the way interviews start.
  2. 2Draw the designBoxes for CDNs, services, caches, queues and databases, joined by arrows.
  3. 3Run the load testSend the real traffic through it, then fail a machine and see what holds.
  4. 4Defend itAn AI review of your board, then the follow-ups, Fresher to Senior.

Apps you use every day

Classic problems in familiar clothes: a ticket rush, payments, live video, live location, a flash sale. Every number is an assumption for the exercise, not the company’s.

The classics

The three that come up most, and the usual place to start.

blur