Initial contact came through a recruiter and HR. I was then connected to the hiring manager and had a phone interview with him.
The phone interview focused on the relevant technical area (algorithm research & development), close to my expertise and expected area of work. This went well, and I was invited for a day of onsite interviews.
The onsite interviews were disappointing. Both the recruiter and hiring manager were not available, and I did not get to speak to them at all. Several interviewers were not related to the team I was interested in and seemed to be randomly selected. They barely introduced themselves.
Most interview questions were computer science related, some very easy and some hard. Almost none of the interview questions were actually relevant to the position I was interviewing for. The interviews were very impersonal; the interviewers were focused on getting through their standard questions and recording my answers. They were not interested in my background or testing whether I could actually solve problems relevant to the position. As a result, there was almost no relevant discussion or engagement with the interviewers possible.
I received almost zero feedback from the recruiter afterwards, other than that "impressions were mixed".
Given a sequence of n digits, where each digit can represent three (or four) letters from the alphabet (as on a phone keypad), list all words that can be formed that are also in a given dictionary.
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.