Taro Logo

Software Engineer Interview Experience

March 8, 2015
Neutral ExperienceNo Offer

Process

Applied through an employee referral.

Was contacted by a recruiter who asked me about my background and told me about the interview process: 1-2 phone screens and then approximately 5 on-site interviews. He then scheduled a phone screen with one of their engineers.

The phone screen was a bit odd, I think. The interviewer didn't really introduce herself and jumped right to the questions. The rush made me a little more nervous, but I guess she didn't think the usual background/interests chat mattered. Otherwise, the format was very similar to other technical phone screens I've done.

It took a rather long time for the recruiter to get back to me. Actually, it wasn't until I sent him an email over 3 weeks later that he promptly replied. He stated he coincidentally just received the results and there weren't enough positives to move forward.

Questions

Started off with some knowledge questions about graphs (no coding).

Then, a rather tricky combinatorics problem that involved a base-9 number system (as opposed to binary base-2 or hex base-16).

I stumbled on the solution in the end, but was way too nervous, and that probably didn't look too good.

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