Taro Logo

Software Engineer Interview Experience - Seattle, Washington

January 3, 2025
Positive ExperienceNo Offer

Process

Phase 1: Initial Screening

  1. Recruiter Screen (30 minutes)

The recruiter asked questions to assess my resume and experience, such as:

  • "Can you briefly describe your most challenging project and your role in it?"
  • "Why are you interested in Google?"
  • "What are your salary expectations?"
  • "Are you comfortable working on distributed systems?"

I shared details about my intelligent document processing experience, highlighting achievements, and kept my answers concise and confident.

Phase 2: Technical Phone Interview (45 minutes)

The interviewer briefly introduced themselves and jumped into the problem:

Problem:

"Given a matrix of integers where each cell represents the cost of stepping on it, write a function to find the minimum cost to reach the bottom-right corner from the top-left corner, moving only down or right."

I clarified the problem, asked if there were constraints (e.g., matrix size), and confirmed edge cases. Then, I:

  • Explained a brute-force solution using recursion.
  • Optimized it with dynamic programming, detailing time and space complexity.
  • Wrote clean code in Python.

Questions

About OOPs Concepts and Asynchronous Programming

Was this helpful?

Interview Statistics

The following metrics were computed from 96 interview experiences for the Google Software Engineer role in Seattle, Washington.

Success Rate

16%
Pass Rate

Google's interview process for their Software Engineer roles in Seattle, Washington is very selective, failing most engineers who go through it.

Experience Rating

Positive74%
Neutral18%
Negative8%

Candidates reported having very good feelings for Google's Software Engineer interview process in Seattle, Washington.

Google Work Experiences