Taro Logo

Software Engineer Interview Experience

October 1, 2015
Negative ExperienceNo Offer

Process

In October, I was contacted and filled out a survey about CS interests and experience. Following that, I scheduled back-to-back phone interviews. One interview went acceptably, while the other went quite well.

Two weeks later, I was contacted for a third phone interview. Another couple of weeks passed, and I was informed I was in the host matching phase. This was in early December.

I waited two months, with regular check-ins to my recruiter, and never received a call from an engineer. In early February, I was told there weren't any "strong enough matches" and thus I would not receive an offer.

It seems they need to streamline their process, and I should have been rejected after the interviews. It was a shame I didn't even get to speak with a project leader, which led to me and several others being strung along without benefit.

My recruiter was not unhelpful but provided very little information during the host matching phase, beyond "keep waiting and keep your fingers crossed."

They do provide decent resources to prepare for the interview and host matching process.

Questions

Tricky questions involving arrays and graphs. It's helpful to think of data structures you can use to solve the problem.

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