A recruiter contacted me via LinkedIn and called to ask basic career questions. Then, I was given online coding problems to solve. I solved them all just in time; none of my friends finished in time, though.
Next, I had a phone interview, coding in a Google Doc. The engineer called on time. He spoke exceptionally softly and had a very heavy Indian accent that made it very hard to understand what he was saying. I felt bad asking different variations of "Can you repeat that?" so many times, but I really couldn't make out his questions otherwise. I think he might have seen this as me not understanding the question and may have counted it against me.
The document they sent to prepare said I could do the questions in C#, so that's what I prepared to do, but the engineer seemed thrown off. We had a bit of a complication when he didn't know if null in C# was the same as null in Java.
I didn't get to the next interview, but it was a positive experience nonetheless.
Weave two linked lists together into one.
Rod cutting problem.
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.