← Reddit Interview InsightsSoftware Engineer

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

Senior
Jun 2026

Summary

Reddit system design round, one big question about building a live chat system from scratch. Pretty open-ended and they clearly wanted to see how far you could push the design before running out of ideas.

Questions Asked (1)

Q1

Design a live chat system that supports both 1:1 and group conversations, including message delivery, ordering, presence indicators, read receipts, message history, and offline/push notification support.

System DesignTechnical Trade-offsData Modeling
Author's notes

This one sprawls fast.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and scale (e.g., number of concurrent users, message volume, latency expectations). Then propose a high-level architecture with separate services for connection management, message routing, storage, and notifications. Dive into data modeling for conversations and messages, and discuss trade-offs for delivery guarantees, ordering, and presence.

Pro tip: Emphasize idempotency and exactly-once semantics for message delivery, and discuss how to handle out-of-order messages using sequence numbers or timestamps. Also, mention the importance of backpressure and rate limiting to prevent abuse.

1. Clarify Requirements and Scale

Ask questions to understand functional and non-functional requirements: number of users, message throughput, latency, consistency needs, and supported platforms. Estimate scale to inform design decisions.

2. High-Level Architecture

Outline core components: WebSocket gateways for real-time connections, a message service for routing and persistence, a presence service, a notification service, and databases for messages and metadata. Explain how they interact.

3. Data Modeling and Storage

Design schemas for users, conversations (1:1 and group), messages, and read receipts. Choose appropriate databases (e.g., Cassandra for messages, Redis for presence) and discuss partitioning and indexing strategies.

4. Message Delivery and Ordering

Describe how messages are delivered reliably: use message queues, sequence numbers for ordering, and acknowledgments. Discuss at-least-once vs exactly-once delivery and how to handle duplicates and out-of-order messages.

5. Presence, Read Receipts, and Notifications

Explain presence tracking using heartbeats and pub/sub, read receipt propagation, and offline notification via push services. Discuss trade-offs between consistency and latency for these features.

Key Points to Mention

  • WebSocket vs long polling for real-time communication and connection management at scale.
  • Message ordering using sequence numbers per conversation and handling out-of-order delivery.
  • Data partitioning strategies for message storage (e.g., by conversation ID) to ensure scalability.
  • Presence indicators using heartbeat mechanisms and pub/sub (e.g., Redis) with TTL.
  • Read receipts: how to efficiently update and propagate read status to all participants.
  • Offline support: push notifications (APNs/FCM) and message queuing for offline users.

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