I started the interview process with an email from a recruiter on LinkedIn. Many people at my college received the same email.
The first interview was a standard phone screen where we went over my resume and summer experiences, and I had any questions I had about Google.
Next, a technical phone interview was scheduled.
I consistently attended Google alumni talks at my school to network and ask questions, and I received news that they would be skipping my technical interview and flying me straight onsite.
Once there, I had two 45-minute technical interviews, a casual lunch with a Google employee (not an official interview), and two more 45-minute interviews.
The questions were quite creative and a little more complicated than the average algorithm or data structures questions.
The entire process took close to two months, with self-scheduled time in between to help me manage my academic life. The recruiters were quick to respond, and everything was handled very smoothly.
Can you tell me a little bit about the internship you did over the summer and some previous projects or internships you've had?
Onsite:
Questions about trees, binary search trees, and an unusual puzzle/map problem.
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.