I interviewed for Dropbox in Seattle. Initially, my recruiter informed me that I would have a phone screen, a two-hour onsite interview at the Seattle office, and a full-day loop at the headquarters.
The first phone screen seemed to go well. The interviewer was engaging, and we had a good technical conversation for the entire hour. I appreciated this aspect of Dropbox: they ask interesting, real-world scenario questions rather than standard ones like binary trees or linked lists.
After more than a week, the recruiter contacted me to say that I would have one more phone screen instead of the two-hour onsite interview in Seattle. The second phone screen went okay. The interviewer was rude. Although I solved the problem, I knew it could be improved, but there was no discussion from their end. It felt as if the most optimized solution was expected on the first attempt.
I received a thank-you email two days later.
Group duplicate files in a folder, log file manipulation, and querying.
The following metrics were computed from 8 interview experiences for the Dropbox Software Engineer role in Seattle, Washington.
Dropbox's interview process for their Software Engineer roles in Seattle, Washington is extremely selective, failing the vast majority of engineers.
Candidates reported having good feelings for Dropbox's Software Engineer interview process in Seattle, Washington.