They contacted me through email, and the recruiter set up two separate phone interviews on the same day, within one hour of each other. The recruiters were very nice and gave me a lot of information before the interviews.
The interviewers were okay. One of them directly went into the technical questions and did not talk much about anything, acting mostly like a robot. He would point out if my code had a bug, and I would try to solve it.
However, I was not that prepared, as this was my first technical interview ever. Overall, I did finish all of the programming exercises, and they worked when I checked afterwards. My main issue, though, was that I wouldn't notice the bugs myself before they were pointed out to me.
I got stuck a little bit with classes and objects. Make sure to check if the input is null or not when creating methods for a class.
They asked me to create a class and then create a function where the input is from the same class.
Then they asked how I can check if the input is appropriate.
I had to use instanceof().
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.