WARN Notices Expose the Hidden Costs of Tech Layoffs After the Headcount

On June 24, California's Employment Development Department published a Worker Adjustment and Retraining Notification filing that put a number to what had been rumored for weeks: Walmart is cutting 306 jobs at its technology campus in Sunnyvale, California, including 198 from its Crossman Avenue offices. Those offices opened in April 2025, barely fourteen months earlier, as what the company called a "next-generation workplace." The WARN filing made the layoffs official and, under federal law, started a 60-day clock.

A week later, on June 30, California published another set of WARN filings. This time it was Cisco, with 471 Bay Area positions on the list, as TechTimes reported. Software engineers topped the breakdown. And earlier in June, American employers collectively announced 97,006 job cuts in a single month, according to outplacement firm Challenger, Gray & Christmas, as cited by MSN. That made May 2026 the worst May for job cuts since the pandemic's first wave in 2020.

The WARN Act, passed in 1988, requires employers with 100 or more full-time workers to give 60 calendar days' notice before a plant closing or a mass layoff. The law was designed to give workers, their families, and the communities around them time to adjust. In practice, what happens during that 60-day window varies so dramatically by employer that the filings have become a kind of Rorschach test for how a company values its engineering workforce. The filings are public, the numbers are precise, and yet they obscure as much as they reveal.

The Walmart filing is instructive. Three hundred and six workers in Sunnyvale, spread across two addresses, all classified as permanent layoffs. The company had been cutting tech-side jobs in waves throughout the year, AOL reported, even as it continued to invest heavily in its e-commerce platform and automation infrastructure. The Crossman Avenue office had been pitched as a hub for exactly the kind of engineering work Walmart now says it can consolidate elsewhere or automate. A WARN notice cannot tell you whether the roles being eliminated are front-end developers or machine learning infrastructure engineers. But it does tell you the addresses, and that is often enough to trace the arc of a company's technology strategy.

Cisco's filing is similarly granular. The 471 Bay Area positions spanned multiple job categories, with software engineers making up the largest share. The company had announced the cuts in May, but the WARN filing, published at the end of June, translated a corporate press release into a list of specific job titles and work sites. That translation matters. A corporate restructuring announcement is a narrative. A WARN filing is a spreadsheet, and spreadsheets are harder to spin.

What the WARN Act does not require, and what the filings do not capture, is any information about severance. The 60-day notice period is effectively a federally mandated minimum runway. After that, the severance package, if any, is whatever the company decides it wants to offer, or whatever the employment contract stipulates, or whatever a group of laid-off workers can collectively negotiate. The result is a landscape of wildly divergent outcomes.

Consider the events of this spring. In May, TechCrunch reported that Oracle workers affected by the company's layoffs of thousands of employees attempted to negotiate better severance terms. Oracle said no. The company had announced the cuts earlier, with Reuters citing CNBC's reporting that thousands of positions were being eliminated as the company shifted resources toward artificial intelligence. The workers' attempt to bargain for more than the standard package was rebuffed. The severance formula was the severance formula.

Contrast that with Salesforce. In June, Business Insider's Ashley Stewart reported on the company's standard severance package as a new round of layoffs began. The package, according to the reporting, applies uniformly to US employees. There is a formula. There is a floor. The existence of a disclosed standard is itself a signal: it tells departing workers what to expect and makes the cost of a layoff legible to the organization's own finance team. Whether the formula is generous or merely adequate, the transparency creates a different kind of exit than the one Oracle workers experienced.

Then there is Meta. Forbes reported, in a piece whose headline asked "There Must Be A Better Way Of Being Let Go," that the company laid off 8,000 workers via an automated email sent at 4 a.m. The email was the notice. The severance package, whatever its terms, arrived in the same inbox. The WARN Act's 60-day notice requirement can be satisfied by continuing to pay workers for 60 days after the notice, even if they are not expected to work. Meta's approach collapsed the notice and the severance period into a transaction conducted by a script.

One way at Meta, at least last week at 4 a.m. when 8,000 were let go via an automated email., Forbes, reporting on Meta's May 2026 layoffs

The WARN Act was not written for automated emails. It was written in an era when a plant closing meant a factory in a midsized town, where 60 days of notice gave the mayor time to convene a task force and the community college time to stand up retraining programs. Today, the typical tech layoff hits a distributed workforce, often concentrated in high-cost metros where the labor market is deep enough to absorb engineers relatively quickly, and where the community impact is diffuse. The 60-day window has become, in many cases, a compliance choreography: file the notice, pay out the notice period, calculate the severance multipliers, and move on.

What gets lost in that choreography is the information asymmetry. WARN filings are public, but they are published state by state, in formats that vary from California's searchable database to other states' barely machine-readable PDFs. Outfits like the WARN Tracker newsletter and the Challenger firm aggregate and analyze the data, but the federal government does not maintain a real-time national dashboard. The result is that the most comprehensive picture of tech layoffs in the United States is stitched together by journalists, data scrapers, and volunteer researchers.

