Quick Answer
Chat system interview phrases in English: explain one-to-one and group paths, presence, and delivery states — then say how you keep message order under load.
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
Client ↔ chat gateway ↔ message service ↔ store.
What to say on figure 2
Show online push vs offline sync.
What to say on figure 3
Show group fan-out.
What to say on figure 4
Show presence service beside the gateway.
Key vocabulary
| Term | Plain meaning | Say it in an interview |
|---|---|---|
| WebSocket | Long-lived client connection | “Clients stay connected over WebSockets.” |
| Presence | Online/offline status | “Presence shows who is online.” |
| Delivery receipt | Server/device got the message | “We mark the message as delivered.” |
| Unread count | Count of unseen messages | “Each inbox keeps an unread count.” |
ESL English phrases and transitions
Clarify
- “One-to-one only, or groups too?”
- “Do we need read receipts and media attachments?”
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 |
|---|---|---|
| Polling-only design | High latency | Prefer push for online users |
| Ignoring ordering | Confusing UX | Mention per-chat ordering briefly |
| Summary | Every new box needs one spoken reason. | |
Common English mistakes
| Mistake | What the interviewer concludes | Better English |
|---|---|---|
| No persistence | Messages vanish | “We store before acknowledging success.” |
| Group as afterthought | Missed scale | Call out large-group fan-out cost |
What the interviewer is testing
This is a communication test as much as a design test. Can you explain a chat 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
- “One-to-one only, or groups too?”
- “Do we need read receipts and media attachments?”
Watch Out
Do not open with a finished architecture. Show the path.
Chat system design
Use this sequence for chat system design. For each stage, say what changes, why, and what can still go wrong.
Connect
Clients maintain a connection; a gateway maps user → server.
Send 1:1
Store message, push to recipient if online, else queue for sync.
Groups
Fan-out to members carefully; watch large-group cost.
Presence & receipts
Heartbeat for presence; delivered/read states on messages.
Weak vs strong answers
Weak
“Use socket.io.”
Strong
“Clients connect through a gateway that tracks presence; messages are persisted first, then pushed to online recipients.”
Metrics and how to say numbers
| Write | Say |
|---|---|
| message latency | end-to-end message latency |
| online connections | concurrent online connections |
Follow-up questions you will get
Likely follow-ups
- “How do offline users catch up?” → “They sync from a cursor/last-seen message ID on reconnect.”
Practice drill
Checklist
- Connect
- 1:1 send
- Group note
- Receipts
“If you can explain a chat 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 | how-to-explain-a-news-feed-in-english |
| 12 | Chat System Interview Phrases in English (ESL) (you are here) | 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
- Chat System Interview Phrases in English (ESL) — you are here
- 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.