This was my first interview experience so negative that it prompted me to write my first interview review.
Dropbox held a Software Engineering workshop on campus, which got me really excited for my upcoming Dropbox interview. The engineers at the workshop made Dropbox engineers seem enthusiastic and approachable.
My interview experience was the exact opposite. My MIT-grad interviewer spoke very quickly and was extraordinarily apathetic. It sounded as if he had conducted the same interview 250 times previously, and I was the 251st candidate. He wasn't paying attention to how I was solving the problem or to what I was saying. One time, I asked him for his thoughts, and he said, verbatim, "Yeah, I don't know, whatever." I tried to make small jokes and laugh with him, but his attitude was impenetrable.
Worse, I had put a lot of preparation into this interview, and I learned nothing from it. The question was easy; I came up with an optimal solution immediately (I checked online after the interview). I solved the question and follow-ups with ease in 40 minutes out of the 1 hour scheduled.
If they weren't going to pass me, at least they could have given me a hard question so I could learn something from the interview.
As usual, there was no feedback from the interview. I even asked the interviewer for feedback as the interview ended, and he actually declined to respond. Don't waste your time with this company as I had.
How would you scale your solution?
The following metrics were computed from 13 interview experiences for the Dropbox Software Engineer (Internship) role in San Francisco, California.
Dropbox's interview process for their Software Engineer (Internship) roles in San Francisco, California is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Dropbox's Software Engineer (Internship) interview process in San Francisco, California.