Design a multi-tenant Image Processing System

Last updated: August 11, 2025

Quick Overview

Design a multi-tenant image processing system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

Slack
System Design
Software Engineer
Slack
August 11, 2025
Software Engineer
Onsite
System Design
Hard

8

6

1,155 solved


Design a multi-tenant image processing system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

System design interviews at Slack 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
Consistency models and replication
API design and rate limiting
Monitoring, logging, and alerting
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 migrate from a monolithic to a microservices architecture?
  • What monitoring and alerting would you set up on day one?
  • How would you implement rate limiting to protect the system?
  • How do you ensure data consistency across multiple services?
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. Multi-Tenant Support: The system should support multiple tenants (i.e., different Slack workspaces) securely and efficiently.
  2. Image Processing: Support variou...
Capacity Estimation

Assuming Slack has around 12 million daily active users, with each user making an average of 5 image processing requests per day:

  • Total Requests per Day: 12M users * 5 requests = 60M requests/da...

Submit Your Answer
Markdown supported

Related Questions