A framework that always works
Drive the conversation through these steps instead of jumping to a diagram.
- Clarify requirements — functional (what it does) and non-functional (scale, latency, consistency).
- Estimate — back-of-envelope QPS, storage, and bandwidth to justify your choices.
- Define the API — a few core endpoints frame the whole design.
- High-level design — client, load balancer, services, database, cache, queue.
- Deep-dive — the interviewer will pick one component; go deep on data model and bottlenecks.
- Address scale — sharding, replication, caching, and the trade-offs each forces.