Two numbers are circulating in the same news cycle, and they are describing two different things.
AI is now the most cited reason for layoffs, accounting for roughly a quarter of all job cuts announced this spring. At the same time, a survey of 750 CFOs found that only 44 percent plan any AI-related job cuts at all, and where cuts are planned, they amount to something close to 0.4 percent of total workforce, a figure the researchers themselves described as a rounding error against the scale of the public narrative.
Both numbers are real. They are not measuring the same phenomenon, and InRhythm sees the confusion between them play out constantly in conversations with enterprise leadership teams deciding how to talk about, and act on, their own AI-driven workforce changes.
What the Layoff-Announcement Number Actually Measures
A layoff announcement citing AI is measuring what a company chooses to say publicly, not necessarily what is structurally true about labor demand inside that organization. “We are becoming more efficient with AI” is a clean, board-approved, investor-legible explanation for a headcount reduction. It does not require disclosing that a division over-hired, that a product line underperformed, or that a reorganization was driven by factors leadership would rather not detail. That does not mean AI played no role in every one of these decisions. It means the announcement and the underlying cause are not guaranteed to be the same thing, and treating every AI-cited layoff as clean evidence of AI-driven displacement overstates what the data actually supports.
What the CFO Data Is Actually Telling Enterprise Leaders
The 44 percent, 0.4 percent figures point toward something closer to the operational reality inside most organizations: AI is not yet built into workforce planning as a major line item for the majority of finance leaders. That does not mean AI will never meaningfully change workforce size at scale. It means the public narrative of imminent mass displacement is running well ahead of what most companies’ own internal planning currently reflects.
The Distinction That Actually Matters for Engineering and Technology Leaders
InRhythm works with enterprise engineering organizations navigating this exact tension, and the pattern we consistently observe is this: a headcount reduction and a genuine operating model redesign are frequently announced using identical language, and they produce very different outcomes for the organization.
A genuine redesign starts by examining what the work itself should look like once a meaningful share of it can be generated, drafted, or accelerated by an agent. It results in a new allocation of responsibility across roles, sometimes reducing headcount, sometimes reallocating it toward validation and governance functions the new workflow requires more of, and it typically comes with a documented before-and-after picture of what changed and why.
A headcount reduction with no accompanying redesign removes people from a workflow whose underlying structure has not actually changed. It tends to concentrate in entry-level roles, because junior work often looks automatable on paper, without a corresponding plan for how the organization will develop the senior judgment it will still require in five years. This is the pattern showing up in the broader entry-level hiring data across the technology sector, and it is the pattern InRhythm most frequently helps clients identify and correct before it becomes a structural talent gap.
What This Means Going Forward
The useful signal for a technology leader is not whether the mass-displacement narrative in the press turns out to be accurate. It is whether an organization’s own AI-driven workforce decisions can be described with specifics, this function, this headcount, this documented change in role architecture, rather than only with the word efficiency. This is the distinction InRhythm’s advisory work is built around: helping enterprise engineering organizations tell the difference between a genuine operating model redesign and a headcount reduction wearing a transformation narrative, before that distinction becomes visible the hard way, in a talent pipeline gap nobody planned for.