Dropbox Software Engineer Interview Questions
51+ questions from real Dropbox Software Engineer interviews, reported by candidates.
Round Types
Top Topics
Questions
Applicants for the Dropbox Metadata Software Engineer role should be aware of a significant discrepancy between the position's infrastructure focus and the content of the Online Assessment (OA). While
Build a python class for a banking system Level 1: Support creating new accounts, depositing money into accounts, and transferring money between two accounts. Level 2: Ranking accounts (i.e top_spenders) based on...
PocketPills | SDE2 | GGN | Dec 24
Round 1: DS/PS Gas Station Singleton class and implementation. final, static, transient, synchronized and volatile keywords and their usage. Immutable class in Java and implementation. Round 2: System Design Design a...
System design batch delete and recover system
Recently preparted for system design and came this design question with Tt on how to design a system to batch delete and undo-delete within some centains times. I feel like...
Dropbox front end phone interview
A # | B # | | C <-- access # | | D # | E <-- access # |___ F ---- G # folders = [(\'A\', None), (\'B\', \'A\'), (\'C\', \'B\'), (\'D\',...
Dropbox | Phone Screen | Senior Software Engineer | Reject
File access System I was asked the following question. If given the folder access tree and given query folder name, return TRUE|FALSE is user have access to it. for eg. below -...
Avalara | SDE1 | Pune | Oct 2022 [Reject] (Ghosted)
Status: 1.5 Year Experience, Tier 3 college Current Position: SDE1 at Early startup Interview Date: sep, 23 and 29, 2022 Applied on career webiste. Got a call from recruiter about the interview schedule....
TruEra | SSE | Bangalore (India) | July 2022 | Ghosted after selection
Participated in virtual drive. 1st Rounds (DS) Minimum Spanning Tree 2nd Round (HLD) Design Dropbox 3rd Round: (LLD) Create snake game Note: Passed all the interview and VP was pushing me to take decision in just...
Dropbox | OA2 Internship
Hi, I got my first Online assignment from dropbox which was Codesignal: 4 different questions in different levels in 1 hour and 10min (sort of leetcode style) and got ahead with...
I applied for a Senior Software Engineer position at Grab in Singapore and failed. Online coding : codility I got two questions. Q1 : https://gist.github.com/rogeliorv/0a4b8e39d25a8d4707169fb81111ff8b Q2 : https://leetcode.com/discuss/interview-question/306379/dropbox-quality-engineer-phone-screen Good luck guys and Practice.
Dropbox Interview Telephonic + Onsite
YOE : 6+ Location : Bay area Telephonic: 1.) https://leetcode.com/discuss/interview-question/417262/dropbox-phone-screen-permissions-in-a-file-system They just expect you to save the data as dictionary with parent child relationship and just traverse it to find if the...
Dropbox Interview | Phone Screen | Onsite | Questions | [Offer]
I had my onsite in January 2021. Phone: Game of Life (look it up) Onsite: 1. Reader-Writer Lock 2. All-Around Interview with a Hiring Manager 3. Id Allocator 4. Design a Logging Service The question packet and...
GupShup | SDE2 | Bangalore
Status: 1year 9 months experience Position: SDE2 at GupShup Location: Bangalore Date: May 2020 Was directly called by recruiter, did not apply anywhere. 1st Round on Hackerearth with Interviewer(Team Lead) (1 hour): - Algorithm question...
Dropbox phone interview
This was for sw2. I was supposed to search a dir to find files that have have the same content. Ex. hello.txt = "hello" and fjalfja.txt = "hello" and main.cpp,...
Dropbox Phone Screen | Rejected
Had a phone screen with an arrogant L3 engineer and was rejected after coming up with working BFS solution. # # A # |___ B # | |___ C <-- access # | |___...
Dropbox | Phone Interview | Reject with interesting experience!
I got the file permission question similar to https://leetcode.com/discuss/interview-question/417262/dropbox-phone-screen-permissions-in-a-file-system and the follow-up was to modify implementation so that only the parent has access, for example: A -> B \t ----> C if we have...
This was for an Android Developer position. The question given was an image with an outer bigger rectangle and inside it were a bunch of smaller reactiongles. (Parent view and child...
Dropbox | phone screen
I was asked the below question, during my phone screen today. Can anyone help me on this. Write a method for ColumnLayoutManager that takes input arguments: list of views with width and...
Dropbox | Game of Life
Status: 6 Years of Experience Position: Senior SWE - Full Stack Location: HQ Phone Interview (1 hour): https://leetcode.com/problems/game-of-life/ Follow up: what if the board was very large, how would you deal with that? Interviewer said i...
Dropbox @ Quality Engineer phone screen
Problem : A non-empty zero-indexed array A consisting of N integers is given. Array A represents a linked list. A list is constructed from this array as follows: \u2022 the first node (the...
What Dropbox Looks for in Software Engineer Interviews
Dropbox Software Engineer interviews are calibrated against the level and scope expected of the role. Across 51+ verified candidate reports on LeakCode, the consistent signals interviewers look for: clear problem decomposition before coding, explicit complexity reasoning, structured handling of edge cases, and the ability to articulate trade-offs between two reasonable approaches.
The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the solution. It is the path to the solution: did you ask clarifying questions, did you state your approach before coding, did you handle edge cases without prompting, and did you communicate your reasoning throughout. Reports tagged "no hire" frequently cite a working solution with poor communication; reports tagged "strong hire" cite clear thinking even when the final solution was incomplete.
How To Use This Question Set
Real interview reports are a calibration tool, not a memorization target. Companies update their question pools every 2-4 months; memorizing exact problems risks misleading you when the interviewer uses a variant. The high-leverage use: identify the patterns that appear repeatedly in Dropbox Software Engineer reports, practice those patterns on similar (not identical) problems, and use the reports to understand the interviewer's typical follow-up depth.
Filter the questions below by round type, difficulty, and recency. Focus first on reports from the past 6-12 months; older reports may reference questions that have since rotated out of Dropbox's pool. Reports tagged with quantified difficulty (e.g., "medium-hard") are higher-signal than reports without difficulty tags.
Round-by-Round Expectations
Dropbox Software Engineer loops typically span 4-6 rounds across phone screens and on-site or virtual on-site interviews. The structure varies by company: some run 1 recruiter screen + 1 technical phone + 3-4 on-site rounds; others run 1 recruiter screen + 1 OA + 4-5 on-site rounds. The recruiter screen is logistics and culture-light; the technical phone screen is medium-difficulty coding; the on-site loop covers coding, system design (at L4+ levels), and behavioral rounds.
Each round is designed to surface a specific signal. Coding rounds: correctness, code quality, complexity reasoning, communication. System design rounds: requirements clarification, design judgment, operational thinking. Behavioral rounds: ownership scope, leadership, ambiguity tolerance, conflict navigation. Strong candidates explicitly hit each signal dimension out loud during the round; weak candidates focus only on solving the prompt.
Common Interview Mistakes At This Combination
Reports tagged "no hire" at Dropbox Software Engineer commonly cite: jumping into code without clarifying requirements, coding silently for 10+ minutes without verbalizing approach, missing edge cases (empty input, single element, very large input, overflow), and producing a working solution that the candidate cannot explain or refactor when probed. Strong candidates avoid these patterns by following a consistent template: clarify, verbalize approach, code with narration, test with examples.
Behavioral and design rounds have their own failure modes. Behavioral: stories that use "we" instead of "I" diluting individual signal, stories with no quantified outcome, defensiveness when probed about failure. Design: not asking clarifying questions, not stating requirements out loud, designing for a single server when the prompt clearly implies scale, ignoring operational concerns (deployment, monitoring, rollback). These show up in roughly half of Dropbox Software Engineer interview retrospectives on LeakCode.
See All 51 Dropbox Software Engineer Questions
Full question text, answer context, and frequency data for subscribers.
Get Access