# 20,342 WARN Layoffs Hit in 3 Weeks. Their Profiles Still Say 'Present'

_20,342 WARN layoffs take effect over three November weeks, and those workers still look employed. Sort filings by effective date to reach engineers first._

- Canonical URL: https://www.refolk.ai/blog/warn-effective-date-calendar-laid-off-engineers
- Published: 2026-11-14
- Reading time: 9 min
- Keywords: WARN notice layoffs list, how to find laid off engineers, recruit laid off software engineers, WARN act effective date vs notice date, Workday layoffs Pleasanton

If your sourcing waits for an Open to Work signal, you'll miss most of the 20,342 people whose WARN separations take effect over the next three weeks. They're still on payroll, and their LinkedIn profiles still name the employer.

One WARN tracker counts 7,354 separations the week of Nov 14, 6,925 the week of Nov 21 and 6,063 the week of Nov 28. Many of the engineers in those counts were told in September or October, and LinkedIn is now rolling out a "Present" label that puts their current job in even clearer view. By the time they signal, the recruiters who worked from the filing have already called.

## Why do laid-off engineers still look employed?

They look employed because on paper they still are. A WARN notice puts a gap of at least 60 days between telling workers and letting them go, and paychecks keep arriving until the effective date. That means the profile, the payroll and the job title all say "current."

The WARN Act (Worker Adjustment and Retraining Notification Act) is the US federal law that makes employers with 100 or more employees give advance notice of mass layoffs. It's why the public can see these layoffs at all. It also explains why the affected people don't show up in a normal search.

LinkedIn's "Present" label highlights current positions. I haven't seen anything showing that it changes how Open to Work filters behave. The issue is visibility. An engineer whose last day at Workday is Nov 30 now has a profile that says they're there, in clearer type than before.

The bigger problem is that almost nobody signals. In Refolk's index of professional profiles, 592,944 people in the US hold Software Engineer, Senior, Staff or Principal titles. Only 177 of them have "open to work" in their headline.

> **0.03%** US software engineers with "open to work" in their headline
>
> 177 of 592,944 in Refolk's index. A lower bound, since it misses the photo frame and the recruiter-only setting.

Part of the reason is runway. Amazon's current Washington notice gives at least 90 days. Workday's 2025 round came with minimum severance of 12 weeks' pay. Someone paid for months is under no pressure to post about it publicly.

## WARN Act effective date vs notice date: which one matters?

The effective date is the one that matters. The notice date is when the employer files and tells workers; the effective date is when employment ends, and your sourcing window closes with it.

News coverage peaks on the notice date, which is why most recruiters react late. Microsoft filed a Redmond notice on Sep 22 covering 277 workers, effective Nov 21. Both of its 2026 Washington filings ran exactly 60 days. If you read about that filing this week, you've already lost most of the window.

| Filing | Workers | Notice | Effective | Window |
|---|---|---|---|---|
| Workday, Pleasanton | 142 | Sep 29, 2026 | Nov 30, 2026 | 62 days |
| Microsoft, Redmond | 277 | Sep 22, 2026 | Nov 21, 2026 | 60 days |
| Amazon, Washington | 95 | Notified Oct | Dec 7 to Jan 25 | 90+ days |
| VCA, Los Angeles | 36 | 66 days after jobs ended | Already passed | None |

The Amazon row is the best opportunity on this list. Its separations run from Dec 7, 2026 to Jan 25, 2027, and the affected roles include software development engineers and data engineers. Those people are still weeks away from their last day, which leaves time to run a full process.

## What does the WARN notice layoffs list show for the next three weeks?

It shows 20,342 scheduled separations across the weeks of Nov 14, 21 and 28. Over the full 90-day window, the same tracker lists 680 notices covering 61,488 reported workers, and 29 of those notices don't give a worker count.

| Week of | Separations taking effect |
|---|---|
| Nov 14 | 7,354 |
| Nov 21 | 6,925 |
| Nov 28 | 6,063 |
| Total | 20,342 |

