I was invited for a round of interviews at the Google office in NYC. The recruiter tried to be helpful and gave me the standard resources to prepare for the interview, such as how to code on a whiteboard, algorithms, and data structures—pretty basic stuff.
I had six interviews in one day, each lasting about 45 minutes, with a lunch break in the middle.
Some of the interviewers asked very good questions that allowed for different approaches and a robust discussion. Others, however, were quite shallow and seemed to know nothing beyond a single question they had prepared.
The interview process and questions were not out of the ordinary for a tech company.
What I found a little disconcerting is that some interviewers didn't talk about their own jobs with enthusiasm when I asked them about it at the end of the interview. Also, I wanted to find out what area or team I'd be joining if offered a job, but I could only get general answers.
Several weeks later, the hiring committee finally reviewed my case and decided not to extend an offer. I'm not sure how the committee works. Are they the same people who interviewed me? What do they remember about the interview after several weeks?
Strangely, I received no negative feedback communicated to me by the recruiter, but also no offer.
It was a little disappointing, however, overall, I did enjoy the interview experience.
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.