The interesting parts of the Google interview process are all under NDA, and you can't discuss them for two years after the interview. Here's what I can tell you:
The interviews are extremely technical and involve real programming exercises, manipulating data structures, analyzing or describing algorithms, etc. Be prepared to iterate what you're doing on the board. Be ULTRA prepared with knowledge of standard search and sort algorithms and junior-level CS data structures; also be aware of their big-O complexity. While the interview questions aren't exactly complicated, they cover so much territory that there is no way to study for them from "cold." If you are not programming on a daily basis in the languages in which you're being interviewed, you will not pass these tests.
The process moves extremely quickly, at most a day or two between steps. Depending on how your scheduling works, you could go from first contact to an offer in less than two weeks.
Absolutely everything you have read about Google perks and benefits is entirely true. It's hard to imagine a company with better employee benefits.
Interview questions are protected by a non-disclosure agreement.
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.