Taro Logo

Software Engineer Interview Experience

October 23, 2014
Positive ExperienceNo Offer

Process

The interview process was handled in a very professional manner throughout. It's great to know that your recruiters will accommodate your schedule (e.g., giving you a few weeks to prepare if you need that time) and keep you updated at every stage.

Although I originally applied for a non-engineering job (given my background), I was contacted by a recruiter who asked if I was willing to apply on the software engineering track, with a focus on my niche skills. Since it didn't hurt to try and actually learn about computer science fundamentals, I gave it a shot.

I was interviewed by 6 people total: 1 phone screen and 5 onsite interviews in a single day, with lunch in the middle. Over the course of the process, I was in contact with 2 recruiters: one for the phone screen stage and one for the on-site stage.

Some of the interviewers seemed to be aware of my niche skills and had obviously been selected to interview me based on the match between their skills and mine. Some of the interview questions did reflect that concentration, but most didn't and were focused on CS fundamentals, algorithms, and data structures.

Overall, it was fun and challenging.

Questions

The most unexpected question I had to answer had to do with some research I did more than 10 years ago as part of my PhD dissertation.

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