The interview process began with a generic HR question-and-answer session. This was followed by two one-on-one phone interviews, each lasting approximately an hour.
Next, a full day on-site included five one-on-one interviews, also around an hour each. These interviews focused on difficult technical questions, although thankfully, the rumored logic puzzles and riddles were not part of the assessment.
The on-site interviews covered a broad range of topics, including: basic skills, data structures (both existing ones and the creation of custom structures to solve example problems), performance scaling, and networking. The interviewers were helpful, encouraging me to articulate my thought process. No one was hostile, and I found all seven one-on-one interviews (two by phone, five in person) to be rather enjoyable.
Accommodations were pleasant, and the cafeterias were very nice. Everyone was tremendously friendly, and I also liked the town.
My only criticism is that the wait time for news and information about the next steps after each interview seemed quite long. Overall, the process was thorough but felt a bit drawn out.
To diagnose why bandwidth was bad (hypothetically, of course) between sites. After a few obvious questions to ask, I was stuck because that really wasn't my area.
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.