Design a Search for Slack
Last updated: June 6, 2026
Quick Overview
Design a event-driven search system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Slack
June 6, 20263
13
1,953 solved
Design a event-driven search system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
This is a common system design question asked during Technical Screen at Slack. The interviewer expects you to demonstrate your ability to design large-scale distributed systems, make well-reasoned trade-offs, and communicate your thought process clearly. Slack values engineers who can think about scalability from day one.
What the Interviewer Expects
- Systematically gather requirements and estimate capacity (QPS, storage, bandwidth)
- Design a scalable architecture with clear component responsibilities
- Make well-reasoned database and caching decisions with trade-off analysis
- Address consistency vs availability trade-offs specific to the use case
- Discuss partitioning strategy, replication, and data modeling
- Cover failure handling, monitoring, and alerting strategies
Key Topics to Cover
How to Approach This
- Start by clarifying functional and non-functional requirements with the interviewer.
- Estimate the scale: QPS, storage, bandwidth. This drives your design decisions.
- Draw a high-level architecture first, then deep dive into 1-2 critical components.
- Discuss trade-offs explicitly (e.g., consistency vs availability, SQL vs NoSQL).
- Address failure scenarios, monitoring, and how the system handles 10x traffic spikes.
Possible Follow-up Questions
- What would the deployment pipeline look like for this system?
- How would you handle a 10x increase in traffic overnight?
- How would you handle a region-wide outage?
- What monitoring and alerting would you set up on day one?
Practice a Similar Problem on Codemia
Solve a related problem with our interactive workspace, get AI feedback, and view detailed solutions.
Solve on CodemiaSample Answer
Requirements
- Functional Requirements:
- Ability to search messages, files, and channels in real-time.
- Support for filtering search results by user, date, or channel.
- Autocomplete suggestions while ...
Capacity Estimation
- User Base: Assuming 10 million active users.
- Search Requests: If each user performs 5 searches per day, that's 50 million search requests daily.
- QPS Calculation:
- 50 million reque...
Submit Your Answer
