The recruiter allowed me to bypass the phone screen. The onsite consisted of 5 interviews. I opted for the front-end engineering track, so of the 4 technical interviews, 2 were front-end-focused. The other 2 were algorithms/data structures, and then there was 1 behavioral interview.
I was worried that the 2 front-end-focused interviews would be algorithm-heavy, but they were pretty straightforward and practical.
Both a plus and a minus is that you talk to people from all over the company, not necessarily anyone you would be working with. This allows you to get different viewpoints, but also means there's no real lasting connection.
Google's decision-making process is known for being slow-paced, but since I had another offer, they were able to speed up the turnaround time.
Equivalent of LeetCode mediums; questions involving knowledge of asynchronous calls in JavaScript.
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.