Hiring Junior Developers in the AI Era: What the Data Shows

Hiring of junior developers has fallen further than any other part of the software job market since 2022. Payroll data shows employment of US software developers aged 22 to 25 down nearly 20% from its late-2022 peak by September 2025, and new graduates now make up a small share of hires at both large tech companies and startups. Researchers disagree on how much of this is AI and how much is interest rates, but for a small team the practical question is the same: a junior hire works only if someone senior has time to review their work.

What the data shows

• Employment of young developers is down. In the Stanford Digital Economy Lab's payroll study (ADP data), employment for software developers aged 22 to 25 had declined nearly 20% from its late-2022 peak by September 2025, while older age groups kept growing.
• The gap keeps widening. In the August 2026 update, employment of 22–25-year-olds in highly AI-exposed occupations stands about 19% below where it would be had it kept pace with less-exposed peers, up from a 15% gap in July 2025. The adjustment happens "primarily through reduced hiring of young workers rather than increased separations."
• New graduates are a small share of hires. SignalFire's 2025 report found new grads made up just 7% of hires at the 15 largest tech companies, down 25% from 2023 and over 50% from 2019. At VC-backed startups, they were under 6% of hires, down 11% from 2023 and over 30% from 2019.
• The rebound is senior. US software development postings have grown almost 15% since early 2025, but 71% of the increase between May 2025 and May 2026 came from senior roles (Indeed Hiring Lab).
• Graduates are taking other paths. According to LinkedIn's Economic Graph, 55% of computer science graduates started in non-software-engineering jobs in 2023 and 2024, against 49% in 2016, and entry-level software engineering hiring did not rebound at the end of 2025.

Is AI the cause? Two readings of the same trend

The Stanford authors argue their results are consistent with generative AI affecting entry-level work. Declines are concentrated in occupations where AI tends to automate tasks rather than augment workers. In a February 2026 note, they also tested the interest-rate explanation and found that "more AI-exposed jobs are actually less exposed to interest rates on average." With stricter controls, they find the decline is significant only after 2024, and they acknowledge that the fall in young developer employment has "various factors," not AI alone.

LinkedIn's economists read their own data differently. They find that software engineering hiring, junior and overall, has tracked the broader tech sector and national hiring, and that changes in real interest rates explain most of the variation over the past decade. They call the lack of an entry-level rebound "concerning for job seekers" but say it is not enough to blame AI.

Both camps agree on the fact that matters for you: the entry level is weak, and the recovery so far favours experienced people. For the wider market picture, see how AI is changing the developer job market.

The paradox: juniors gain the most from AI

The same tools that may be reducing junior hiring help juniors the most. In randomised field experiments with 4,867 developers at Microsoft, Accenture and a Fortune 100 company, an AI coding assistant increased completed tasks by 26.08% on average, and less experienced developers both adopted it more and gained more.

There is a catch. In a user study published at the ACM CCS 2023 security conference, participants with an AI assistant wrote significantly less secure code than those without, and were more likely to believe their code was secure. Participants who trusted the AI less and engaged more with their prompts produced fewer vulnerabilities. A junior with AI can produce a lot of plausible code quickly; without review, that is a risk, not a gain. Our checklist on AI-generated code security lists what to check.

Should your startup hire a junior developer?

It can work if

• You already have a senior developer or technical lead who can review every change and has scheduled time for it.
• The product's architecture is settled, and the backlog contains well-defined tasks: UI components, tests, internal tools, small integrations.
• You have automated tests and continuous integration, so mistakes show up before production.
• You can wait a few months for the hire to become fully productive.

Think twice if

• You are pre-MVP with no technical lead. A junior should not be the person deciding architecture, authentication or data models.
• Your product handles payments, health data or other sensitive information and no one can review security.
• You need speed now. The research on AI coding assistant productivity shows gains depend on review and testing, which a junior alone cannot supply.

If you lack senior capacity, you can rent it: a fractional CTO or development partner can provide the review and direction that make a junior productive.

How to make a junior hire work with AI tools

1. Make code review non-negotiable. Every pull request gets a senior review before merge.
2. Ask juniors to explain AI-generated code. If they cannot explain a block line by line in review, it does not get merged. This keeps learning happening.
3. Route sensitive work to seniors. Authentication, payments, permissions and database migrations stay with experienced people until the junior has shown they handle them well.
4. Give them tests to write. Writing tests teaches the codebase and strengthens the safety net that AI-heavy teams need.
5. Track progress. Watch the number of review rounds per pull request; it should fall over the first months.
6. Document onboarding. A written setup guide and coding conventions help juniors and AI tools alike. See our guide to onboarding a remote developer.

The long-term cost of skipping juniors

Every senior developer was once a junior. If companies stop hiring at the entry level, the pool of experienced people who can review AI-generated code will shrink over time. For a single startup that is not a reason to hire someone you cannot support, but it is a reason not to dismiss junior candidates outright once you have the review capacity in place.

Frequently asked questions

Is it harder for junior developers to get hired in 2026?

Yes. Employment of US developers aged 22 to 25 fell nearly 20% from late 2022 to September 2025, and most of the 2025–2026 recovery in postings has been for senior roles.

Is AI replacing junior developers?

Partly, according to Stanford's payroll research, which links the decline to AI-exposed occupations. LinkedIn's analysis points mainly to interest rates and the economic cycle. The cause is debated; the weak entry-level market is not.

Should a startup hire a junior developer?

Only if a senior person can review their work regularly and the tasks are well defined. Without that, a junior with AI tools can produce code faster than anyone can check it.

How should junior developers use AI tools safely?

Use them, but treat output as a draft: understand every line, write tests, and get a senior review. Research shows AI users can write less secure code while feeling more confident about it.

Sources

1. Canaries in the Coal Mine? Six Facts about the Recent Employment Effects of Artificial Intelligence (working paper, November 2025 version), Stanford Digital Economy Lab, 2025-11
2. Canaries in the Coal Mine: August 2026 update, Stanford Digital Economy Lab, 2026-08
3. Canaries, Interest Rates, and Timing: More on Recent Drivers of Employment Changes for Young Workers, Stanford Digital Economy Lab, 2026-02
4. SignalFire State of Talent Report 2025, SignalFire, 2025-05
5. U.S. Software Engineer Talent Landscape, LinkedIn Economic Graph, 2026-02
6. AI and Job Postings: From Destruction to Creation?, Indeed Hiring Lab, 2026-07
7. The Effects of Generative AI on High-Skilled Work: Evidence from Three Field Experiments with Software Developers, Microsoft Research (Cui, Demirer, Jaffe, Musolff, Peng, Salz), 2025-06
8. Do Users Write More Insecure Code with AI Assistants? (ACM CCS 2023), Perry, Srivastava, Kumar, Boneh (arXiv), 2023-12