← Back to Directory

Dropbox

Large Enterprises

Screna has 17 Dropbox interview write-ups. The most reported round is the technical phone screen (8).

17 interview notes · updated Jun 2026

Dropbox·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Dropbox system design round, picking up mid-conversation from a previous scaling discussion. The task was to implement an async file crawler with a work queue, worker pool, and result aggregation, all from a provided scaffold. Less about architecture from scratch, more about getting the concurrent control flow right under pressure.
  • Given a scaffold for an async file crawler, implement the task scheduling, work queue, worker pool, and result aggregation. The focus is on correct concurrent control flow, backpressure handling, and graceful shutdown.

“The scaffold part threw me a little.”

View Post

Dropbox·Software Engineer·Technical Phone Screen

Jun 2026
Dropbox coding screen for a software engineer role. The problem was a classic in-memory banking system, Level 1 style, so basically just getting the plumbing right before things get complicated.
  • Build a simple in-memory bank system that supports creating accounts, depositing money, and transferring funds between accounts. Handle edge cases like missing accounts and insufficient balances.

“Spent the first few minutes just mapping out what state I needed to track.”

View Post

Dropbox·Software Engineer·Technical Phone Screen

Jun 2026
Dropbox SWE interview that took the classic word-guessing game and made it adversarial. The twist was interesting enough that I kept second-guessing whether I was even solving the right problem.
  • You're building a word-guessing game where the word-selector is adversarial and can swap the secret word mid-game, as long as the new word stays consistent with all prior hit/miss feedback. The guesser wants to minimize the worst-case number of guesses. What's the strategy, and can you write pseudocode for it?

“The adversarial framing is what got me.”

View Post

Dropbox·Software Engineer·Technical Phone Screen

Jun 2026
Dropbox SWE interview with a two-part question that started as a coding problem and then pivoted hard into distributed systems design. The coding part felt manageable but the follow-up was where things got real.
  • Write a file system crawler that starts from a root directory, walks through all files and subdirectories, and processes each one (e.g. compute size, hash, or extract metadata).
  • Now redesign that crawler as a distributed system. You need a database to track discovered nodes and their processing state, an API layer for accepting crawl requests, and an async worker service. The key twist: a worker processing a directory can discover subdirectories and enqueue new async jobs for those. How do you handle exactly-once processing, cycles, retries, and concurrency bounds?

“Pretty standard recursive traversal.”

View Post

Dropbox·Software Engineer·Onsite - System Design / Architecture

May 2026
Dropbox system design round, one question the whole time: build a thread-safe token bucket rate limiter. Felt manageable at first but the concurrency and edge case discussion dragged on longer than I expected.
  • Design and implement a thread-safe Token Bucket rate limiter that supports concurrent access from multiple clients, with a fixed capacity, a configurable refill rate, and an allow() method that returns whether a request can proceed.

“The basic structure came to me fast: store lastRefillTime and currentTokens, recompute tokens lazily on each call using elapsed time instead of running a background thread.”

View Post

Dropbox·Software Engineer·Technical Phone Screen

May 2026
Dropbox SWE interview that leaned pretty heavily on recursive tree construction. The Fibonacci tree problem was the main focus and they wanted more than just code, they pushed on complexity analysis too.
  • Implement a Fibonacci tree: T(0) and T(1) are single nodes, and for n >= 2, T(n) has T(n-1) as its left subtree and T(n-2) as its right subtree. Build the tree for a given n, then discuss its size, height, leaf count, and time/space complexity.

“The recursive definition feels clean on paper but I kept second-guessing whether I was double-counting nodes since the subtrees share structure conceptually.”

View Post

Dropbox·Software Engineer·Onsite - System Design / Architecture

May 2026
Dropbox system design round, no coding, just a whiteboard conversation about scaling a file crawler from single-machine to distributed. The scope was wide and they clearly wanted to see how you reasoned through tradeoffs rather than recite a textbook answer.
  • You have a working single-machine file crawler that walks a directory tree and processes files. How would you scale it to handle much larger workloads? Walk through your concurrency model, how you'd partition the file space, queueing and dispatch, deduplication, fault tolerance and retries, throttling, and what metrics you'd track.

“This question ate up the entire session.”

View Post

Dropbox·Software Engineer·Onsite - System Design / Architecture

May 2026
Dropbox system design round, one meaty question about building a key-value store with hit counting baked in. Took longer than I expected to get through all the follow-ups and I'm not totally sure I nailed the scaling piece.
  • Design a key-value store that tracks how many times each key is accessed, supports querying a key's hit count, and can return the top-N most-accessed keys. Discuss data structures, concurrency handling, time-window variants, and horizontal scaling.

“Started with the obvious hashmap for key-to-count, then they pushed me on top-N and I went straight to a min-heap of size N which felt right.”

View Post

Dropbox·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round at Dropbox for a software engineering role. The format was more conversational than I expected, basically a deep dive into one project with the interviewer following up on specific details rather than moving through a list.
  • Walk me through one of your major projects from start to finish.
  • What was the most surprising finding you came across during that project?
  • Did anything turn out differently from what you originally expected, and how did you adjust?
  • Can you talk about your career path so far and where you see yourself heading?

“This was the anchor for the whole conversation.”

View Post

Dropbox·Software Engineer·Technical Phone Screen

Apr 2026
Dropbox software engineer interview with a filesystem traversal coding problem. Pretty focused on the implementation details and the tradeoffs around recursion vs iteration, which I wasn't fully prepared to articulate on the spot.
  • Implement a function that recursively lists all files under a given path, using only a provided helper that returns a path's immediate children. Discuss your choice of iterative vs recursive traversal and analyze the complexity.

“I went recursive first because it felt cleaner to write, and the interviewer pretty quickly asked what happens on a very deep directory tree.”

View Post