Google's Aug 5 Kirkland WARN: The 30-Day Ex-Google Recruiter Window

On August 5, 2026, Google filed a Washington WARN cutting 52 employees across Kirkland, Redmond, and Seattle. Buried in the role list, next to software engineers and mechatronics engineers, sit a handful of technical recruiters, and the window to sign them closes in about four weeks.

If you are a Series A or B founder building a technical hiring function in Seattle, or a TA leader planning a Q4 push, this is the most portable talent cohort in the Puget Sound this quarter. The rest of this piece is the tactical playbook.

Why this WARN is different from every other 2026 Google filing

This is Google's largest publicly disclosed Washington reduction since Alphabet's 2023 restructuring, and the first FAANG WARN in the current cycle to explicitly name recruiters alongside engineers in a single Puget Sound batch. Composition is what matters. Alphabet is guiding 2026 capital expenditure toward $195B to $205B, most of it on AI infrastructure, so this is reallocation, not distress. Recruiters cut in a reallocation wave screen dramatically better in reference checks than recruiters cut in a performance wave.

The dated facts:

• 52 total roles eliminated across Washington in the Aug 5 filing
• ~21 in Kirkland (747 6th Street S. Building C, 451 7th Avenue S. Building D, and 425 Urban Plaza Suite #223)
• ~20 in Seattle (620 Boren Avenue, 1000 Mercer Street, 520 Westlake Avenue)
• 8 in Redmond, with separations anticipated Oct. 4
• Notifications began July 8; separations run Sept 6 through Oct 4
• Roles include software engineers, engineering and product managers, mechatronics engineers, UX designers, and recruiters

Those street addresses are not trivia. They are where agencies will door-knock in September. If you plan to compete with Recruiting from Scratch and Axe Recruiting for the recruiter subset, you need a Seattle-based sourcer on the ground before they sign these people as 1099 sub-contractors.

The Google Kirkland layoffs recruiters cohort, in one table

Here is the dataset every TA leader planning a September push should have on one page.

The bottom row is the whole point. In Refolk's index, only about 1.4% of the US technical recruiter population has Google on their resume. The Aug 5 cohort is a fraction of that fraction, concentrated inside a 15-mile radius of Microsoft Redmond and Amazon South Lake Union.

412

Why ex-Google recruiters are the arbitrage, not ex-Google engineers

The smarter buy is the recruiters who used to hire the engineers, not the engineers themselves. Recruiters carry the rolodex, and the rolodex is the compounding asset.

A senior technical sourcer who spent three years running Google Cloud ML hiring out of Kirkland has warm intros to hundreds of Amazon and Microsoft ML engineers, because that is who they were poaching from. Axe Recruiting's own market read puts it plainly: for any company trying to hire AI and ML talent in Seattle in 2026, the central challenge is not finding qualified candidates, it is competing with Amazon and Microsoft for them. Ex-Google Kirkland sourcers already know how to win those exact battles, on those exact teams, in those exact zip codes.

Compare the supply curves:

• Ex-Google engineers: tens of thousands globally, dozens of buyers, saturated LinkedIn inboxes.
• Ex-Google technical recruiters: ~412 globally, ~1.4% of the US recruiter pool, and a Seattle-clustered subset measured in single digits per WARN event.

The FAANG recruiter poach pool is structurally small because Google has historically been sticky for recruiting talent. Refolk's sample of the top 25 employers for the "Google + technical recruiter" cohort shows Google itself dominating 18 of those 25 slots, meaning most of these people have never left. When they do leave in a batch, it is a rare available cohort.

The rolodex is the compounding asset. Buy the recruiter, and the engineers show up in month two.

The 30-day signing window, mapped

The signing window is roughly four weeks starting the first week of September, and the strongest candidates will be off the market by mid-November. Standard Google severance historically covers 60+ days of paid transition, which is what puts the cliff at mid-November for the earliest separations.

1. Week of Sept 1: Kirkland separations begin. Severance clocks start. This is when agencies pitch 1099 contract work.
2. Weeks of Sept 8 to Sept 22: The "I need a break" phase. Strong candidates take one to two weeks off, then start real conversations. Best inbound window.
3. Week of Oct 4: Redmond separations. Second wave of availability, including the 8-person Redmond subset.
4. Late Oct to mid-Nov: Severance cliffs approach for early-September separations. Offer decisions crystallize.
5. After Nov 15: The strongest candidates are signed to Anthropic, xAI, Meta, or established Seattle AI infra teams. Remaining pool skews toward less senior or less specialized profiles.

Competing Seattle demand is real. Nominal, the LA industrial-AI company opening a permanent Seattle office, currently has 11 people at a downtown co-working space and expects to more than double that by year-end. Silurian is building foundation models for Earth simulation out of Seattle. Boundary (BAML) is hiring on the AI infra side. Anduril, which assembles talent from Oculus VR, Palantir, General Atomics, SpaceX, Tesla, and Google, is active in the region. All of them are pulling from the same well. If you are not talking to these ex-Google sourcers by mid-September, they will be running req loads for a competitor by October.

How to actually find this cohort before the agencies do

Filter for Google tenure that ended in Q3 2026, technical recruiting or sourcing titles, and a Seattle metro location, then move on outreach within 72 hours of the target's last day. The bottleneck is not the search, it is the specificity of the query and the speed of first contact.

The manual version is painful. You are stitching together LinkedIn filters that do not really support "left Google in the last 45 days," GitHub for cross-checks on which teams they staffed, and open-web signals like conference speaker bios and Puget Sound recruiter meetup rosters. This is the exact gap Refolk closes for sourcing technical recruiters in Seattle: you describe the person in plain English and get a ranked shortlist across LinkedIn, GitHub, and the open web.

The signals that separate the strong candidates from the rest:

• Req specialty: Did they staff ML infra, Cloud, Search, Ads, or hardware? Cloud and ML infra map cleanest to Seattle AI startup needs.
• Tenure length: 3+ years at Google usually means they built real internal networks. Sub-18-month tenures are less differentiated.
• Prior stops: Ex-Amazon or ex-Microsoft recruiters who then went to Google understand all three hyperscaler comp structures. Unusually valuable in a bidding war.
• Conference and community footprint: RecOps Slack, SourceCon speaker history, local Seattle recruiter meetups. These correlate with rolodex quality.

The competitive context: WA is already saturated with cut talent

The Google WARN lands in an already-crowded Washington candidate market, which means recruiter quality signal beats recruiter quantity signal for the next six weeks.

Washington WARN filings hit 3,420 in the first quarter of this year, up 56% from the previous quarter. Amazon alone cut more than 2,300 Washington positions in the current cycle. Oracle cut 491. That saturation cuts two ways:

• Against you: candidates have options. A senior technical sourcer will get inbound from ten agencies and five in-house teams in their first week off.
• For you: the noise gives you cover. Well-targeted, specific outreach from a founder ("I saw you ran GCP ML hiring; we are Series B, 40 people, hiring 12 ML engineers by March, here is why our comp structure works for you") cuts through the agency spam trivially.

1.4%

Google holds close to 1.8 million square feet across greater Seattle and Kirkland. This cohort is embedded in local networks, not remote imports. They know the school pipelines, the meetup organizers, the ex-Amazonians who are about to churn. Remote-only offers waste that arbitrage. The differentiated pitch versus a Bay Area competitor is in-person or hybrid-Seattle, ideally within a short drive of Kirkland or SLU.

What to say in the first message

Skip the "sorry to hear about Google" framing, lead with the specific req load and comp structure, and close with a 20-minute window in the next five business days.

The generic condolence opener is the tell that separates in-house TA leaders from experienced sourcers. Ex-Google recruiters have read that template. They wrote that template. What actually moves them:

1. Specificity about your req load: "12 ML engineers, 4 infra, 2 staff-level, target close by end of Q1 2027."
2. Specificity about comp: Cash band, equity band, refresh policy. Ex-Google recruiters read comp fluency as a proxy for whether you will be a functional partner.
3. Specificity about their prior work: Reference a specific team they staffed at Google. This is where an index that surfaces open-web signals beats a LinkedIn scroll.
4. A 20-minute window in the next five business days, not "let's find time next week."

For founders moving on the Google WARN August 2026 cohort specifically, the play is simple: build the shortlist this week, first-touch by mid-September, second-touch with a comp band by end of September, offers out by mid-October. Anything slower and you are buying the second-tier remaining candidates from the agencies at a 20% premium.

FAQ

How many of the 52 Google WA cuts are actually recruiters?

The state filing does not break out a role-by-role count, but the disclosed role list explicitly names recruiters alongside software engineers, engineering and product managers, mechatronics engineers, and UX designers. A reasonable working assumption is a single-digit recruiter subset out of 52, concentrated in Kirkland where Google Cloud and ML hiring has historically been run. Against a global ex-Google technical recruiter universe of ~412, even four to six available profiles in one metro in one month is a meaningful cohort.

Should I hire these people as 1099 contractors or full-time?

Depends on your req load. If you have 20+ open technical reqs and a six-month horizon, full-time wins because you get the rolodex plus the process-building. If you have 5 to 10 reqs and are still finding product-market fit, a 1099 contract with a conversion clause is the smarter buy, and it is what the agencies will offer, so you need to at least match the structure. Ex-Google recruiters cut in a reallocation are often open to either, and the severance runway (typically 60+ days paid) gives them room to be selective.

Is Seattle actually better than the Bay Area for AI recruiter poaching right now?

For this specific cohort, yes. Seattle's talent density is second only to the Bay Area in raw numbers of experienced AI practitioners, and the ex-Google Kirkland recruiter subset lives within 15 miles of Microsoft, Amazon, and every Seattle AI startup worth hiring for. Bay Area ex-Google recruiters are competing with hundreds of AI startup TA roles; Seattle ex-Google recruiters are competing with dozens. The math favors Seattle for the next quarter.

What is the fastest way to build a shortlist without an agency?

Start with a plain-English query against an index that spans LinkedIn, GitHub, and the open web, then hand-verify the top 8 to 12 profiles. The manual LinkedIn filter path takes a week and misses the candidates who have not updated their profile yet, which is most of them in the first 30 days post-separation. Tools built for this pattern, including Refolk, compress the shortlist step to under an hour so you can spend the rest of the week on outreach quality instead of list-building.