Sent out resume in December. Was contacted by a recruiter via e-mail a few months later, in May.
Set up a brief phone conversation with the recruiter, then a one-day technical/behavioral interview loop.
Interviewers were supposed to ask specific questions about frontend engineering. Ended up over-prepping based on experiences I'd read, since no interviewers asked questions any deeper than "do you understand how Promises work". The interviews mostly focused on general algorithms questions.
The recruiter had also shared Google-curated interview prep packets, which was a surprise.
The loop went well. I was able to meet with various technical leads for prospective teams, one in-person in Kirkland.
Offer extended in June; accepted in July.
Given a string like "{a,b,c}d", provide an algorithm to expand this string, similar to how Bash expands strings (e.g., "ad bd cd").
You're running a silent auction and need to print betting sheets for auctioneers. Some numbers are ambiguous when flipped upside down. Implement a function to determine if a line should be placed underneath an auctioneer's number to disambiguate it from other possible readings (e.g., 118 can be read as 811).
General JavaScript questions covering a basic understanding of async and ES6 Promises.
Using the first letter of each US state, and assuming travel is only allowed between consecutive states, implement a program to exhaustively generate all possible words. This can be achieved by starting at any given state and "driving" between states (e.g., Missouri - Oklahoma - Missouri spells "MOM").
The following metrics were computed from 96 interview experiences for the Google Software Engineer role in Seattle, Washington.
Google's interview process for their Software Engineer roles in Seattle, Washington is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Google's Software Engineer interview process in Seattle, Washington.