Layoffs just cooled 53%. AI still led the cuts.

Layoffs dropped by half in June. AI still ranked #1 for the fourth month straight. Read that gap, because your board already did.

On Wednesday, July 1, Challenger, Gray & Christmas released its June report. Two numbers sit next to each other and do not agree.

US employers announced 45,849 job cuts in June - down 53% from May and the lowest monthly total since December 2025. The panic-hiring-freeze phase is cooling. And yet AI was the single most-cited reason for cuts for the fourth consecutive month - a streak with no precedent since Challenger began tracking AI as a distinct reason in 2023. Technology led every sector at 139,156 cuts through June, up 83% year over year, now nearly a third of all US layoffs. AI has been named in 101,743 announced cuts this year.

Then, two days later, the July 3 BLS report landed: the economy added just 57,000 jobs, well under expectations. Layoffs slowed. Rehiring did not pick up the slack.

When the volume drops but AI stays #1, you are no longer looking at a cost-cutting cycle. You are looking at a permanent reallocation - and the AI Wage Gap is the shape it leaves behind.

Challenger said the quiet part on the record: companies are "reallocating budgets toward new capabilities." Meta cut 8,000 in May while guiding capex to $115-145B. Cisco's CFO called its 4,000-person cut "not savings-driven." The payroll dollars are not being saved. They are being moved - out of median headcount and into compute, and into the small number of people who can point that compute at real work.

That is the two-path split, now visible in the macro data.

Path one: your operators become the people who direct the AI - they own the workflows, the evals, the judgment the models still cannot supply - and their comp climbs because the reallocated budget flows to them.

Path two: your people are the line item the reallocation is coming out of. The June slowdown makes this feel safer than it is. Fewer cuts this month does not mean your role got more durable - it means the boards that already cut are now quietly deciding which surviving roles are directing the machine and which are waiting to be automated into it. The rehiring number tells you which way they are leaning.

This week, take ONE role on your team - ideally your own - and answer one question in writing: in the last 30 days, did this role direct AI, or get directed around by it?

Directing looks like: built a prompt library the team reuses, owns an eval set, set the guardrails on an automated workflow, made a call the model got wrong. Getting directed around looks like: produced output a model now produces faster, spent the month on tasks that are one integration away from gone.

If you cannot name one artifact the role directed this month, that is your Column B. The reallocation is already priced into your board's model. Get on the directing side of one workflow before the next report makes the decision for you.

The operators pulling ahead this quarter are not the ones who survived June. They are the ones who can point to the specific thing they built that the AI now runs under them.

———————————————————————————

📊 Get your BEAST Score - the free 0-100 read on your AI Wage Gap. Take it →

🎯 July Portfolio Executive Cohort - 3 seats left. Build the artifact, not the policy →

———————————————————————————

The Leverage Signal is written by Yuri Kruman: 3x CHRO/CLO, AI trainer at Meta, Microsoft and OpenAI, founder of Portfolio Leverage Co. and author of the forthcoming Closing the AI Wage Gap. Reply to this email. I read every one.

📬 Forwarded this? Subscribe free → One signal, one move, every weekday.

]]>