Design a Chat for Confluent

Last updated: September 25, 2025

Quick Overview

Design a scalable chat system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

Confluent
System Design
Software Engineer
Confluent
September 25, 2025
Software Engineer
Technical Screen
System Design
Hard

7

13

2,407 solved


Design a scalable chat system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

System design interviews at Confluent typically last 45-60 minutes. You are expected to drive the conversation, starting from requirements gathering through to a detailed architecture. The interviewer will evaluate your ability to handle ambiguity and make practical engineering decisions.

What the Interviewer Expects
  • Drive the design discussion proactively with minimal interviewer guidance
  • Perform detailed capacity estimation and use it to inform design decisions
  • Design for global scale with multi-region deployment and data consistency
  • Deep dive into 2-3 critical components with implementation-level detail
  • Address complex trade-offs: CAP theorem, eventual consistency, conflict resolution
  • Discuss operational excellence: deployment strategy, chaos engineering, SLOs/SLIs
  • Propose a phased rollout plan from MVP to full-scale system
Key Topics to Cover
Security and authentication
Requirements gathering and capacity estimation
Partitioning and sharding strategies
Failure handling and fault tolerance
High-level architecture and component design
How to Approach This
  1. Start by clarifying functional and non-functional requirements with the interviewer.
  2. Estimate the scale: QPS, storage, bandwidth. This drives your design decisions.
  3. Draw a high-level architecture first, then deep dive into 1-2 critical components.
  4. Discuss trade-offs explicitly (e.g., consistency vs availability, SQL vs NoSQL).
  5. Address failure scenarios, monitoring, and how the system handles 10x traffic spikes.
Possible Follow-up Questions
  • How would you implement rate limiting to protect the system?
  • How would you optimize costs as the system scales?
  • What would the deployment pipeline look like for this system?
Practice a Similar Problem on Codemia

Solve a related problem with our interactive workspace, get AI feedback, and view detailed solutions.

Solve on Codemia
Sample Answer
Requirements

Functional Requirements

  1. Real-time Messaging: Users should be able to send and receive messages in real-time with low latency.
  2. Group Chats: Support for one-on-one chats and group chat...
Capacity Estimation

Assuming Confluent has 1 million active users, we estimate:

  • Peak Concurrent Users: 10% (100,000 users)
  • Messages per User per Day: 50
  • Total Messages per Day: 100,000 users * 50 messag...

Submit Your Answer
Markdown supported

Related Questions