A Dropbox recruiter contacted me. After speaking with the recruiter about the opportunity and culture, I decided to submit my resume.
The entire process was really pleasant and fast.
I was scheduled for a phone interview within a few days of submitting my resume. The initial phone interview was technical but did not involve coding. It was more of a screening, testing the candidate's knowledge in various technical areas:
It wasn't hard, but it wasn't easy either. My advice is to study and understand tradeoffs. The interviewer actually looked into my resume and tried to ask questions relevant to my area of expertise. The first 15 minutes were introductory, and the rest was breadth technical.
The interview result was revealed a day after.
What is a conditional variable?
When would you use threads versus processes?
How would you find bottlenecks in your web application, both client-side and server-side?
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.