System Design Interview Study Plan (6 Weeks)
A 6-week System Design study plan that sequences every topic — foundations, data, distributed systems, HLD case studies, LLD and patterns, then mock interviews — into a day-by-day path from zero to interview-ready.
🔵 Resource · Study Plan · Bookmark this
Knowing what to study is half the battle; knowing the order is the other half. This is a 6-week System Design study plan that sequences every article on GyaanPost — Start Here → Fundamentals → HLD → LLD — into a day-by-day path from zero to interview-ready. Adjust the pace to your timeline; the order is what matters.
Week 1 — Foundations & the framework
Get the mental model and the interview method. What is system design → how the web works → client-server-DB-API → latency/throughput/availability → scale from zero to millions. Finish with the 6-step interview framework and capacity estimation.
Week 2 — Data & storage
Where most designs live or die. SQL vs NoSQL · indexing · replication · sharding · ACID & isolation levels · caching strategies · LSM-tree vs B-tree.
Week 3 — Distributed systems
The hard, high-signal topics. CAP theorem · consistency models · consistent hashing · load balancing · message queues · rate limiting · Saga transactions · consensus · resilience patterns. Skim the cheat sheet to tie it together.
Week 4 — HLD case studies
Apply it all to "Design X." Start easy and build up: URL shortener → rate limiter → news feed → chat → YouTube → Uber → payments. Do each on paper first. (Full list of 14 in the hub.)
Week 5 — LLD & design patterns
For SDE-2/senior machine-coding rounds. LLD approach → OOD basics → SOLID → the design patterns (use the patterns cheat sheet). Then code the classics: parking lot, ATM, Splitwise, LRU cache.
Week 6 — Mock interviews & review
🔴 Simulate the real thing: pick a random "Design X," set a 45-minute timer, and go end-to-end out loud — requirements, estimates, API, architecture, deep dive, bottlenecks. Record yourself. Review weak spots against the cheat sheet. Redo the two designs you found hardest. Confidence comes from reps, not re-reading.
Tips that actually move the needle
- Always state assumptions and drive the conversation — interviewers score your process, not a "correct" answer.
- Do the math (QPS, storage) — it justifies every later decision.
- Talk trade-offs, not absolutes: "I'd use X because…, accepting Y."
- Draw as you talk — a clear diagram carries the interview.
What to read next
- The complete System Design guide (hub) — every article, in order
- System Design Cheat Sheet · Design Patterns Cheat Sheet
- The 6-step interview framework — start here on interview day