Software Engineering Interview Experience - Seattle, Washington
Process
Initial application
Coding snapshot (2 problems - 90 minutes; looking at documentation is ok)
Back-to-back phone interview with Google engineers (roughly 45 minutes each).
After that, the host matching phase asks basic questions, but expect detailed answers, such as what team you are interested in and why.
Questions
This was a variation of the problem found at https://leetcode.com/problems/decode-string/.
Was this helpful?
Interview Statistics
The following metrics were computed from 4 interview experiences for the Google Software Engineering role in Seattle, Washington.
Success Rate
Google's interview process for their Software Engineering roles in Seattle, Washington is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very good feelings for Google's Software Engineering interview process in Seattle, Washington.
Google Work Experiences
- 1.0I hate myselfSoftware Engineering • Former EmployeeSeattle, Washington, United StatesNovember 22, 2010Pros: Free food, easy work hours.Cons: Never got to see my product make it to launch.
- 5.0Good software companySoftware Engineering • Current EmployeeLondon, England, United KingdomOctober 22, 2025Pros: Benefits, good salary, no real cons.Cons: No real cons for now.
- 3.0Good projects, good people, but lots of chaosSoftware Engineering • Current EmployeeMountain View, California, United StatesApril 2, 2025Pros: - You get to work with smart people. - If you're on the right team, you can work on cutting-edge tech.Cons: - Too many reorgs and shifting priorities recently. - Work-life balance is not as good as it used to be, but the extra effort also often goes unrecognized.
Google Interview Questions
