Netflix's WARN Covers 494 of 1,000 Cuts. Source the 506 It Missed

Netflix's Oct 14 memo cut about 1,000 jobs, roughly 6% of the company, and product, tech, legal and HR took the most. California's WARN notices cover only 494 of those jobs, and the Los Gatos notice, received two days after the memo, lists Sept 14 as its effective date. If you want to hire laid off Netflix engineers, the public record shows you less than half of them, and the dates in it may not mean what they seem to.

What do Netflix's California WARN notices actually say?

Two October notices cover 494 jobs: 227 at the Los Gatos headquarters (121 Albright Way) and 267 at 5808 Sunset Blvd in Los Angeles. The state received the Los Gatos notice on Oct 16, and it gives Sept 14 as the effective date.

A WARN notice is a filing an employer must make before a mass layoff at a single site, and it normally has to go out 60 days in advance. California's log now shows three Netflix notices covering 553 jobs. The third is an August filing for 59 more LA roles, which makes October at least Netflix's third cut of 2026.

One correction, because it's spreading. Some coverage, including KRON, says the cuts "weren't officially announced until Oct. 16." That's wrong. Co-CEOs Greg Peters and Ted Sarandos sent the memo on Oct 14. Oct 16 is the day the state received the Los Gatos notice.

Here is the visible pool next to the part nobody filed for:

What the table tells you:

• About 49% of the announced cuts show up in a WARN filing.
• The other ~506 appear in no public filing.
• Netflix had about 16,000 full-time employees at the end of 2025, so the 1,000 figure fits the "6%" in the memo.

Does the Sept 14 date mean they've been job hunting for six weeks?

Not necessarily. Sept 14 falls a month before the memo, but Netflix's earlier LA filing has the same gap. That points to how Netflix fills in the form, not to a quiet layoff in September.

A law-firm layoff tracker calculates that the Los Gatos notice was dated 32 days after the jobs ended. The August filing looks the same: effective July 14, dated Aug 13, received Aug 14. Two notices from the same employer with the same roughly 30-day lag is a pattern.

32 days

One plausible explanation is that Netflix enters the day people stopped working, not the day they stopped being paid. If employees were released from duties and kept on payroll through a notice period, both dates can be true at once. Nobody outside Netflix knows for sure. Class-action firm Strauss Borrelli PLLC is investigating whether the 227 Los Gatos employees got the required 60 days' notice, which tells you the timing is disputed.

This matters for your pipeline because the two readings lead to different candidates:

• Released Sept 14 and paid through a notice period: they may have been interviewing for six weeks, and the best of them may already hold offers.
• Told on Oct 14: they're just starting, and they're still sorting out severance and benefits.

So treat "they've been on the market since September" as something to check, not something to assume.

The WARN date is a guess about someone's timeline. Ask the candidate, then build your offer around the answer.

Ask every candidate two separate questions: what was your last working day, and what is your last paid day? Then ask whether they're already in final rounds anywhere. Don't bring up the WARN filing or the investigation in outreach. Nobody wants a recruiter opening with their legal situation.

Where are the ~506 Netflix layoffs that no filing shows?

They're outside California: in New York, Seattle, remote US roles and Warsaw. WARN only applies to mass layoffs at a single site, so staff spread across states may never trigger a filing, and staff outside the US never appear in a US one.

A Netflix engineer working from home in one state, and a handful more spread across others, may never push any state over its threshold. The layoff happened, but no state ever logs it.

Refolk's index shows how big that blind spot is. 1,552 US engineering profiles (SWE, Senior SWE, EM, Data and ML engineer titles) mention Netflix in their headline. In a sample of 25, 19 list Netflix as their current employer. Here's where the sampled engineers live:

• Bay Area (SF, San Jose, Mountain View, Cupertino, Menlo Park): 9
• New York / Brooklyn: 5
• "United States" only: 4
• Seattle: 3
• Los Angeles: 1

That's 12 of 25, or 48%, in New York, Seattle or listed only as "United States." The sample is small, so read it as a direction, not a census. Still, it suggests that nearly half of Netflix's US engineers sit where a California filing can't see them.

48%

The practical problem is that you can't type "laid-off Netflix ML engineer, Seattle or remote, streaming infrastructure" into a WARN database or a basic LinkedIn filter. Location fields say "United States," titles say "Senior Software Engineer," and the Netflix connection is in a headline or a GitHub bio. Refolk handles this kind of search: you describe the person in plain English, and it returns a ranked list from GitHub, LinkedIn and the open web.

One caveat about these numbers. They're headline keyword matches. Between 76% and 88% of each sample lists Netflix as their current employer, so some are alumni, and no profile in the index marks anyone as laid off. Use the counts to size the market and to know where to look. Don't read them as a list of who was cut.

Warsaw, not Amsterdam, is the overseas pool

Netflix's EMEA headquarters is in the Netherlands, but its only tech hub outside the US is Warsaw, with about 300 employees. Refolk's index finds 138 Netflix engineering profiles across the UK, the Netherlands, Spain and Poland. In a sample of 25, 21 are in Poland (17 in Warsaw) and 22 list Netflix as their current employer. Łukasz Romaniuk is Content Engineering Director at the Warsaw hub.

