Dropbox

Large Enterprises

Most of these Dropbox write-ups come from Software Engineers (27), then Product Managers (13) and Data Scientists (4). The most reported rounds are the technical phone screen (15), the product sense round (12), the system design round (11) and the behavioral / leadership round (5).

46 interview notes · updated Jul 2026

Dropbox·Data Scientist·Technical Phone Screen

Jul 2026

Dropbox data scientist interview with a deep experimentation design question focused on their file recommender system. Single question but it covered basically every dimension of experiment design you can think of, from randomization unit to alpha spending to Simpson's paradox. Dense.

Design an online experiment to evaluate a file recommender system in production across multiple organizations, where users within the same org can influence each other's behavior. Cover: primary metrics, secondary metrics, guardrails, randomization unit, clustering and ICC assumptions for sample size, variance reduction, sequential monitoring, ramp schedule, novelty/carryover controls, logging for exposure and attribution, a difference-in-differences fallback if full randomization isn't possible, and stop/ship criteria including how to handle Simpson's paradox across tenants and roles.

“This was a lot.”

View Post

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·Machine Learning Engineer·Onsite - Behavioral / Leadership

Jul 2026

Behavioral research deep-dive for an MLE role at Dropbox. The whole thing was about an hour and they just kept pulling on the same thread, so you can't really rehearse your way out of it.

Walk me through a past research project. What problem were you solving and why did it matter?
What other approaches did you consider before settling on your method, and what made you choose the one you did?
How did you design and validate your experiments for that project?
What trade-offs did you make during the project and what drove those decisions?
What failed during the project and what did you take away from it?
If you were starting this project over from scratch today, what would you do differently?

“This is where I started strong but probably oversold the impact.”

View Post

Dropbox·Product Manager·Onsite - Product Sense / Strategy

Jul 2026

PM interview at Dropbox with a market sizing question about Airbnb's revenue. Pretty standard case-style prompt but it requires you to actually know how to structure a bottom-up estimate without falling apart mid-calculation.

Estimate Airbnb's annual revenue.

“I started with supply side (number of listings, occupancy rates, average nightly price) and worked toward a GMV number before applying a take rate.”

View Post

Dropbox·Product Manager·Onsite - Product Sense / Strategy

Jul 2026

Short Dropbox interview, just one question about how you'd handle shutting down a product or feature. Not much else to go on.

How would you go about sunsetting a product or feature?

“This one tripped me up more than it should have.”

View Post

Dropbox·Data Scientist·Technical Phone Screen

Jun 2026

Dropbox data scientist interview where the main event is a deep project walkthrough, basically 8-10 minutes of you defending every decision you ever made, followed by two follow-ups designed to find the cracks in your story.

Walk me through one significant project from your resume: the problem, business goal, your specific role, key design decisions you made and alternatives you rejected, and the quantified outcomes.
What were the riskiest assumptions in your project, and how did you validate or retire them before they became real problems?
How did you measure the impact of your project causally, not just correlationally? What were the limits of your measurement approach?
Where does your system or model break down at scale? Give me concrete numbers on the limits you know about.
How did you handle security or privacy constraints in your project, and did those constraints change any of your technical decisions?
What failed during the project and how did you recover? Be specific about what you got wrong and what you changed.

“This is the bulk of the interview and you really do need to go 8-10 minutes without them stopping you.”

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·Product Manager·Onsite - Product Sense / Strategy

Jun 2026

Got a product design question for a PM role at Dropbox. Pretty open-ended, which I wasn't fully prepared for.

How would you design a car stereo?

“I fumbled the opening because I jumped straight into features before asking any clarifying questions.”

View Post

Dropbox interview FAQ

What rounds are in the Dropbox interview?

Candidates most often report a technical phone screen (15 write-ups), a product sense round (12), a system design round (11) and a behavioral / leadership round (5).

What does the Dropbox technical phone screen cover?

Across 15 technical phone screen write-ups, the most tagged question topics are Technical Trade-offs (16 questions), Algorithms & Data Structures (14) and System Design (11).

What is asked in the Dropbox product sense round?

Across 12 product sense write-ups, the most tagged question topics are Product Analytics & Metrics (8 questions), Product Strategy (7) and Product Sense & Ideation (4).