The severance data is even more opaque. There is no federal requirement to disclose severance terms, and most companies treat them as confidential. When Business Insider reports on Salesforce's standard package, or when TechCrunch reports that Oracle refused to negotiate, those disclosures are exceptions. The norm is silence. Workers who sign separation agreements often sign away their right to discuss the terms. The market for severance, unlike the market for compensation, operates in the dark.

This opacity has consequences. Severance packages function, economically, as a kind of insurance premium that employers pay for the option to reduce headcount quickly. If a company knows that each layoff will cost, say, two months of WARN-mandated pay plus an additional two to six months of severance, that cost gets priced into the decision to hire in the first place. When the terms are opaque, the pricing is inaccurate. Companies that lowball severance are essentially underpricing their own workforce flexibility. Workers who accept roles without knowing the severance formula are taking on unquantified downside risk.

The Oracle case is particularly revealing here. The company is shifting resources toward AI infrastructure, a capital-intensive undertaking that, as MSN reported, could affect as many as 21,000 workers globally. When those workers tried to negotiate collectively for better terms, the company's refusal sent a clear signal: the severance budget was fixed, and the headcount reduction was going to proceed on the company's timetable and on its financial terms, regardless of what the affected engineers thought was fair.

The WARN filings from Walmart and Cisco tell a parallel story. Walmart's 306 Sunnyvale cuts come after a year in which the company repeatedly reduced its tech workforce while simultaneously growing its overall headcount in other divisions. The WARN filing captures the reduction but not the reallocation. Cisco's 471 cuts capture the Bay Area impact but not the engineering work that may be shifting to lower-cost locations or to different teams. The filings are snapshots of a moving picture.

What the gap between notice and severance actually costs

There is a structural tension built into the WARN Act's design. The law requires notice but does not require severance. The 60-day period is, in effect, a severance floor of two months of pay. But two months is not a lot of runway for an engineer in the Bay Area, where a job search can take three to six months and where the cost of maintaining health insurance through COBRA can run north of a thousand dollars a month for a family. The gap between the WARN floor and what workers actually need to bridge the transition is where severance packages do their real economic work.

Companies that offer four to six months of severance, or that extend the WARN notice period with additional paid non-working time, are effectively acknowledging this gap. Companies that offer the legal minimum, or that structure their layoffs to avoid triggering WARN requirements entirely by keeping each round just under the threshold, are shifting the cost of the transition onto the workers and, indirectly, onto the public safety net. The WARN Act does not prevent this cost-shifting. It merely makes the timing of some layoffs more transparent.

The May 2026 Challenger data, showing 97,006 job cuts in a single month, suggests that the pace of restructuring is accelerating even as the broader labor market remains relatively tight for skilled engineers. The layoffs are concentrated in technology, and the stated reasons, according to TechTimes' analysis of the Challenger figures, increasingly cite artificial intelligence as the driver. AI has led US job cuts for a record four consecutive months as of July 2026, with the tech sector accounting for 31 percent of all layoffs in the first half of the year.

If AI is the stated reason for a growing share of layoffs, then the severance question becomes more acute. Workers displaced by automation are precisely the cohort the WARN Act was designed to protect, but they are also the cohort least likely to find equivalent roles quickly. A software engineer whose primary skill was maintaining a legacy inventory management system at Walmart's Sunnyvale campus is not going to walk into an AI research role at a frontier lab. The retraining gap is real, and the 60-day notice window is not nearly long enough to close it.

What the WARN filings do provide, even in their incomplete form, is a public record. The addresses, the headcounts, the job categories. When KRON4 reported on the Walmart cuts, the station could cite the Crossman Avenue address and note that the office had opened barely a year earlier. That juxtaposition, a "next-generation workplace" and a WARN notice for the same building, is the kind of story that only becomes tellable because the filing is public. Without the WARN Act, the layoff would have been a private transaction between employer and employee, invisible to everyone else.

The question for the rest of 2026 is whether the WARN Act's transparency function can keep pace with the volume and velocity of tech layoffs. The Challenger data says the cuts are accelerating. The state-level WARN databases are not integrated. The severance terms remain private. And the workers filing out of the Crossman Avenue office in Sunnyvale, or the Cisco engineers receiving their notices in San Jose, will each negotiate their own exit on terms set by a company that knows far more about the labor market than any individual worker does. The 60-day window closes. The severance runs out. And the WARN filing becomes another row in a database that nobody is funding to analyze in real time.

If the pattern holds, the July and August WARN filings will surface another wave of cuts as companies prepare their third-quarter budgets and the restructuring cycles that began in the spring work their way through the 60-day notice pipeline. The numbers will be precise. The addresses will be public. The severance terms, for the vast majority of affected workers, will remain invisible until someone leaks them, reports them, or files a lawsuit. And the gap between what the law requires and what the transition actually costs will remain, for now, a private burden carried by the people whose names do not appear in the WARN filing at all.