These numbers move. Two weeks earlier, the same tracker reported 8,453 workers for the week of Nov 14. Now it's 7,354, a drop of about 13%. Dates slip and plans change. Use the counts to decide where to look, but don't treat them as rosters.

You're also competing with every company hiring engineers right now, not only with other recruiters.

> **Engineering roles open in San Francisco** - [see the open roles](https://www.refolk.ai/jobs/search?family=engineering&location=san-francisco)
>
> Live postings competing for the same Bay Area engineers this calendar surfaces.

## Worked example: the Workday layoffs in Pleasanton

Workday's Nov 30 notice covers 142 people at its Pleasanton headquarters, 6110 Stoneridge Mall Road. It was filed on Sep 29, 2026, the same day as the company's 8-K. If you've seen 617 quoted, that number is from the notice dated Feb 5, 2025, with a layoff date of Apr 6, 2025. It isn't this round.

Here's what's in the 2026 California filings:

- **First round:** 154 jobs, noticed Feb 4, effective Apr 6.
- **Second round:** 142 jobs, noticed Sep 29, effective Nov 30.
- **Scope:** one outlet describes the September cut as 2.5% hitting the Product and Tech team.
- **Concentration:** the 142 Pleasanton roles make up roughly a quarter of the whole round, all on one campus.

That concentration is good news for a sourcer. One campus and one function means you can describe the target pool in a single sentence.

### Why searching "Workday" pulls the wrong people

If you search for the employer name, nearly half of what comes back isn't Workday staff. Workday is also a product, so its name shows up on the profiles of engineers who build on it, integrate it or administer it for other companies.

In Refolk's index, 803 US engineers with Software Engineer or Software Development Engineer titles mention "Workday" in their headline. A 25-person sample of that group breaks down like this:

| Segment | Count |
|---|---|
| Headline mentions "Workday" (SWE + SDE titles, US) | 803 |
| Sample: current employer is Workday | 14 of 25 (56%) |
| Sample: current employer elsewhere | 11 of 25 (44%) |
| Sample: located in Pleasanton | 2 of 25 |

The sample is directional only, but the pattern is clear. The other 44% work at Wells Fargo, Walmart, Deloitte, KeyBank and similar companies. They work on Workday's HR software. They aren't Workday employees, and none of them is on Workday's notice. A keyword search treats both groups the same.

The fix is to filter on current employer, not keywords, and then narrow by geography and function: current employer is Workday, based in Pleasanton or the wider Bay Area, working in product or engineering. Doing that by hand with Boolean is tedious. It's the gap [Refolk](/) closes: you describe the person the way you would to a colleague, and you get back a ranked shortlist.

> **Example search:** "Software engineers currently at Workday in Pleasanton or the Bay Area, working on product or platform teams, senior level or above." - [run it on Refolk](https://www.refolk.ai/s/gpkxrpw4dh)
>
> A ranked shortlist of current Workday engineers with the HR-software ecosystem filtered out, plus profile and GitHub links for each.

Only 2 of the 25 sampled profiles listed Pleasanton. A location filter set to one city will drop people you're looking for. Use a metro-level radius.

## How do you build a WARN effective-date calendar?

Pull WARN filings every week, sort them by effective date instead of filing date, and work the filings whose effective dates fall 30 to 90 days out. That gives you time to make contact, run a process and have an offer ready around the last day.

1. **Pull the sources.** Layoff Atlas and WARNTracker track filings. The California EDD WARN page (edd.ca.gov) publishes the California notices themselves.
2. **Re-sort by effective date.** Record the filing date, then put every notice on a calendar by separation date.
3. **Filter to tech employers and addresses.** A Pleasanton HQ address tells you more than the company name does. Engineering-heavy campuses are worth the time. Distribution centers usually aren't, unless you hire for them.
4. **Turn each filing into a people search.** Use current employer plus metro plus function, as in the Workday example. With Refolk that's one plain-English query per filing instead of a Boolean string rebuilt every week.
5. **Re-pull weekly.** The week of Nov 14 lost about 13% of its count in two weeks. Remove notices that were amended, and add the ones that were filed late.
6. **Prioritize by days remaining.** Amazon (Dec 7 to Jan 25) goes above Microsoft (Nov 21), even though Microsoft's notice is larger, because Microsoft's window has nearly closed.

Step four is where most teams stall. Building the calendar is the easy part. Turning 142 people on one campus into a screened shortlist, and doing it again for the next notice, takes sourcing hours most recruiting teams don't have. If the role is hard to fill and the effective date is three weeks away, the window can close before the shortlist is done.

## What does the WARN calendar miss?

It misses startups and anything filed late. Federal WARN doesn't apply below 100 employees, and some notices reach regulators after the jobs are already gone.

The gaps:

- **Startups.** A company under 100 employees files no federal notice, however many engineers it cuts. The calendar finds big-company engineers, not early-stage ones.
- **Late filings.** VCA's 36 Los Angeles corporate support workers got official notice 66 days after their jobs ended. A notice like that is old news before it's filed.
- **Previously announced rounds.** Amazon's Washington notices belong to a round whose workers were told in October. The WARN filing confirms news that's already out. It doesn't break it.
- **Partial counts.** 29 of the 680 notices in the current window list no worker count at all.

For startup engineers you need different signals, such as a founder posting a list of people looking for roles. The WARN calendar won't surface them.

## What should the first message say?

Lead with the timeline, not the layoff. Engineers on notice may not have told their network yet. A message that opens with "saw you were laid off" exposes something they may have chosen to keep private.

What works better:

- **Reference the start date, not the separation.** "I'm hiring for a role starting in early December" lines up with a Nov 30 effective date without saying so.
- **Respect the severance.** Someone at Workday may have 12 weeks of pay coming, based on the 2025 terms. Don't push a start date that makes them give it up.
- **Be specific about the work.** The Workday round hit the Product and Tech team. Name the problem they'd work on, the stack and the team size.
- **Make it easy to say "not now."** People with 90 days of notice, like Amazon's SDEs, are collecting options. A low-pressure first message keeps you on their list.

> The person with the "Present" label and a Nov 30 end date is the best candidate you'll never see in a filter.

They aren't hiding. They're getting paid, they're in no hurry, and the profile shows what's true for a few more weeks. The recruiters who reach them are the ones working from the effective date.

## FAQ

### How do I find laid off engineers who haven't turned on Open to Work?

Start from WARN filings instead of profile signals. Sort notices by effective date, pick the tech employers with dates 30 to 90 days out, then search for people whose current employer is that company, in the metro on the filing, in engineering or product roles. In Refolk's index only 0.03% of US software engineers put "open to work" in their headline, so filtering on that signal misses nearly everyone.

### Is the Workday Pleasanton layoff 617 people or 142?

The current round is 142. Workday's notice dated Sep 29, 2026 covers 142 employees at its Pleasanton headquarters, effective Nov 30, 2026. The 617 figure is from the February 2025 round. Workday also filed for 154 California jobs in February 2026, effective Apr 6.

### Where can I get a WARN notice layoffs list?

Layoff Atlas and WARNTracker track filings, and Layoff Atlas reports scheduled separations by effective week. For California, the EDD WARN page publishes the notices directly. Pull them weekly, because counts change: one tracker's figure for the week of Nov 14 fell from 8,453 to 7,354 in about two weeks.

### Does LinkedIn's new "Present" label hide people from Open to Work filters?

There's no evidence that it changes filtering. The label makes current positions more prominent, so someone on a WARN notice looks more firmly employed than before. The practical problem is the same either way: people still on payroll rarely signal, so you have to find them through the filing, not the profile.

---

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