The process began with a single telephonic interview. It took a month to receive the results of this initial call.
Next, I had an onsite interview consisting of four one-on-one sessions. The interviews proceeded as they did; interviewers were busy scribbling notes on what I was saying or writing on the board. They mentioned they had to report this to senior management or the hiring committee. This was quite distracting, especially when they jotted down the code as I wrote it on the board and made changes. I was concerned they might misinterpret something and make an unfavorable decision.
The recruiter initially stated they did not require references unless they were in the final stages of making a decision. However, a week after my onsite interview, they requested my references and insisted I provide professional ones.
This presented a challenge as my last job was four years ago and in a different country. (I completed my master's degree after that and have been working at my current company for two years.) I was only able to secure references from colleagues at my previous company. They preferred evaluations from individuals who had directly supervised me rather than professors.
Ultimately, I was not hired.
Binary Tree Successor
The following metrics were computed from 21 interview experiences for the Google Software Developer role in Mountain View, California.
Google's interview process for their Software Developer roles in Mountain View, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Google's Software Developer interview process in Mountain View, California.