Quick Start

How the system design interview works, and how to use this guide.

  1. 1 How to Use This Guide "I'd like to start by clarifying the core use cases and the scale, then sketch a simple design that works end to end, and then spend most of our time on the two or three parts most likely to break." 4 min read
  2. 2 What System Design Interviews Test "Before designing, let me confirm the core use cases and the scale. I'll state my assumptions as numbers, then get a simple design working end to end, and then we can go deep on the parts most likely to break. Stop me if you'd like to focus somewhere specific." 4 min read
  3. 3 50-Minute Interview Framework "Here's my plan: about five minutes on requirements and scale, then entities and a small API, then a simple design that works end to end. After that I'd like to spend most of the time on the riskiest parts, probably seat contention and the on-sale spike, and finish by walking one booking through ... 4 min read
  4. 4 Common Mistakes "Let me step back: I've spent a while on the database choice. The bigger risk here is fanout for popular accounts, so let me move to that, and I can come back to storage if we have time." 4 min read
  5. 5 7-Day Crash Plan "Let me confirm the core use cases and scale first. I'll state assumptions as numbers, get a simple design working end to end, and then spend most of our time on the two or three riskiest parts." 3 min read
  6. 6 30-Day Study Plan "I'll start by clarifying the core use cases and scale, then propose a simple design and deep dive into the main bottlenecks." … "To wrap up, here's one request end to end; the biggest remaining risk is X, and with more time I'd add Y." 4 min read