# 28,844 WARN Exits Land by Dec 8. Source by Exit Date, Not Headline

_28,844 workers are scheduled to separate by Dec 8. Time outreach to laid-off engineers by WARN separation date and turn each notice into a list of names._

- Canonical URL: https://www.refolk.ai/blog/warn-notice-separation-date-sourcing-laid-off-engineers
- Published: 2026-11-04
- Reading time: 10 min
- Keywords: WARN notice layoffs list, upcoming layoffs WARN tracker, how to recruit laid off engineers, WARN Act separation date, sourcing laid off tech workers

Most sourcers time outreach to laid-off engineers by the headline, and headlines run on the announcement date, weeks or months before anyone is actually free. Layoff Atlas counts 28,844 workers scheduled to separate between Nov 3 and Dec 8, and more than 22,000 of them leave in just three weeks. If you want to recruit laid-off engineers this quarter, stop timing outreach to the news and time it to the day people actually leave.

## Why the separation date matters more than the headline

The separation date is the day a WARN-covered employee actually stops working and stops being paid, so that's the date your outreach calendar should follow. The announcement date only tells you when the press noticed.

A **WARN notice** is a public filing that employers covered by the federal WARN Act (and state "mini-WARN" laws) must submit before a mass layoff. It lists how many people are affected, where they work, and when they go. The **WARN Act separation date** is the effective date on that filing: the last day on payroll.

The gap between the two dates is bigger than most recruiters assume. WARNAct.io tracks 33 Amazon filings that publish both a notice date and a layoff date. The median gap across them is 90 days, against a federal minimum of 60. That stretch is the **paid-notice window**: the period when affected employees are still employed, still paid, and, at Amazon at least, still able to land an internal transfer that cancels the layoff.

Layoff Atlas says it outright: someone counted in the Nov 17 week may have been told in September or October. A recruiter who pitched them on headline day reached someone with two months of salary left and no reason to hurry.

## What 28,844 scheduled exits look like, week by week

The 28,844 separations aren't spread evenly. The weeks of Nov 10, Nov 17, and Nov 24 hold 22,800 of them, about 79% of the total, and the week of Nov 24 alone holds 9,300.

| Week of | Scheduled separations |
|---|---|
| Nov 3 | 2,350 |
| Nov 10 | 6,887 |
| Nov 17 | 6,613 |
| Nov 24 | 9,300 |
| Dec 1 | 2,398 |
| Dec 8 | 1,296 |

Source: Layoff Atlas, week-ahead WARN calendar sorted by effective date.

Zoom out to Layoff Atlas's 90-day window and the scale grows: 658 notices covering 62,497 reported workers. The top states:

- California: 18,196
- Washington: 17,215
- Illinois: 3,649
- Texas: 2,978
- Virginia: 2,373

Four caveats before you staff up around these numbers:

- **They are reported plans, not confirmed job losses.** People transfer internally, and dates move between updates.
- **Coverage varies by state.**
- **Small layoffs are missing.** Cuts below the filing thresholds never show up on any WARN notice layoffs list.
- **They cover all industries.** 28,844 is not an engineer count. Treat it as a measure of overall volume and timing.

## Why "open to work" searches miss almost everyone on a WARN notice

People in the paid-notice window are still employed, so their profiles still show the company laying them off. In Refolk's index, only 129 of 353,390 US profiles titled "Software Engineer" have "open to work" in the headline, and exactly one says "laid off."

> **0.037%** Share of US Software Engineers with "open to work" in their headline
>
> 129 of 353,390 profiles in Refolk's index. One says "laid off."

| Segment | Count | Share of base |
|---|---|---|
| All current US Software Engineers | 353,390 | 100% |
| Headline contains "open to work" | 129 | 0.037% |
| Headline contains "laid off" | 1 | 0.0003% |
| Upcoming WARN separations, Nov 3 to Dec 8 (all industries) | 28,844 | about 224x the open-to-work pool |
| Bay Area tech WARN notices, 12 months to June | 14,500+ | n/a |

Rows 1 to 3 come from Refolk's index, row 4 from Layoff Atlas, and row 5 from Bloomberg's reporting on California EDD data. The 224x ratio only compares scale, not like with like, because the WARN figure covers every industry.

