AI Layoffs Just Crossed 981 a Day. Here Is the CHRO Pressure Gauge for H2 Planning

Most Chief Human Resources Officers (CHROs) heading into H2 planning are looking at last quarter's headcount numbers, last quarter's attrition, last quarter's posting fill rate. Those are lagging indicators. And right now, they're pointing at a reality that is already six weeks behind you.

The forward-pressure question for H2 is different: is the tech layoff wave in your sector accelerating, peaking, or rotating into a new hiring pattern? That's what your board will want to know by August. And answering it requires a different set of metrics than what most human resources information system (HRIS) dashboards surface by default.

Here's the pressure gauge.

What the June 1 Data Actually Says

According to TrueUp's layoff tracker as of June 1, 2026, the tech industry has displaced 148,092 workers across 354 separate events since January 1, 2026. That works out to 981 tech jobs eliminated every single day, running 46% above the 2025 daily average of 674 per day.

That gap matters more than the headline number. A daily rate running nearly half again above the prior year baseline is not noise. It's a signal about the pace at which companies are restructuring their workforces, not just trimming headcount.

Within the broader economy, the picture is sharper. Challenger, Gray and Christmas data for 2026 attributes roughly 50,000 of those tech cuts to artificial intelligence (AI) directly. Across all industries, approximately 300,000 total layoffs have been announced in 2026 to date, making AI-attributed cuts about 17% of the total.

But the more strategically important data is the skills bifurcation running alongside the layoff wave. Tech job postings have fallen 36% from their 2020 levels overall, according to a CompTIA and TechTimes composite analysis. Machine learning (ML) and AI engineer role postings are up 59% year-over-year. General software developer postings sit 49% below pre-pandemic levels.

Those two numbers moving in opposite directions inside the same industry are the signal CHROs should be tracking. CompTIA counted more than 275,000 active US job openings mentioning AI skills in January 2026, up 153% from January 2024. The market is not contracting uniformly. It's rotating.

Key Facts

• 148,092 tech workers displaced across 354 events in 2026, running at 981 per day, 46% above the 2025 baseline of 674 per day (TrueUp, June 1, 2026)
• ML engineer postings up 59% year-over-year; general software developer postings down 49% from pre-pandemic levels (CompTIA / TechTimes composite, 2026)
• Software developers aged 22-25 have seen employment fall approximately 20% since 2024; older developers' headcount has held steady or grown (Stanford 2026 AI Index, April 2026)

Why CHRO Lagging Indicators Just Stopped Working

Most H2 board presentations in previous years were built around three internal metrics: net headcount change, voluntary attrition rate, and time-to-fill on open requisitions. Those metrics still matter. But they stopped being the primary signal this year because companies are cutting and hiring inside the same quarter, in different role families, at the same time.

That's the rotation effect. A company announces 1,200 layoffs in software engineering and operations roles in March, then posts 400 ML engineer and data platform roles in April. Your internal headcount tracker shows a net reduction of 800. But the posting-mix shift tells a completely different story about where the company is actually investing.

If your industry peers are doing the same thing, and your company is not, you're falling behind on the talent mix that actually drives productivity in an AI-era stack. If they're doing it and you are too, you're moving in step with the wave.

The problem is that lagging indicators can't tell you which situation you're in. By the time voluntary attrition data reflects a skills shortage, the shortage is already six to nine months old. By the time time-to-fill metrics spike on ML roles, the candidate pool has already been thinned by every competitor in your sector posting simultaneously.

Forward indicators change the timing. They let a CHRO present to the board in August with a read on where the wave is going, not where it was in Q1. And the four metrics that matter most for that read are all available from data your organization already has.

The 90-Day Hiring Pressure Gauge (4 Metrics)

The pressure gauge gives CHROs a fast way to separate broad labor-market noise from the workforce risks inside their own company.

This framework takes roughly 30 minutes to populate from a standard HRIS export. The goal is not precision. It's directional clarity: for each row, you want to know whether your company is accelerating into the wave, tracking flat with it, or already rotating out of it.

Populating this from Workday, BambooHR, or ADP takes one filtered export per row. Daily Rate Trajectory comes from your industry's public layoff announcements (Layoffs.fyi or TrueUp filtered by sector). Posting-Mix Shift comes from your applicant tracking system (ATS) req data. Salary Spread comes from your HRIS compensation module. Cohort Effect comes from your headcount data filtered by hire date and age band.

The threshold values worth flagging: if your industry's daily rate is running more than 20% above your 2025 baseline, you're likely still inside the acceleration phase of the wave. If your posting-mix shift shows AI and ML roles below 15% of total open reqs in a tech-adjacent sector, you're probably under-rotating relative to peers. If your salary spread is below 1.3x (ML start versus generalist start), your comp bands likely haven't kept pace with the market premium for AI skills. For more on why that spread is widening, see how the AI wage premium has doubled since 2024 and what it means for comp rebanding.

The cohort metric has no clean threshold. But a 12-month trailing count showing less than 15% of your hires in the 22-25 band, when that group represents roughly 18-20% of the available labor pool in most sectors, is a flag worth surfacing.

What Boards Will Actually Ask in H2

Three questions will come up in every board conversation about workforce this fall. The CHRO who walks in with the pressure gauge pre-populated has a 20-minute board update. The one who walks in with last quarter's lagging data has a 60-minute explanation.

