This Round of Big Tech Layoffs Is Hunting the Product Managers Who Just Pass Messages Along
Line up a few things that actually happened this month.
According to Layoffs.fyi, as of July 20, the tech industry has logged 302 layoff events in 2026, affecting roughly 200,000 people — about a thousand jobs lost every single day. More than half of those layoff notices name-checked AI in one way or another.
Microsoft cut 4,800 people. Sales, consulting, Xbox — nobody got a pass. But Microsoft’s HR chief, Amy Coleman, said something that ran exactly counter to the crowd: “The roles eliminated today were not replaced by AI.”
Meta is even more tied in knots: it cut around 8,000 people — a tenth of its workforce — and at the same time moved about 7,000 people into newly created AI-priority roles. One hand pushing people out the door, the other stuffing people into the AI division.
Put these side by side and something strange jumps out: everybody is saying “AI took the jobs,” but when you drill into any one company, even they can’t tell you what AI actually replaced. Microsoft is busy distancing itself; Meta is cutting and hiring in the same breath. Only the bystanders are dead certain the machines stole the paychecks.
So what actually got cut?
What’s being cut isn’t headcount — it’s a layer
Lay out the roles that got mass-cut over the past six months and you’ll notice an unflashy thing they have in common.
The deepest cuts rarely land on the best doers on the front line, or on the top specialists. They land on the middle layer — the people who translate the boss’s intent into tasks, roll up the front line’s progress into reports, and align information between two departments. When GitLab restructured for “the agentic AI era,” it said plainly that what it cut was a couple of layers of management. What Meta has done over and over these past two years goes by the name “flattening.”
The core work of these roles boils down to one thing: passing messages.
Take what A said, translate it into something B can execute; take what B did, roll it up into progress A can understand. Meetings, alignment, chat threads, weekly reports, chasing schedules — at the end of a day, the part that actually creates something from nothing is tiny. Most of the time is spent shuttling information between people.
And shuttling information happens to be exactly the work AI does most smoothly and takes over first. A model that never tires, can read every requirement doc at once, sync every project’s status, and generate a structured report on demand lands precisely on the message-passing layer. So what this round of layoffs is really erasing isn’t a bunch of individual heads — it’s an entire layer of “relay” function.
Once passing messages can be handed to a tireless model, the roles that live on passing messages become the line item on the layoff list that needs the least explaining — even Microsoft can’t be bothered to chalk it up as an AI win.
Product managers are one of the most message-dense roles there is
Right about here, product managers should be shifting in their seats.
Because if you ranked every role by “message density,” product managers would almost certainly sit near the top. Picture a typical PM’s day: a morning requirements review, where you translate the boss’s one-liner “we want an AI feature” into a PRD; an afternoon of cross-team alignment, relaying design’s ideas to engineering and engineering’s worries back to ops; an evening of chasing progress, updating the schedule, prepping tomorrow’s report.
How much of that did you create with your own hands, and how much of it was you shuttling information between groups of people, clearing up misunderstandings, syncing the pace? For a lot of PMs, the latter is the bulk of the job.
This isn’t to say that message-passing has no value. In the past, when information moved poorly inside companies and the walls between departments were thick, a person who could pass the word cleanly and keep everyone in step was genuinely worth money. The catch is that this value rested on one premise — that moving information was expensive — and AI is driving the cost of moving information toward zero. Requirements can be auto-structured, progress can be auto-synced, and the cross-team information gap can be flattened by a single shared model. When passing messages becomes free, the role whose whole job is passing messages ends up in the most awkward spot in the room.
Product managers aren’t going away. But a PM who has bet their entire value on “I can get everyone coordinated” is standing exactly where AI sweeps first this round.
So which kind of PM survives
The contrast makes it obvious.
Say two PMs both spot that “this flow is broken.” The first one’s move: write a doc, schedule a review, relay the requirement to engineering, wait two weeks, get a demo back, take it and check whether it’s right. The whole chain is message-passing and waiting.
The second one’s move: in a single afternoon, use AI to stand up a clickable, runnable prototype themselves, put it in front of users to watch the reaction, and — once it’s right — hand it to engineering to harden into a product. Those two weeks of “relay, schedule, wait” got swallowed in one go by doing it themselves.
The difference isn’t who’s smarter. It’s that the first person’s value grows out of “information routes through my hands,” and the second person’s value grows out of “results come out of my hands.” AI can replace the former; it can’t replace the latter.
Those 7,000 people Meta moved from old roles into the AI division were moved in exactly this direction — from “the message-passing seat that maintains old processes” to “the doer’s seat that gets AI to actually produce things.” The company doesn’t want fewer people. It wants fewer of the seats whose only job is passing messages.
So the signal this round of layoffs sends product managers is very concrete: the better you are at turning “I have an idea” straight into “here’s something that works,” the fewer messages need to pass through you, and the harder you are to catch in this sweep. Knowing how to use AI is just the entry ticket. What actually opens up the gap is whether you can turn a single sentence into a running result — by yourself.
Last thing
Microsoft’s line — “not replaced by AI” — may be the most honest and most easily overlooked thing said in the past six months.
The unspoken second half is this: if a role’s entire value is shuttling between pieces of information, then who replaces it is only a question of timing and naming. This year it’s called AI. Last year it was called cost-cutting. The year before that, flattening. The name changes every year; the seat that gets picked doesn’t.
The layoff list gets refreshed every year. The people sitting in the message-passing seat are always near the front of it.
Discussion