ServiceNow's Split WARN: 404 California Layoffs Hidden in Two Filings

ServiceNow filed two California WARN notices 48 days apart at the same two street addresses, and no single tracker has added them together. The combined footprint is 404 permanent cuts, the September 28, 2026 effective date is a starting gun, and the eliminated Quality Engineering department is the highest-value slice inside it. If you source platform or QE talent, you have about two weeks before this cohort gets crowded.

The 404 number nobody is quoting

ServiceNow's true California layoff footprint is 404 people, not the 287 or 117 numbers currently circulating. The figure is buried because ServiceNow filed two separate California WARN notices, 48 days apart, hitting the same two addresses in different EDD reporting periods.

Here is what each filing actually contains:

• June 10, 2026 filing, effective August 17, 2026: 117 employees, split 54 at 2225 Lawson Lane in Santa Clara and 63 at 4801 Eastgate Mall in San Diego.
• July 28, 2026 filing, effective September 28, 2026: 287 employees, split 154 at 2225 Lawson Lane and 133 at 4801 Eastgate Mall.
• Combined: 404 permanent California cuts across four WARN line items at exactly two ZIPs.

Neither filing states a reason. California WARN has no reason field, and ServiceNow filed no SEC restructuring disclosure to fill the gap. That leaves Blind and internal memos as the primary employee-side source, and Blind's ServiceNow tracker separately lists a rumored 3,000-person (roughly 15%) global cut dated July 28, 2026, the same day as the second California filing. The California 404 is almost certainly a visible slice of a much larger global action.

404

The mechanical reason no tracker aggregates the two is dull and important: they sit in different EDD reporting cycles. Whether or not the split was deliberate, the effect is that every layoff tracker under-counts ServiceNow by 71% if it only carries the July filing, or 29% if it only carries the June one. Blind users have called this pattern "rolling micro layoffs to avoid WARN" on ServiceNow before, and this is what it looks like in the wild.

Why the QE cohort is the interesting one

Inside the 404, Quality Engineering is the segment worth chasing, because ServiceNow has eliminated the QE role entirely rather than trimming it. A verified ServiceNow employee posted on Blind on October 15, 2025 that the QE Engineer title has been retired, most managers and senior-level QE were laid off, and remaining QE engineers must convert into Developer roles or exit.

The India tier structure reported on Blind makes the mechanic explicit:

1. M4+ QE managers: told to exit or find another role within a month.
2. M3 QE managers: forced into individual-contributor developer work.
3. QE ICs: doing dev work at the same pay, on a stopwatch.

That matters for sourcing in two ways. First, the addressable pool is bigger than the 404 named on the WARN, because it includes every QE engineer currently sitting inside ServiceNow who cannot or will not clear the dev bar. Second, "still at ServiceNow" is not a disqualifier on a LinkedIn or GitHub profile right now. Some of the strongest people to reach out to are the ones whose current title still reads Senior Quality Engineer at ServiceNow, because they are the exact people the internal conversion policy is quietly pushing out.

Describing that shape to a keyword search engine is painful. Describing it to Refolk in plain English is the point: "Senior Quality Engineer or SDET currently at ServiceNow in Santa Clara or San Diego, or ex-ServiceNow QE in the last 90 days" is a query, not a Boolean, and it returns the same shortlist a human sourcer would build over three afternoons.

What Refolk's index says about the outbound pool

The scarce commodity here is not QE labor in general, it is ServiceNow-trained QE and platform labor specifically, and the US pool is startlingly small. Refolk's index gives the shape:

Two numbers on that table deserve their own paragraph. Only 27 US profiles surface for "ServiceNow platform" software engineers, 17 of them still badged at ServiceNow. For a platform every Fortune 500 IT org runs, that is a thin pool. Every displaced Now-trained platform engineer is a genuinely scarce asset, and system integrators (Accenture, Deloitte, LTIMindtree) will move first.

The second is 110. That is the total global count of QE profiles that carry ServiceNow as a keyword in Refolk's index, and 62% sit in Hyderabad (8), Pune (4), and Bengaluru (4). The US 404 is the tip of the iceberg. The real QE outbound flow is Indian, invisible to WARN, and already being tracked by LTIMindtree, which is the #1 external employer of ServiceNow-adjacent QE talent in Refolk's data.

The US 404 is the visible slice. The QE cut in India is bigger, invisible to WARN, and where the arbitrage lives.

The 14-day timing arbitrage

The sourcing window on the September 28 cohort opens around September 14 and closes by mid-October. California WARN pays through the effective date, and serious job-search behavior spikes roughly two weeks before separation, when severance math is finally settled and people stop waiting.

Here is the calendar for the combined 404:

• August 3 to August 17, 2026: 117-person cohort actively searching, severance clock starts August 17.
• September 14 to September 28, 2026: 287-person cohort actively searching, severance clock starts September 28.
• Mid-October 2026: The August cohort's severance runway starts running out, competing recruiters flood in, response rates drop.
• November 2026 onward: LTIMindtree, Accenture, and internal ServiceNow customer platform teams have picked the strongest profiles.

That is the practical reason to reconstruct the 404 now instead of waiting for a clean summary to appear. There is no clean summary coming, because the WARN filings are the summary and they were split.

The two addresses are literal geo filters

