Taro Logo

Software Engineer Interview Experience

June 1, 2015
Negative ExperienceNo Offer

Process

I had a first phone interview where I was asked some questions pertaining to C and did some coding. The interviewer was slightly condescending, but it was generally okay. A few weeks later, I had another phone interview. It started right off the bat with the interviewer asking me to write a function declaration in C++ without even an introduction.

The interviewer also had an extremely thick accent, and the connection was bad, so I could barely hear what she was saying. When I asked her to repeat herself several times to make sure I understood, she became very impatient and extremely rude.

For the last question, I was in the middle of optimizing my code when she abruptly specified that time was up and immediately hung up. It honestly seemed like she had given up on me midway through the interview after I had asked her to repeat herself a couple of times. After that, it felt like she was barely paying attention to what I was saying.

This was one of the worst phone interviews I've had.

Questions

First interview:

  • Basic C questions
  • Read a piece of code and described what it does
  • Wrote a function to merge two linked lists.

Second interview:

  • How to design an interface
  • How to create a class.

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