Taro Logo

Software Engineer Interview Experience

March 1, 2022
Positive ExperienceNo Offer

Process

A Google recruiter reached out to me on LinkedIn. We set up a phone screen, and then I was scheduled for an online coding assessment.

The assessment was 45 minutes long, and I was on the phone with a facilitator to help me through the steps. The assessment wasn't hard; it was reasonable, like an easy LeetCode problem. However, I didn't have enough time to finish. I needed two hours, not 45 minutes, but I knew how to complete all the steps.

Essentially, you have to list:

  • Assumptions
  • Observations
  • Questions
  • Pseudocode
  • The actual working implementation
  • Testing outputs
  • Efficiency

This is quite a bit to fit in just 45 minutes.

Overall, the people seemed relatively nice. Although it's unfortunate I didn't pass the assessment, I'm not sure if I would have passed the next five steps, which are more data structure/algorithm heavy. My life goal is not to pass a Google interview, lol. I am what I am, and I just thought it was worth checking out.

Questions

Assumptions:

Observations:

Questions:

Pseudo:

Solution:

Tests:

Efficiency:

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