All 404 cuts sit at exactly two street addresses: 2225 Lawson Lane, Santa Clara and 4801 Eastgate Mall, San Diego. Use them as literal filters, not fuzzy location strings.

The workflow that produces the cleanest list:

1. Pull LinkedIn profiles listing ServiceNow with a Santa Clara or San Diego location string. These are the WARN-eligible cohort.
2. Cross-check GitHub commit patterns for QE or test tooling (Selenium, Playwright, TestNG, JUnit, ATF for ServiceNow-specific automation). QE engineers who committed to internal dev branches in the last quarter are the ones already halfway converted.
3. Filter by tenure: 3+ years at ServiceNow signals real platform expertise. Sub-18-month hires are less differentiated from generic QE.
4. Score by title volatility: profiles whose title changed from "Quality Engineer" to "Software Engineer" in the last 6 months are the internal conversions the Blind memo describes.

The third and fourth steps are where structured sourcing tools break. LinkedIn cannot filter on "title changed from X to Y in the last 6 months at the same employer." Boolean cannot express "committed test tooling then pivoted to feature work." Describing the pattern to Refolk in one sentence is the entire pitch: you get the ranked list back, with the signal explained per row, instead of building four separate searches and reconciling them by hand.

The macro backdrop matters for pricing

October 2025 US job cuts hit a 22-year high of roughly 153,000, per Challenger, Gray & Christmas, which means the ServiceNow cohort lands into a market where displaced engineers are competing with a huge volume of other layoff cohorts. That works two ways for a sourcer.

• Response rates are higher. Displaced engineers respond to specific, personalized outreach at multiples of steady-state rates, because their inbox pattern shifted.
• Comp anchors slip. The market is soft enough that offers 10 to 15% below prior TC will clear, especially for QE-to-Dev converts who have not yet re-established a market rate.

CEO Bill McDermott confirmed on April 22 that ServiceNow will not backfill natural attrition through year-end, using AI productivity gains to keep 2027 headcount flat. That is the on-record framing, and it tells you the QE elimination is not a one-off correction. It is a structural bet that AI-assisted development compresses the QE-to-Dev ratio permanently. Anyone still at ServiceNow QE has read that quote and drawn the same conclusion.

The $7.75B Armis acquisition closed April 21, 2026, which adds another layer: overlapping platform and security roles from the Armis side are the next likely WARN wave, and sourcers watching the Santa Clara and San Diego addresses should expect a third filing before year-end.

27

What to do this week

If you are sourcing off this event, three concrete moves clear most of the value:

1. Rebuild the 404 as one list. Do not trust any tracker that shows 287 or 117 in isolation. Both filings are public; the sum is 404 at two addresses.
2. Prospect inside ServiceNow, not just outside. The QE-to-Dev conversion memo means people currently badged at ServiceNow are actively looking. A "current at ServiceNow" filter is a feature, not a disqualifier.
3. Watch LTIMindtree, Accenture, and Deloitte hiring pages. They are the natural landing pads for ServiceNow-trained platform engineers, and their new hires in October and November 2026 will be the shadow WARN list for anyone who never appeared on a California filing.

For engineering leaders reading this from the buy side, the same logic inverts: your window to pick from a scarce Now-trained platform pool without bidding against a system integrator is roughly two weeks per cohort. After that, LTIMindtree quietly wins.

FAQ

How many people did ServiceNow lay off in California in 2026?

The combined confirmed figure is 404 people, split across two separately-filed California WARN notices. The June 10, 2026 filing covers 117 employees effective August 17, 2026, and the July 28, 2026 filing covers 287 employees effective September 28, 2026. Both filings hit the same two addresses (2225 Lawson Lane in Santa Clara and 4801 Eastgate Mall in San Diego), which is why no single EDD reporting period shows the 404 total.

Why is the ServiceNow QE department layoff not showing up in the WARN filing?

California WARN filings do not carry a reason field, so the QE elimination is not visible in the state document. The source is a verified ServiceNow employee post on Blind dated October 15, 2025, which describes the QE Engineer role being retired, most senior QE and QE managers being laid off, and remaining QE engineers being forced to convert into Developer roles or exit. The tiered India reorg (M4+ exit, M3 forced IC, ICs doing dev at same pay) confirms the pattern extends well beyond the California addresses.

Where are ex-ServiceNow QE engineers most likely to land?

Refolk's index shows LTIMindtree as the #1 external employer of ServiceNow-adjacent QE talent, followed by other system integrators (Accenture, Deloitte) and enterprise ServiceNow customers running internal platform teams. Geographically, the top external destinations for the small US "ServiceNow platform" cohort are the San Francisco Bay Area (5 profiles) and San Diego (4 profiles). For the global QE cohort, 62% of the 110-profile pool sits in Hyderabad, Pune, and Bengaluru, meaning the real outbound flow is Indian and mostly invisible to any WARN-style disclosure.

When is the best time to reach out to the September 28 cohort?

Roughly September 14 through mid-October 2026. California WARN pays through the effective date, and serious job-search behavior spikes about two weeks before separation, when severance math is settled. By mid-October the August 17 cohort's severance runway begins to run out, competing recruiters flood in, and response rates drop. The clean 14-day arbitrage window is the two weeks before September 28.