Taro Logo

Software Engineer Interview Experience

January 1, 2014
Neutral ExperienceNo Offer

Process

I had 5 onsite interviews.

One interviewer was so rude and that showed he is not experienced. He didn't allow me to think further and just pushed me to implement my first solution, which I had mentioned would take a long time to implement. Clearly, I didn't manage to finish on time, and he left the room after describing what a mess I had made. He was very arrogant.

He was being shadowed, though.

The fourth interviewer was a bit better but still had communication problems. He kept interrupting me while I was implementing my code. I had to stop him by telling him to just stop and let me finish my code, and then I would review it with him and he could feel free to ask questions. He ultimately apologized in the end, but clearly, I became rude to him this time because he was just bugging me. In the end, this would turn against me, I guess.

I am waiting for the interview results.

The other three interviewers were polite and experienced.

I would say an interview has two sides, and your side is the more important side. However, there is another side who might not be experienced enough to manage an interview session.

Questions

Honestly, not difficult questions. Just basic stuff.

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