The interview process was chaotic; I was handed off across multiple recruiters over the course of just a couple of months.
Initially, I was told I would need to go through a phone screen, then that I wouldn't be. Ultimately, I did not participate in a phone screen and went directly to a virtual version of the on-site interview.
The on-site questions felt better than I expected, and I thought that I answered most of them well. I had forgotten about one particular data structure and had to use some features of my programming language that I hadn't prepared for. I noted this and continued with pseudocode.
Upon receiving word on my hiring decision, my last recruiter emailed me an upbeat email asking to schedule a time to talk. This doesn't set up good expectations. According to my friends who do recruiting, this shouldn't be done for a rejection call.
They were able to give feedback, but I thought their reasons for rejection were bad. I would have preferred no feedback to that.
If you're not desperate for a job or even a little rusty on your undergraduate work, I do not recommend taking the time to interview with Google.
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.