Quick answer: Entry-level tech hiring has dropped sharply since 2019. New graduates made up just 7% of new hires at Big Tech companies in 2024, down 25% from the year before and more than 50% below pre-pandemic levels, according to venture firm SignalFire. AI is absorbing the routine tasks junior developers used to learn on the job. But the jobs themselves haven't vanished — the on-ramp into tech is being rebuilt, and freelance or contract work is quickly becoming the new starting point for many junior developers.

If you're a computer science grad who's sent out hundreds of applications and heard nothing back, you're not imagining things. And if you're a hiring manager wondering why your senior engineer search keeps coming up empty, the two problems are connected. Let's walk through what's actually happening, and what you can do about it either way.

The Numbers Behind the Squeeze

Start with the headline stat. SignalFire's State of Talent Report tracks hiring across more than 600 million LinkedIn profiles, and its 2024 data shows recent graduates made up just 7% of new hires at the 15 largest tech companies. That's down 25% compared to the year before. Stack it against 2019, before the pandemic reshaped hiring, and the drop is more than 50%.

Startups tell a similar story. Graduate hiring there fell from roughly 30% of new hires in 2019 to under 6% in 2024, a steeper collapse than at Big Tech.

The pattern isn't limited to the US. A 2026 Linux Foundation report, which surveyed nearly 400 hiring and training managers, found something that looks contradictory at first glance: AI is driving a 27% net increase in overall tech hiring across Europe, even as entry-level hiring in the same region contracted by 3%. Compare that to the rest of the world, where junior hiring actually grew by 14% over the same period. Europe is the outlier, and the report's own authors point to slower AI infrastructure adoption and a wider cybersecurity skills gap as part of the explanation.

Put the two data sets together and the message is consistent. Tech hiring overall isn't shrinking. The bottom rung of the ladder is.

It's Not Just Tech's Imagination — Here's What Changed

AI Is Absorbing the Tasks Juniors Used to Learn On

For decades, junior developer jobs worked the same way an apprenticeship does. You got handed the unglamorous work: fixing small bugs, writing boilerplate code, running routine QA checks. It wasn't exciting, but it taught you how a codebase actually behaves, and it gave senior engineers a low-risk way to evaluate you.

That work is exactly what generative AI tools now do well. Brookings Institution research found that AI could automate more than 50% of tasks in entry-level roles, roughly five times the automation risk facing more senior positions. When a coding assistant can draft, test, and clean up routine code in seconds, the traditional justification for hiring a junior developer to do that same work gets a lot weaker.

Sead Ahmetovic, CEO of global developer hiring platform WeAreDevelopers, argues the popular framing of this shift misses what's really going on. Talking to The New Stack, he put it this way: junior roles aren't disappearing, but the work that used to define them is, so the whole definition of what a junior role even means needs to catch up.

The Economics of Training vs. Hiring

There's also a cold, practical reason for the freeze. The Linux Foundation's research found that organizations are 3.7 times more likely to invest in training their existing staff than to hire someone new. New hires also take longer to become productive than most companies would like, with nearly a quarter of that ramp-up time burned in just the first six months.

Run the math from a manager's chair, and the short-term case for skipping junior hires and upskilling current staff instead looks obvious. Whether that's a smart long-term bet is a different question entirely.

The Uncomfortable Trade-Off: Killing the Senior Pipeline

Here's the part that should worry every engineering leader currently celebrating leaner headcount. Senior engineers aren't hired fully formed. They're built over years of exactly the kind of hands-on, lower-stakes work that's now disappearing.

Ahmetovic frames it simply: you cannot grow a senior engineer without ever hiring a junior one first. A widely shared piece on this topic put a sharper edge on it, arguing that companies are trying to buy experienced engineers without funding the years of mistakes and mentorship required to create that experience in the first place. That decision might look efficient on a spreadsheet today. In three or four years, when the senior engineering shortage that companies keep warning about actually arrives, it may look like one of the more expensive mistakes the industry made in this decade.

"Junior" Doesn't Mean What It Used to Mean

If entry-level roles are surviving in a different shape, the obvious question is: what does that shape look like now?

