Google's Aug 5 WA WARN: 52 Cuts, 7 Buildings, and Why Recruiters Are the Steal

On Aug 5, 2026, Google filed a Washington WARN cutting 52 employees across Kirkland, Redmond, three Seattle offices, and roughly three remote workers. It is Google's largest publicly disclosed Washington cut since Alphabet's 2023 restructuring, and it is small enough that a sourcer can work it as a named-target list instead of a search. The counter-intuitive move: the recruiters on the list are the highest-leverage hires in the pool.

What the filing actually says

Google's Aug 5, 2026 Washington WARN eliminates 52 roles across seven buildings in Kirkland, Redmond and Seattle, plus about three remote workers, with separations staggered from early September through Oct 4. Notifications began on Jul 8 and ran through Aug 4, meaning the earliest-notified Kirkland ICs have already been on the market for weeks by the time you read this.

Roles named in the filing:

• Software engineers
• Engineering managers and product managers
• Mechatronics engineers
• UX designers
• Recruiters

The mix matters. A filing that pairs mechatronics engineers with UX designers and PMs in the same 52-person cohort does not read like a horizontal RIF. It reads like a specific hardware-adjacent product pod (or two) winding down. Sourcers should look for clustered team affiliations inside profiles, not just "ex-Google, Seattle."

For context, the Puget Sound Business Journal notes Google has grown past 8,000 local employees. That makes this cut roughly 0.65% of Google's WA footprint. It is a scalpel, not a mass event, which is why the segmentation below actually works.

The 52 broken down by building and date

Here is the WARN split by location, headcount, and notification window, mapped against the Seattle supply pools in Refolk's index of professional profiles.

The Kirkland cohort is the epicenter, and it is also the coldest. Those 21 ICs were notified as early as Jul 8, which means many have been quietly interviewing since mid-July. Redmond's eight, by contrast, got their notice on Aug 4 with an Oct 4 separation. They are still inside an active severance runway with a full month of Google email access and a soft floor under negotiation. Different buildings, different playbooks.

Why the recruiters on the list are the sleeper hire

The most valuable people on this WARN are not the software engineers. They are the recruiters, and the numbers say why.

In Refolk's index, Seattle surfaces about 200 profiles for "Software Engineer / Senior / Staff" but only 43 for "Recruiter / Technical Recruiter / Sourcer." That is a 4.7x thinner supply on the recruiter side. Worse for competitors, the top employers of Seattle recruiters in the index are staffing shops, not FAANG in-house teams:

• Insight Global (3)
• The Brattle Group (2)
• Port of Seattle (2)
• NW Recruiting Partners (2)
• AWS (1), Amazon (1), TEKsystems (1)

Read that carefully. When ex-Google recruiters land in Seattle, they historically flow to Insight Global and TEKsystems, not back to Amazon or Microsoft in-house. Which means a startup that moves fast on a WARN'd Google recruiter is not competing with FAANG in-house talent teams for that person. It is competing with staffing agencies. Startups can out-mission and out-title staffing agencies all day.

There is a second reason. A Google recruiter carries a live mental map of every candidate the Seattle org was actively pursuing this quarter: shortlists, pass reasons, competing offers, comp bands, which staff engineers ghosted, which teams overpaid. That knowledge does not sit in an ATS you can export. It sits in the recruiter's head, and it walks out the door at separation.

4.7x

What to actually ask the recruiter in the first call

Skip the "tell me about your background" opener. If you have 20 minutes with a WARN'd Google Seattle recruiter, spend it on:

1. Which pods were they filling for in Q2 and Q3 2026?
2. Who were the top three candidates they lost to competing offers, and to whom?
3. What comp bands did Google use for L5 and L6 in Seattle this year?
4. Which internal hiring managers were pipeline-hungry and which were slow to close?

That is a 90-day head start on your own sourcing plan, delivered by someone who is now on your payroll.

The Kirkland vs Redmond timing arbitrage

Kirkland's 21 ICs have been notified since as early as Jul 8. Redmond's eight got their notice on Aug 4. That four-week gap changes how each cohort responds to outreach, and you should segment cadence accordingly.

Kirkland cohort behavior to expect:

• Already three to four weeks into a covert job search.
• Likely has two to four interview loops in flight at Amazon, Microsoft, or Apple.
• Responds best to specificity: named team, named comp, named timeline. Generic "we're hiring" gets deleted.
• Comp anchor is whatever Amazon offered them last week.

Redmond cohort behavior to expect:

• Still inside the severance runway. Full Google email, full Slack access, less panic.
• Will negotiate harder but reply faster to warm intros because they have runway to be picky.
• Comp anchor is still their Google total comp, including unvested equity they are about to lose.
• Sep and Oct calendars are wide open for onsites.

This is the exact gap Refolk closes for a filing like this one: you describe the cohort in plain English, including the building, the role, and the separation window, and get a ranked shortlist instead of a keyword search that also returns every Google intern from 2014.

