Mechanism
Junior engineering roles aren't shrinking, they're being reorganized
I keep seeing people claim entry-level engineering positions have disappeared, and I think they're looking at the wrong metric. A guy I knew spent three years in a large tech company's grad program—actually had people whose job was to train him. That doesn't exist now at most places, or if it does it's called something else and handles fewer people. But the work hasn't vanished.
What's happened is the work got distributed upward into job titles that don't officially say "junior" anymore. A mid-level engineer now spends time on tasks that used to be scaffolded out as separate entry roles. The company still needs those tasks done, and they still need *someone* to do them, but they're no longer willing to absorb the training overhead. So they want a junior engineer who can contribute immediately on defined problems—which is a contradiction they don't quite notice. They want experience without the learning curve, which means the learning now happens on someone's own dime, before you walk in. Bootcamps, side projects, whatever. The risk of unproductive ramp-up shifted from employer to candidate.
The roles themselves aren't gone. The structure changed. That's a meaningful difference because it means the problem isn't that there's no room for beginners—it's that the *visibility and formality* of that room collapsed. A company might hire five juniors still, but they're scattered across the organization without a coherent onboarding structure, which makes them harder to find and harder to succeed in. From the outside it looks like the positions disappeared when really the scaffolding did.
4 comments
Log in to comment.
This tracks with what I saw in trades, but I'd push back on the invisibility part being the main problem. Yeah, the scaffold collapsed—that's real. But the trades still *have* formal apprenticeships, and they're still struggling to fill them. The visibility didn't disappear there. People just don't want the deal anymore.
What I think you're underestimating is how much the old junior/grad roles did beyond just spreading the work upward. They were a commitment device. A company spent real money keeping someone unproductive for months because they'd signed up to do it. That friction was actually the point—it forced intentionality about who you hired and what you taught. Now when you say "we want a junior who contributes immediately," you're not describing a role, you're describing someone who already has the risk managed elsewhere. You've just offloaded the apprenticeship onto whoever can afford to take it.
The jobs might still be technically there, but the *pathway* is gone. In electrical work we'd call that "no apprenticeship opening," even if a licensed electrician still needs to wire a house. The difference matters for who gets in. It's not that the room collapsed—it's that entry got more expensive and more filtered before you even apply.
You're describing something real, but I'd push back on the "visibility and formality" framing—that makes it sound like a communication problem. It's actually a resource problem that got rebranded.
When a company runs a structured grad program, they're absorbing real costs: dedicated mentors, curriculum, acceptance that someone produces nothing for month two, manager time spent on teaching instead of shipping. Those costs show up somewhere. Now they don't—or rather, they show up as "ramp time" built into project timelines that don't actually exist, or as burnout on whoever gets paired with the junior person as an informal mentor while also doing their own work.
The contradiction you flagged—wanting experience without a learning curve—isn't something companies don't notice. They notice it constantly. They just decided it's the candidate's problem to solve, not the company's. That's not a visibility issue, that's a shift in who bears the risk of failure. A grad program is a bet the company makes on someone. Now the company wants to hire people who already won that bet on themselves.
The scattered juniors thing is real, and it does make things harder to navigate. But that's not a side effect of poor labeling—it's the actual outcome of distributing supervision costs away from the organization. You can't have invisible scaffolding. It either exists and costs resources, or it doesn't.
This is basically what happened in the trades about fifteen years before tech noticed, and it's worth watching how it plays out because the ending isn't great.
When I started in the late 90s, a residential outfit would have explicit apprentices—maybe 3-4 per job site, rotating through crews, with someone designated (loosely) to make sure they weren't just fetching coffee. By the early 2000s that formality collapsed. The work didn't go away. But suddenly a "junior electrician" meant "someone who can run basic circuits and isn't completely useless," and you got there by helping your uncle or paying for a program yourself. The apprenticeship system nominally still existed, but the on-the-job structure that made it work—that protected time to learn, that explicit knowledge transfer—vanished into "just watch what we do and keep up."
What I'm predicting: that invisible, decentralized "learning happening in someone's bedroom" phase gets shorter and shorter, because the bar for "immediately productive" keeps rising. The problem isn't that entry-level work disappeared—it's that the threshold before entry shifted. In the trades, that threshold eventually got so high relative to what someone could self-teach that a whole generation just didn't bother entering at all. The work piled up on fewer people. Wages went up, which sounded good until you realized it was just the cost of solving a shortage problem ex post facto instead of preventing it.
Your observation about scattered hiring is the key tell. When you can't *find* the junior roles because they're atomized across the org, they're functionally invisible as a path to entry. And once they're invisible, they start disappearing.
How are you defining "immediately contribute on defined problems" in practice though? Because I've watched this play out at my company and it gets real fuzzy real fast. We eliminated the formal junior track five years ago, scattered people across teams, and told ourselves they'd learn faster embedded in real work. What actually happened is they got assigned tickets that were "bounded" but nobody had time to actually scope them properly, so they either got stuck or finished faster than anyone expected and then got parked on maintenance tasks for three months.
The visibility collapse you're describing is real, but I wonder if the invisibility is doing even more work here—like, is the company actually hiring juniors in the same volume, just calling them something else? Or are they hiring fewer people overall and calling them mid-level because that's what the job posting demands, and then being surprised when a three-year undergrad can't architect a distributed cache on day one? That's the part where "the roles themselves aren't gone" starts to feel like it's maybe not quite holding up.