# The entry-level collapse breaks the experience filter

AI is absorbing the junior work that used to mint experienced candidates. Screens built on years of experience now filter a shrinking pool that the production data says was never predictive.

> By Saad Bin Shafiq, Founder of Nodes · Jul 20, 2026
> Canonical: https://www.nodes.inc/blog/entry-level-collapse-breaks-experience-filter

**Answer:** The entry-level hiring collapse is AI absorbing work that used to produce experienced candidates. Experience screens assume that pool refills itself. At one carrier, zero of 3,597 testable resume keywords predicted the production milestone after correction. In an exact n=50 reference subset, the industry-experience filter would have excluded 80% of eventual top performers. The finding is a reason to test a screen against local outcomes, not a transferable error rate.

---
The junior rung is being pulled up. This week's coverage of the entry-level hiring collapse describes the same move across finance, consulting, and professional services: smaller analyst classes, smaller first-year cohorts, junior intake deferred another quarter, because the work that trained those people is the work AI absorbs first.

Most of the commentary treats this as a story about young careers. It is also a story about a screening filter that was already failing, and is about to fail faster.

## The assumption inside every experience screen

A years-of-experience requirement is a training outsource. "Three years required" means someone else hired this person three years ago, into exactly the kind of junior work that is now disappearing, and paid for their reps. The screen works only while the rest of the market keeps running the school.

That is the quiet dependency. Every experience filter assumes the pool of experienced candidates refills itself. Pull the bottom rung across an industry and the refill stops, on a delay, which is to say: the shortage is already in the pipe and nobody's requisition system knows it yet.

## The ladder math

Walk the arithmetic forward. A firm that cuts its first-year intake this year is deciding how many three-years-experienced candidates exist in three years. Multiply across an industry doing the same thing in the same quarter and the mid-level talent pool of the late 2020s is being set right now, by hiring freezes that look local and reversible from inside any one company.

The first symptom will not announce itself as a pipeline problem. It will show up as time-to-fill creep on mid-level requisitions, and it will be misread as a compensation problem, because that is what unfilled requisitions usually get blamed on. Recruiters will widen screens by hand. The exceptions process will become the process, unlogged and uncalibrated. By the time the pattern is visible in quarterly numbers, the cohort that should have been ramping is three years gone.

None of that math requires a prediction about AI capability. It only requires this year's intake decisions, which are already public.

## The filter did not deserve the trust

Here is the part the workforce commentary keeps missing: the experience screen was not a good filter that lost its supply. It was a bad filter with a good reputation.

At one Fortune 500 insurance carrier, we parsed 8,181 unique skills from four years of applicant data and tested the 3,597 with enough coverage to measure against post-hire production. After Bonferroni correction, zero predicted the production milestone. Thirty pointed the wrong way. In an exact n=50 reference subset, the industry-experience filter would have excluded 80% of eventual top performers and the cumulative screening funnel would have excluded 98%. Separately, a retrospective counterfactual found that the experience rule would have excluded 2,863 producing hires associated with $17.7M in observed annual premium credit.

