Design at-least-once notification delivery
GoogleSoftware Engineer · Technical Screen
Last updated
This question evaluates expertise in reliable distributed systems design, including at-least-once delivery semantics, idempotency and deduplication strategies, retry and dead-letter handling, API and message-schema design, ordering and out-of-order handling, and scalability for high-throughput multi-tenant notification platforms.
Design a notification system that guarantees at-least-once delivery. Define producer and consumer interfaces, deduplication keys, retry with exponential backoff, out-of-order handling, and user-facing idempotency to avoid duplicates.
Solution walkthrough is for members
Get the full walkthrough with reference code and complexity analysis, plus Kitty Coach at 300 messages a day. Hints, the code runner and community answers stay free.