Design a Notification System
Candidates have reported this prompt twice. A senior engineer in a US loop in 2025 got it as the system design round, between a Go concurrency challenge and calls with the hiring manager and a director. A candidate in a September 2026 onsite got it as the second of two design rounds. In that one the interviewer pasted the requirements in a single block and set the load at about a million writes a second, arriving in bursts. The candidate's first estimate said the data would fit in Postgres. The interviewer pushed back, and the discussion moved to Kafka, Cassandra and why Cassandra writes are fast.
A notification system does three jobs. It accepts a request to tell someone something. It works out who should hear it and on which channels. Then it hands each message to a delivery provider, such as an email service, an SMS gateway or a mobile push service. The million a second makes the first job hard. The providers make the third one hard, because they accept far less than that and throttle you when you push. Most of the design deals with the gap between the two.
Draw one boundary early. The monitoring service design decides whether a node is really down and whether to page anyone. This design starts after that decision. It's how the notice reaches people, so leave the up and down logic where it lives.
CoreWeavePremium lesson · System design round
The CoreWeave design, worked end to end.
- Requirements and scopeSystem design · Frequently asked
- The API and data model
- The design, drawn out1 diagram
- 5 deep divesWith the tradeoffs
$49 a year · all 107 companies · instant access
20,000+ candidate reports · guide updated
CoreWeave interview guideKnow what CoreWeave asks before you walk in.
8 coding · 4 system design · 15 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.