Quick Answer
How to explain a notification system in English: cover triggers, fan-out, channels, and retries — and say soft vs hard failure without dumping every vendor name.
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
Event → notification service → queue → channel workers.
What to say on figure 2
Show preference service check.
What to say on figure 3
Show push/email/SMS branches.
What to say on figure 4
Show retry / dead-letter path.
Key vocabulary
| Term | Plain meaning | Say it in an interview |
|---|---|---|
| Push notification | Mobile/web push message | “We send a push to the device.” |
| Fan-out | Expand one event to many recipients | “Fan-out creates per-user notification jobs.” |
| Idempotency | Safe to retry without duplicates | “Delivery must be idempotent.” |
| Quiet hours | Do-not-disturb window | “We suppress alerts during quiet hours.” |
ESL English phrases and transitions
Clarify
- “Which channels — push, email, SMS — and can users opt out?”
- “Is this soft alerts or hard transactional messages?”
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 |
|---|---|---|
| Sync fan-out in request path | Latency spike | “Fan-out is asynchronous via a queue.” |
| Infinite retries | User spam | “Backoff and a max retry limit.” |
| Summary | Every new box needs one spoken reason. | |
Common English mistakes
| Mistake | What the interviewer concludes | Better English |
|---|---|---|
| Vendor list as design | No architecture | Describe flow before vendors |
| No opt-out talk | Missed product risk | Mention preferences early |
What the interviewer is testing
This is a communication test as much as a design test. Can you explain a notification 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
- “Which channels — push, email, SMS — and can users opt out?”
- “Is this soft alerts or hard transactional messages?”
Watch Out
Do not open with a finished architecture. Show the path.
Notification system design
Use this sequence for notification system design. For each stage, say what changes, why, and what can still go wrong.
Trigger
An event enters the system (like, comment, payment).
Preferences
Filter by user settings and quiet hours.
Fan-out & queue
Create delivery jobs per user/channel.
Deliver & retry
Workers call providers; retry with backoff; avoid duplicates.
Weak vs strong answers
Weak
“We’ll use FCM and SendGrid.”
Strong
“Events go to a notification service that checks preferences, enqueues per-channel jobs, and retries failed deliveries without spamming duplicates.”
Metrics and how to say numbers
| Write | Say |
|---|---|
| delivery latency p95 | ninety-fifth percentile delivery latency |
| opt-out rate | opt-out rate |
Follow-up questions you will get
Likely follow-ups
- “How do you prevent duplicate pushes?” → “Idempotency keys per notification ID on the worker.”
Practice drill
Checklist
- Trigger
- Preferences
- Queue
- Retry English
“If you can explain a notification 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 (you are here) | 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)
- 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 — you are here
- 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.