Orientation. Before you learn any component, understand what this field is, how to study it, and what you’re being tested on.
Time for this part: about 1–2 days. Don’t rush it — the study method in How to Use This Guide determines whether the next twelve weeks work.
| # | Chapter | Time | What you get |
|---|---|---|---|
| 1 | What Is System Design? | 12 min | The field, via a to-do app that breaks nine times as it grows |
| 2 | How to Use This Guide | 10 min | The learn → explain → build → apply loop. The most important page here. |
| 3 | Prerequisites & Self-Assessment | 30 min | Whether you’re ready, and where to start if not |
| 4 | The Interview Formats You’ll Face | 12 min | What actually happens in the room, and how the bar shifts by level |
| 5 | Glossary | reference | Every term in the repo, one page. Bookmark it. |
my-notes.md file. Three lines per chapter, reviewed weekly.“Do I need work experience to learn this?” No. You need to understand constraints — scale, failure, latency, cost — and constraints can be taught. Most of this guide’s examples are built up from a single-server app you could write today.
“How long until I’m interview-ready?” With genuine effort: 10–12 weeks from zero for junior/mid roles. 4 weeks if you already have 2+ years of experience and just need structure. Less than that is cramming, and it shows.
“Should I learn AWS / Kubernetes / Kafka first?” No. Learn the concepts — where compute goes, how data is partitioned, how messages are buffered. Tools are 3-day problems once you understand what they’re for. Concepts are the 12-week part.
“Is this enough on its own?” For interviews, yes, if you actually do the exercises and mocks. For mastery, add Designing Data-Intensive Applications and real production experience. See Reading List.
“I have an interview in 5 days.” The Framework, Common Mistakes, Back-of-the-Envelope, then as many Tier-1 and Tier-2 case studies as you can fit. Good luck.