I applied at a career fair and had a 30-minute technical interview in person the next day. The question was straightforward, asking to find the possible permutations of a string. I wrote up the code on a laptop due to the lack of a whiteboard, but the style was the same as whiteboard coding.
A couple of days later, I received an email to set up a 1-hour phone interview. I was asked how to find duplicate files in a filesystem, and I wrote up the code on Coderpad.
Another few days later, I received an email to set up an on-site interview. This consisted of three technical interviews, lunch with an engineer, and an engineering Q&A. The questions were interesting and a bit more challenging than your average interview. Be sure to be able to analyze space complexity in terms of bytes, not just Big-O notation. I don't think I can disclose the actual questions asked during the on-site, but they were all fairly straightforward and did not require fancy algorithm or data structure knowledge. While I did solve all the questions and follow-ups, I don't think we were always on the same page, and the interviewer had to nudge me in the direction they were hoping to go.
I received an email less than a week later telling me that I would not be receiving an offer.
List all duplicate files in a filesystem, given the root directory.
The following metrics were computed from 8 interview experiences for the Dropbox Software Engineering role in San Francisco, California.
Dropbox's interview process for their Software Engineering roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Dropbox's Software Engineering interview process in San Francisco, California.