Taro Logo

Software Engineer Interview Experience - Mountain View, California

January 22, 2013
Negative ExperienceNo Offer

Process

The interviewer called 15 minutes late. He had an accent and a deep voice. I was not able to understand a word, nor the questions.

This went on for the whole interview, and I was feeling very uncomfortable. I kept telling him, "Could you please repeat what you said? I didn't hear you well." We both were frustrated.

To compensate, he said he would leave the shared document open for 30 minutes after the interview so that I could have more time to solve the problem. I was happy with this remedy, but when I tried to input my solution after 10-15 minutes, I was unable to do so because the document was blocked!

I informed the recruiters of what happened, and then they gave me another chance interview, which was good. I managed to solve all coding problems well. But then I received an email stating that I didn't make it to the second round based on both interviews.

To make sure that was the case, I asked the recruiter to confirm, and she did.

Overall, the experience was very bad. Such a process (although you guys are doing a great job in getting brainiacs) is doing injustice to many extremely qualified people!

Questions

Print the largest sequence in an array.

Print the indices of numbers of an array that is a subset of another array.

Was this helpful?

Interview Statistics

The following metrics were computed from 748 interview experiences for the Google Software Engineer role in Mountain View, California.

Success Rate

20%
Pass Rate

Google's interview process for their Software Engineer roles in Mountain View, California is very selective, failing most engineers who go through it.

Experience Rating

Positive64%
Neutral23%
Negative14%

Candidates reported having very good feelings for Google's Software Engineer interview process in Mountain View, California.

Google Work Experiences