Workday's Pleasanton WARN Is 27% of the Cut. Source Before Nov 30

Workday filed its 8-K and its California WARN notice on the same day, Sept 29, 2026. As of Oct 19, the 142 Pleasanton employees on that notice are still on payroll and still reachable. They have about six weeks until a Nov 30 separation date that puts them in front of every recruiter in the Bay Area at the same moment. The window is real, but the WARN list covers barely a quarter of the people affected, and the obvious search for them mostly returns the wrong people.

What did Workday file on Sept 29?

Workday announced a cut of about 2.5% of its workforce, roughly 525 roles, "primarily within Workday's Product and Technology team." On the same day it filed a California WARN notice for 142 permanent layoffs at its Pleasanton site, effective Nov 30, 2026.

A WARN notice is the advance layoff filing California requires at least 60 days before a mass separation at a single site. The key details:

• Site: 6110 Stoneridge Mall Road, Pleasanton.
• Notice period: 62 days, so it just clears the 60-day minimum.
• Scale: about 525 jobs globally, based on 21,070 employees in the latest annual report.
• Division: KRON reports the Bay Area cuts all appear to sit in the technology division.
• Other changes: the 8-K also mentions reductions in leased office space.
• Cost: one employment-law summary of the filing puts charges at $65M to $80M, with $40M to $55M in cash severance and benefits. Other outlets cite $65M to $85M, so check the 8-K before you quote a number.

This is Workday's second layoff round in 2026 and its third Pleasanton reduction since early 2025. Aneel Bhusri, the co-founder, came back as CEO in February 2026 after Carl Eschenbach left. The company has restructured twice this year while saying it still plans to hire in key strategic areas and locations through fiscal 2027.

One trap to avoid: at least one law-firm page labels the September notice as "296 jobs." That number is the two-filing total for 2026 (154 plus 142), not the size of this round. If a client quotes 296 Pleasanton layoffs back to you, that's the source.

Why is the WARN list only a quarter of the pool?

The WARN list covers roughly 27% of the people affected, because California WARN notices are filed per site. The 142 Pleasanton layoffs are about 27% of the ~525 global roles. Everyone else works remotely, at another office, or outside California, and none of them appear in the state's log.

27%

This matters for how you work. Free trackers like californiawarn.com and @WhatLayoff on X surfaced the Pleasanton notice within days, so every agency recruiter in the Bay Area has the same 142-person starting point. The other ~383 people are where the competition thins out, and they aren't counted in a filing that only cares about one building.

The WARN list is a map of one building, not a list of the people who lost their jobs.

So the WARN notice tells you when and which division. It doesn't tell you who. For that you need a people search, and that's where most sourcers go wrong.

How many Workday product and tech people can you actually find?

In Refolk's index of professional profiles, a US headline search for "Workday" returns 803 software engineers, 209 product managers, and 40 engineering managers or directors. That works out to about 3.8 engineers per PM and about 20 engineers per engineering leader.

The third column is the one that should change how you search. Nearly half the "Workday engineers" a keyword search hands you don't work at Workday.

Why does searching "Workday" return the wrong people?

Searching "Workday" mixes in non-employees because Workday is both a company and a skill. In the software-engineer sample from Refolk's index, 44% (11 of 25) worked somewhere else entirely, as Workday integration developers at Wells Fargo, Walmart, KeyBank, and Deloitte.

44%

The people who configure and integrate Workday for their employers put it in their headline because it's their specialty. A Workday integration developer at KeyBank is a fine hire for some roles, but they won't be on a severance clock on Nov 30, and they didn't build Workday's product.

The noise falls as you move up in seniority:

• Software engineers: 44% outside Workday.
• Product managers: 36% outside Workday, once VNDLY is counted.
• Engineering leaders: 16% outside Workday, once VNDLY and Adaptive Planning are counted.

The fix is to stop treating "Workday" as a keyword. Search on current employer (Workday, plus acquired brands like VNDLY and Adaptive Planning), then narrow by a Bay Area location and a product or engineering title. That's a three-filter query that boolean strings handle poorly. It's also the exact gap Refolk closes: you describe the person in plain English, and it returns people who actually work there rather than everyone who has touched the software.

Which Workday teams are probably on the list?

The people leaving most likely worked on older product surfaces, not on AI. That's an inference from Workday's own hiring and product moves, not something the company has confirmed, but the signals point the same way:

