Quick Answer
How to design Twitter timeline in English: clarify timeline vs search, estimate tweet and read QPS, then compare fan-out-on-write versus fan-out-on-read with clear tradeoffs.
Diagrams and what to say while drawing
Draw as you speak: requirements → APIs → estimates → boxes → deep dive → bottlenecks. Western panels score the narration as much as the diagram.
Key vocabulary
| Term | Plain meaning | Say it in an interview |
|---|---|---|
| Timeline | Home feed of tweets | “Home timeline is read-heavy.” |
| Fan-out | Distribute a tweet to followers | “Fan-out-on-write precomputes timelines.” |
| Tweet | Short status object | “Tweets are small; fan-out cost is social graph size.” |
| Search index | Find tweets by keyword | “Search is a separate path from timeline.” |
ESL English phrases and transitions
Open and clarify
- “I’ll clarify home timeline versus user profile timeline.”
- “The hard part is fan-out to millions of followers.”
- “I’ll compare push and pull timelines with tradeoffs.”
UK/US system design moves
- “The tradeoff is X versus Y.”
- “I’ll deep-dive this component next.”
- “A single point of failure here would be …”
Pair this chapter with Mockly’s System Design interview English hub.
Key English language pitfalls
| Pitfall | Sounds like | Say instead |
|---|---|---|
| Same strategy for all users | Celebrity meltdown | Hybrid fan-out. |
| Mixing search into timeline design | Scope creep | Park search unless asked. |
| No latency target | Vague | State freshness expectations. |
| Summary | Clear tradeoffs are how Western panels hear senior engineers. | |
Common English mistakes
| Mistake | Why it hurts | Fix |
|---|---|---|
| Only drawing boxes | No tradeoffs | Say CPU/network cost of fan-out. |
| Forgetting retweets/likes | Incomplete product | Mention briefly or defer. |
| Silent QPS math | Weak signal | Narrate numbers. |
What the interviewer is testing
For Twitter/X timeline design, UK/US interviewers test structured thinking, scale intuition, and calm spoken English - not accent perfection.
They listen for clarify → estimate → design → tradeoffs → bottlenecks. If those moves are audible, you sound hireable.
How to open in English
First 20 seconds
- “I’ll clarify home timeline versus user profile timeline.”
- “The hard part is fan-out to millions of followers.”
- “I’ll compare push and pull timelines with tradeoffs.”
twitter timeline system design
Use this sequence for twitter timeline system design. Say the step name before you do it.
| Step | What to say |
|---|---|
| Clarify | Post tweet, follow, home timeline, search in/out of scope. |
| Estimate | Tweets/sec, timeline reads/sec, storage growth. |
| APIs | postTweet, getHomeTimeline, followUser. |
| Fan-out choice | Write-time push for normal users; pull/hybrid for celebrities. |
| Scale pieces | Sharded tweet store, timeline cache, load balancers. |
Weak vs strong answers
Weak
Everyone’s tweets go into one big database.
Strong
I’d shard tweets, precompute home timelines for most users, and for accounts with millions of followers I’d switch to fan-out-on-read or a hybrid - here’s the tradeoff…
How to say the key terms
| Term | Say it |
|---|---|
| fan-out-on-write | “fan-out on write” |
| celebrity / hot key | “hot key problem” |
Follow-up questions you will get
Expect these
- “How do you handle a user who follows 10,000 accounts?”
- “Where does ranking happen?”
Practice drill
Set a timer for twelve minutes. Design Twitter/X timeline design out loud in English. Record yourself. Check: clarify, estimate, tradeoffs, bottlenecks.
Repeat tomorrow focusing only on the deep-dive section.
Answer frameworks you can reuse
Clarify → APIs → Estimates → Data model → High-level → Deep dive → Bottlenecks.
For every deep dive: options → tradeoffs → recommendation.
Technical Software Interview English knowledge base
← Technical Software Interview English knowledge base - start at How to Walk System Design Interviews 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 Technical Software Interview 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 Walk System Design Interviews in English | system-design-interview-seven-steps-in-english |
| 2 | How to Design Pastebin in English Interviews | pastebin-system-design-in-english |
| 3 | How to Design Instagram in English Interviews | instagram-system-design-in-english |
| 4 | How to Design Twitter Timeline in English (you are here) | twitter-system-design-in-english |
| 5 | How to Design Yelp Nearby Search in English | yelp-nearby-system-design-in-english |
| 6 | How to Design Uber Dispatch in English | uber-system-design-in-english |
| 7 | How to Design Ticketmaster in English | ticketmaster-system-design-in-english |
| 8 | Long Polling vs WebSockets vs SSE in English | long-polling-websockets-sse-in-english |
- How to Walk System Design Interviews in English
- How to Design Pastebin in English Interviews
- How to Design Instagram in English Interviews
- How to Design Twitter Timeline in English - you are here
- How to Design Yelp Nearby Search in English
- How to Design Uber Dispatch in English
- How to Design Ticketmaster in English
- Long Polling vs WebSockets vs SSE in English
FAQ
Questions
More questions? Email us at contact@mocklyenglish.com.