The phone screen lasted one hour, with approximately 50 minutes dedicated to problem-solving and over 5 minutes for asking the interviewer questions.
The interviewer began with some algorithm questions, followed by a coding problem, and concluded with questions about Python.
Coding was done in a Google Doc, and the questions were pasted into it.
(Note: I advanced to the onsite interview, but have not yet received an offer.)
Algorithm questions:
Coding question: Convert a given integer into an Excel-style letter string for columns, such as 0 to A, 1 to B, ..., 26 to AA, etc. This problem seemed simple but had a subtlety: it's not exactly the same as converting between different bases. I struggled a bit, and the interviewer helped me by making up examples. Finally, I figured it out. He was really willing to help. I thought there would be two coding problems, but there was only one.
Questions about Python (which I used for coding):
range() and xrange()? What happens to the array generated by range() when the loop ends?list.append() for each element of the string.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.