Zillow Cut 7% While Revenue Grew 18%: Working the 91 Seattle Names

Zillow filed a Washington WARN notice on August 4, 2026 covering 91 Seattle roles effective October 5. The same week, CEO Jeremy Wacksman told investors Zillow is "rapidly becoming an AI-native company," and the cut landed while revenue grew 18% year over year. If you source senior ML leadership, the market is misreading this one.

What the WARN actually says

Zillow's Washington WARN lists 91 Seattle roles from a global reduction of roughly 500 (about 7% of a 7,058-person workforce as of March 31), and the axe fell on directors and senior managers rather than junior IC bands. That skew is the entire story.

The titles named in the filing, per HousingWire's read of the notice:

• Director of engineering
• Director of legal
• Senior managers of machine learning engineering
• Senior managers of research science
• Senior managers of software development engineering
• Principal content, program, and product designers
• Business intelligence manager
• Senior program managers and senior software development engineers

Employees were notified August 4 and terminated effective October 5, 2026. The worksite is Zillow Group HQ at 1301 Second Ave, Floor 36, Seattle. Per HousingWire, severance included a six-month COBRA-equivalent lump sum, which matters for how you pitch these candidates.

91

Why Seattle is only 18% and why that number is misleading

Seattle looks like a small slice at 18% of the global cut, but Zillow went "Cloud HQ" remote-first in 2020, so Seattle headcount is disproportionately senior. This is a decapitation of the leadership layer, not a proportional trim.

The mechanism is simple. When a company adopts distributed-first hiring, the roles that stayed anchored to the legal HQ address are the ones with fiduciary, reporting, or director-level obligations. The junior and mid-tier ICs got hired wherever they lived. So a WARN notice that names 91 Seattle employees at a company that has been remote-first for six years is filtering, by geography, straight into the org chart's top three or four bands.

If you are hiring your first head of ML at a Series A, treat this WARN as a shortlist, not a long list. Ninety-one names in a normal 500-person cut would be background noise. Ninety-one names at post-Cloud-HQ Zillow are almost entirely people who ran teams.

The January vs August sequencing is the tell

Zillow already ran its performance-based reduction earlier this year, which means the August cohort is structural, not underperformance, and any recruiter who screens both rounds the same way will discard exactly the senior ICs worth calling.

Chrissy Roebuck, Zillow's spokesperson, told Axios the January 2026 round of about 200 people was explicitly performance-based, following annual reviews. The August round is 2.5x larger and framed differently: Zillow told GeekWire the cuts were about "having the right people in the right roles and being able to move faster." That is org-design language, not a performance PIP.

The practical implication for sourcers:

1. The performance filter has already been applied, in January, by Zillow itself.
2. The August names cleared that filter earlier in the year.
3. The August names are being let go for structural reasons that have nothing to do with individual output.
4. Revenue grew 18% alongside the cut, so this is not a company in trouble shedding weight; it is a company reallocating a payroll line.

That is the "involuntarily available" pool. It is worth more than the raw title lists suggest.

The offshoring signal buried in the WARN

Zillow told the press AI did not drive the layoffs, but the WARN filing itself adds a line the announcement did not: some terminations "are the result of, or are expected to result in, the relocation or contracting out of operations and/or employee positions." Translation: the work still exists, the skills still matter, only the cost structure changed.

That reframes every conversation you have with these 91 people. Their skills were not obsoleted. Their salaries were the problem. If you are an AI-first startup that can offer equity and mission instead of matching a Seattle director base, you are competing on a completely different axis than Zillow was optimizing on.

The work still exists. The skills still matter. Only the cost structure changed.

Combine that with the six-month COBRA lump sum HousingWire flagged, and you get a very specific behavioral prediction: these candidates can afford to hold out. They will not take the first offer. Lead with the problem you want them to own, not with speed.

Refolk's index: Zillow is the #1 employer of this exact cohort

In Refolk's index, a US-wide search for real-estate and internet Directors of Engineering plus Senior Managers of ML returns 209 currently-employed people, and Zillow sits at #1 with 4 profiles, ahead of Compass (2), Cushman & Wakefield (2), and Redfin (1). That concentration is why 91 Seattle exits matter more than a generic 500-layoff headline.

Four out of 209 sounds small until you notice it puts Zillow ahead of every direct real-estate competitor. If you are staffing an AI-native proptech play, Zillow's roster was already an over-indexed talent pool for the exact leadership shape you need. The WARN just made a chunk of it available.

