Taro Logo

Software Engineer Interview Experience

November 30, 2015
Negative ExperienceNo Offer

Process

I was contacted by a recruiter roughly two months after completing the third level of programming challenges on foo.bar. The recruiter was nice, but it was a bit frustrating that he did not take the time to read the application materials he had requested (resume and transcripts). When we talked on the phone, it was clear he was just scanning my resume for the first time.

I ended up having two technical phone screens. Both engineers I spoke with seemed distracted and apathetic. The second was particularly frustrating: the engineer was talking with a third party the whole time, and at the end, when I asked him what he thought of my code, he raved about my performance. Then, it turned out he didn't even recommend me for an onsite. It was super frustrating.

I left feeling like they made little effort to actually evaluate my qualifications and ended up wasting a bunch of my time. I think a lot of their process depends on the luck of the draw with who you interview with.

Questions

Museum Problem

Given a 2D grid of rooms which can be closed, open with no guard, or open with a guard. Return a grid with each square labeled with the distance to the nearest guard.

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