Taro Logo

Software Engineer Interview Experience

January 1, 2019
Neutral ExperienceNo Offer

Process

There was a 90-minute coding challenge online prior to the phone technical interview, with two questions, 45 minutes each.

The scheduling of the phone technical interview was a nightmare and took about a month and a half due to a lack of communication on their end.

Eventually, I got to the phone technical interview, which involved editing a Google Doc while someone on the other end watched. I performed quite well on it (even catching something the interviewer missed and adjusting the code), but did not advance to the next stage, without a reason, of course.

I was never contacted by my recruiter, which is standard, so I reached out and received the email rejection.

I'm not salty about not getting the position, but I was a bit shocked at the lack of professionalism for a company like Google.

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