Taro Logo

Software Development Engineer Interview Experience

March 1, 2016
Positive ExperienceNo Offer

Process

The interview process was pretty straightforward. There were two back-to-back interviews.

I was a bit surprised by the first one's fast pace and messed it up. The second one was much better, but it didn't help. I was rejected by call and email.

The first interview focused mostly on small questions, like derived classes, binary search, and DFS. The second interview was much more complicated. Obviously, I could not finish it in 45 minutes, so the interviewer directly asked me to write only key functions. At last, we were still short of time, so pseudocode was also allowed. I'm pretty sure I did well in the second part.

Questions

Questions about derived classes, and binary search application using tree traversal. It took a bit of time to write the whole code, so the interviewer allowed me to write key functions instead.

Was this helpful?

Interview Statistics

The following metrics were computed from 111 interview experiences for the Google Software Development Engineer role in United States.

Success Rate

10%
Pass Rate

Google's interview process for their Software Development Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive57%
Neutral35%
Negative8%

Candidates reported having very good feelings for Google's Software Development Engineer interview process in United States.

Google Work Experiences