I had two phone interviews with Google.
In the first phone interview, the interviewer pasted a data structure from Python and brought up a question, while I mentioned I would use Java or C++. The sound was not clear either. When I asked about the data structure, he said he was not good in Python. I started to write code to convert the DS so that it would fit C++ or Java objects. This took a lot of my time, and the interviewer did not mention that I could skip it. At the end, I couldn't finish because of the lack of time.
When I told my recruiter about this, he arranged a second phone interview, and the second one went well. The recruiter told me that I was selected for an on-site interview.
During the on-site interview, I had four interviews.
The third interviewer, who came in barefoot, asked his question, and it was vague. When I asked questions to clarify things, he was saying that he was not feeling well and should have taken the day off.
I would say, except for the third interview, the others went well, and I liked the challenges and questions.
Unfortunately, after a couple of days, I got a call from my recruiter that they had decided not to continue.
For my second phone interview, the question required a breadth-first search of a tree.
The following metrics were computed from 21 interview experiences for the Google Software Engineer role in Waterloo, Ontario.
Google's interview process for their Software Engineer roles in Waterloo, Ontario is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Google's Software Engineer interview process in Waterloo, Ontario.