Taro Logo

Software Engineer Interview Experience

May 1, 2018
Neutral ExperienceNo Offer

Process

I applied through the LinkedIn jobs page and was invited to take a Snapshot challenge (Google's version of a coding challenge). A couple of days later, I was asked to fill out a host matching questionnaire and provide availability for two back-to-back interviews.

A week after the interviews, I was asked to schedule a third interview. The recruiter forgot to give me the date, which required multiple attempts to reach out in order to reschedule.

Overall, the process was pretty long and exhausting. Three phone interviews plus a two-hour coding challenge (with more interviews if I get a host match interview) has burnt me out a little bit. The unprofessionalism in interview coordination also provided a lot of unnecessary stress during the process.

It took me around one week to hear back after the first two interviews and three to four weeks to hear back after the third interview.

Questions

Interview 1: Easy-ish question involving data structures.

Interview 2: LeetCode medium with DP.

Interview 3: Design-ish problem, LeetCode hard.

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