A recruiter reached out to me via email and scheduled a call to discuss what kind of role would best fit my skills. It ended up being one of the best recruiter phone calls I've ever had, because the recruiter paid great attention to detail and personalized our conversation based on our discussion and my skills.
After that call went well, we scheduled a technical phone screen with an engineer. I didn't know who would be interviewing me beforehand, which is something I would have appreciated. Knowing the interviewer's name would have helped me research them and ask more targeted questions about their experience at the company.
The phone screen went well (I thought), and I was able to address all three questions within the allotted time. I managed to optimize my initial naive solution, reducing it from 26 lines of code to 7 lines.
Ultimately, I was rejected because I apparently spent too much time on the naive solution and not enough on the optimized one, which baffles me.
Overall, I would describe the experience as neutral. The recruiter phone call was very positive, but my technical phone screen experience was negative.
Basically, rewrite the getElementByClassName() method from scratch.
The following metrics were computed from 204 interview experiences for the Dropbox Software Engineer role in United States.
Dropbox's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having good feelings for Dropbox's Software Engineer interview process in United States.