ScaleCrafts

Design Dropbox

MediumFile syncObject storageChunking

Store files in the cloud and keep them in sync across all of a user’s devices, like Dropbox or Google Drive.

Functional requirements

  • Upload and download files up to 50 GB
  • Changes sync to all of a user’s devices
  • Share files and folders with others

Non-functional requirements

  • Files are never lost or corrupted
  • Small edits sync within seconds
  • Uploads resume after a dropped connection

Scale

  • 100M users, 1 PB of new data per month
  • About 200 files per user
  • Most edits change a small part of a file

How you’ll be scored

11 checks covering your diagram and your notes, and any valid approach counts. Hints appear for anything you miss. Common mistakes, such as single points of failure or components you never explain, cost points. How grading works

What interviewers look for

  • Clarify before you draw. State what is in and out of scope. For “Design Dropbox”, that starts with: Upload and download files up to 50 GB; Changes sync to all of a user’s devices; Share files and folders with others. Interviewers notice candidates who pin the requirements down first.
  • Turn the scale into numbers. The scale (100M users, 1 PB of new data per month; About 200 files per user; Most edits change a small part of a file) should become requests per second, storage and bandwidth, and those figures should drive your choices. Estimates with units carry more weight than adjectives.
  • Show how each quality is met. Your design should visibly deliver: Files are never lost or corrupted; Small edits sync within seconds; Uploads resume after a dropped connection. Saying that it does isn’t enough; point to the part of the design that makes it true.
  • Expect follow-ups on the hard parts. Interviewers usually probe file sync, object storage and chunking here. This is a medium problem, so interviewers expect you to weigh two reasonable options, such as consistency against latency, and to say why you picked one.
  • Explain failure and trade-offs. Say what happens when a component fails, where a single point of failure would hurt, and what you chose not to build. Naming a trade-off is a stronger answer than claiming there isn’t one.

Related problems

Loading your workspace…