one for every twenty-four
A count of 615,000 open jobs, published this weekend, found one junior software posting for every twenty-four senior ones. That’s usually read as a hiring story. I think it’s a story about school.
One for every twenty-four.
That’s the ratio of junior-labelled to senior-labelled software jobs in a count of 615,566 openings on 14,700 company career sites, published on Sunday by Gleanery, an independent job-data project. Of 17,792 software roles, 2.1 percent used junior terms in the title. Just over half said senior, staff, principal or lead.
The numbers around it point the same way. Indeed’s Hiring Lab reported in July that senior roles made up 69.3 percent of US software postings in the first quarter. Senior postings were up 14.7 percent from a year earlier, and entry-level postings were down 7.5. Stanford’s Digital Economy Lab, working from ADP payroll records, has software developers aged 22 to 25 down about 20 percent in employment since late 2022. Stanford’s 2026 AI Index, using the same payroll data, found developers aged 30 and older at the same companies up 6 to 12 percent over that period. The figure making the rounds this week is the juniors’ half of that split.
This isn’t a shrinking field. Indeed says software postings are up about 15 percent since early 2025, and 71 percent of that growth was senior roles. Indeed economist Sneha Puri says employers need developers “to supervise automated coding, refine products and guide clients.” GitHub data, as reported by TechTimes, has AI agents involved in one of every three pull requests as of October.
So the industry is hiring. It’s hiring people who already know how.
what the junior was for
The usual explanation is substitution. Agents now write the boilerplate, fix the small bugs and write the tests, which was the work juniors used to get. Fewer juniors needed. That’s true, and it misses the point.
The junior’s work was never the product. It was the tuition. Companies were paying for training and calling it labor. It worked because the labor was worth about what it cost, so nobody had to say out loud that the real output was a person who’d be good in five years. The ticket was the excuse, and the engineer was the result.
Aristotle made the point in the Nicomachean Ethics that the arrangement relied on without saying so: “the things we have to learn before we can do them, we learn by doing them, e.g. men become builders by building and lyre-players by playing the lyre.” You don’t get judgment from reading about it. You get it from fixing the bug yourself and finding the second bug under it, and from shipping the bad abstraction and living with it for a year. The boring work was the curriculum.
Now an agent does that work for less, and the hidden subsidy shows. A company looking at a junior today sees a salary set against output an agent produces for pennies, and the training value that used to ride along for free now has to be paid for on purpose. Most companies won’t, and one in twenty-four is what that looks like. Firms will still buy builders. They’ve mostly stopped making them.
That can’t last. The experience premium is a scarcity rent, and it has an expiry date. It’s rising because nobody is making more people like that. Sooner or later something gives. One way out is apprenticeship turning into an explicit, priced thing, closer to a medical residency than an entry-level job: paid at a loss, under contract, with the training as the stated deliverable. The other is that senior engineering becomes a guild that slowly ages out, and the people supervising the agents in 2035 learned on machines nobody runs anymore.
where that leaves you
If you’re mid-career, the market is paying you for judgment, the supervising Puri describes. That judgment came from years of the reps nobody gets now. Aristotle’s point cuts both ways, though. You become a builder by building, and you stay one the same way. A senior engineer who spends five years only reviewing agent output is drawing down an account that isn’t being refilled. Keep some work you do by hand on purpose, and make it the hard part, not the easy part.
If you lead a team, the junior you didn’t hire this year is the reviewer you won’t have in 2032. Make the case for one anyway, and make it honestly: the hire is tuition, the budget line says so, and the output you measure is the person. That’s an easier argument to win than pretending the junior will out-produce an agent.
If you’re early, nobody is going to hand you the reps as tickets. You’ll have to go where the doing is still yours: small companies, open source, on-call rotations, anything where you fix the thing yourself and see what breaks. It’ll be slower and it won’t look like a career path for a while.
And whatever level you’re at, it’s worth asking before you hand a task to the agent: is this a task or a rep? Most of the time it’s a task, so give it away. But if you’ve stopped being able to tell the difference, that’s a sign you’ve been giving away the reps too.
The work was the school. We automated the school and kept the requirement for experience.
Sources: Gleanery on DEV: 615,566 open jobs, one junior for every 24 senior ↗ · Indeed Hiring Lab: the labor market is tilting toward seniority ↗ · Stanford Digital Economy Lab: Canaries dashboard (ADP payroll) ↗ · crypto.news: Stanford AI Index, ages 22–25 down nearly 20%, 30 and older up 6–12% ↗ · TechTimes: postings up 15%, 71% senior, Puri, GitHub one in three ↗ · Aristotle, Nicomachean Ethics, Book II, trans. W. D. Ross ↗