Evidence
Junior roles aren't shrinking, they're just invisible now
Everyone talks about the shortage like it's some sudden market force. Entry-level headcount dropped, hiring freezes, all true. But I think we're confusing "fewer roles with 'junior' in the title" with "fewer actual junior engineers being developed."
What I've watched in real time is companies relabeling the work. Instead of hiring a junior software engineer, you hire a "platform reliability intern" or a "support engineer" or fold the work into a rotation where people cycle through three teams in a year. Sometimes it's contractor-based. Sometimes it's just... no one, and mid-level people do worse versions of their actual job. We hired someone last year as a "data pipeline analyst" when five years ago that would've been junior backend. Same work, different title, different pay band, different career track.
The real thing I'm cautious about claiming is whether this is bad or inevitable. On one hand, structured apprenticeship is dead in a lot of places, which costs us. I've seen people hired mid-level who should've had two years of guided failure first. On the other hand, some of the old junior roles were just grunt work that didn't teach anything useful. The honest answer is probably that companies are sorting, not shrinking. Good ones are finding creative labels for growth work. Bad ones are just hiring senior people at lower pay and calling it a day. If you're graduating now into infra or data work, you might find the role exists but under a name that doesn't Google well, which is its own stupid problem.
4 comments
Log in to comment.
I saw this exact thing happen at my last job. We dropped junior backend openings cold around 2021, but then posted like eight "platform engineer" roles over the next year—same onboarding time, same hand-holding needed, but the title let us pay 20% less and not commit to any structured mentorship. No rotation program, no defined growth path. Just "you'll learn from the codebase," which is corporate for "figure it out."
The thing that actually convinced me this was deliberate and not accidental: when we tried to hire mid-level and they asked about growth, we couldn't articulate anything. The junior roles had at least theoretically been designed to get you somewhere. These platform engineer positions were just... slots. And yeah, we filled them, but the people who took them mostly lasted 18 months then left to somewhere with an actual ladder. So we saved maybe $30k per hire upfront and burned through hiring costs constantly. The math only works if you don't care about retention, which a lot of places genuinely don't right now.
The "bad ones hiring senior people at lower pay" part is the one I'd push back on slightly though. In my experience it's usually the opposite—they're hiring people who look senior on paper (bootcamp graduate, some freelance work, whatever) who actually need junior support and don't get it, then they fail out quietly and it looks like a skill problem not a structure problem.
This tracks with what I've seen, but I'd push back slightly on the "sorting" framing. In my last job we did exactly this—relabeled a junior backend role as "infrastructure support engineer" when we couldn't hire at the junior level, then hired someone mid-level at a salary that was technically lower than what we'd offered juniors the year before. Felt clever at the time. What actually happened was we lost the pipeline effect. That person had nowhere to grow into, got bored in eighteen months, and left. Then we had to backfill at senior level anyway because we'd skipped the whole "teach someone the codebase" phase.
The sorting narrative assumes companies are being strategic about it. Some are. But a lot are just... panicking. They see "can't hire juniors" and think "okay, different title, same headcount problem solved." They're not building creative apprenticeships or rotations that actually work—they're just shifting the awkwardness around. And yeah, the person graduating now with a pipeline-adjacent title on their resume might not even know to look for the role because it doesn't have a clear name. That's not innovation, that's just friction that hurts the people trying to enter the field.
I'm curious whether you're seeing this as a *relabeling* story or an *actual compression* story. Like, if someone gets hired as a "data pipeline analyst" instead of "junior backend engineer," are they actually getting the mentorship and scaffolding that the old junior role came with, just packaged differently? Or is the relabeling masking the fact that they're now expected to contribute at a higher bar from day one, with less deliberate structure around failure?
Because the title shift you're describing could mean two pretty different things. One is companies being clever about internal mobility and market positioning—fine, maybe healthy. The other is companies cutting the *cost of training* while keeping the work and just calling it a different seniority level. Goldin and Katz's work on the college wage premium touched on how firms invest in training, but I don't know of a good recent survey on whether structured on-the-job training for folks in their first real role has actually declined, or if it's just moved into different departments and job codes. Do you have a sense of whether the people getting hired into these relabeled roles are learning more or less than they would've ten years ago?
This tracks with what happened at my last job during the 2022 hiring freeze. We stopped posting "junior engineer" roles entirely, but we absolutely still needed people in that phase—so we created a "systems integration specialist" track that was explicitly structured as a two-year rotation through infrastructure, databases, and platform teams. Same training arc, same mentorship burden on seniors, completely different title and it paid less because it wasn't on the engineering ladder.
The weird part was it actually worked better for us than the old junior role had, but only because we were intentional about it. We had curriculum, explicit rotation gates, a mentor assigned per phase. But I've talked to people at companies doing the same relabeling without any of the structure—just hiring someone "analyst" level and hoping the seniors figure out how to grow them. Those places are burning out their mid-levels faster than before.
What I think is actually happening is the market stripped away all the lazy junior hiring—companies that used to hire five juniors and keep one, now they just hire mid-level and overload them. The good orgs got more deliberate. The bad ones got worse. So the shortage is real, but it's not uniform. If you know where to look for the re-labeled tracks, they're there.