• May 4, 2026: a Pleasanton posting for a Principal ML Engineer on "Agent Factory" described small, senior AI pods. Workday is still staffing that group.
• Sept 29: the 8-K talks about realigning "team structures" inside Product and Technology.
• Oct 13, at Rising: two weeks after the cut, Workday made Sana, the AI assistant from its roughly $1B acquisition, the new "Workday Home" and announced a partnership with Anthropic.

Joel Hellermark, Sana's founder and now Workday's Chief AI Officer, sums up the strategy as "AI is the new UI." When a company moves its main interface onto an AI assistant while still hiring senior AI pods, the teams that get realigned are likely the ones building the surfaces being replaced.

That changes the pitch. "Come do AI" falls flat with someone who just watched AI take over their roadmap. Lead with scope and ownership instead: a product they'll own end to end, a team they'll shape, a codebase that isn't being deprecated around them.

Expect one more effect. Workday is explicitly still hiring, so some of the 142 may move into internal roles, Agent Factory or similar, before Nov 30. The pool you can actually hire from may be smaller than the filing suggests.

When should you reach out, and when will they start?

Reach out in October and November, but plan for December start dates. Affected staff stay on payroll through Nov 30, and with $40M to $55M in cash severance and benefits on the table, most will want to collect through separation and sign a release before starting anywhere new.

The notice period isn't dead time for the employee. It's paid time spent looking for the next job, with a financial reason not to leave early. A "can you start next week?" pitch asks them to give that money up. An offer signed in November that starts in December lets them keep it.

A workable calendar:

1. Oct 19 to Oct 31: first outreach. Short, specific, and focused on scope. No pressure on dates.
2. November: interviews, while they're still on payroll.
3. By late November: get the offer signed, with a start date after Nov 30.
4. December: start dates, after the release is signed.

The competition for their attention is heavy. Bay Area News Group, in Ethan Baron's WARN coverage, counts more than 14,000 Bay Area tech job cuts in 2026 so far, against 10,170 in all of 2025. That's about 38% more with weeks still left in the year. After Nov 30, these 142 people join that crowd. Before Nov 30, they're a named, dated group that most recruiters haven't sorted yet.

Why are the 40 engineering leaders the real prize?

Affected Workday engineering managers are the scarcest group in this pool. Refolk's index shows only 40 US engineering managers, directors, or VPs with Workday in the headline, against 803 software engineers. Any manager in the cut is a small, high-value target.

The leaders are also easier to find. Their headlines are 84% clean once you count VNDLY and Adaptive Planning, so a targeted search wastes little time. Their location tells you what kind of role will win them. In the sample, engineering managers cluster in Fremont (4 of 25), San Jose (3 of 25), and San Ramon (1 of 25), while software engineers turn up in Pleasanton and Danville.

This is a commuter pool from the East Bay and South Bay, not from San Francisco. Consider what that means:

• A hybrid role with an East Bay or South Bay office beats an SF-only role on commute alone.
• A fully remote role takes the commute question off the table entirely.
• A founder hiring a first engineering manager in San Jose or Fremont starts with an advantage over a downtown SF company.

If you're hiring leaders, start with the 40 profiles and work outward. Refolk handles that kind of narrow, location-aware search well: ask for current Workday engineering managers within commuting distance of Fremont, and you get people, not a boolean string to debug.

FAQ

How many people did Workday lay off in 2026?

Workday ran two rounds in 2026. February's cut was about 2%, mostly in Global Customer Operations, and included 154 Pleasanton jobs with a last day of Apr 6. September's cut was about 2.5%, roughly 525 roles, mostly in Product and Technology, with 142 in Pleasanton separating Nov 30. The two California WARN filings total 296 jobs, which some sites wrongly attribute to the September notice alone.

Should I contact affected Workday staff before Nov 30?

Yes. The weeks before separation are when affected people are actively looking and least crowded by other recruiters. Be realistic about timing, though. Most will want to stay through Nov 30 to collect severance and sign their release, so pitch a December start date rather than an immediate one.

Are the laid-off Workday engineers AI specialists?

Probably not, for the most part. Workday is still hiring senior AI pods for Agent Factory and has made Sana its new home interface. That suggests the cut fell on teams working on older product surfaces. This is an inference, not confirmed by Workday, but it argues for pitching ownership and scope rather than AI work.