Mechatronics engineers are the rarest role on the list

Mechatronics engineers do not appear in the Seattle "Software Engineer" top-titles at all in Refolk's index. If you are a hardware, robotics, or AV startup in the Kirkland-Redmond corridor, treat the WARN'd mechatronics ICs as a named list, not a search query.

Mechatronics is the discipline that combines mechanical engineering, electronics, and embedded software. It is what you hire when you need someone who can spec a servo, lay out the driver board, and write the firmware that controls both. Washington has been one of Google's largest engineering hubs outside the Bay Area for more than 20 years, with local work spanning Android, Chrome, Cloud, Maps and Ads, which is part of why a hardware-adjacent pod winding down in Kirkland is a plausible read on this filing.

Practical implication: mechatronics is one of five role categories inside a 52-person filing, so the affected mechatronics headcount is small by construction. If you are hiring in that discipline in the Pacific Northwest this quarter, you have a narrow window to identify and warm-intro those engineers before the September separations start.

The capex-versus-headcount frame that lands in outreach

Alphabet has raised its 2026 capital expenditure forecast to between $195B and $205B, with much of the spending expected to support AI infrastructure. Google filed a WARN for 52 Washington employees on Aug 5. Those two facts, next to each other, are the sharpest opener you can send to a WARN'd IC this month.

You were cut from the team that ships while your employer guided to $195B to $205B in capex. Come build something you own.

That framing is not a rhetorical flourish. It is factually anchored, it flatters the recipient's technical judgment, and it names the specific dissonance every WARN'd Googler is feeling but has been trained not to say out loud. It works because it is true.

0.65%

Who you are actually competing with for these 52

For the engineers, you are competing with Amazon, Microsoft, and Apple. For the recruiters, you are competing with Insight Global and TEKsystems. And this month, you are also competing with Zillow's own recovery.

In Refolk's index of Seattle "Software Engineer / Senior / Staff" profiles, the top current employers are:

• Amazon (6)
• Microsoft (5)
• Apple (3)
• Google (2)

Translation: an ex-Googler exiting to the Seattle market ends up at Amazon or Microsoft by default. If your startup is not on that shortlist inside the first 10 days after their WARN notice, you are pitching a candidate who already has two Amazon loops booked.

Adjacent pressure on the same bench: Zillow Group disclosed it is eliminating 91 jobs in Washington state this week, weighted toward senior staff. Senior IC and manager supply in Seattle is elevated across the whole month, which means everyone who wants to hire ex-FAANG in the Pacific Northwest is running the same play at the same time. Speed and specificity are the only edges.

For sourcing ex-Google engineers at this scale, the workflow that wins is: pull the WARN'd cohort by building and notification date, cross-reference against your product needs, and reach out with a named-team pitch inside 72 hours. That is what Refolk is built for, and it is the difference between hiring ex-Google software engineers and reading about them joining Amazon next quarter.

FAQ

How do I find the 52 people named in Google's Aug 5 Washington WARN?

The WARN filing itself does not publish individual names, only role categories, buildings, and notification and separation dates. To reconstruct the pool, cross-reference the role list (software engineers, EM/PM, mechatronics engineers, UX designers, recruiters) against public profiles that show Google Kirkland, Redmond, or Seattle affiliations and either a recent "open to work" flag or a July or August 2026 tenure end. Refolk lets you describe the cohort in plain English, including building and separation window, and returns a ranked shortlist without hand-building boolean strings.

Why should I hire a laid-off recruiter instead of a software engineer?

Because supply is thinner and switching costs are higher. Seattle surfaces about 4.7x more software engineer profiles than recruiter profiles in Refolk's index, and ex-Google recruiters typically flow to staffing agencies rather than FAANG in-house teams, meaning startups compete with Insight Global and TEKsystems instead of Amazon. A WARN'd Google recruiter also carries live pipeline knowledge, comp bands, and hiring-manager intelligence that arrive with them on day one.

What is the right outreach window for the Kirkland cohort vs the Redmond cohort?

Kirkland ICs were notified between Jul 8 and Aug 4, so many are already three to four weeks into a covert search and likely have Amazon or Microsoft loops booked. Reach out immediately with a specific, named-team pitch. Redmond's eight were notified Aug 4 with an Oct 4 separation, so they have a full severance runway, will negotiate harder, and can afford longer onsite scheduling into September and October. Segment your cadence and comp anchor by building.

Is 52 people big enough to justify a dedicated sourcing sprint?

Yes, because it is 52 people you already know exist, at named buildings, with known separation dates, in roles you can filter for. Compare that to a generic search for "ex-Google Seattle senior software engineer," which returns thousands of profiles with no signal about who is actually on the market this quarter. Named lists convert better than open searches, and mechatronics engineers in particular are rare enough in the Pacific Northwest that even a small shortlist is worth a dedicated week of outbound.