Zillow Cut 500 in a Quarter It Grew 18%. Source This Cohort Differently.

On August 4, 2026, Zillow announced a restructuring cutting more than 500 employees, about 7% of its workforce. The next day it reported Q2 revenue up 18% to $772 million. If you still triage layoff cohorts by desperation, this is the one that will beat you: the candidates are strong, the severance is generous, and the self-identification window is unusually long.

The Zillow cut is the cleanest example of a "growth-layoff" so far

A growth-layoff is a workforce reduction announced by a company posting double-digit revenue growth, framed as an "AI-native" strategic rebalance rather than a cost cut. Zillow's Q2 2026 numbers make the label unavoidable:

• Revenue: $772M, up 18% year over year
• Mortgage revenue: $84M, up 75%
• Rentals revenue: $209M, up 31%
• EBITDA: $176M, a 23% margin
• Net result: a $4M net loss, driven by a $36M restructuring charge, with $23M to $28M more expected in Q3

The Aug 5 shareholder letter, signed by CEO Jeremy Wacksman and COO/CFO Jeremy Hofmann, opens by calling Zillow "AI-native, at the core of the transaction, empowering both consumers and professionals from end to end." In Q1, the same team told shareholders their engineers were shipping 40% more code each on average thanks to internal AI tooling. No executive attributed the August cut to AI. None denied it either.

That gap between "AI-native" positioning and "we're not saying AI did this" is the tell. It is a legal hedge, and it tells you exactly which functions got hit.

The affected roles are senior ICs whose leverage got automated

The Zillow cohort skews senior product and engineering, not junior, and not the ML org. Washington WARN filings show 91 Seattle-area roles including senior and director positions. Severance runs up to 21 weeks. This is not a distressed layoff.

The mechanism: when Zillow's leadership says engineers ship 40% more code each with AI tools, they are describing leverage. Leverage lets you keep output flat while removing the layer that used to produce that output the old way. That layer is:

• Mid-to-senior platform engineers whose review and integration work compresses under AI coding tools
• Tech leads adjacent to PM whose glue work AI agents now handle
• Directors of engineering managing teams that no longer need to be that large
• Senior product managers whose spec work is increasingly template-generated

If you are sourcing from the Zillow cut and looking at ML researchers, you are looking in the wrong org. The affected population is the boring, load-bearing senior IC layer. Which is, incidentally, the population most founders would kill to hire and never get access to under normal market conditions.

The addressable pool is 312 people, and most of them still say "Zillow"

In Refolk's index, a search for US-based senior, manager, and director level product and engineering profiles with "Zillow" in the profile returns 312 people currently indexable. Roughly one in five of a sampled set still lists Zillow as their current employer, which is the pre-attrition baseline you are working against.

312

Title distribution and destination employers matter more than the raw count. The dominant title in the cohort is Senior Software Engineer, with Principal Engineer and Director of Engineering rounding out the top three. When ex-Zillow senior IC and manager talent moves, they most often land at Microsoft, Apple, Meta, Google, and Airbnb, in that order. Top metros are the SF Bay Area, NYC, and Seattle.

Read that destination list carefully. This is not a cohort that ends up at Series A startups by default. It ends up at FAANG-tier employers because those are the recruiters who move fast on senior ex-Zillow profiles. If you are a founder, your window to compete is the two-to-six-week gap between the WARN filing and the FAANG offer landing.

The self-identification tail is unusually long, and that changes tactics

Most layoff cohorts front-load their "open to work" posts within 72 hours. The Zillow cohort did not. Housingwire reported more than a week after the announcement that impacted employees were still self-identifying on LinkedIn on a rolling basis.

Two things drive the long tail:

1. Severance up to 21 weeks removes the panic-post reflex
2. The "AI-native restructuring" framing gives affected employees permission to take their time and land somewhere they actually want to be

For sourcers, the implication is direct: inbound and "open to work" filters will miss roughly half the cohort. You have to go outbound, and you have to search on structural signals, not self-declared status. The correct Boolean is closer to "formerly Zillow" plus an end date in the August through October 2026 window, filtered by seniority band and function.

This is the exact gap Refolk closes for sourcing laid off engineers who have not raised their hand yet. You describe the person in plain English and get a ranked shortlist across LinkedIn, GitHub, and the open web without depending on the candidate flipping a status toggle.

The table you actually need on the wall

Here is the full dataset for the Zillow growth-layoff, laid out the way a sourcing lead should track it:

Two numbers in that table deserve their own moment. The 40% code-shipping lift is what leadership used to justify the leverage. The jump in average round size from 440 to 518, across fewer companies (278 down to 237), is what tells you the market is consolidating layoffs into fewer, larger, higher-quality cohorts. Waiting for aggregate trend pieces means you are always one cohort late.

