A recruiter reached out to me to start the interview process. I sent in my resume and received a long list of suggested prep material. I say 'suggested' because candidates don't necessarily have to stick to it, and interviewers will most likely ask at least a few questions not covered by the list.
I set up a phone interview that lasted for about 45 minutes. In total, I was asked only two technical questions.
For the first, I was asked to write an algorithm to solve a random problem. I wasn't sure how to proceed at first, so I talked through my thought process until I came up with a solution. The interviewer then asked about the running time and what kind of tests I would write for it.
The next question was about web programming and networking. This question wasn't on the prep material list, but it wasn't completely out of bounds. The interviewer was vague initially, but as we talked, I was finally able to understand what they meant and what kind of response they expected.
After that, it was all behavioral questions and topics like the projects I'm currently working on.
What is a project you are currently working on?
The following metrics were computed from 211 interview experiences for the Google Software Developer role in United States.
Google's interview process for their Software Developer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Google's Software Developer interview process in United States.