The proxy did not survive contact with production data. The methodology is public in [Decision Traces](https://arxiv.org/abs/2604.19819), and every statistic above is registered on [the evidence page](https://www.nodes.inc/evidence).

Read those two facts together. The screen that is about to run out of candidates was rejecting the best ones while supply was plentiful. The collapse does not break a working tool. It removes the excuse for keeping a broken one.

## The collapse compounds the error

Two things happen to an experience screen when the entry rung disappears, and they stack.

The pool that clears the proxy shrinks. Requisitions age. Hiring managers escalate. The screen gets waived case by case, which means the real screening criteria become whatever each recruiter improvises under deadline, invisible to calibration and impossible to defend later.

The survivors become a stranger sample. The people who still show three years of experience got their reps at the firms slowest to automate. Title inflation rises as candidates stretch to clear bars the market stopped helping them clear honestly. The proxy stops measuring capability and starts measuring where someone happened to be standing when the music stopped.

The exact n=50 reference result does not establish how the filter will behave as the wider labor pool changes. It is a warning to test the rule on current local outcomes instead of assuming either its pass rate or error rate transfers.

## What replaces the rung

Three moves, in order of how soon they pay.

What replaces the missing rung is customer-owned outcome evidence, including counterexamples and uncertainty. It does not use a selected employee as a template or establish an individual result, and a named human decides. Related: [Interview signal beats pedigree signal](/blog/interview-signal-vs-production-signal)

Instrument the ramp. If capability is the input, the milestone trail is the receipt. A hire scored on capability and tracked against production milestones produces the calibration data that makes the next screen better. Tenure-based development plans assume the old ladder. Milestone-based ones survive its absence.

Rebuild a deliberate junior intake. When the screen reads capability, an entry hire stops being a resume gamble, and the economics of getting them productive are measurable. The firms that keep a rung will own the experienced market in three years, because everyone else outsourced training to a school that closed.

## Pressure-test your own funnel this quarter

You do not have to take the carrier's numbers on faith, and you should not take your own funnel on faith either. The audit is three joins on data you already hold.

Pull every hire from the last three or four years. Join each one to the screening verdicts they received on the way in: which filters they cleared, which they cleared by exception, what the screen scored them. Then join both to the production outcomes your business tracks, whatever production means in your world: quota, caseload, billable ramp, quality measures.

Now ask the uncomfortable question. What fraction of your current top quartile would have been excluded by your own screens if no recruiter had intervened? In the carrier's exact n=50 reference subset, the answer for one filter was 80%. Do not import that rate. Recalculate it on your own cohort, role, outcome, and time window before changing a rule.

For any screening filter, a People Decision Engine treats measured outcomes as governed evidence with uncertainty, never categorical truth or proof of an individual's success. Human decisions provide context and a named human makes the final call. Calibration or production promotion requires validation. The 10,765 people are only the historical study cohort, never Nodes throughput, meaning they were not individually scored, recommended, gated, or processed through Nodes. Enterprise talent at one Fortune 500 insurance carrier is the sole current production proof. Underwriting, lending, and admissions are ready for historical validation.

## Two objections, answered

Some roles carry mandatory licensure or certification. Keep those requirements. The point is the difference between a credential a role cannot operate without and a proxy that stands in for capability nobody measured. The study's anti-predictive keywords were proxies. Licenses are table stakes. A funnel that cannot tell the two apart treats both as sacred, and only one deserves it.

And if AI keeps climbing, will the mid-level rung not thin next? Probably, which strengthens the argument. When role shapes change faster than title taxonomies, the only stable screening target left is demonstrated capability against your own outcomes. Titles describe the old ladder. Production describes the person.

## The workforce-planning bill arrives last

Succession models assume feeder ranks. [Internal mobility assumes a bench](/blog/internal-mobility-is-a-data-problem). Both inherit the hole the entry freeze digs, and both report to planning horizons long enough that the hole is invisible until someone models it on purpose.

The planning exercise worth running this quarter is simple to state: take the current intake rate, project the internal candidate pool for every role family three to five years out, and price the gap between that pool and the succession plan's assumptions. For most organizations the number will be the strongest argument the junior intake has ever had.

Run the same projection against attrition while you are at it. Every mid-level departure in a thin-intake world is replaced from a pool your own freeze helped shrink, at a market price your own freeze helped set. The replacement cost curve bends up over the exact years the succession plan assumed a bench. Modeling that curve now, before it prices itself, is the cheapest decision in this entire subject. A [governed outcome evidence](/blog/what-is-a-performance-genome) for each role family tells you what to screen the new intake for. The production data already knows.

The rung is not coming back. The proxy it fed was never predictive. Score what predicts.

## Sources

- [Decision Traces, the published methodology](https://arxiv.org/abs/2604.19819)
- [Nodes evidence and methodology registry](https://www.nodes.inc/evidence)


*Saad Bin Shafiq is the founder of Nodes, serving data-sensitive enterprises. Methodology: [Decision Traces](https://arxiv.org/abs/2604.19819).*