Mock Interviewer

Ask Coach

Ask Coach
Clarify requirements before you design — kept separate from your stage notes.

Tap a question to start, or type your own below.

Dropbox System Design

Visual Problem Diagram

Dropbox System Design architecture diagram

Scenario

A user uploads a 10 GB video on hotel Wi-Fi—the upload must resume after disconnect while another device still shows "syncing" with the wrong version until metadata catches up. Chunked storage, revision sync, and conflict copies define Dropbox-class design.

Design a cloud file sync product where files are split into chunks, stored in object storage, and synchronized across devices with a clear metadata model. Users blame data loss and silent conflicts—your design must address resume, revision, and conflict UX.

You should support folder tree, upload/download, delta sync, sharing, and conflicts. Be ready to explain content-defined chunking and revision-based sync.

Constraints

Functional

Folders/files, chunked upload, sync, share links, conflict copies, delete/trash

Non-functional

99.999999999% durability (11 nines) goal for blobs, resume uploads, sync seconds-level, ACL enforced

Scale

700M users, exabytes storage, billions files, viral share links

Stages ahead

1Requirement Analysis
2API Design
3High-Level Design
4HLD Extensions
5Trade-offs

Log in to start practicing

Preview the problem below. Sign in to start your timed session, save progress, and use the AI coach.