Dropbox Software Engineer interview questions

27 Software Engineers have shared notes from their Dropbox interviews, with the questions they were asked in each round. That is 59% of the 46 Dropbox interview notes on Screna AI.

27 Software Engineer interview notes

Dropbox·Software Engineer·Technical Phone Screen

Jul 2026
Dropbox SWE interview with a file system access problem. Pretty well-scoped question but the follow-up about efficiency tripped me up more than I expected.
  • Design and implement a HasAccess function for a hierarchical file system where access to a folder is inherited by all its descendants. Given a set of directly accessible folders, return whether a user can access a given folder path.

“My first instinct was to just check if the path is in the set, which is obviously incomplete.”

View Post

Dropbox·Software Engineer·Onsite - System Design / Architecture

Jul 2026
Dropbox system design round, one meaty question that took up the whole session. The problem sounds straightforward until you're actually in it trying to juggle concurrency, data structures, and distributed scaling all at once.
  • Design a key-value store that also tracks how many times each key has been accessed. It should support querying a key's hit count and returning the top-N most-accessed keys, both over all time and optionally over a sliding time window. Walk through your data structure choices, how you'd handle concurrency, and how the system scales horizontally.

“I started with the obvious hashmap for O(1) gets and a max-heap for top-N, which felt fine until they pushed on the sliding window part.”

View Post

Dropbox·Software Engineer·Technical Phone Screen

Jul 2026
Dropbox software engineer interview with a coding round built around implementing the core feedback logic for a Wordle-style game. Pretty clean problem once you break it down, but the misplaced match counting tripped me up at first.
  • Implement the feedback function for a word-guessing game: given a dictionary of valid words, a secret word, and a player's guess, return the number of exact position matches and the number of misplaced (right letter, wrong position) matches. Invalid guesses should be signaled clearly.

“The exact match part is straightforward, just zip the two strings and count.”

View Post

Dropbox·Software Engineer·Technical Phone Screen

Jun 2026
Dropbox technical phone screen for a software engineer role, centered on a pretty gnarly adversarial word-guessing problem. The question had layers and pushed into algorithm design and pseudocode territory, which I wasn't fully warmed up for.
  • You have a word-guessing game where the word-selector is adversarial and can secretly swap the target word mid-game, as long as the new word stays consistent with all previously revealed hits and misses. How does the guesser minimize the worst-case number of guesses? Walk through your strategy and write pseudocode.

“This wrecked me a little.”

View Post

Dropbox·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Dropbox SWE interview with a system design question about ID management. Pretty focused problem, not a lot of fluff around it.
  • Design a module that allocates unique User IDs from a shared pool and reclaims them when they're released back for reuse.

“My first instinct was a simple counter but they pushed back pretty fast on that.”

View Post

Dropbox·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at Dropbox for a software engineering role, pretty much one big deep-dive question about a past project. Left feeling like I either crushed it or completely missed the point.
  • Walk me through a significant project you owned. What surprised you during it, what turned out differently than expected, and how did that change what you did next?

“This is the kind of question that sounds easy until you're actually in it and realize they want everything: context, your specific role, the decisions you made, the results, and then some reflection on how it shaped you afterward.”

View Post

Dropbox·Software Engineer·Technical Phone Screen

Jun 2026
Got a Dropbox SWE problem that's basically adversarial Wordle with a twist: the host can swap the hidden word after each guess as long as it stays consistent with what's been revealed. Took me a while to even understand what 'optimal' meant here since you're not just solving a word, you're forcing the adversary into a corner.
  • You have a set of distinct lowercase words of equal length. An adversarial host picks one but can switch to any consistent word after each guess. Each turn you guess one new letter and the host reveals where it appears (or says it's absent if some valid word lacks it). What is the minimum number of letter guesses needed to guarantee identifying the hidden word, assuming optimal guessing strategy?

“This one messed with my head for a bit.”

View Post

Dropbox·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Dropbox system design round focused entirely on building a distributed file system crawler. Pretty deep dive, they wanted the full picture from APIs down to failure handling and client-facing progress reporting.
  • Design a distributed service that crawls a large file system from a root path, where a client can start a crawl job via API and background workers traverse directories asynchronously, recursively spawning child tasks as needed.
  • What does the data model look like for crawl jobs, individual crawl tasks, and the file metadata you discover along the way?
  • How do workers recursively schedule child tasks when they encounter subdirectories during a crawl?
  • How would you handle retries, idempotency, and deduplication so that partial failures don't corrupt the crawl state or cause duplicate processing?
  • How would you scale this system to handle very large directory trees with potentially millions of files and thousands of concurrent tasks?
  • How do you expose crawl progress and final results back to the client?

“This was the whole interview, basically.”

View Post

Dropbox·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Dropbox system design round, no coding, just a whiteboard conversation about scaling a file crawler. The interviewer wanted to go pretty deep on every layer of the design and I felt underprepared for how far into the weeds they wanted to go on fault tolerance specifically.
  • You have a working single-machine file crawler that walks a directory tree and processes files. How would you scale it to handle a much larger workload? Walk through your concurrency model, how you'd partition the file space, queuing and dispatch, deduplication, fault tolerance and retries, throttling, and what metrics you'd track.

“This is basically a distributed systems design question dressed up as a file crawler question.”

View Post

Dropbox·Software Engineer·Technical Phone Screen

May 2026
Dropbox coding round, extending a bank system with a ranking function. Pretty focused problem, felt like a Level 2 follow-up where they want to see if you can handle aggregation logic without getting sloppy about what counts as outgoing.
  • Given an existing bank system, add a topNOutgoing(n) method that returns the top N account IDs ranked by total outgoing spend. Only transfers and payments sent out should count, not incoming deposits or transfers. Break ties by account ID.

“The tricky part is being precise about what counts as outgoing.”

View Post