The system design interview: a complete guide
The short answer
A system design interview is a 45 to 60 minute conversation where you design a large software system, such as a chat app or a URL shortener, on a whiteboard. There is no single right answer. You are scored on how you gather requirements, how you reason about scale, and how clearly you explain the trade-offs you choose.
Written by Roni Das, who teaches the System Design course on this site. Jump to the courses and prices.
What the round is for
Coding rounds test whether you can write a correct function. The design round tests something different: whether you can plan a system that many people will use, before anyone writes code. Companies use it to decide your level as much as whether to hire you.
The interviewer gives you a short, open prompt, such as "design a URL shortener". Everything else is up to you to ask about. That is on purpose: real projects start with vague requests too.
The 45-minute structure
Strong candidates move through the same six steps. The minutes are a guide, not a rule.
Step 1, 5 to 8 minutes
Requirements
Ask what the system must do and for whom. Agree on the two or three features that matter, and on limits such as how many users and how fast a page must load.
Step 2, 3 to 5 minutes
Estimates
Work out rough numbers: requests per second, data stored per year, and the ratio of reads to writes. These numbers decide the design, so say them out loud.
Step 3, 5 minutes
API and data model
Name the main calls the system offers and the main tables or records it stores. This keeps the design concrete.
Step 4, 10 to 15 minutes
High-level design
Draw the main parts and walk one request through them, from the user to the database and back.
Step 5, 10 to 15 minutes
Deep dive
Pick the hardest part, often the one the interviewer asks about, and go deep: what breaks first, and how you fix it.
Step 6, 3 to 5 minutes
Wrap-up
Say what you would improve with more time, and the trade-offs you chose.

How the round is scored
Interviewers fill in a form after the round. The headings differ by company, but they come down to these five questions.
- Did you ask about requirements before drawing anything?
- Do your numbers support the parts you chose?
- Can you explain why you chose one option over another, and what it costs?
- Did you find the bottleneck and the failure points yourself?
- Could the interviewer follow your thinking from start to finish?
Notice what is missing: nobody scores you on naming the most products. A simple design you can defend beats a crowded one you cannot.
What changes at mid, senior and staff level
Mid level
You are expected to produce a working design with the standard parts: load balancer, services, a database, a cache and a queue where they help. The interviewer guides you towards the deep dive.
Senior
You lead the whole round without help. You choose the deep dive yourself, you compare two or three options for the hard part, and you explain failure handling without being asked.
Staff
You still draw the design, but the round is about judgement. You question the requirements, you explain what you would build first and what you would postpone, and you talk about cost, operations and how teams would own the parts.
Nine worked designs you can study free
Each walkthrough below goes through all six steps for one classic question. Read one, then close it and redo the design on paper.
- URL shortener: How to create short codes that never collide, and why reads far outnumber writes.
- Rate limiter: Token bucket against sliding window, and where the counter lives when there are many servers.
- Typeahead search: Serving suggestions in a few milliseconds from a structure built ahead of time.
- News feed: Writing posts to followers' feeds ahead of time, and what to do about accounts with millions of followers.
- Message queue like Kafka: An append-only log split into partitions, and how consumers keep their place.
- Notification system: Fan-out to many channels, retries, and respecting each user's preferences.
- Chat app like WhatsApp: Long-lived connections, delivery receipts and messages for users who are offline.
- Ride hailing like Uber: Finding nearby drivers quickly by splitting the map into cells.
- Video streaming like Netflix: Encoding each video many ways ahead of time and serving it from caches near users.
Before the walkthroughs, the free lessons on latency, throughput and cache invalidation give you the words you will use in every round. There are 125 walkthroughs like these in the interview section, and the full System Design course has 770 lessons. For a step-by-step plan that takes you from the building blocks to practising answers out loud, see system design interview prep.
Guides for engineers in other countries
The round is the same everywhere, but visas, the interview language and our live class time are not. Each guide below covers one country, with its own official sources.
Questions
How long is a system design interview?
Most rounds last 45 to 60 minutes. About 45 minutes go to the design itself, and the rest to introductions and your questions.
Do I need to write code in a system design interview?
Usually not. You draw boxes and arrows, write a few API calls and table outlines, and explain your choices. Some companies add a little pseudocode for one part.
How long does it take to prepare?
Someone who writes code every day usually needs four to eight weeks of steady practice, a few hours a week. The key is doing full timed rounds out loud, not just reading.
Is the round the same in every country?
Yes, the format is the same. What differs is the hiring process around it, such as visas and the language of the interview. Our country guides below cover those.
Prepare with the full course
The free lessons and walkthroughs above are a real start. The course takes you the rest of the way, from the basics to staff-level design. You pay once and keep it for life.
The best value
Both courses together
Lifetime access to the System Design course and the AI Engineering course, in one payment.
₹1,999 in India · $59 everywhere else
You save ₹445 against buying the two separately. You save $11 against buying the two separately.
Get both coursesSystem Design course
The full self-paced course, from the basics to staff-level design, with lifetime access.
₹1,111 in India · $35 everywhere else
System Design Interview Bootcamp
A self-paced bootcamp: one recorded class a week, with drills, watched on this site whenever suits you.
₹20,000 in India · $400 everywhere else
Interview prep packs
Question-and-answer packs for the week before an interview. One pack, or all nine together.
₹999 a pack, ₹3,000 for all nine in India · $20 a pack, $49 for all nine everywhere else
AI Engineering course
The full self-paced course on Generative AI and agentic AI in production, with lifetime access.
₹1,333 in India · $35 everywhere else
AI Engineering Live
A live class every Saturday evening, India time, where we build one AI project together. Every class is recorded, so you can join now and catch up.
₹20,000 in India · $400 everywhere else
AIOps on AWS
A hands-on course that builds AI agents for DevOps on AWS. Early access includes every part released later.
₹3,333 in India · $100 everywhere else
The price rises to ₹7,777 when the course is complete. The price rises to $177 when the course is complete.
In India you pay in rupees by UPI or card through Razorpay. Outside India you pay in US dollars, by card through Razorpay, or by PayPal. Live programmes are sold at the full fee in one payment.