Meta’s 8,000 Job Cuts To Foot The $145B AI Bill

URL has been copied successfully!

Meta Platforms Inc. (NASDAQ:META) is starting its latest round of job cuts this week, and the framing from the top is deliberate. Starting Wednesday, May 20, Meta is laying off approximately 8,000 employees, representing about 10% of its workforce. The company also canceled plans to fill 6,000 open positions. For retail investors, the question is not whether this is painful. It clearly is. The real question is what Meta’s AI layoff strategy reveals about where the company is actually heading.

Record Profits Did Not Stop the Cuts

Here is the contradiction that demands attention. These cuts arrive on the heels of one of the most lucrative quarters in the company’s history, with revenue hitting $56.31 billion and net income reaching $26.8 billion in the first three months of 2026. Furthermore, Meta’s 2025 results showed revenue of $201 billion, up 22% year over year, with free cash flow of $43.6 billion. Meta is not cutting because it is struggling. It is cutting because it has chosen where to redirect the money.

Meta raised its 2026 capital expenditure forecast to between $125 billion and $145 billion, citing higher component pricing and additional data center costs. The company also added $107 billion in contractual commitments in a single quarter for cloud and infrastructure deals. In short, those 8,000 jobs are not disappearing because Meta is in trouble. They are disappearing because they are, in management’s own words, an offset for the AI bill.

Wall Street Is Not Entirely Sold

Despite the bullish guidance, the stock tells a more complicated story. META has fallen roughly 6% over the past year and sits more than 22% below its 52-week high of $796.25, reached in August 2025, underperforming most of its megacap peers. That underperformance is notable. Meta is posting record earnings, spending at historically aggressive levels …

Full story available on Benzinga.com

Please follow us:
Follow by Email
X (Twitter)
Whatsapp
LinkedIn
Copy link

This post was originally published here