Zillow is not the only one. Build a watchlist.

The growth-layoff pattern is generalizing across profitable tech, and a repeatable trigger already exists: double-digit YoY revenue growth plus a 5% to 10% workforce cut announced within five days of earnings.

Cisco is the cleanest parallel. It announced 4,000 layoffs as part of a restructuring the same window it reported record fiscal Q3 2026 revenue of $15.8 billion. Executives framed the cut as investing in "key growth areas." Same script as Zillow.

The August 2026 cohort cited alongside Zillow by Layoffs.fyi also includes Salesforce, LinkedIn, Rapid7, and Etsy. The counter-example is Oracle, which cut 21,000 positions in June and explicitly attributed them to AI. That is a different animal. Oracle's framing tells candidates their roles were replaced. Zillow's framing tells candidates the company got more leveraged and rebalanced. The first cohort arrives on the market defensive. The second arrives confident. You approach them differently.

Recruiters treating a Zillow ex-employee like a 2023 SVB-collapse candidate will misprice them by a level.

The watchlist mechanic, in five steps

1. Monitor 8-K restructuring-charge disclosures the day of filing, not press releases
2. Cross-reference against the same company's most recent earnings release for YoY revenue growth
3. Flag any company posting 10%+ growth and a 5%+ cut within a five-day window
4. Pull the WARN filing for geographic breakdown
5. Run the seniority and function search against your sourcing index within 48 hours

Steps four and five are where Refolk earns its keep. When the next WARN drops, the recruiters who convert are the ones who had a plain-English query already saved and ran it before the FAANG inbound teams did.

What to actually say to a Zillow senior engineer in September 2026

A cold outbound message to this cohort should acknowledge two things the candidate already knows: their old employer is growing, and their skills were not the reason they left. That is different from every layoff outreach template written between 2022 and 2025.

Concrete moves that work on growth-layoff cohorts:

• Skip "sorry to hear about Zillow." They got up to 21 weeks of severance. They are fine.
• Lead with the specific team problem you want them on, not the mission statement
• Reference their pre-cut work (the platform, the mortgage stack, the rentals surface) by name
• Assume competing offers. Ex-Zillow senior ICs land at Microsoft, Apple, Meta, Google, and Airbnb by default. If you are not one of those, your compensation and scope pitch has to be sharper on week one, not week four.

The Zillow window will close sometime in October 2026. The Cisco window is closing faster because 4,000 is a bigger cohort and FAANG recruiters have already re-tuned their pipelines. The generalizable insight, the one worth taking into every 8-K disclosure from here forward, is that "growth-layoff" is now its own candidate class. Source it accordingly.

FAQ

How is a growth-layoff different from a normal tech layoff for sourcing purposes?

A growth-layoff cohort has stronger average signal than a distressed-layoff cohort because the cut reflects leverage rebalancing, not skill obsolescence. Zillow's engineers were not shed because they stopped delivering. They were shed because the company's Q1 disclosure of 40% more code shipped per engineer under AI tooling let leadership carry less senior headcount into a flat housing market. Price these candidates like passive senior ICs at a healthy company, because that is functionally what they are, with a two-to-six-week availability window bolted on.

Where does ex-Zillow senior product and engineering talent tend to land?

Per Refolk's index, the top follow-on employers for ex-Zillow senior IC and manager talent are Microsoft, Apple, Meta, Google, and Airbnb, concentrated in the SF Bay Area, NYC metro, and Seattle. That destination pattern is your competitive set. If you are a Series B startup sourcing from this cohort, assume every candidate has at least one FAANG conversation running and shape scope and comp accordingly.

What is the earliest signal that another company is about to run a Zillow-style growth-layoff?

Watch 8-K restructuring-charge disclosures filed within five days of an earnings release that showed double-digit YoY revenue growth. That five-day window is the fingerprint. Cisco fit it with 4,000 cuts against $15.8B in record Q3 revenue. Salesforce, LinkedIn, and Rapid7 all clustered into the same August 2026 window. WARN filings then confirm geographic concentration, usually two to three weeks later.

Can I find the Zillow cohort without waiting for "open to work" signals?

Yes, and you should, because the self-identification tail on this cohort ran well past the usual 72 hours and inbound-only sourcing will miss roughly half of it. The correct mechanic is outbound Boolean on "formerly Zillow" plus end dates in the August through October 2026 range, filtered by seniority and function. Refolk runs that query in plain English across LinkedIn, GitHub, and the open web and returns a ranked shortlist, which is faster than rebuilding the Boolean by hand every time a new WARN filing drops.