AI InterviewGet started

Design a Notification System: System Design Practice

Design a Notification System as a system design interview question: Send push, SMS and email notifications for many product events, honouring each user's…

How do you answer "Design a Notification System" in a system design interview?

Services send events to a notification service, which checks the user's preferences, quiet hours and rate limits, renders a template and puts a job on a queue per channel. Workers for push, SMS and email call the providers (APNs/FCM, an SMS gateway, an email service), retry temporary failures with backoff, and use idempotency keys so a duplicate event never notifies twice.

  • Level: Intermediate
  • Scored out of: 100
  • Cost: Free to read; a free account gets the review

Send push, SMS and email notifications for many product events, honouring each user's preferences.

The scale

10 million notifications a day with bursts of 10 times the average; three delivery channels.

What a strong answer covers

  1. Requirements (20 points). States the functional requirements in scope and the non-functional ones that drive the design (scale, latency, availability, consistency), and leaves out what is out of scope.
  2. Scale estimates (15 points). Turns the stated scale into requests per second (average and peak), storage and bandwidth, with the arithmetic shown, and uses the numbers to make a decision.
  3. API and data model (20 points). Defines the main API calls with their inputs and outputs, and a data model whose keys and store fit the access patterns.
  4. Architecture (25 points). Chooses components that fit the requirements and explains how a request moves through them, for the main read and write paths.
  5. Bottlenecks and trade-offs (20 points). Names the real bottlenecks and failure points at this scale and how the design handles them, weighing the alternatives (consistency vs availability, push vs pull, cost).

How the practice works

Write your design in sections — functional and non-functional requirements, scale estimates, the API, the data model, the request flow and a deep dive on the bottlenecks — and pick the components to draw the architecture. A review scores it on the five areas above in under a minute, then you can defend it in an AI mock interview.

The reference design

Design a Notification System: the walkthrough, with animated figures.

Common questions

How do you answer "Design a Notification System" in a system design interview?

Services send events to a notification service, which checks the user's preferences, quiet hours and rate limits, renders a template and puts a job on a queue per channel. Workers for push, SMS and email call the providers (APNs/FCM, an SMS gateway, an email service), retry temporary failures with backoff, and use idempotency keys so a duplicate event never notifies twice.

What scale is "Design a Notification System" designed for here?

10 million notifications a day with bursts of 10 times the average; three delivery channels. Your estimates turn that into requests per second, storage and bandwidth before you pick components.

How is a design scored?

Out of 100 on a fixed rubric: requirements (20), scale estimates (15), api and data model (20), architecture (25), bottlenecks and trade-offs (20). The review names what the design covered and what it missed, then points to the reference design.

Is "Design a Notification System" a good first system design problem?

It is rated intermediate. Start with the beginner problems — the URL shortener and the rate limiter — and the System Design notes on load balancing, caching and sharding first.

Do I need an account?

Not to read the problem or the reference design. Getting your design reviewed needs a free account.

More design problems