Google basically does not care what you have done, and doesn't interview you for any particular position. They mainly want to know if you are talented at answering academic computer science questions.
Does this build a good company? I don't think so, but it's up to them to decide that, I guess.
Six interviewers asked me incredibly detailed data structure and algorithm questions. Nothing that anyone asked me would have distinguished me from a recent graduate. I thought I did pretty well, but apparently not well enough. My recruiter sounded as surprised as I was that I didn't get an offer.
Apparently, anyone who interviews you can veto, so it's everyone's loss that one of my interviewers was a terrible interviewer.
Be sure to buy, and at least skim, a copy of "Programming Interviews Exposed; Secrets to Landing Your Next Job" (Mongan/Suojanen/Giguere?), recommended directly by Google recruiters.
Best of luck.
Let's say you have a lot of numbers and you want to sort them. What do you do?
The following metrics were computed from 13 interview experiences for the Google Engineering role in Mountain View, California.
Google's interview process for their Engineering roles in Mountain View, California is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having good feelings for Google's Engineering interview process in Mountain View, California.