The reason behind that tiny share is simple. Amazon pays wages and benefits through the separation date unless the employee resigns first. Anyone who lands an internal transfer before that date is not laid off at all. If you're on full pay with a shot at an internal move, you have no reason to post your status to every recruiter on LinkedIn.

The 129 who do flag it back this up. Among them, Amazon and AWS (4 combined), Google, Oracle, Uber, and Notion still appear as *current* employers, and Seattle ties for the most common region. That pattern fits people quietly looking during a paid notice period. So the job-seeking keyword search, the default way most people go about sourcing laid-off tech workers, finds a rounding error. Searching by employer, location, and role finds the cohort.

## How to turn a WARN notice into a searchable list of names

Pull three fields from the notice (employer, site or city, and job titles), then search for current employees who match all three. Used this way, a notice gives you a precise search query. A press release only gives you a company name.

How much each notice tells you depends on the state:

- **California's** mini-WARN applies at 75+ employees at a single location, and notices give the number affected at each street address.
- **Washington's** version generally requires 60 days' notice when 50+ jobs are cut within 30 days across the state, and its notices list job titles.

Amazon's Washington notice, filed Nov 2, shows how much detail you get. It covers 95 roles. The titles include software development engineers, data engineers, and a director of software development. Separations run from Dec 7, 2026 to Jan 25, 2027, and staff were told starting in July.

Here's the process:

1. **Pull the notice** from the state site or an aggregator. Note the filing date, separation date range, and every address.
2. **Copy the job titles exactly** as written. "Software development engineer" is Amazon's title, and profiles use it.
3. **Map addresses to cities and metros.** A suburban office address means you also search the surrounding metro, since profile locations are loose.
4. **Search current employees** at that employer, in those metros, with those titles. Leave out every open-to-work keyword.
5. **Cross-check on GitHub and the open web** so you can lead with real work, not a guess about someone's job security.
6. **Tag every name with its separation date.** That date is your send schedule.

Steps 3 to 5 are where most sourcers lose an afternoon to Boolean strings across three tabs. [Refolk](/) handles that part: you describe the person the notice describes, in plain English, and get back a ranked shortlist drawn from GitHub, LinkedIn, and the open web.

