First, a timed online survey with two coding questions. I finished the first to my satisfaction but was unable to get any code for the second within the time frame.
I was called within a couple of days by a recruiter who set up a phone interview for the following week. The phone interview consisted of two more coding questions.
I was called by my recruiter the day after the phone interview, who said they were interested in moving forward and transferred me to a location-specific recruiter. I scheduled an onsite interview for two weeks later.
From receipt of the initial survey to the notice of no offer, the total process was about 7 weeks.
There were no overly complex or trick questions. All were doable within the scope and time constraints of the interview, with help from the interviewer for unclear areas.
Focus was on algorithms and the run time of solutions, along with the thought process that went into forming the solution.
No trick questions.
Focus preparation on actual coding, especially on data structures and run time.
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.