DOP 351: The Developer Job Market in the Age of AI

Episode 351

Show Notes

#351: Entry-level tech jobs are down 67% since 2022. Junior developer roles are down 40 to 50%. The instinct is to blame AI and call it unprecedented, but the layoffs are not the new part. The boom-bust cycle has happened before – dot-com to dot-bomb, the 2020 hiring spree to the 2022 correction, now this. The new part is that the thing replacing the bottom of the ladder is not a cheaper human in another country. It is an agent that takes instruction and ships code overnight.

Here is the uncomfortable reframe. A junior developer is told what to do, does not change the architecture, does not make decisions, and produces better work the more detail you give them. Replace the word junior with agent and the description does not change. That is the whole problem. The traditional path from junior to senior assumed five years of grunt work would teach you the things grunt work teaches. The grunt work has a new owner now, and nobody knows what the new on-ramp looks like.

Seniors are not safe either. If you have spent 30 years writing pretty code and you have already started rejecting the idea that an agent can do it better, history is not on your side. The same people who refused to embrace cloud and containers are the people who will refuse this – and the SSH-key-maker on the team that took a week to provision a key is not pivoting to AI either. Two types of employees. The ones you can replace in five minutes and the ones whose departure feels like a loss. Only one type thrives in this cycle.

So what actually works? Capacity to learn over experience. Specific knowledge over generic knowledge – if every developer on the internet can do what you do, the model trained on the internet can too. The job is becoming managing a team of agents the way a manager manages people: figure out what should be done, how, and when, then check on the team and work with individuals. The hiring test that still works after all these years is the one where the candidate switches to the browser and Googles. That is the person who can adapt. That is the person who survives this market.

Frequently Asked Questions

How is AI changing the developer job market?

Darin Pope frames DevOps Paradox episode 351 around two markets running at once: companies paying data scientists 750,000 dollars or more, while Amazon lays off 16,000 people and Block sheds several thousand more. Viktor Farcic reads it as a boom and bust cycle the industry has been through before, comparing it to the dot-com collapse. What is genuinely different this time, he says, is the speed and the width of the scope.

Why are junior developer roles disappearing?

Darin Pope cites figures on DevOps Paradox episode 351 putting entry-level tech positions down 67 percent since 2022 and junior developer roles down 40 to 50 percent. Viktor Farcic’s explanation is uncomfortable: a junior is typically told what to do rather than deciding, and produces better work the more precisely they are instructed. Replace the word junior with agent, he argues, and the description does not change.

Are senior developers safer than juniors from AI?

Viktor Farcic is not convinced on DevOps Paradox episode 351. He argues history suggests seniors will be the ones rejecting the change, insisting no AI reviews code or connects to a machine as well as they can. His test runs on different lines: if your work rests on knowledge many people have, and models were trained on that public material, you are replaceable. Specific knowledge gets complemented rather than replaced.

What skills keep a developer employable?

Darin Pope’s list on DevOps Paradox episode 351 is system design, orchestration, security and governance, domain expertise, communication, and judgment. He adds that a decade at one company without understanding what the business does is its own kind of risk. Viktor Farcic offers a blunter test for anyone with more than ten years behind them: if you have already changed what you do and how you do it several times, you are fine.

How should a developer start using AI coding tools?

Darin Pope’s suggestion on DevOps Paradox episode 351 is to spend twenty dollars for a month, pick something non-trivial, and build it. Viktor Farcic adds the warning that matters: do not judge the tools by the results of the first week. He compares it to a first week with Java, which does not produce code serving a million concurrent users, and says giving up after a week is the actual mistake.

What should you look for when hiring a developer now?

Viktor Farcic says on DevOps Paradox episode 351 that he has always valued capacity to learn over specific experience, and that this counts for more now rather than less. He tells the story of a junior hiring test where candidates worked on a company laptop that had a browser open alongside the editor. The candidate who switched to the browser and searched for an answer got the job.

What is the DevOps Paradox podcast?

DevOps Paradox is a weekly podcast co-hosted by Darin Pope and Viktor Farcic, covering DevOps, platform engineering, and modern software delivery. Episode 351, “The Developer Job Market in the Age of AI,” works through why entry-level roles are vanishing, whether seniors are any safer, and which skills still hold value. Every episode page carries audio, video, and a full transcript.

Topics

Share and Download

Hosts

Viktor Farcic

Viktor Farcic

Viktor Farcic is a member of the Google Developer Experts and Docker Captains groups, and published author.

His big passions are DevOps, Containers, Kubernetes, Microservices, Continuous Integration, Delivery and Deployment (CI/CD) and Test-Driven Development (TDD).

He often speaks at community gatherings and conferences.

He has published DevOps Paradox and Test-Driven Java Development.

His random thoughts and tutorials can be found in his blog The DevOps Toolkit.