Variety reports that about 70% of Netflix staff are believed to be in the US and Canada. If the cuts were spread evenly, roughly 30% would land outside North America. Polish layoff rules have nothing to do with US WARN, so none of those people will appear in any US record.

Why shouldn't you count LA's 267 as engineers?

Sunset Blvd is the content and marketing side of Netflix, not engineering. The tech pool is Los Gatos plus out-of-state remote engineers, so reading 494 as "laid-off engineers" overstates it.

The content side is going through its own reorganization. Peter Rice replaced Bela Bajaria as chief content officer, and Dan Lin, Doug Belgrad and Carolina Garcia also left. The 267 LA roles are much more likely to come from that side of the house than from the product and tech org. Only 1 of the 25 sampled US engineers in Refolk's index is in LA. One analysis warns plainly that the WARN total "is not a count of software engineers."

What follows for engineering leaders:

• The California filings only point you to the 227 in Los Gatos, and not all of those are engineers.
• The larger engineering opportunity is the remote and East Coast group the filings don't show.
• If you hire for content, marketing or studio operations, LA is your pool, not the 227.

You're also not the only one hiring, and Netflix isn't the only source. Disney said in September it would cut about 300 jobs, mostly in HR and technology, which puts a second group of media-tech workers on the market at the same moment.

Why should you move on Netflix product managers first?

There are about ten Netflix engineering profiles for every Netflix product, design, HR or legal profile, and the memo named product as one of the hardest-hit functions. A smaller pool with more demand gets hired faster.

Refolk's index finds 149 US profiles with Netflix in the headline and product, design, HR, recruiter or counsel titles, against 1,552 engineering profiles. In a sample of 25, 21 are current Netflix employees. Product Manager (8) and Senior PM (7) are the most common titles.

The org chart points the same way. Elizabeth Stone was promoted to chief product and technology officer, with product, engineering and data under her, so the hardest-hit product and tech org now sits under one leader.

Hiring for a senior consumer PM role is usually slow. You spend weeks searching for people who have run product at this scale, then you either pay an agency fee or watch your shortlist accept other offers while you're still screening. In a layoff, the window is shorter than that process.

If you're sourcing PMs yourself, search by what they did, not by title. "Netflix" plus "experimentation," "personalization," "growth" or "member experience" finds a profile faster than "Product Manager" alone. With only 149 profiles in the pool, you need to know quickly which few dozen fit.

How should you reach laid-off Netflix staff this week?

Go to the PMs and the engineers the filings miss first, start the conversation with the work you're hiring for, and confirm their timeline before you build an offer.

1. Start with PMs anywhere. The pool is about a tenth the size of the engineering one, and product was named among the hardest-hit functions.
2. Search outside California on purpose. Look for New York, Seattle and "United States" profiles. They're close to half the engineering sample, and no recruiter will find them through a WARN filing.
3. Work the 227 in Los Gatos next. That's the only filing that points at the tech org, and every recruiter reading the news can see it too.
4. Treat Warsaw as its own pool. 17 of the 25 sampled European engineers are there. Polish employment rules and notice periods apply, not US ones.
5. Read the Blind threads before you write anything. Netflix staff compare notes on teamblind.com. Use the threads to understand which teams were affected, and never quote them back to anyone.
6. Talk about the role, not the layoff. Explain the problem they'd own and who they'd work with.
7. Ask for both dates. Last working day and last paid day tell you whether you're competing with six weeks of other interviews or with none.

FAQ

How many people did Netflix lay off in October 2026?

About 1,000, or roughly 6% of the workforce. Co-CEOs Greg Peters and Ted Sarandos announced the cuts in an Oct 14 memo, with product, tech, legal and HR hit hardest. California WARN notices cover 494 of them: 227 in Los Gatos and 267 in Los Angeles. That leaves about 506 with no public filing.

Why does the Netflix layoffs WARN notice say Sept 14?

The Los Gatos notice was dated 32 days after the jobs ended, and Netflix's earlier LA filing showed the same gap (effective July 14, received Aug 14). One possible reason is that Netflix records the last working day while paying people through a notice period, but that hasn't been confirmed. Strauss Borrelli is investigating whether the 60-day notice requirement was met.

Are Netflix's Warsaw employees part of the layoff?

Netflix hasn't broken out the cuts by country. Warsaw is its only tech hub outside the US, with about 300 employees, and about 70% of Netflix staff are believed to be in the US and Canada, leaving roughly 30% elsewhere. Any Polish cuts fall under Polish law, not US WARN, so they won't appear in any US filing. Ask candidates directly.

How do I find laid-off Netflix engineers who aren't in the WARN filings?

Search by location and skills instead of by filing. In Refolk's index, 48% of sampled US Netflix engineers are in New York, Seattle or list only "United States," so a California filing never covers them. Search their headlines, GitHub profiles and personal sites for Netflix plus the specific systems they worked on, and confirm current status in the first conversation.