System Design Interview Framework

A four-step system design interview framework with timings, six practice questions, 40 core topics from CAP to Bloom filters, and a link to a diagram tool.

The interactive tool loads here when JavaScript runs.

About this tool

What is System Design Interview?

This page lays out a four-step approach for a 45 to 60 minute system design interview: requirement gathering, high-level design, detailed design, and scaling. Each step has a suggested time box, the things to cover and a few tips. You can tick steps and core concepts as you practise them.

The Practice Questions tab lists six classic prompts (chat app, URL shortener, news feed, video streaming, ride sharing, search engine) with the components and focus areas an interviewer will expect. The Advanced Topics tab holds short explanations of about 40 building blocks, grouped into scalability, storage, indexing, probabilistic data structures, protocols, reliability and caching.

It is a framework and a reference, not a mock interviewer. Ticks are saved in this browser only. The Whiteboarding tab links to the site's Excalidraw-based Diagram Tool for drawing your architecture.

  • Four-step framework with time boxes, steps and tips
  • Six practice prompts with key components and focus areas
  • About 40 core topics with short explanations, including CAP, QUIC, gossip and Merkle trees
  • Checklists for framework steps and core concepts, saved in your browser
  • Link to an Excalidraw-based diagram tool for architecture sketches
Read the guide: System Design Interviews: A Four-Step Method with Real Numbers

Updated

How to use System Design Interview

  1. Open the Framework tab and read the four steps with their time boxes before your first practice session.
  2. Pick a prompt from the Practice Questions tab and set a 45 minute timer.
  3. Work through the steps in order: requirements and estimates, then a high-level diagram, then one or two components in detail, then bottlenecks and scaling.
  4. Use the Advanced Topics tab to look up any building block you reached for but could not explain clearly, such as consistent hashing, Bloom filters or the saga pattern.
  5. Draw the final design in the Diagram Tool from the Whiteboarding tab, and tick the steps and Core Concepts you handled well.

Worked example

Sizing the URL shortener prompt

Input

Design a URL Shortener: 100 million new links per month, 10:1 read to write ratio, keep links 5 years

Output

About 40 writes/s and 400 reads/s average; 6 billion links over 5 years; 7 Base62 characters is enough

100 million a month divided by about 2.6 million seconds is roughly 40 writes per second. Six billion links fit easily in 62⁷ (3.5 trillion) codes. At 500 bytes per row, storage is about 3 TB, so the hard parts are caching hot links and generating unique codes, not raw scale.

Background and insight

System design rounds are open-ended on purpose. There is no single right answer, so the interviewer is scoring how you get to one: whether you pin down requirements before drawing boxes, whether your numbers are in the right order of magnitude, whether you can go deep on one component, and whether you name trade-offs instead of presenting one option as free. Seniority shows mostly in the last two.

Back-of-the-envelope numbers anchor everything. A day has 86,400 seconds, so 100 million requests a day is about 1,160 per second on average, and peak is commonly two to three times that. A 7-character Base62 short code gives 62⁷, about 3.5 trillion, combinations. A single SSD-backed database node can usually serve thousands of simple indexed reads per second, so 1,000 QPS rarely needs sharding, while 100,000 usually needs caching or partitioning.

The CAP theorem is often stated as "pick 2 of 3", which is misleading. Network partitions happen whether you choose them or not, so the real decision is what the system does during a partition: refuse some requests to stay consistent, or keep answering and risk stale reads. PACELC extends this with the latency versus consistency trade-off that applies even when the network is healthy, and it is a better lens for most interview discussions.

Common use cases

  • Preparing for a senior engineering loop

    Practise one prompt every few days with the four-step framework until the timing feels natural.

  • Filling knowledge gaps

    Use the Advanced Topics list as a checklist of building blocks you should be able to explain in two sentences.

  • Running mock interviews

    As an interviewer, pick a prompt and use its focus areas as the probes for the detailed design step.

  • Reviewing real designs

    Apply the same requirements, estimates and trade-offs structure when reviewing a design doc at work.

Tips and limitations

  • Spend the first five to ten minutes on requirements. Designing the wrong system well is the most common way to fail this round.
  • Write your estimates on the board. Interviewers forgive rough numbers but not missing ones.
  • Pick one or two components for the detailed design and go properly deep instead of touching ten things lightly.
  • Every choice has a cost. Say what you give up when you add a cache, a queue, a replica or a shard.
  • Do not lead with microservices. Start with the simplest design that meets the requirements and split it when a number forces you to.

Sources and further reading

  1. Brewer's conjecture and the feasibility of consistent, available, partition-tolerant web services, ACM SIGACT News. Gilbert and Lynch's proof of the CAP theorem
  2. CAP twelve years later: How the "rules" have changed, IEEE Computer. Eric Brewer on why "pick two of three" misleads
  3. Consistency Tradeoffs in Modern Distributed Database System Design, IEEE Computer. Daniel Abadi's PACELC formulation
  4. Caching Best Practices, Amazon Web Services. Cache-aside and write-through compared

Frequently asked questions

How should I structure a system design interview answer?

Use four phases: clarify functional and non-functional requirements and estimate scale, sketch a high-level design with the main components and APIs, go into detail on one or two critical components, then discuss bottlenecks, scaling and trade-offs. Say the structure out loud at the start so the interviewer can steer your time.

How long should each part of a system design interview take?

In a 45 minute round, aim for about 5 to 10 minutes on requirements and estimates, 10 to 15 on the high-level design, 15 to 20 on detailed design, and the remaining time on scaling and trade-offs. If the interviewer pulls you into a topic early, follow them; the timing is a guide, not a script.

Does the CAP theorem mean I pick two of consistency, availability and partition tolerance?

Not really. Partitions are not optional in a distributed system, so CAP says that during a partition you must choose between consistency and availability. Outside partitions the trade-off is usually latency versus consistency, which is what the PACELC model adds. Say which behaviour your design wants when a partition happens.

How do I do back-of-the-envelope estimates for system design?

Start from daily active users and actions per user, divide by 86,400 seconds (round to 100,000) for average requests per second, and multiply by two or three for peak. Multiply object size by count for storage. Round aggressively; the goal is the order of magnitude that decides whether you need caching, sharding or a CDN.

What system design questions come up most often?

Classic prompts include a URL shortener, a chat app, a news feed, a video streaming service, a ride-sharing backend, a rate limiter, a web crawler and a key-value store. They recur because each one forces a distinct trade-off, such as fan-out on write versus read for feeds or geospatial indexing for ride sharing.

Do junior engineers get system design interviews?

Often not, or only a lighter version. Many companies add a system design round from mid-level upward and weight it heavily for senior roles. Junior candidates may get an object-oriented or API design exercise instead. Ask your recruiter which rounds are in your loop; it is a normal question.

Is there an in-depth guide to System Design Interview?

Yes. “System Design Interviews: A Four-Step Method with Real Numbers” covers the background, how it works, common pitfalls and worked examples. Read the full guide.