Is the junior developer dead? A contrarian view from a company that hires juniors on purpose
The popular theory: AI does what the junior used to do, so why hire one? Big companies cut graduate programmes, and forums are full of graduates without a single interview. I will say something contrarian: the junior did…

The popular theory: AI does what the junior used to do, so why hire one? Big companies cut graduate programmes, and forums are full of graduates without a single interview. I will say something contrarian: the junior did not die — the old “junior work” died. And the company that understands the difference gets the best talent of a generation with the least competition.
What actually died
- Two years of writing CRUD forms “to learn”.
- Small bug tickets as a school of patience.
- The senior as the single source of knowledge.
An AI agent now does all of that faster and without boredom. Whoever was really selling “junior hours” is suffering. But that was never the junior’s value; it was only the old method of training them.
What did not die
A good junior does not bring code. They bring questions we stopped asking, energy we no longer have, and new tools they learn in a day while we need a week.
On our team, the fastest to adopt Claude Code and master MCP agents was a 2025 graduate, not a 2015 engineer. They carried no baggage of the old “right way”, so they learned the new way clean.
How we hire juniors today
- Full tools from day one. No “learn without AI first” — that is teaching driving with a horse cart.
- On a real product in week one, with a small complete task (a screen, an integration, a report), and a senior reviewer on every PR.
- We measure reviewing, not typing: do they read what the agent produced? Do they notice the forgotten case? That skill is the job now.
- We teach the domain: why does the salon want this reminder? Why does the investor need eKYC? Understanding cannot be delegated.
- We ask them to write: a weekly summary in Arabic and English of what they did, learned and did not understand.
The arithmetic everyone ignores
A junior + an AI agent + good senior review produces today what a mid-level engineer produced three years ago, at a fraction of the cost, and becomes a real mid-level within one year instead of three. The company that stopped hiring juniors will discover in three years that it has no mid-levels, and will buy them at the highest price in the market.
For the junior reading this
- Do not compete with the agent at typing. Compete at noticing, understanding and verifying.
- Build a small, complete product — with users — before applying for any job.
- Pick a domain and read about it more than about frameworks.
- Learn to say “this is wrong, and here is why” to code written by a model or a manager.
The junior did not die. The junior who waits to be handed boring tasks in order to learn is the one who died. The difference between the two is a decision.


