Unit 0: How system design interviews work
Learn the step-by-step way to answer any design question before you learn the parts. Without a method, even good knowledge comes out messy under pressure.
The big picture
Interviewers grade how you think: do you ask the right questions, size the problem, start simple and then improve the weak spots? A clear method shows all of that, even when you don't know every technology.
Lessons in this unit
- Meet the building blocks: a map of a typical web system: Most large web systems are built from the same dozen parts, connected in a familiar shape: clients, DNS, a CDN, load balancers, app servers, caches, databases, queues, workers and object storage.
- The high-level design interview: a step-by-step answer framework: A repeatable order of steps for answering any 'Design X' question in about 45 minutes.
- Back-of-the-envelope estimation: Quick, rough maths to estimate traffic, storage and bandwidth, so your design decisions are based on scale.
- The low-level design interview: a step-by-step approach: A repeatable way to answer 'Design the classes for X' (a parking lot, an elevator, Splitwise) and write the key code.