I had a phone screen interview, and the interviewer was prompt to call me at the right time. He then asked me about my current position, and 15 minutes into the interview, he gave me a problem to solve. Before solving the problem, I described the solution to him and ran a couple of test cases with my pseudocode to verify my logic. I then asked the interviewer if he was satisfied with my logic and that I should write a working solution. I finished up the code, but it had a small bug, but the partial output was printed correctly. But because we ran out of time and the interviewer had to free the meeting room for someone else, he closed the coder pad, which stopped the session, and all my code was gone in the middle of me fixing that tiny issue. He then said, "I understand your logic, and that it's a very tiny issue which could be fixed in two minutes if we had time." After the interview, I Googled the question and found out that the solution that I had given was the most optimal solution, and the code was also correct. Two days later, I got a rejection letter that I was not fit for the team. Such a waste of time and energy giving the right solution and then getting rejected.
Game of life.
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.