Taro Logo

Software Engineer Interview Experience

October 1, 2015
Negative ExperienceNo Offer

Process

I was referred by someone at Google. The original process was great. I was contacted by one recruiter and had two 45-minute technical interviews. The recruiter got back to me a week later and told me that I would be handed to another recruiter, and that they would like to have an additional technical interview with me.

Then the nightmare began. There were two weeks of silence, and I had no idea who my new recruiter was. Then I missed a phone call from the new recruiter. When I tried to call back, no one answered. A few minutes later, I got a rejection letter from the recruiter. I was surprised and asked her what happened to my additional tech interview. She told me that she had not noticed that I still had one interview and that she started a new application for me to reschedule the interview. The next week I had the interview and waited for more than two weeks before she called me to tell me that I was rejected.

I guess that the interview experience really depends on the recruiter you have. So good luck!

I wish that none of you need to have someone send rejection letters twice during one interview.

Questions

How do you add information to a class without increasing the memory usage of an object?

Was this helpful?

Interview Statistics

The following metrics were computed from 3,728 interview experiences for the Google Software Engineer role in United States.

Success Rate

12%
Pass Rate

Google's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive59%
Neutral29%
Negative12%

Candidates reported having very good feelings for Google's Software Engineer interview process in United States.

Google Work Experiences