A recruiter from Google's college recruiting team contacted me after my friend referred me.
The process was very fast.
I had a phone interview with an engineer from Google's NYC office two weeks later. It was a standard 45-minute technical interview.
The interviewer started the interview with a coding problem directly. We used Google Docs as the whiteboard.
I finished the first coding problem with two solutions, and the interviewer verified both of them. However, we didn't have much time left for the second problem. I wrote down some code, and then time was up.
One week later, I received the onsite invitation.
The onsite interview included four sessions. All of them were technical interviews.
Almost two weeks after the onsite interviews, my recruiter called with bad news.
Most questions are not simple, because you need to think thoroughly.
The following metrics were computed from 111 interview experiences for the Google Software Development Engineer role in United States.
Google's interview process for their Software Development 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 Development Engineer interview process in United States.