← Pinterest Interview InsightsSoftware Engineer

Pinterest·Software Engineer·Onsite - System Design / Architecture·Senior

SeniorPrefer not to say
Jun 2026

Summary

Pinterest system design round focused entirely on building a notification system from scratch. Pretty deep dive, they wanted the full stack: API, storage, fan-out, delivery channels, the works.

Questions Asked (1)

Q1

Design an in-app notification system that supports real-time and persistent notifications (mentions, replies, system events), read/unread state, badges, notification history, and handles large-scale fan-out with durability, deduplication, and graceful degradation.

System DesignData ModelingTechnical Trade-offs
Author's notes

This one sprawled fast.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and scale, then propose a high-level architecture that separates real-time delivery (e.g., WebSocket) from persistent storage and fan-out processing. Dive into data modeling for notifications, read/unread state, and deduplication, and discuss trade-offs for large-scale fan-out, durability, and graceful degradation.

Pro tip: Emphasize idempotency and deduplication using unique notification IDs and consumer-side deduplication, as this is critical for exactly-once semantics in large-scale systems. Also, discuss how to handle read/unread state efficiently with write-optimized stores and caching.

1. Clarify Requirements and Scale

Ask about expected QPS, fan-out size, latency requirements, and consistency needs. Define functional requirements: real-time delivery, persistence, read/unread, badges, history, and deduplication.

2. High-Level Architecture

Propose a system with an ingestion service, message queue (e.g., Kafka), fan-out workers, real-time delivery service (WebSocket), and storage layers (e.g., Cassandra for notifications, Redis for unread counts).

3. Data Modeling and Storage

Design schemas for notifications (user_id, notification_id, type, content, timestamp, read_status) and unread counts. Choose storage optimized for write-heavy workloads and fast reads (e.g., Cassandra, DynamoDB).

4. Real-Time Delivery and Badges

Explain how to push notifications via WebSockets or long-polling, update badges in real-time, and handle offline users with persistent storage and sync on reconnect.

5. Scalability, Durability, and Degradation

Discuss partitioning, replication, deduplication (idempotent processing), and graceful degradation (e.g., fallback to polling, dropping non-critical notifications under load).

Key Points to Mention

  • Use of message queues (e.g., Kafka) for decoupling and handling fan-out spikes.
  • Deduplication via unique notification IDs and idempotent consumers.
  • Read/unread state management with write-optimized stores and caching (e.g., Redis for unread counts).
  • Real-time delivery mechanisms: WebSockets, SSE, or push notifications, with fallback to polling.
  • Data partitioning and replication strategies for scalability and durability.
  • Graceful degradation: prioritizing critical notifications, rate limiting, and circuit breakers.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.