System Design Tracker

20 weeks, 120 sessions. Foundations → HLD building blocks → LLD & patterns → classic HLD problems → timed mocks. One session a day, Day 7 is review.

Saved in this browser
0 / 120 done 0 timed & unaided 0 to revisit 0/ HLD · 0/ LLD
done timed & unaided revisit Start date
How to run a session (read once, then every mock)
  1. Read / Estimate days (30–45 min): read the concept tab, then close it and write the reference card from memory. Log one sentence: what decision does this concept let me make?
  2. Design days (45 min, timed): 5 min requirements & non-functional goals · 5 min estimation · 10 min high-level boxes and API · 20 min deep-dive on the two hardest parts · 5 min failure modes and what you'd change at 10× scale. Speak out loud; draw on paper or a whiteboard app.
  3. Code days (60 min): requirements → use cases → classes & interfaces (draw) → code the core flow → one extension to test the design. Write real, runnable code.
  4. Mark "timed & unaided" only if you finished inside the time box without opening notes or the lesson.
  5. Log every session: the key requirement that shaped the design, the trade-off you stated, the bottleneck, one thing you missed.