I received a referral and was contacted by a recruiter within a couple of days. I was then invited to an onsite interview.
I had five interviews in total: four were general coding interviews, and one was about program analysis. The coding questions were at an intermediate level. I was able to describe different approaches and came up with a solution on the whiteboard. I felt good about my performance after the interviews. However, my overall experience was not as I expected.
My first two interviews were held in a nice room with a sufficiently large whiteboard. The first two interviewers were very pleasant. After lunch, my room was changed. It was a small room with a really, really small whiteboard, approximately 30 inches wide. It was challenging to code on such a small board and to write clean code. I had to erase parts I had written earlier to fit everything. One of the interviewers was inattentive; he was not paying attention to the interview. He mentioned he had a meeting afterward, and I suspect he was preoccupied with it.
Unfortunately, Google did not request any feedback on the interview. I might have felt more positive about the interview process if I had had the opportunity to provide my feedback directly to Google.
Signed 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.