> **Example search:** "Software development engineers and data engineers currently at Amazon in the Seattle area, Washington" - [run it on Refolk](https://www.refolk.ai/s/w2pgmnxda0)
>
> A ranked shortlist of current Amazon engineers matching the notice's titles and region, with LinkedIn and GitHub profiles side by side.

## When to send the first message

Send your first message about two to four weeks before the separation date. Earlier than that, you're competing with full pay and the internal job board. Later, you risk arriving after they've already decided.

Amazon's timeline shows why. Staff heard in July. Separations start Dec 7. Everyone in between is still paid and can still land an internal transfer that would cancel the layoff entirely. A July pitch competes with Amazon's own internal mobility, at full salary, from a stranger. A mid-November pitch reaches someone close to the date who now has to decide.

Here's a working cadence for each cohort:

1. **Notice filed:** log it, build the list, tag separation dates. No pitch yet.
2. **Four weeks out:** first message. Lead with the role and the work, not the layoff.
3. **Two weeks out:** one follow-up with something concrete, like a team, a comp range, or a timeline.
4. **Separation week:** a final, short note. People are now acting.
5. **After separation:** move non-responders to a 30-day check-in, not a sequence.

For Amazon's Dec 7 cohort, that puts first messages between roughly Nov 9 and Nov 23. The Jan 25 tail of the same notice is a separate campaign that starts in late December.

> The notice tells you who and where. The separation date tells you when. The headline tells you nothing you can schedule.

## Why your WARN calendar needs a weekly refresh

WARN calendars change as new notices are filed and old ones are amended, so last month's peak week may not be the peak now. Rebuild your outreach calendar every week instead of setting it once.

Layoff Atlas's own updates show how much it moves. In data as of Oct 11, the week of Nov 15 was the heaviest at 7,644. An earlier version had the weeks of Nov 14 and Nov 21 holding 15,378 of 30,881 scheduled separations, or 49.8% of six weeks of volume in two weeks. The current version puts the peak at the week of Nov 24 with 9,300.

Two consequences:

- **Staff for peak weeks, not the average.** A six-week average of about 4,800 a week hides a week nearly twice that size.
- **Re-pull your sources every Monday.** Any upcoming layoffs WARN tracker is a snapshot. Moved dates shift people between your send windows.

## Bay Area volume is not Bay Area opportunity

Bay Area WARN filings nearly doubled, but demand for software engineers there has fallen 42% since 2022. That makes it a buyer's market for generalist engineering hires and still a competitive one for AI specialists.

Bloomberg's Sept 17, 2026 story by Francesca Maglione found that tech employers filed layoff notices for more than 14,500 Bay Area workers in the 12 months ending June. That's almost double the year before, according to California EDD data. The piece follows people like Basem Istanbouli, a former Google employee who started un(PTO), a community for laid-off Bay Area tech workers.

> **42%** Drop in Bay Area software-engineer demand since 2022
>
> Lightcast data, while AI-related roles rose 37% over the same period.

The Lightcast numbers explain the mismatch. Software-engineer demand is down while AI-related roles are up 37%. A recruiter hiring backend or platform generalists is in a buyer's market and can be choosy.

A recruiter hiring for AI roles has the opposite problem. A WARN list is a thin source for that search, because with AI demand up 37%, any specialist who does appear on a notice is someone every other AI recruiter is chasing too.

Also don't assume California is the whole story. In Layoff Atlas's 90-day window, Washington's 17,215 reported workers come close to California's 18,196, and Seattle is where the open-to-work engineers in Refolk's index cluster. For a recruiter, that makes Seattle as important a metro to watch over the next six weeks as San Francisco.

> **Engineering roles open in Seattle right now** - [see the open roles](https://www.refolk.ai/jobs/search?family=engineering&location=seattle)
>
> A live view of who is hiring engineers in the metro where Washington's WARN cohort lives.

## The Monday routine

A repeatable WARN sourcing routine comes down to four things every week: refresh the calendar, pull new notices, build lists, and schedule sends by separation date. Layoff Atlas covers 51 jurisdictions, so one source handles most of the first step.

1. **Refresh the calendar** on Layoff Atlas and note any week that moved.
2. **Pull new filings** from state sites and check company histories on WARNAct.io, which shows 37 Amazon filings covering 12,649 workers.
3. **Extract employer, sites, and titles** from each new notice.
4. **Build the list** by searching current employees on those three fields, with no open-to-work keywords.
5. **Schedule sends** at four and two weeks before each cohort's separation date.

## FAQ

### What is the WARN Act separation date?

The WARN Act separation date is the effective layoff date on a WARN notice, meaning the last day the affected employee is on payroll. Federal law requires at least 60 days between notice and separation, but large employers often give more. Amazon's median gap across 33 filings with both dates is 90 days. For recruiters, it's the most useful date on the notice because it tells you when someone moves from "paid and maybe transferring" to "actually looking."

### Where can I find an upcoming layoffs WARN tracker?

Layoff Atlas publishes a week-ahead calendar sorted by effective date across 51 jurisdictions. WARNAct.io keeps company-level filing histories. For detail, go to the state source: California's notices give counts by street address, and Washington's notices list job titles. Refresh weekly, because dates and totals shift between updates.

### Is it appropriate to contact engineers during their notice period?

Yes, if the message is about a real role and not about their layoff. People in the paid-notice window are deciding between internal transfers and outside offers, and a relevant role two to four weeks before separation helps them. Don't open by referencing the WARN filing. Lead with the work, the team, and a concrete next step.

### Does every layoff show up in WARN data?

No. Smaller cuts fall below filing thresholds, such as California's 75-employee single-site trigger or Washington's 50-job, 30-day rule. Coverage also varies by state. And notices report plans, not confirmed job losses, since some affected employees transfer internally before their date. Treat WARN as a strong timing signal for the cohorts it covers, not a complete census of who is on the market.

---

_From the Refolk blog. More posts: https://www.refolk.ai/blog/index.md_