The Linux Foundation report points to a broader shift happening at every level of tech hiring, not just entry level. Companies increasingly want people who combine software engineering with AI fluency, security awareness, and enough product and business understanding to use AI tools responsibly rather than just competently.

Junior roles used to reward writing code from scratch. Now they reward reviewing and correcting AI-generated code. They used to reward following existing patterns. Now they reward judgment about when AI output is wrong. They used to reward learning syntax and tooling. Now they reward understanding system context and business logic. They used to reward individual task completion. Now they reward oversight of AI-assisted workflows. And where a CS degree used to be the main filter, demonstrated, verifiable project work is quickly becoming the real one.

This is a demanding shift for anyone starting out, since it asks for the kind of judgment that traditionally came after a few years of experience, not before it.

What Junior Developers Can Actually Do About It

Most coverage of this trend stops at the diagnosis. Here's the part that actually matters if you're the one applying.

Treat freelance and contract work as your new entry point. With full-time junior roles scarce, freelance platforms let you build a track record of shipped, verifiable work without waiting for a company to take a chance on you first. A handful of completed freelance projects, visible and checkable by a future employer, can do more for your credibility right now than a degree alone.

Specialize in AI oversight, not just AI use. Everyone can prompt a coding assistant. Fewer people can catch when its output is subtly wrong, or explain why a suggested fix breaks something three steps downstream. That review-and-judgment skill is exactly what companies say they're short on.

Build a portfolio that shows judgment, not just output. A GitHub repo full of AI-assisted projects proves you can use a tool. A short write-up explaining a decision you made, a mistake you caught, or a trade-off you weighed proves you can think. Employers are filtering for the second thing now.

Take the smaller reps. A short-term contract, a fractional role, or a well-scoped freelance gig gives you the same kind of low-stakes learning that a traditional junior role used to provide, just structured differently. It's a real way to accumulate the "years of mistakes and mentorship" the industry still needs, even if no one's calling it a junior job title anymore.

What This Means for Companies Hiring Right Now

If you're on the hiring side, the smart move probably isn't to keep the junior pipeline frozen indefinitely. It's to redesign it.

That could mean restructuring junior roles around AI oversight and review from day one, rather than expecting new hires to first cut their teeth on tasks AI now does faster. It could mean using contract-to-hire or freelance arrangements to evaluate junior talent with less upfront risk than a full-time offer requires. And it likely means investing in faster, more structured onboarding, since the Linux Foundation data shows companies already rank technical training above compensation as their top retention tool, cited by 93% of the organizations surveyed.

The pipeline problem doesn't fix itself. Someone has to decide to hire the next generation of engineers, even while AI keeps getting better at doing junior-level work. The companies that figure out how to do that profitably will have a real advantage over the ones that just keep waiting.

FAQ

Why are companies not hiring junior developers? AI now handles many of the routine tasks that junior developers traditionally learned, like writing boilerplate code and running basic QA. Combined with the cost and time it takes to bring a new hire up to speed, many companies are choosing to invest in training existing staff instead of hiring new graduates.

Is AI really taking entry-level tech jobs? The data suggests AI is a major factor, though not the only one. Brookings Institution research estimates AI could automate more than 50% of tasks typically done in entry-level roles. Interest rates, startup funding conditions, and broader cost-cutting have also played a role.

Will junior developer jobs come back? Most researchers and industry leaders expect the junior role to be redefined rather than disappear entirely. Companies still need a pipeline of new talent to eventually become senior engineers, and several industry voices, including WeAreDevelopers' CEO, argue that pipeline can't be skipped without long-term costs.

How can new grads get a tech job in 2026? Freelance and contract work is increasingly serving as the new entry point, letting new grads build a verifiable portfolio without waiting for a traditional full-time offer. Specializing in AI oversight and review, rather than just AI usage, is also becoming a differentiator.

What skills do junior developers need now because of AI? Employers are increasingly looking for AI fluency combined with judgment: the ability to review AI-generated code, catch errors, and understand broader business and security context, rather than just writing code from a blank page.