System Design File Storage and Sync: Interview Talk Track

System Design File Storage and Sync: Interview Talk Track

"Design a cloud file storage and sync service" asks you to build something most people use every day: upload a file on one device, see it on another, share it with a teammate. It's a rich prompt because it combines large binary data, metadata consistency, synchronization across devices, and conflict handling.

This system design file storage interview guide gives you a talk track for a 45-minute round. Use it as a skeleton, and let the interviewer choose where to go deep.

1. Clarify requirements (about 5 minutes)

Functional:

Non-functional:

State assumptions out loud: "I'll assume hundreds of millions of users, files from a few kilobytes to several gigabytes, read-heavy access, and very high durability requirements."

2. Key idea: separate metadata from content

Say this early, because the rest of the design builds on it:

Metadata is small and queried often. Content is huge and mostly immutable. They have different scaling and consistency needs, so they should live in different systems.

3. Chunking

Split each file into chunks, for example a few megabytes each, and identify each chunk by a hash of its content.

Benefits:

A file version becomes an ordered list of chunk hashes. Mention that fixed-size chunks are simple, while content-defined chunking handles insertions in the middle of a file better, at some cost in complexity.

4. Upload flow

  1. The client splits the file into chunks and computes hashes.
  2. It asks the metadata service which chunks are already stored.
  3. It uploads only the missing chunks to blob storage, ideally using short-lived pre-signed URLs so bytes skip the application servers.
  4. It commits a new file version to the metadata service: file ID, parent folder, chunk list, and the version it was based on.
  5. The metadata service records the version and publishes a change event.

The commit in step 4 is what makes the new version visible, so a half-finished upload never appears as a corrupted file.

5. Sync across devices

Each client needs to learn about changes quickly.

This "notify, then pull from a cursor" approach is robust: if a notification is lost, the next poll still catches up.

6. Conflicts

Two devices edit the same file while one is offline. What happens?

Mention that real-time collaborative editing of documents is a different problem with different techniques, and that you're designing file-level sync. That scoping shows judgment.

7. Sharing and permissions

8. Scaling

9. Durability and failure handling

10. Wrap-up

Summarize: metadata separated from content, content-addressed chunks for dedup and delta sync, a commit step for atomic versions, a change log with notifications for sync, conflict copies for concurrent edits, and replication plus careful garbage collection for durability. Offer extensions: search across files, thumbnail previews, or storage quotas.

Practice the talk track out loud

This design has many moving parts, so structure is everything. Rehearse the outline with a timer and practice switching gears when the interviewer asks you to go deep on chunking or conflicts. Luna Interview gives you a structured place to practice that kind of spoken walkthrough and stay calm under follow-up questions.

Talk track checklist