Applied online and got back from a recruiter within an hour. Had a conversation with the recruiter a week after, and he said I could go straight to the onsite for interviews.
I was interviewing at many other places in parallel, so I scheduled the onsite two weeks after the day I spoke with the recruiter. They don't seem to care how quickly you take the onsite, so choose a time to give yourself enough time to prepare.
There were five onsite interviews, with one lunch with a developer (I heard that the lunch is not an interview). I had to write solutions on a whiteboard for all of the questions, so be prepared.
I had never heard of any of the questions they asked, but studying LeetCode and interview books helped me figure out ways to solve algorithm questions.
All of the interviewers were nice, and the interview felt like I'm solving a real work problem with a coworker.
Think about time complexity and efficiency at all times when you come up with a solution.
It took less than 2 weeks to get an offer. I think this can be different for different people.
Algorithm questions
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.