The process was quite streamlined and got me straight to the in-house interviews.
The full day of interviewing was okay. During the interviews, I was actually disappointed. I expected well-known "to see how you think" types of questions; instead, I received a bunch of typical CS problems that had to be coded under about 30 minutes of time pressure. There was really no time to think; you had to know how to solve it or know a similar problem. Overall, 45 minutes included questions from both sides and coding.
Advice to those who choose to interview with Google: study sample interviews and read what exact questions they ask. No one cares how you devise a solution; they care for you to come up with an optimal answer within 5-10 minutes.
Again, the reason why I was disappointed was that I expected them to evaluate people on potential and way of thinking instead of "academic" CS knowledge of solutions to their questions.
Interviewed in NYC.
Forward linked list, traverse in reverse in O(1) memory.
Question with two dictionaries.
The following metrics were computed from 344 interview experiences for the Google Software Engineer role in New York, New York.
Google's interview process for their Software Engineer roles in New York, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Google's Software Engineer interview process in New York, New York.