Resume screen - Ensure you're something resembling qualified; overview the process stages.
Online code sample - One hour, two questions: one easy, one less so.
Phone interview - Code in a shared Google Doc.
On-site interview - Two interviews before lunch and two more after. Individually, not bad, but with only 30-45 minutes in each interview for coding on the whiteboard, speed can be an issue.
Hiring committee - Assuming you don't bomb the on-site interviews, they will review your information and feedback from the individual interviews and make a final decision.
Without going into detail (NDA), some things that were needed for the coding portions included:
Also, be prepared to talk about anything on your resume that might conceivably be of interest to a software engineer.
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.