AI Hasn’t Torched Junior Dev Jobs — It Has Changed What The Job Looks Like

From programmer to agent manager

A post doing the rounds this week looks at employment data and concludes that AI has torched the market for junior programmers. The headline numbers are striking — youth employment in software down, entry-level postings shrinking — and I am sure the data is real.

But I read the article and came away with a different take. Because the same data also shows that overall developer employment is growing, GitHub is adding accounts faster than ever, and the roles that are expanding are the ones where judgment matters more than typing.

The original article is worth reading. Here is my take on what is really happening.

AI raises everyone’s ceiling

The narrative that AI replaces junior developers implies that senior developers are somehow immune. I don’t believe that. A developer with fifteen years of experience who knows what good code looks like can use AI to produce better code faster. But so can a junior who is curious, willing to learn, and not afraid to challenge the AI’s output.

The difference is not seniority. It is the ability to evaluate what the AI produces. Can you tell when the generated code is wrong? Do you know when to accept it and when to rewrite it entirely? Can you spot a security issue in something the AI wrote confidently but incorrectly?

Those skills come from experience and from caring about the quality of your work. They are not automatically granted by a job title.

From programmer to agent manager

What I see happening around me is a shift in what the job looks like. The traditional technical person — call them a developer, an engineer, a sysadmin — is becoming a manager of agents. You describe what you need, review what comes back, iterate, correct, and integrate. The hands-on keyboard work shifts from writing every line to directing, reviewing, and orchestrating.

This is not a downgrade. It is an upgrade. You are moving up the stack, not out of the industry.

But here is the catch: if you do not have the underlying knowledge — security, architecture, long-term maintainability, the trade-offs between different technologies — you cannot effectively drive the AI. Your results will be spotty, and you will not know why. AI amplifies good judgment and bad judgment equally.

The people who embrace it will transition, not disappear

I think the junior programmer job title as we knew it is probably going away. The idea of spending your first two years fixing typos and writing unit tests while you slowly absorb how the system works feels outdated when an AI can generate the tests and spot the typos for you.

But the people who would have filled those roles are not going to be left behind. They will transition into something else — something closer to what the data scientists and systems analysts are already doing. They will work at a higher level of abstraction, sooner, because the AI handles the lower levels.

The ones who embrace the change, stay curious, and build their technical judgment will be fine. The ones who expect the old career path to stay intact will struggle — but that was always true, with or without AI.

Not a conclusion, just a thought

I do not have a tidy answer here. The data is real, and it is affecting real people’s careers. But I think framing this as “AI killed junior dev jobs” misses the point. The job is evolving, and the people who evolve with it will end up in a better position, not a worse one.

What do you think?

Related Articles

Testing Paperclip: What I Learned

Paperclip dashboard showing agent orchestration UI

Paperclip recently caught my attention as it allows you to orchestrate teams of specialised AI agents through a beautiful self-hosted web UI, so I had to give it a try.

What Works Well

The concept is solid: specialized agents for different tasks, all tracked through a ticketing system. The UI looks clean and modern. Navigation feels intuitive. Watching my “CEO” agent hire a UI/UX designer, then a CTO, all coordinating through the interface, was entertaining.

For users who want AI agent orchestration without building everything from scratch, Paperclip provides a polished starting point.

Where It Fell Short for Me

I deployed Paperclip using Docker Compose (my preferred approach for managing services). The setup required some debugging—it always does, of course. Permissions, configs of some utilities not where I was expecting to find them. Probably my fault for trying to optimise too early but, really, I was trying to learn. Nothing insurmountable, but it added complexity not needed at the beginning of a project.

More importantly, I noticed my coding credits depleting steadily while Paperclip was running… with nothing actually happening. My team consisted of a CEO and a designer, happily chatting away, checking tickets in and out, burning credits through heartbeat checks and status polls. The UI showed “agents working” but no real output was being produced.

The pretty interface, it turns out, hides the mechanics. For someone who lives in logs and CLI output, this opacity was a little confusing.

The Simpler Alternative

I stepped back and asked: what am I actually trying to achieve here? Agent orchestration. I then investigated how OpenClaw could solve the same problem and realised I could probably achieve most of what I wanted without the extra software and overhead. Like I said, the UI/dashboard is nice but I can’t just sit there and watch the credits slowly disappear.

If you’re already running OpenClaw, n8n, or similar tools? You’re probably already 80% there with infrastructure you understand end-to-end.

What Paperclip Does Differently

Here’s where Paperclip differs from other harnesses. It’s an orchestrator of harnesses, therefore it can orchestrate multiple different AI harnesses as a single team. As Paperclip puts it “if OpenClaw is an employee, Paperclip is the company”. The employees don’t need to be all of the same type, you could have Claude Code, an OpenClaw and an Hermes Agent all working as part of the same team/organisation.

Paperclip on GitHub — check out the project if you’re curious.

All working together, checking out tickets, assigning work to each other. Paperclip lets you mix and match.

For me, that wasn’t the missing piece. But if you’re building a multi-agent system where different agents need different strengths, it’s worth considering.

If You Want to Try It

The concept shows promise. The project has real potential. If you’re curious about AI agent orchestration and want something with a polished UI, give it a spin.

Learn from my mistakes:

  • When deploying with Docker, pin a stable release, not latest
  • Watch your credit usage closely until you understand what it’s doing (maybe set some alerts if you can)
  • Start with a small project to see results quickly
  • Understand that there is some complexity going on which is nicely hidden under the UI

If you, on the other hand, are already using some alternative AI harness and all you want is an easier way to manage an AI team/agents, look more deeply into what your software of choice already supports.

Hope it helps!

Andrea

Related Articles

Sys admin levels explained

Interesting article on the different levels and skill sets of System Administrators. It breaks down what separates a junior sysadmin from a senior one and the kind of knowledge you accumulate along the way.

Whether you are just starting out or have been managing servers for years, it is a good read to reflect on where you are and what you might want to learn next.

Read the full article on Linux Journal

Enjoy!

Hello World!!!

Apparently, this is how it all starts. Hello World!!!

I have been wanting to start this blog for more than a year, but only today I actually made it happen. It is the first post of many, I hope. :-)

What will this blog be about? Open source software, Linux tips, programming, and anything else that crosses my path. Stick around if that sounds interesting to you.

Enjoy!