The comparable Seattle senior-ML pool is small

Named-comparable senior ML and applied-scientist ICs in Seattle concentrate at Microsoft, Apple, and DAT Freight & Analytics, per Refolk's index, which means the Zillow tranche is a rare batch drop into a market otherwise locked up at FAANG-scale employers. You do not usually get 91 senior names from one company in one month in this metro.

Widen slightly and it gets more interesting. KVI reported that Google also filed for 52 Washington cuts effective September 6, 2026. Stack those against Zillow's 91 effective October 5, and the sourcing window from roughly September 6 through year-end covers a meaningful share of the region's senior ML managerial supply. This does not happen twice a year.

The competitive read: Microsoft and Apple will absorb the ex-Zillow directors who want an incumbent's stability and a matching base. Anyone who wants to actually go build something at an AI-native shop is available to you, but only if you find them before every Seattle AI startup runs the obvious LinkedIn scrape.

How to actually work the list

Assume you have 6 to 10 weeks of clean access before the obvious names are all in conversations, and structure outreach around what these candidates actually need to hear.

• Skip the "sorry to hear about the layoff" opener. They took a structural cut alongside 18% revenue growth. They know they were not the problem. Anything that sounds like sympathy reads as condescension.
• Lead with the technical problem. These are people who ran teams at a company with real ML in production. Show them a problem that is technically harder or organizationally cleaner than what they left.
• Do not compete on base. With six months of COBRA lump sum plus severance, these candidates can wait. Compete on equity, scope, and reporting line.
• Use the Jan vs Aug distinction in your intake with the hiring manager. If the founder thinks "layoff = risky hire," walk them through the sequencing: performance-tied departures were in January, structural in August. This roster is the second group.
• Do not send the same message to a director and to a principal designer. The WARN names lump them together. Your outreach cannot.

Describing "senior ML manager who ran a team of 8+ shipping recommendation systems, left Zillow post-Aug 2026 WARN, not already at Microsoft or Apple" as a single sentence to Refolk beats stringing that same intent through Boolean strings, current-title filters, and departure-date guesses on LinkedIn Recruiter.

What "AI-native" language actually signals about the roster

When a CEO tells investors the company is becoming "AI-native" the same week the WARN drops 91 senior names, the signal for sourcers is that the roles being replaced are being replaced by lower-cost distributed teams plus tooling, not by fewer humans doing the same jobs. That is a hiring opportunity, not a warning.

The failure mode is treating "AI-native restructuring" as a proxy for "these people got outperformed by their own AI systems." That is not what happened here. Zillow denied AI drove the layoffs, the WARN itself points at contracting-out, and revenue grew 18% while the cut was announced. The people leaving built the systems Zillow now says are core to its future. They know how those systems work. They are three to six months away from your competitor's offer letter.

Work the list, not the headline.

FAQ

When exactly does the sourcing window open?

Employees were notified August 4, 2026 and terminated effective October 5, 2026. Practically, the notice period is when people start taking calls quietly, and the post-termination weeks are when they take them openly. If you want first-mover access, initial outreach from mid-to-late August through September is the right window. By November, the obvious names will be in late-stage conversations elsewhere.

How do I tell structural cuts from performance cuts at Zillow specifically?

Use the round. Zillow's January 2026 reduction of about 200 people was explicitly performance-based per spokesperson Chrissy Roebuck to Axios. The August 2026 reduction of about 500 people, 91 in Seattle, was framed as org design, disclosed contracting-out in the WARN, and hit senior titles disproportionately. If a candidate departed Zillow in January, dig on performance. If they departed in August or October, assume structural until the reference call says otherwise.

Why does 91 names in one WARN filing matter more than a bigger cut elsewhere?

Concentration. Refolk's index shows Zillow was the #1 employer among US real-estate and internet Directors of Engineering plus Senior Managers of ML, out of a cohort of 209 currently-employed people. A cut at a company that over-indexed on your target cohort produces a much larger supply shock than a bigger cut at a diversified employer. Ninety-one senior Seattle names from Zillow moves this specific market.

Should I compete on base salary with these candidates?

No. Per HousingWire, terminated staff received six months of COBRA-equivalent lump sum plus severance, so most of these candidates have runway to be selective. Competing on base against Microsoft or Apple as a Series A is a losing game. Competing on scope, technical problem, equity, and reporting line is the axis that filters for candidates who actually want to build rather than land somewhere safe.