System Design Interview: A 45-Minute Framework That Works
A step-by-step framework for system design interviews: requirements, estimates, high-level design, data model, deep dives and trade-offs, with timings.
Contents
System design interviews are open-ended on purpose. The interviewer wants to see how you handle ambiguity, make decisions and explain trade-offs. A predictable structure keeps you from getting lost.
Minutes 0–5: requirements
Ask before you draw:
- Functional: what must the system do? For a URL shortener: create short links, redirect, maybe custom aliases and analytics.
- Non-functional: scale, latency, availability, consistency, data retention.
- Out of scope: say explicitly what you will not design.
Minutes 5–10: estimates
Rough numbers guide every later decision. Example: 100M new links per month is about 40 writes per second; with a 100:1 read ratio, about 4,000 redirects per second; 500 bytes per record is about 50 GB per month. You don’t need precision — you need the order of magnitude.
Minutes 10–20: high-level design
Draw the main path: client → load balancer → stateless service → cache → database, plus asynchronous parts like a queue for analytics. Name the responsibility of each component in one line.
Minutes 20–25: data model and API
Define the key entities and how they are accessed. Choose storage by access pattern: a key-value store for short_id → url lookups, a relational database if you need transactions and flexible queries.
Minutes 25–40: deep dives
The interviewer will usually pick one or two areas. Common ones:
- ID generation: counter with base62 encoding vs random IDs with collision checks.
- Caching: cache-aside, TTLs, invalidation, hot keys.
- Scaling the database: replication for reads, sharding by a well-distributed key.
- Reliability: retries with backoff, idempotency keys, timeouts, graceful degradation.
Minutes 40–45: trade-offs and wrap-up
Summarize the design, name its weakest point and what you would do with more time. Saying “this is the bottleneck, and here is how I’d address it” is a strong signal.
Practice tips
- Practice out loud with a timer; silent practice hides gaps.
- Keep a short list of numbers in your head: memory vs SSD vs network latency, typical requests per second per server.
- Always state at least two options and why you chose one.
Start with our list of system design interview questions. During real interviews, Sottena presents architecture questions as a compact card: components, flows, what to clarify and trade-offs.
Get answer points in real time during your interview
Sottena listens to the interviewer, detects each question and shows short answer points in about a second. 150 free credits, no card required.