I had been contacted by a couple of Google recruiters in the past, but I wasn't interested at that point. When I decided to pursue an opportunity with Google last month, I just contacted them back, and they set me up for a loop.
Since I was interviewing for a role in MV, there was one phone screen. The question itself wasn't very interesting, but I had to write code in a shared Google Doc.
The next day, I was told that the phone screen had gone well and was invited for the onsite rounds. There were five technical rounds (and an hour around noon for lunch). Each round had two questions and some time for my questions.
While I won't discuss the actual questions here, I'll say that it wasn't 'difficult' – basic data structures and algorithms. There were no questions involving fancy data structures (binomial heaps, skip lists, etc.) either.
Two days after the onsite interview, I was told that the hiring committee had approved it. A week after that, I got the final offer.
The NDA prevents me from discussing the actual questions I was asked.
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.