I was contacted by a recruiter who set up a phone interview. During this interview, I coded in a Google Doc shared by the interviewer. I was then invited to an on-site interview in Mountain View, where I had four hour-long interviews and an hour-long lunch with a Google employee.
There were a couple of issues I had with the process:
The initial recruiter somehow determined I had a year of professional experience in Android development, which was not true. Therefore, she initially placed me on the hiring track for someone with professional Android experience rather than the hiring track for a recent college graduate. I passed the phone interview on this track, but then the next recruiter I spoke with discovered the error and switched me over to the recent college graduate track for the in-person interview.
My recruiter never showed up in the lobby to pick me up for the in-person interview. Twenty minutes after the interview was supposed to start, my first interviewer called to find out where I was. She requested that I come to the building where she was, but the secretary said I wasn't allowed to walk there by myself and that she had to come pick me up. I had to tell her to come pick me up, then we went back to the building and started the interview quite late. The entire time, interviewers tried to make up for lost time by shortening their interviews, so it was a fairly frustrating experience.
Travel reimbursement worked well, and it was a nice chance to visit Mountain View, so that was a plus. The interviewers were also very welcoming, if a bit rushed.
Whiteboard coding questions covering CS fundamentals.
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.