A Google recruiter contacted me early in the summer (I had interviewed with them previously) and set up a phone interview. I passed that, and they sent me an invitation for an on-site interview.
The visit to their Mountain View HQ was very pleasant. I had:
I did not find the interview problems particularly difficult and solved most of them well before time ran out, so I ended up with a lot of time to chat with the interviewers. I think I got them all correct (I hope!), because the interviewers didn't really have many comments about my solutions, and they didn't tell me that anything was wrong.
They told me it would take around two weeks to give me my decision, but it ended up taking ten weeks. This was because one of the interviewers left the company without turning in their interview feedback, so I had to do another phone interview. I think some other stuff got lost, so the recruiter contacted me and asked me to fill out some more forms. Either way, it took a really long time, and I was disappointed when I did not get an offer :(
I signed an NDA, so I cannot say. However, there are some brainteasers before the main coding question in some of the interviews.
The following metrics were computed from 3,728 interview experiences for the Google Software Engineer role in United States.
Google's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Google's Software Engineer interview process in United States.