Progress Β· 0/5 phases
ποΈ ποΈ 90-Day HLD Roadmap β High-Level System Design
3 min read Β· Notion
ποΈ Frontend β Systems Engineer transition. 90 days. 5 phases. High-Level Design mastery from first principles to staff-engineer level.
π How to use this template
- Work through phases in order β each phase builds directly on the last
- Every day: study the topic β sketch a design β log one mistake you caught yourself making
- Use the Daily Tracker database to stay accountable
- Open each Phase page for full topic breakdowns, projects, real-system references, and mistake corrections
π‘ The #1 rule of HLD: Never draw a single box until you've written down the requirements and estimated the scale. Senior engineers spend 40% of a design session on constraints before touching architecture.
πΊοΈ Roadmap at a glance
| Phase | Days | Focus | Projects |
|---|---|---|---|
| Phase 1 β Foundations | Days 1β15 | Vocabulary, estimation, CAP, building blocks | URL Shortener requirements, Estimation CLI |
| Phase 2 β Core Components | Days 16β35 | Caching, queues, CDN, load balancing, search | Caching layer design, Rate limiter doc |
| Phase 3 β Distributed Patterns | Days 36β55 | Sagas, consistency, sharding, consensus | Job scheduler, Saga design, Sharding doc |
| Phase 4 β Real System Designs | Days 56β75 | Twitter, Uber, Netflix, Payments, WhatsApp | Full HLD docs, Mock interview |
| Phase 5 β Expert Systems | Days 76β90 | Multi-region, migrations, staff review | Notification system, Architecture critique |
β‘ The RESHADED Framework
Use this structure for every system design β interview or production.
- R β Requirements (functional + non-functional)
- E β Estimation (QPS, storage, bandwidth, memory)
- S β Storage schema (which DB, why, what schema)
- H β High-level design (component diagram)
- A β APIs (REST/gRPC endpoints, contracts)
- D β Detailed design (deep dive on 2β3 critical components)
- E β Evaluate (failure scenarios, bottlenecks, tradeoffs)
- D β Distinguish (what makes your design better than the naive approach)
π My progress
- Current phase: Phase 1
- Current day: Day 1 of 90
- Systems fully designed: 0 / 12
- Design docs written: 0
π Quick links
- π Phase 1 β Foundations of System Design
- βοΈ Phase 2 β Core System Components
- π Phase 3 β Distributed System Patterns
- ποΈ Phase 4 β Real System Designs
- π§ Phase 5 β Expert-Level Systems
π Latency numbers every designer must know
| Operation | Latency |
|---|---|
| L1 cache reference | ~1 ns |
| L2 cache reference | ~4 ns |
| RAM reference | ~100 ns |
| SSD read (4KB) | ~100 Β΅s |
| Read 1MB from SSD | ~1 ms |
| Network round-trip (same DC) | ~0.5 ms |
| Network round-trip (cross-region) | ~100 ms |
| Read 1MB from network | ~10 ms |
| HDD seek | ~10 ms |
These numbers drive every architecture tradeoff. Memorise them. Use them in every estimation.
π HLD Daily Tracker