Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallSome links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Yes—but the precise claim is that public U.S. WARN filings identified at least 2,837 VMware-related jobs affected shortly after Broadcom completed its acquisition. Broadcom closed the transaction on November 22, 2023, but did not announce that 2,837 was the final worldwide layoff total.
What happened
Broadcom completed its acquisition of VMware on November 22, 2023. Within days, state Worker Adjustment and Retraining Notification (WARN) filings began identifying large numbers of affected VMware employees. By December 1, contemporaneous reporting had counted at least 2,837 workers across multiple U.S. states.
The figure came from government filings reviewed and reported by technology publications—not from a Broadcom announcement. The filings generally listed an economic reason for the employment actions, but they did not provide a detailed explanation for every position eliminated.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Broadcom had not publicly disclosed a definitive global headcount reduction at that point. Accordingly, “at least 2,837” is the defensible wording; “Broadcom laid off exactly 2,837 employees” is not.
Broadcom’s acquisition-closing filing confirms the November 22 closing date.
Why reports used both $61 billion and $69 billion
The two figures describe different parts of the transaction. The deal represented approximately $61 billion in equity value, while Broadcom also assumed roughly $8 billion of VMware debt. Media reports therefore commonly described the overall transaction as a deal worth approximately $69 billion.
That does not mean Broadcom paid $69 billion in cash directly to VMware shareholders. A more precise description is that Broadcom acquired VMware in a transaction valued at approximately $69 billion, including assumed debt.
How the 2,837-plus figure was calculated
WARN laws require certain employers to provide advance notice of qualifying mass layoffs or facility closures. The filings can identify an employer, location, number of affected workers, and anticipated effective dates. They are useful public evidence, but they are not a worldwide employment ledger.
Contemporaneous reporting identified the following locations and counts:
Rank #2
| Location | Reported affected employees |
|---|---|
| Palo Alto, California | 1,267 |
| Colorado | 184 |
| Georgia | 217 |
| Massachusetts | 154 |
| New York | 169 |
| Washington | 158 |
| Virginia | 116 |
| Subtotal shown above | 2,265 |
This abbreviated table does not fully reconcile to the broader count of 2,837 reported by Ars Technica and Channel Futures. Additional notices or locations were included in the broader tally. The table should therefore be read as a selection of locations identified in contemporaneous coverage, not as a complete state-by-state reconciliation.
WARN data also has important limitations:
- Not every layoff requires a WARN filing.
- State notices do not cover employment actions in other countries.
- A notice may specify a future effective date, so it does not necessarily mean every affected employee had already departed when the count was published.
- Employees who resigned, declined a new offer, transferred, or left for another reason should not automatically be counted as involuntary layoffs.
Which workers and offices were affected?
The largest publicly identified concentration was VMware’s Palo Alto, California, campus, with 1,267 reported job eliminations. Notices were also reported in Colorado, Georgia, Massachusetts, New York, Washington, and Virginia.
Free tools Windows power users keep installed
One-click scans. No signup required.
The public filings did not provide a complete role-by-role breakdown. The affected workforce appeared to include corporate, administrative, sales, and other VMware functions, but the available evidence does not establish that engineering, sales, or any particular product group accounted for most of the reductions.
VMware had roughly 38,000 to 38,300 employees before the acquisition, depending on the source and reporting date. Comparing the U.S. WARN count with that approximate global workforce can provide rough scale, but it cannot produce a reliable percentage of the worldwide reduction.
Why Broadcom made the cuts
The layoffs were consistent with Broadcom’s stated post-acquisition operating strategy. In acquisition materials, Broadcom described plans to improve VMware’s profitability and remove duplicated general-and-administrative functions, including areas such as human resources, finance, legal, facilities, and information technology.
That strategy fit Broadcom’s broader move into enterprise software. Before VMware, Broadcom had expanded beyond semiconductors through acquisitions including CA Technologies and Symantec. VMware was intended to become a central part of Broadcom’s infrastructure-software business, managed with a tighter focus on operating efficiency and profitability.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →The strategy explains why the cuts appeared quickly after closing, but it does not prove that every individual position had been selected before the acquisition was completed.
In a December 7, 2023 filing, Broadcom disclosed that it expected approximately $1.3 billion in acquisition-related cost-reduction charges through fiscal 2025. That was a restructuring-cost estimate, not a forecast of the number of jobs to be eliminated. Such charges can include severance, facilities, systems, consulting, integration, and other expenses. The figure cannot be divided by an assumed cost per employee to calculate a credible headcount.
See Broadcom’s December 7 filing and the SEC merger documentation for the disclosed integration and cost-reduction objectives.
Leadership and organizational changes
The workforce reductions were part of a wider reorganization rather than an isolated staffing event. VMware CEO Raghu Raghuram stepped aside after the acquisition closed. Broadcom reorganized VMware into four business areas with separate leadership.
Rank #4
VMware President Sumit Dhawan also departed and later became CEO of Proofpoint. These leadership changes, combined with the elimination of duplicated functions, marked a shift from VMware’s previous independent structure to Broadcom’s operating model.
What the cuts meant for customers and partners
For customers, the layoffs did not by themselves prove that VMware products would stop receiving support or that a technical outage would occur. Workforce restructuring, licensing changes, product retirement, and support quality are separate issues.
However, the reductions created practical uncertainty. Contemporaneous channel reporting described concerns about:
- Loss of established account-manager and sales contacts.
- Changes to enterprise agreements and partner coverage.
- Product bundling and licensing direction.
- Support relationships and escalation paths.
- The future shape of VMware’s product portfolio.
A smaller organization can maintain or improve a product, so headcount alone is not a measure of technical quality. Customers should instead evaluate service-level commitments, support contacts, renewal terms, roadmap requirements, application certification, and the vendor’s ability to meet their specific operational needs. CRN’s channel reporting documented the uncertainty among partners and customers at the time.
Recommended Free Tools
What VMware customers should evaluate
The layoffs alone do not answer whether a customer should renew VMware or migrate. The decision depends on the organization’s technology and contract position.
Best Value
- Renewal timing: Review the next contract deadline, subscription terms, price changes, bundling, and support commitments.
- Workload dependencies: Identify reliance on vSphere, vSAN, NSX, Aria, VMware APIs, backup integrations, and third-party certifications.
- Migration cost: Model hardware, storage, networking, retraining, application testing, downtime, and consulting costs—not just software license fees.
- Internal expertise: Compare existing VMware skills with the operational requirements of Kubernetes, Linux, Hyper-V, HCI, or another platform.
- Long-term direction: Consider whether the organization is already moving toward containers, public cloud, or cloud-native infrastructure.
Potential paths include remaining on VMware, moving VMware workloads to Azure VMware Solution, evaluating Azure Local, considering Nutanix AHV, adopting Red Hat OpenShift Virtualization, using Proxmox VE, or adding a multi-platform management layer such as HPE Morpheus Software.
These are not interchangeable choices. Azure VMware Solution preserves the VMware stack while relocating it to Azure; Azure Local is more suitable for Microsoft-centered hybrid environments; Nutanix generally involves evaluating an integrated HCI platform rather than a standalone hypervisor; OpenShift Virtualization fits teams prepared to operate VMs alongside containers; Proxmox may suit technically capable smaller organizations; and Morpheus is primarily a management and automation layer.
Current pricing is generally quote-driven or dependent on cores, hardware, support, geography, and contract terms. Microsoft documents Azure Local billing by physical processor core through an Azure subscription in its billing documentation. Red Hat publishes subscription information through its OpenShift pricing page. Neither page creates a universal apples-to-apples comparison with VMware.
What the number does not tell us
- It is not Broadcom’s confirmed final global layoff total.
- It is not a complete count of all departures after the acquisition.
- It does not provide a complete breakdown by job function or product team.
- It does not establish that every listed employee was already terminated on the date the news appeared.
- It does not prove that VMware support or product quality deteriorated.
- It cannot be used to calculate future VMware performance or the total cost of the restructuring.
Chronology
- May 2022: Broadcom announced its planned acquisition of VMware.
- November 22, 2023: Broadcom completed the transaction.
- November 27 to December 1, 2023: WARN filings and reports made the initial post-closing workforce reductions public.
- December 7, 2023: Broadcom disclosed its estimate of approximately $1.3 billion in acquisition-related cost-reduction charges through fiscal 2025.
The early count of 2,837 was therefore the first publicly documented U.S. measure of the post-closing cuts—not a lifetime total for Broadcom’s VMware workforce reductions. Later restructuring activity should be reported separately rather than inferred from the initial WARN notices.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
