Dropbox software engineer candidates report a CodeSignal-style online assessment, a recruiter call, then coding, code review, system design and behavioral rounds. Here is what to prepare for each stage.
$183K
Avg. Base Comp
$300K
Avg. Total Comp
4-5 rounds
Typical Rounds
Not reported
Process Length
Most candidates describe the online assessment as the first real filter. Several report a proctored CodeSignal test with four levels. Later levels build on earlier ones, and a stuck early level can block the rest. Reported tasks include filesystem and string work, an in-memory file-sharing or database design, and a banking-system exercise that rewards clean object-oriented structure. One candidate had to work inside a Django, Spring or ASP.NET service under a one-hour limit. Practice multi-stage problems without autocomplete and with documentation lookups limited.
After the assessment, candidates typically describe a recruiter call and then technical interviews. Several mention a code review or debugging round alongside a LeetCode-style problem, where you read existing code, find logic errors and suggest improvements. Coding questions reported include 2 Sum, Number of Islands-style problems, backtracking and a file-scanning task. One 2024 candidate was asked about concurrency and race conditions, and another about making a solution multithreaded.
System design appears for some candidates, including a notification broadcasting service. Another candidate, who stopped at the assessment, was told the later loop included a take-home case study on a collaboration feature for video content. Behavioral conversations commonly cover why Dropbox, which products you use, and an in-depth walk through a past project.
Most of these reports end in a rejection, so prepare thoroughly. Reports from candidates at different levels differ, so treat senior and intern loops as separate paths.
Synthesized from 17 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Dropbox process.
The process moved pretty quickly and felt unusually transparent. I started with a take-home OA, which was more of a design-style coding assessment than a pure LeetCode screen. It had four parts, and each part got a bit harder as I went, with the main task being to design a system to do a specific job. After that came two technical rounds. One of them was a straightforward coding interview where I got a 2 Sum-style question, so it wasn’t especially exotic, but they were clearly checking fundamentals and how I talked through the solution. The other technical round was system design, followed by a wrap-up call with the hiring manager.
The phone screen was pretty standard: tell me about yourself, walk through projects I’d worked on, and explain why I was interested in Dropbox. What stood out most was how fair and organized the whole thing felt. The recruiter kept me updated on the process in detail, and after I didn’t pass the technical interviews, they even offered a feedback call, which I hadn’t seen elsewhere. That was appreciated even though the outcome was a no. Overall, I’d say the bar was solidly technical, with a mix of coding, design thinking, and behavioral questions, and the main thing to prepare for is being comfortable with both a simple coding problem and a more open-ended system design discussion.
Prep tip from this candidate
Be ready for a take-home that is really a multi-part design exercise, not just implementation, and practice explaining your approach as the difficulty ramps up. Also prepare for a basic coding round like 2 Sum plus a system design conversation, since both showed up in the process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Dropbox
Write a function to return any subset of the input list where the elements sum to zero and that does not contain the number 0.
| Question | |
|---|---|
| Find Duplicate Numbers in a List | |
| Hurdles In Data Projects | |
| Target Indices | |
| Shortest Path Algorithms | |
| Client Solution Pushback | |
| LRU Cache 1 | |
| Dropbox Database | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Random SQL Sample | |
| String Shift | |
| Comments Histogram | |
| Largest Salary by Department | |
| Top 5 Turnover Risk | |
| Minimum Change | |
| Rolling Bank Transactions | |
| Prime to N | |
| Customer Orders | |
| Find the First Non-Repeating Character in a String | |
| Upsell Transactions | |
| Top 3 Users | |
| Find the Missing Number | |
| Raining in Seattle | |
| Rectangle Overlap |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a timed, proctored online assessment, often on CodeSignal with about four escalating levels. Tasks mentioned include filesystem and string manipulation, an in-memory database or file-sharing system, and a banking-system design. One candidate reports a one-hour framework-based assessment, and another a design-style take-home. Passing early levels cleanly appears to matter.
Candidates typically describe a short recruiter conversation after or around the assessment. Topics reported include background, interests, projects and why Dropbox. One candidate reports it was brief and conversational. Timing varies between reports, so confirm next steps with your recruiter.
Several candidates report one or two technical interviews of about an hour each. They mention LeetCode-medium-style problems such as 2 Sum, island-style graph problems and backtracking. Several also report a code review or debugging exercise where you spot issues and suggest improvements. Some reports mention concurrency discussion.
Some candidates report a system design conversation, such as a notification broadcasting service. Another candidate was told the later loop would include a take-home product case study about a collaboration feature for video content. This stage may not apply to every level or team, so ask your recruiter what your loop includes.
Candidates report behavioral conversations covering why Dropbox, which products they use, and a deep dive into past projects. Others mention conflict, constructive criticism and turning a negative customer experience into a positive one. Prepare concise STAR-style stories and a specific answer about Dropbox's products.
