The interview process is typical, consisting of one phone screen followed by an all-day onsite interview. I was fortunate to receive feedback on each individual interview I had during the day.
The moment the recruiter outlined the interviews I needed to participate in, she mentioned I had to choose a deep dive project. This project should be one I had worked on recently at my current employer. I informed her that I had NDAs and was willing to discuss projects at a very general level, but the recruiter insisted I should be able to go into detail. I explained that I simply couldn't talk about any project due to its internal nature and unreleased status. She then stated that I wouldn't be able to proceed to onsite interviews if I wasn't willing to discuss any project in detail.
This was deeply uncomfortable. I opted for a project that wasn't too important, didn't significantly contribute to the company's bottom line, or wasn't extremely interesting. My goal was to secure the onsite interview and see where things led. I was able to get an onsite interview using this less significant project for the deep dive topic.
However, as the day progressed, it became evident that the interviewers lacked the training to effectively conduct interviews. They didn't design questions in a way that allowed them to gauge a candidate's qualifications.
They would ask trick questions, leaving limited space on the whiteboard and making it impossible to amend code without starting over. While you could ask questions about the problem and clarify requirements, they would often provide misleading information about them, only to change their minds later. They dismissed the importance of code cleanliness, laughing about it cynically, yet still held it against you in the hiring decision.
One interviewer repeatedly interrupted me every two minutes, not even allowing me time to think about the problem. It's impossible to focus and perform work under such constant interruptions. I managed to barely finish the first part of the question, but when it came to the second part, I couldn't continue. I was completely frustrated by the interviewer's interruptions.
As part of the feedback, I was told that my unwillingness to share details about my current employer's confidential projects was a problem. When I mentioned my NDAs, they laughed about it.
Additionally, the interview panel lacked diversity across the board. As a minority, it's difficult to experience looks of judgment from the moment interviewers introduce themselves.
It was an incredibly negative experience, unlike any I'd had before. I wouldn't recommend Dropbox to anyone.
Very easy questions, honestly, but yet all the bad experience above.
The following metrics were computed from 57 interview experiences for the Dropbox Software Engineer role in San Francisco, California.
Dropbox's interview process for their Software Engineer roles in San Francisco, California is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Dropbox's Software Engineer interview process in San Francisco, California.