Taro Logo

Software Engineer Interview Experience

October 9, 2014
Neutral ExperienceNo Offer

Process

I received an email from a recruiter stating that they wished to contact me because I had dropped off my resume last year. They wanted to see if I was still interested in a particular position.

After that, I had an interview with one of the engineers. The interview was fair, including some behavioral questions and one technical question. I was asked to talk about the algorithm for the problem and its complexity before writing it down in a Google Doc. After I finished, I was also asked to state any potential issues.

Two days later, I got a call from the recruiter who informed me that I needed to have a second phone screening with another engineer.

The second interview followed a similar format to the first, with the exception of more behavioral questions and two technical questions. The interviewer only asked me to provide the algorithm for the first technical question. However, I was required to actually write down the code for the second one.

I couldn't finish writing the code because the interview was limited to one hour, and the interviewer called me somewhat late.

A few days later, the recruiter called to inform me that I did not advance to the final round.

Questions

Array ordering

Find the submatrix.

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