Taro Logo

Software Engineer Interview Experience

July 9, 2019
Neutral ExperienceNo Offer

Process

A recruiter contacted me a few months before I was set to graduate from university.

First, there was a non-technical phone screen where I was asked about my interests and future career plans. The next step was to complete an online coding challenge. After this, I had a technical phone interview with an engineer. They asked me a hard problem that I wasn't able to figure out in 45 minutes.

Had I passed that stage, the next and final step would have been an onsite interview. My feeling is that there is some element of luck involved in the technical phone screen. Based on the questions I've seen given to other interviewees, there's quite a bit of variance in the difficulty of questions asked.

Questions

I'd rather not give out the exact details, but my phone interview problem was a tricky one. It involved an array representation of a data structure.

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