Quick Answer
Spoken system design interview framework in English: clarify scope, sketch high-level, deep-dive one bottleneck, then summarise tradeoffs and invite the next focus.
Diagrams and what to say while drawing
Narrate each figure out loud. Point to the box you are talking about.
What to say on figure 1
Show the four-step interview board: Clarify → Design → Deep dive → Wrap-up.
What to say on figure 2
List functional vs non-functional questions you will ask.
What to say on figure 3
Sketch a generic client → API → service → DB flow.
What to say on figure 4
Leave a ‘risks / follow-ups’ box for the end.
Key vocabulary
| Term | Plain meaning | Say it in an interview |
|---|---|---|
| Requirements | What the system must do | “Before I design, I want to clarify requirements.” |
| High-level design | Main boxes and data flow | “I’ll start with a high-level design.” |
| Deep dive | Go deeper on one part | “I’d like to deep-dive on the write path.” |
| Tradeoff | Cost of a choice | “The tradeoff is higher latency for stronger consistency.” |
ESL English phrases and transitions
Clarify
- “I’ll clarify functional and non-functional requirements first.”
- “Do you want me to focus on the API, the data model, or scale?”
Propose and check in
- “The next bottleneck is X, so I would add Y.”
- “Does this level of detail work, or should I go deeper?”
Tradeoffs
- “The advantage is simplicity; the downside is…”
- “I’d choose A over B because…”
Key English language pitfalls
| Pitfall | Sounds like | Say instead |
|---|---|---|
| Over-engineering early | Kubernetes in minute one | Start simple; add complexity with a reason |
| No timeboxing | Endless deep dive | Offer a wrap-up and ask where to go next |
| Summary | Every new box needs one spoken reason. | |
Common English mistakes
| Mistake | What the interviewer concludes | Better English |
|---|---|---|
| Skipping requirements | Looks junior | Spend 1–2 minutes clarifying first |
| No check-ins | Monologue | “Does this level of detail work?” |
What the interviewer is testing
This is a communication test as much as a design test. Can you explain a system design interview framework as a calm collaboration?
Interviewers listen for structure, tradeoffs, and clear English under pressure.
Key takeaway
Your job is to narrate decisions the interviewer can follow and challenge — not to dump tools.
How to open the problem in English
Opening script you can practise aloud
- “I’ll clarify functional and non-functional requirements first.”
- “Do you want me to focus on the API, the data model, or scale?”
Watch Out
Do not open with a finished architecture. Show the path.
System design interview framework
Use this sequence for system design interview framework. For each stage, say what changes, why, and what can still go wrong.
Clarify
Ask about users, scale, latency, consistency, and what is out of scope.
High-level
Draw clients, services, storage, and the main request path.
Deep dive
Pick the riskiest bottleneck and explain it in detail.
Wrap-up
Summarise decisions, name one risk, invite the next focus.
Weak vs strong answers
Weak
Jumping straight into microservices.
Strong
“I’ll clarify scale and consistency, then propose a simple high-level design before any deep dive.”
Metrics and how to say numbers
| Write | Say |
|---|---|
| 30–45 min interview | a thirty to forty-five minute interview |
| 2 minutes clarifying | about two minutes clarifying |
Follow-up questions you will get
Likely follow-ups
- “What if requirements change mid-way?” → “I’ll update the board and rescale the design.”
Practice drill
Checklist
- Clarify 60s
- High-level 3 min
- Deep dive 4 min
- Wrap 60s
“If you can explain a system design interview framework without notes, you are ready to draw it in an interview.”
Answer frameworks you can reuse
Use these spoken templates under pressure. Fill the blanks — do not invent a new structure mid-interview.
Framework 1 — Whole answer
Clarify → High-level → Deep dive → Check-in.
Framework 2 — Each component (B-C-B-C)
Bottleneck → Component → Benefit → Cost.
Framework 3 — Now → Breaks → Next
Current design → failure mode → next upgrade.
Framework 4 — Draw → Name → Why → Risk
Narrate every box as you draw it.
Interview tip
Pick one framework and stay inside it. Switching structures mid-talk makes English sound messy.
System Design English knowledge base
← System Design English knowledge base — start at How to Explain Scaling from Zero to Millions in English for the full chapter index and reading order.
Explore every Mockly article on the blog hub.
All chapters in this series
Jump between System Design English posts below. Each chapter builds spoken English for the same book — use the KB overview when you want the big picture.
| # | Chapter | Slug |
|---|---|---|
| 1 | How to Explain Scaling from Zero to Millions in English | how-to-explain-scaling-from-zero-to-millions-in-english |
| 2 | How to Say Back-of-the-Envelope Estimates in English | how-to-say-back-of-the-envelope-estimates-in-english |
| 3 | Spoken System Design Framework in English (ESL) (you are here) | spoken-system-design-interview-framework-in-english |
| 4 | How to Explain a Rate Limiter in English | how-to-explain-a-rate-limiter-in-english |
| 5 | Consistent Hashing Interview Vocabulary in English | consistent-hashing-interview-vocabulary-in-english |
| 6 | How to Explain a Key-Value Store in English | how-to-explain-a-key-value-store-in-english |
| 7 | How to Explain a Unique ID Generator in English | how-to-explain-a-unique-id-generator-in-english |
| 8 | URL Shortener Interview Phrases in English (ESL) | url-shortener-interview-phrases-in-english |
| 9 | How to Narrate a Web Crawler in English | how-to-narrate-a-web-crawler-in-english |
| 10 | How to Explain a Notification System in English | how-to-explain-a-notification-system-in-english |
| 11 | How to Explain a News Feed in English | how-to-explain-a-news-feed-in-english |
| 12 | Chat System Interview Phrases in English (ESL) | chat-system-interview-phrases-in-english |
| 13 | Think Out Loud: Search Autocomplete in English | think-out-loud-search-autocomplete-in-english |
| 14 | How to Explain YouTube System Design in English | how-to-explain-youtube-system-design-in-english |
| 15 | How to Explain Google Drive System Design in English | how-to-explain-google-drive-system-design-in-english |
- How to Explain Scaling from Zero to Millions in English
- How to Say Back-of-the-Envelope Estimates in English
- Spoken System Design Framework in English (ESL) — you are here
- How to Explain a Rate Limiter in English
- Consistent Hashing Interview Vocabulary in English
- How to Explain a Key-Value Store in English
- How to Explain a Unique ID Generator in English
- URL Shortener Interview Phrases in English (ESL)
- How to Narrate a Web Crawler in English
- How to Explain a Notification System in English
- How to Explain a News Feed in English
- Chat System Interview Phrases in English (ESL)
- Think Out Loud: Search Autocomplete in English
- How to Explain YouTube System Design in English
- How to Explain Google Drive System Design in English
Frequently Asked Questions
Tap a question to expand the answer.