No Juniors Today, No Seniors in 2031 — Blog | Filipe Brito Ferreira — Front-End Engineer<br>Skip to content

⤢ Title

No Juniors Today, No Seniors in 2031<br>Junior hiring is down 40%. AI gave boards the rationale to keep cutting. The apprenticeship lag is 5–7 years — no juniors today means no seniors in 2031.<br>ai / software-engineering / hiring / engineering-management / career

I have been tracking junior software-engineering listings on LinkedIn and Indeed since late 2024. The graph has one shape. Flat in 2024, sloped down through 2025, falling off a cliff through Q1 2026. Big tech is openly senior-only. Mid-tier has followed. The few junior roles that did go up in 2026 advertise lower salaries, higher experience floors, and a take-home test designed to detect LLM use rather than ability.

The data is consistent across sources. Junior developer postings are down around 40% compared to pre-2022 levels, and entry-level hiring at the fifteen biggest tech firms fell 25% from 2023 to 2024. Computer-science graduate unemployment hit 6.1–7% in 2025, the fifth-highest among US college majors. According to a recent LeadDev survey, 54% of engineering leaders plan to hire fewer juniors in 2026 because AI copilots let seniors absorb more work.

AI didn’t start the junior contraction. The post-2022 retraction did. But AI is the rationale boards lean on to keep it going. The apprenticeship pipeline that produces senior engineers has a 5–7 year lag. The cohort we aren’t hiring today is the senior bench we won’t have in 2031.

The predecessor to this piece argued AI didn’t break engineering. We did, by treating it as a quota multiplier. This piece is what that mistake looks like when you compound it five years out.

How Seniors Used to Get Made

Senior engineers aren’t produced by classroom learning. They’re produced by an apprenticeship of specific moments, and almost all of those moments are exactly what AI is removing.

The arc takes five to seven years on average. First commit to staff-level judgment isn’t a graduation timeline, it’s a feedback-loop timeline. You learn to be senior by getting your pull request torn apart in review and having to defend the design choice. By debugging a production incident at 2 a.m. with nobody to ask, when the LLM either doesn’t exist or doesn’t know your system. By owning a feature whose failure mode you didn’t anticipate, and writing the postmortem with your name at the top. By being the person who has to explain in a room of executives why the migration broke.

None of this transfers through documentation. It transfers through accountability. Your name on the broken deployment, your call in the heated design review. And AI risks shortcutting the moments where the cost of failure used to land on the engineer, not on the tool. That is where senior judgment gets built.

In the previous piece I catalogued four habits that hollow out code review: copy-paste without reading, stack traces becoming LLM input, AI-generated tests no one validates, pattern atrophy. Those four habits are also the four exact failures of the apprenticeship loop. Same problem at the per-developer scale of the previous piece, same problem at the industry scale of this one.

You can’t grow a staff engineer in a classroom. You can only grow one in a feedback loop. Apprenticeship is the most common one, self-directed practice with brutal review is the other. AI didn’t remove a job. It removed the apprenticeship loop that produced the next generation of seniors at scale.

What Hiring Actually Did in 2025–2026

This isn’t a prediction. Most of the damage landed in the eighteen months between late 2024 and the end of 2025, and you can feel it in the loops.

I ran two junior hiring loops in 2024 and one in 2025. In 2024 we worked from three good shortlists out of roughly forty applicants per role. In 2025 we had one passable shortlist out of two hundred. The pool wasn’t smaller. The floor was lower. Every recruiter and engineering manager I talked to that year had a version of the same story. We were fishing in the same shallow water, with the same complaints, and the candidates who did show up couldn’t pass a whiteboard problem they’d have solved in 2022.

The macro numbers track what the loops felt like. Junior developer postings are down roughly 40% compared to pre-2022 levels, and entry-level hiring at the fifteen biggest tech firms fell 25% from 2023 to 2024. Employment for software developers aged 22 to 25 has dropped nearly 20% from its late-2022 peak. The contraction concentrates at one end of the ladder. Senior listings stay roughly stable while junior listings fall, which is the shape that should be worrying anyone budgeting for a 2030 staff bench.

The Klarna announcement is the one I kept hearing back about. Roughly 700 jobs cut between 2022 and 2024, AI credited for the savings, the CEO doing a victory lap in interviews about how efficient they’d become. Salesforce and Meta followed through 2025 and into 2026 with...