My interviews with Google started with two phone interviews. Both were comprised of three questions of increasing difficulty.
Each interview had a simple, general knowledge question, a theory question (like how to avoid a deadlock), and then a larger coding problem.
When I went on-site, I had four more interviews, each of which featured complex algorithmic problems. I highly recommend focusing your review on algorithm and data structure theory for your own Google interview.
The problems are challenging but fun, and the interviewers will happily clarify any ambiguity.
Despite what I believe was a strong set of interviews, I did not receive an offer, although they did encourage me to reapply in a year.
What is a deadlock, and how to avoid one? (Thorough understanding required)
The following metrics were computed from 21 interview experiences for the Google Software Developer role in Mountain View, California.
Google's interview process for their Software Developer roles in Mountain View, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Google's Software Developer interview process in Mountain View, California.