"Are we ahead of the wave or behind it in our sector?" This is the daily-rate row. If your sector's monthly announcement rate is decelerating while the national rate stays elevated, your industry is rotating out of the layoff phase earlier than the market. That's a buying opportunity on talent, not a reason to freeze headcount. If it's still accelerating, you're still inside the compression, and capacity planning needs to account for that.

"Are we still hiring the right shape of role?" This is the posting-mix row. Boards are increasingly asking this because they're reading the same data you are. The Deloitte job architecture reset analysis from June 1 frames this as a structural shift in how roles are designed, not just a short-term hiring adjustment. If your req mix still looks like 2023, that's a board-level conversation, not an HR process conversation.

"Are we paying yesterday's market?" This is the salary spread row. The 1.7x spread nationally between ML engineers and CS generalists is real and it's widening. If your internal bands show a 1.2x spread, you're either losing ML candidates to competitors or overpaying generalists relative to market. Neither is the intended outcome. The executive framework for board AI workforce investment covers how to frame comp decisions without triggering internal equity escalations.

There's a fourth question the board won't ask directly but you need to answer before they eventually do. The Stanford AI Index finding that 22-25 developer employment has fallen 20% since 2024 doesn't show up as a board question today. It shows up in 2028 when you don't have enough mid-level engineers to promote into senior roles. The pipeline for your 2028 bench is built from the hires you make in the next 24 months. If the cohort effect row on your gauge is trending wrong, that's the metric worth flagging in your H2 narrative even if no one asks.

For more on building the full board narrative, the executive decision framework for AI workforce strategy walks through how to structure the argument across a planning horizon.

What to Do This Week

Action 1: Pull your industry's last 12 months of monthly layoff announcements and chart the trailing-30-day average against the 2025 baseline. Layoffs.fyi and TrueUp both let you filter by industry. You're looking for the inflection point: is the announcement rate still rising, or has it started to flatten? That single chart tells your CEO whether the H2 planning environment is compressing or opening.

Action 2: Pull your last 12 months of open requisitions from your ATS and compute the AI, ML, and data role share as a percentage of total. Break it by quarter. The trend line is what matters, not the point-in-time number. If the share has been growing, you're rotating with the market. If it's flat or declining, you're not, and that's the conversation to have with your business leaders before headcount requests come in for Q3.

Action 3: Pre-write the one-page H2 board narrative around the four gauge rows before the August quarterly. Don't wait to discover in August that your salary spread is below market or your cohort mix is trending wrong. The CHRO who surfaces these proactively sets the agenda. The one who discovers them reactively spends the quarter explaining. The 12-month AI workforce roadmap for a 200-person organization provides a practical template for structuring the narrative across planning horizons.

The wave at 981 jobs per day is not slowing yet. But the mix is shifting. And the CHROs who read that shift correctly in the next 60 days will have a materially different H2 than the ones still looking at last quarter's attrition data.

Related Reading

• Mercer 2026: 99% of CEOs Expect AI Layoffs, But CHROs Aren't Getting the Planning Time They Need: The CEO-CHRO alignment gap that makes H2 planning harder than it needs to be.
• Deloitte's Job Architecture Reset: What the June 1 Restructure Signal Means for CHROs: Why role design is the structural question underneath the daily layoff rate.
• The AI Wage Premium Doubled in 2026: What CHROs Need to Know About Comp Rebanding: The salary spread data behind the pressure gauge's third row.
• Upskill vs. Hire AI-Native: The ROI Case for Each: How to frame the build-versus-buy decision inside the workforce plan you're building for H2.

FAQ

What is the current daily rate of tech layoffs in 2026, and why does it matter for H2 workforce planning?

According to TrueUp's tracker as of June 1, 2026, the tech industry is averaging 981 layoffs per day in 2026, which is 46% above the 2025 average of 674 per day. For CHROs doing H2 planning, the daily rate is a forward indicator of wave phase: whether the pressure in your industry is still building, holding flat, or beginning to rotate into a new hiring pattern. Most HRIS dashboards don't surface this metric directly, which is why it belongs on the pressure gauge alongside internal data.

How do CHROs find out if their industry is tracking ahead of or behind the national layoff wave?

Filter the publicly available TrueUp or Layoffs.fyi data by your industry category. Compute the trailing-30-day announcement rate for your sector and compare it to the same period in 2025. If your sector's rate is decelerating while the national rate stays elevated, your industry is rotating out of the compression phase earlier than the broader market, which creates a talent acquisition window. If it's still accelerating, your H2 headcount plan needs to account for continued pressure on the candidate supply you're competing for.

Why is the Stanford cohort finding about 22-25 developers important if the board isn't asking about it?

The Stanford 2026 AI Index finding that employment for software developers aged 22-25 has fallen approximately 20% since 2024 is a lagging signal for a future talent pipeline problem. The entry-level cohort hired in 2026 becomes your 2028-2030 mid-level bench. If companies across your sector are systematically under-hiring from this cohort, the mid-level promotion pool available in two to three years shrinks at the same time demand for experienced AI-era engineers is likely to peak. Surfacing this in the H2 board narrative, even without a direct board question, positions the CHRO as the executive who saw the slow-burn risk before it became an escalation.