Design a Task Scheduling for Dropbox

Last updated: May 11, 2026

Quick Overview

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

Dropbox
System Design
Software Engineer
Dropbox
May 11, 2026
Software Engineer
Onsite
System Design
Medium

10

8

4,907 solved


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

Dropbox asks this during the Onsite to assess your architectural thinking. They want to see how you decompose a complex problem, choose appropriate technologies, and reason about failure modes. Strong candidates proactively discuss monitoring, alerting, and operational concerns.

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
Consistency models and replication
Database selection and data modeling
Message queues and async processing
Failure handling and fault tolerance
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 do you ensure data consistency across multiple services?
  • What monitoring and alerting would you set up on day one?
  • How would you handle schema migrations with zero downtime?
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. Task Creation: Users can create tasks with metadata (name, description, priority, due date).
  2. Task Scheduling: Tasks should be scheduled to execute at a specif...
Capacity Estimation

Back-of-Envelope Calculations

  1. User Base: Assume 1 million active users.
  2. Task Submissions: Each user submits an average of 10 tasks per day, leading to a total of 10 million tasks da...

Submit Your Answer
Markdown supported

Related Questions