The interview process began with a phone screen, followed by an on-site interview.
Honestly, I was expecting a much more interactive on-site experience, where I could ask questions and receive feedback on my thought process from the interviewer.
Instead, four out of five interviewers had sub-par communication skills, with extremely hard accents to follow. They wrote poorly explained questions on the whiteboard and seemed irritated by any follow-up communication, including replies to simple clarification questions.
I eventually solved all questions asked, though potentially slowly, and in one case, quite inefficiently.
The lunch interview was not fruitful either. I was matched with a person from an entirely different development team.
Furthermore, the whole process took place at a very remote part of the Google HQ that looked somewhat deserted.
I received a callback from HR the following week. They informed me that I didn't perform well enough but encouraged me to apply next year. I don't think I will.
NDA.
The following metrics were computed from 748 interview experiences for the Google Software Engineer role in Mountain View, California.
Google's interview process for their Software Engineer roles in Mountain View, California is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Google's Software Engineer interview process in Mountain View, California.