Habr: AI is displacing juniors and putting the engineering talent pipeline at risk

On Habr, a column was published with an uncomfortable but important thesis: generative AI may strike not so much at current seniors, but at the channel through which new ones emerge. If newcomers lose the layer of simple tasks, the industry risks losing its own system of reproducing engineers.

The tribal core of the industry

The author proposes an unexpected but understandable metaphor: the IT industry resembles a tribal economy, where quality rests not on the entire mass of specialists at once, but on a core of practices, skills, and people who transmit culture further. This core includes not only strong developers, but also code review, engineering discipline, understanding of architecture, and the habit of taking responsibility for the consequences of decisions. While this system is renewed, the market steadily grows new mid-level and senior engineers.

Juniors in such a scheme are not just cheap labor and not a temporary expense item. They are the layer from which tech leads, architects, and team leads eventually grow. It is on simple, sometimes mundane tasks that a newcomer first encounters other people's code, errors, production limitations, and team requirements.

Without this path of entry, knowledge remains theory and does not transform into engineering thinking, and the person does not learn to speak with more experienced colleagues in their language.

Why AI is dangerous

The problem, according to the author, is that AI automates not the apex of the profession, but its educational foundation. It makes business sense to hand a typical task to an agent if it does it faster and doesn't require time from senior colleagues for training. But this very layer used to serve as a training ground for beginning specialists. If machines take away the routine entirely, a junior loses not only tasks, but also the environment in which they mature as an engineer. First of all, skills disappear that used to be developed on simple tasks:

• fixing minor bugs and dealing with the consequences of their decisions
• reading other people's code and understanding how the system is structured
• feedback on code review and understanding engineering standards
• gradual increase in responsibility without immediate pressure from complex architecture
• the skill to verify, not just write or generate code

In the short term, replacing a junior with AI looks like savings. In the long term—like eating through personnel reserves. Strong engineers don't appear on the market ready-made and in the needed quantity. They grow within the profession when they're given the right to make mistakes, rewrite, figure things out, and gradually take on more responsibility. If this path disappears, the industry still lives on old reserves for some time, and then suddenly faces a shortage of people who can maintain complex systems.

How to rebuild the entry

The author doesn't propose to "cancel AI" and return to the old model where newcomers were kept on routine for years. Rather, the thesis is that the old path of entry is already broken and will have to be rebuilt from scratch. A new junior must learn not only to write code, but also to read it, verify it, criticize it, understand fragile parts of the system, and catch errors that generation brings.

Otherwise, they will remain a prompt operator, not an engineer. Practical measures are also formulated quite down-to-earth: more real internships instead of formal ones, more mentorship within companies, and more incentives for employers who invest in developing beginning specialists. There's also the idea of more transparently separating products where AI was merely a tool from products where human engineering review is minimized.

This is not a ban on automation, but an attempt to honestly show the level of responsibility for results and give customers a clear risk marker.

What this means

The Habr column captures an important shift in the conversation about AI: the question is no longer just about who it will replace today, but about who will become a strong engineer tomorrow. For the market, this is a signal that savings on juniors can turn into a more expensive personnel crisis in a few years, when demand for mature engineers remains high, but the internal school of their training starts to decline.