I had initial email contact with the recruiter on June 30, 2014. The final decision was given on September 16, 2014.
This was my second time interviewing with Google. I was familiar with the entire process. If you've interviewed before and know your stuff, they skip the phone screen and fly you straight out.
I flew to the NYC office. Everything was reimbursed and very quick. I already knew what to study; all that information is really easy to find online, and the recruiter tells you what to study.
I had no problems answering any of the questions, except those involving a data structure that supports map-like and array-like operations.
I was told that I performed well, but that the hiring committee "didn't have enough data," so I didn't get the job.
Study, study, study. That's the best advice I can give. All material and questions to study can be found online easily.
I just got contacted for a third interview. We'll see how it goes.
A data structure that supports both map and array operations without a time complexity penalty.
The following metrics were computed from 4 interview experiences for the Google Software Engineer In Test role in New York, New York.
Google's interview process for their Software Engineer In Test 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 In Test interview process in New York, New York.