Recruiting Teams Get Cut First. How Lean TA Survives.
Recruiting is cut first when growth slows: Uber cut 23% of its People division. Here's how a lean TA team keeps pipeline velocity by making the ATS do coordination.
Ernest Bursa
When growth slows, recruiting is the first team cut. Uber trimmed 23% of its People division in June 2026, and AI has now been the single most-cited reason for U.S. layoffs for four consecutive months, according to Challenger, Gray & Christmas. But the open reqs do not disappear along with the recruiters. So a lean talent acquisition team survives only one way: by making the ATS absorb the coordination work a departed recruiter used to do by hand.
This article is not another “AI will screen your candidates” piece. It is the headcount piece. If your recruiting team just got halved, or folded into another org, or told to “use AI to cope,” you are now running the same or more requisitions with fewer people. The math only closes if the system does the scheduling, the follow-ups, the status updates, and the inbound triage. Here is why the squeeze is structural, and the operating model that keeps pipeline velocity without rehiring.
Why Recruiting Teams Get Cut First
Recruiting is the first function trimmed when hiring slows because a talent acquisition org sized for aggressive growth becomes visibly oversized the moment the growth stops. It is the earliest, easiest line to cut.
The clearest recent example is Uber. On June 3, 2026, Uber cut 23% of its People division, the org that houses HR, talent acquisition, HR operations, workplace (“Places”), and culture. The cuts were concentrated on managers and senior staff (Bloomberg, CNBC, Yahoo Finance). A spokesperson framed the total as “well under 1%” of Uber’s roughly 34,000 employees, so a few hundred people. The share is not the story. The concentration is: a single 23% cut to the People function while the rest of the company was spared.
One honest caveat, because it matters for how you read this. Uber explicitly said the cut was not driven by AI. CEO Dara Khosrowshahi framed it as “necessary to maximize the effectiveness of the People team,” and it followed a leadership reshuffle. So Uber is not evidence that AI cut recruiting. It is evidence of something more durable: People and recruiting get cut first in a restructuring, full stop, even when AI is nowhere in the stated reason. That is the structural exposure. When your headcount plan outruns your hiring plan, TA is where the correction lands.
The AI Layoff Backdrop, and What the Numbers Actually Say
The macro backdrop is real, but it is widely misquoted, so it is worth stating precisely. Two separate facts keep getting blurred into one.
Fact one: AI is the top cited reason for layoffs. Per Challenger, Gray & Christmas’s June 2026 report, AI led all stated reasons for job cuts for the fourth consecutive month, an unprecedented streak in their data. AI was cited in 101,743 job-cut announcements in 2026 so far, about 23% of all cuts. In June alone it accounted for 14,029 cuts (31% of the month’s total).
Fact two: tech is the biggest sector being cut. The technology sector announced 139,156 cuts in the first half of 2026, up 83% from 76,214 in the same period of 2025 (Challenger). That is a sector number, not an AI-attribution number.
Read the fine print on the first figure. The 101,743 is all-sector job cuts where AI was cited as a reason. It is not tech-only, and “cited” is softer than “caused.” Anyone rendering it as “101,743 tech layoffs caused by AI” is stacking two different facts on top of each other. Keep them apart and the picture is still stark: hiring demand is contracting across the board, so the TA orgs that serve that demand get right-sized downward almost everywhere.
The automation target also includes recruiting work itself. In July 2025, Recruit Holdings, the parent of Indeed and Glassdoor, cut 1,300 jobs (about 6%) of its HR-technology segment, with the CEO explicitly tying the move to AI reshaping hiring products. IBM separately replaced roughly 200 HR roles with AI agents in 2026 (though it also rehired in other functions, so treat it as “HR work is a named automation target,” not “HR went to zero”). The call is coming from inside the house.
The Survivor’s Math: Fewer Recruiters, Same or More Reqs
Here is the crux the doom coverage misses. When the team shrinks, the workload does not shrink with it. It moves the opposite direction.
Industry benchmarks compiled by Pin, drawing on data from Gem, Ashby, and Bullhorn, show the load climbing while headcount falls:
| Metric | Then | Now | Source |
|---|---|---|---|
| Reqs per recruiter | ~9 (2021) | ~14 (2026), up ~56% | Gem, 2025 |
| Recruiting team size | ~31 people | ~24, down ~23% (2022–2024) | Gem, 2025 |
| Applications per recruiter | baseline | +170%, to 2,500+ | Gem, 2025 |
| Applications per hire | ~100 (2021) | 291 (Q1 2026) | Ashby, 2026 |
| Time lost to sourcing | — | ~14.6 hrs/week | Bullhorn GRID, 2025 |
| Time-to-hire | 33 days | 41 days | Gem, 2025 |
Treat these as directional benchmarks, not census facts. They are vendor-sourced and best read as a pattern rather than precision. But the pattern is unambiguous. The survivor of a cut inherits more reqs, far more applications, and a slower time-to-hire, on a smaller team. One recruiter now carries roughly 14 open roles and 2,500-plus applications, while losing almost two full workdays a week just searching for people. SHRM characterizes the 2026 market as “low-hire, low-fire,” with “TA teams shrinking alongside hiring demand.” ERE’s David Manaster forecast “wrenching change” as teams consolidate and offload repetitive work.
This is the “do more with less” trap in concrete numbers. And it has a specific failure mode.
Automate the Coordination, Not the Judgment
The single most useful reframe for a downsized team: automate the coordination, not the judgment. The bottleneck for a lean TA team is not deciding who is a good hire. It is the connective tissue around that decision, the scheduling, the triage, the nudges, the status updates, that no longer has an owner.
Most teams get this exactly backwards. They automate judgment (buy an AI ranker to decide who is good) and leave coordination (scheduling, follow-ups, chasing feedback) to overworked humans. It should be the reverse.
Here is the split that survives a cut:
Keep human:
- Final evaluation and the hire/no-hire call
- Hiring-manager calibration and alignment
- Candidate relationships and closing
- Offers and negotiation
Offload to the system:
- Inbound triage and routing
- Interview scheduling
- Stall detection and follow-up nudges
- Status updates on stage changes
- The mechanical parts of review (collecting scores, enforcing who reviews what)
Coordination is where a lean team actually bleeds hours, and it is the part software does better than a rushed human, because it never forgets to follow up. Judgment is where your remaining people add irreplaceable value, so protect their hours for it. The archetypal failure is the follow-up that never got sent: after the cut, nobody owns status updates, so a strong candidate waits nine days for a next-step email, assumes they have been ghosted, and takes another offer. That hire did not fail on judgment. It failed on coordination the team no longer had hands for.
Why “Just Add an AI Screener” Optimizes the Wrong Bottleneck
Leadership’s reflex answer to a cut TA team is “use AI.” Almost always, they mean a resume screener. For a coordination-starved team, that optimizes the wrong bottleneck.
A ranker that spits out a shortlist does not schedule the interview. It does not chase the hiring manager who has not left feedback for a week. It does not tell the candidate they advanced. It does not notice a pipeline has stalled for nine days. Those are precisely the tasks that fall on the floor when you cut recruiters, and they are what determine pipeline velocity and candidate experience. Screening was rarely the constraint. A recruiter can eyeball a shortlist quickly. What they cannot do, at 14 reqs and 2,500 applications, is manually keep every candidate and every hiring manager moving.
Bolting an AI screener onto a team that is starved for follow-up capacity is like adding a faster oven to a restaurant whose problem is that no one is left to take orders or bus tables. The kitchen was never the jam.
The Lean-TA Coordination Stack
If coordination is the work to offload, here is the practical stack that absorbs it, in the order a lean team should stand it up. Each layer replaces a specific “the recruiter who left used to do this” gap.
- Inbound triage and routing. Auto-classify and route inbound candidate email to the right application, and notify the owner. This is the inbox-sorting a coordinator used to do by hand every morning.
- Structured scorecards and team voting. Score every candidate against the same rubric, with a defined vote threshold and required reviewers, so a two-person team’s decisions stay consistent and defensible under load. This replaces “we’ll remember” and “let me chase four people for feedback.”
- Stage automation. Move candidates stage to stage on configured rules, so pipelines progress even when no human remembers to click.
- Stall detection and nudges. Flag stalled candidates and pipelines and send a nudge before the candidate goes cold. This is literally the “did anyone follow up?” job, automated.
- Self-service scheduling. Let candidates self-book interviews from single-use links that bind back to the pipeline automatically. Scheduling is the highest-volume coordination task; take it off the survivors’ plates entirely.
- Candidate portal. Give candidates a self-service view of their status, so “what’s happening with my application?” is answered by the system, not by an email a stretched recruiter never sends.
Run these in order and you replace the departed recruiter’s coordination work with a system that does it on rails. Notice what is not on this list: deciding who to hire. That stays with your people. For the volume side of the same squeeze, see why 300 applications per role breaks manual triage and how communication SLAs stop candidate ghosting.
Do It Without Rehiring: The Kit Angle
Everything in that coordination stack is a default in Kit, not an enterprise add-on. That is the point: a post-layoff TA team should not need a Greenhouse-scale contract or a rehire to get force-multiplied. It needs the coordination layer shipped in the box, at a price a shrinking company can carry.
Concretely, each gap maps to a shipped Kit primitive:
- Auto-triage of inbound routes candidate email to the right application and notifies the team, so nothing rots in a shared inbox.
- Structured scorecards and team review voting enforce a consistent rubric, a vote threshold, and required reviewers, so decisions stay reproducible when two people are covering six people’s reqs.
- Stage automation advances candidates on configured rules instead of a human remembering.
- Stall detection with automatic nudges catches candidates going cold and prompts a follow-up before you lose them.
- Self-service scheduling lets candidates book interviews from single-use links that bind back to the pipeline, removing the biggest coordination sink.
- The candidate portal and careers board answer status questions for candidates directly, protecting your employer brand exactly when a shrinking company can least afford ghosting.
- Higher-signal gates like code assignments with deadlines move real evaluation earlier and let the reminders run themselves.
None of this replaces recruiters, and none of it justifies the cut. It protects the people and the candidates left behind. The configured entry-stage triage is auditable and rule-based, not a black-box ranker deciding who is worthy, because the argument of this whole piece is that black-box screening is the wrong fix. The right fix is offloading the coordination the team lost while keeping the judgment it should never give up.
The teams that come through this restructuring in one piece will not be the ones that bought the flashiest AI screener. They will be the ones that were honest about where the hours actually go, and let the system carry the coordination so their remaining people could carry the judgment. If your recruiting team just got smaller, that is the move: not more manual heroics, and not a ranker aimed at the wrong bottleneck, but a pipeline that keeps itself moving. Kit is built to be that pipeline. Start a free trial and stand up the coordination stack this week, or browse the role templates to see it pre-configured.
Related articles
Ready to hire smarter?
Start free. No credit card required. Set up your first hiring pipeline in minutes.
Start hiring free