Quick Answer
How to explain a news feed in English: contrast fan-out on write vs read, add ranking and cache, then state the scale tradeoff in one clear sentence.
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
Publisher → post service → fan-out workers → follower caches.
What to say on figure 2
Reader → home feed service → timeline cache.
What to say on figure 3
Show celebrity pull path.
What to say on figure 4
Show ranking step before return.
Key vocabulary
| Term | Plain meaning | Say it in an interview |
|---|---|---|
| News feed | Home timeline of posts | “The home feed merges friends’ posts.” |
| Fan-out on write | Push posts to followers at publish | “On write, we push to follower timelines.” |
| Fan-out on read | Pull and merge at read time | “On read, we fetch recent posts and merge.” |
| Celebrity user | Huge follower count | “Celebrity accounts break pure write fan-out.” |
ESL English phrases and transitions
Clarify
- “Is ranking chronological or ranked by relevance?”
- “Roughly how many followers does a typical user have?”
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 |
|---|---|---|
| One strategy forever | Inflexible | Offer a hybrid for celebrities |
| Forgetting cache hydration | Incomplete read path | Timeline stores IDs; content is fetched/cached |
| Summary | Every new box needs one spoken reason. | |
Common English mistakes
| Mistake | What the interviewer concludes | Better English |
|---|---|---|
| No celebrity talk | Missed classic follow-up | Pre-empt the celebrity problem |
| Ranking silence | Unclear product | Say chronological vs ranked |
What the interviewer is testing
This is a communication test as much as a design test. Can you explain a news feed system 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
- “Is ranking chronological or ranked by relevance?”
- “Roughly how many followers does a typical user have?”
Watch Out
Do not open with a finished architecture. Show the path.
News feed system design
Use this sequence for news feed system design. For each stage, say what changes, why, and what can still go wrong.
Publish
Store the post; decide when fan-out happens.
Fan-out choice
Write fan-out for fast reads; read fan-out for huge graphs.
Home feed read
Serve from timeline cache; hydrate post content.
Celebrity hybrid
Hybrid: push for normal users, pull for celebrities.
Weak vs strong answers
Weak
“Just query all friends’ posts.”
Strong
“For most users I’d fan-out on write into timeline caches; for celebrity accounts I’d pull at read time so publish stays fast.”
Metrics and how to say numbers
| Write | Say |
|---|---|
| followers = 200 | about two hundred followers |
| celebrity = 10M | ten million followers |
Follow-up questions you will get
Likely follow-ups
- “How do you rank?” → “Start chronological, then mention signals if the interviewer wants ranking depth.”
Practice drill
Checklist
- Publish
- Write vs read fan-out
- Cache read
- Celebrity hybrid
“If you can explain a news feed system 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) | 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 (you are here) | 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)
- 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 — you are here
- 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.