The process was long and arduous. First, I had a recruiter screen with typical HR questions. Then, after about two weeks, I had a phone screen with an engineer. I needed to write code on a shared document while talking to the engineer on the phone.
After that, the recruiter suddenly changed to a "senior recruiter." This new recruiter seemed to be the lousiest senior recruiter they had at the time. He forgot to schedule the onsite interview, never called or emailed back, and rarely picked up the phone when called directly. More than a month after the phone screen, I finally went to the onsite interview. That went fairly well, but due to the recruiter not doing his job, the hiring committee wanted more information.
After another month, I went back for a second onsite interview. When I heard nothing for more than three weeks, I asked to change recruiters. The change was approved, and after one more onsite interview, I was extended an offer.
Engineers performing the interviews were all professional and nice; no one asked any brain teasers, etc. All questions were highly technical, on par with what I expected from reading Glassdoor and other sources. It would have been a generally positive experience if it weren't for the lousy "senior" recruiter.
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.