I applied online via a career website and was contacted by the recruiter within 24 hours.
We did not have a phone chat, and I was fast-forwarded to the phone interview.
My interview questions were pretty basic. I had two LeetCode-style questions:
I addressed most edge cases on the first question. For the second, I initially provided three suboptimal solutions before coding an optimal one after receiving a hint.
About a week later, I received an email stating they were still waiting for feedback from other team members.
I assume this meant I passed the coding round, but something else went wrong.
I was not provided with feedback, or the feedback was very minimal.
The interview questions were basic, LeetCode medium-easy.
Wrap lines at the nth character using a greedy approach. If a new line would break a word, keep the word on a separate line.
Return the kth element from an unsorted array. They wanted a solution that was not heap-based or sort-based (both would have given n log n time complexity). They were expecting something simpler, perhaps using two variables: one always keeping the maximum, and the other being a buffer of the first, which only contained the previously found maximum.
Yes, very basic 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.