Design a notification service
Send push, email and SMS notifications for every product team, reliably and at the right time.
Functional requirements
- Send to one user or to millions
- Push, email and SMS channels
- Users choose which notifications they get
Non-functional requirements
- Notifications are never silently dropped
- Urgent ones arrive within seconds
- One provider’s outage doesn’t block other channels
Scale
- 1B notifications per day
- Campaigns send to 100M users at once
- Providers limit how fast we can send
How you’ll be scored
12 checks covering your diagram and your notes, and any valid approach counts. Hints appear for anything you miss. Common mistakes, such as single points of failure or components you never explain, cost points. How grading works
What interviewers look for
- Clarify before you draw. State what is in and out of scope. For “Design a notification service”, that starts with: Send to one user or to millions; Push, email and SMS channels; Users choose which notifications they get. Interviewers notice candidates who pin the requirements down first.
- Turn the scale into numbers. The scale (1B notifications per day; Campaigns send to 100M users at once; Providers limit how fast we can send) should become requests per second, storage and bandwidth, and those figures should drive your choices. Estimates with units carry more weight than adjectives.
- Show how each quality is met. Your design should visibly deliver: Notifications are never silently dropped; Urgent ones arrive within seconds; One provider’s outage doesn’t block other channels. Saying that it does isn’t enough; point to the part of the design that makes it true.
- Expect follow-ups on the hard parts. Interviewers usually probe queues, fan-out and retries here. This is a medium problem, so interviewers expect you to weigh two reasonable options, such as consistency against latency, and to say why you picked one.
- Explain failure and trade-offs. Say what happens when a component fails, where a single point of failure would hurt, and what you chose not to build. Naming a trade-off is a stronger answer than claiming there isn’t one.