DEV Community

Shitij Bhatnagar
Shitij Bhatnagar

Posted on

Do we need Junior developers?

Do we need junior developers, freshers, early aspirants in Software Industry (and any other industry)? my take - Yes.

Doesn't the above take seem contrary to the prevalent news about AI taking over junior or senior jobs, why so much narrative about every day work going away to robots (like shown in the movie 'I Robot' released in 2005) - when retail/daily Robotics is at least a decade away and Artificial Intelligence (particularly Agentic AI) is still shaping up?

There is some truth (early strides like use of chatbots for IT support), but lot of hype to aid capitalism, regrettably; still the news circulates on and professionals get effected because taking this narrative path helps justify role reductions or reorgs or strategizing, which leads to cost savings, then leads to higher share prices or opportunity budget that can be deployed elsewhere - just an inference.

However, even if there is some truth, does it mean the industry does not require junior engineers/professionals? This has never been true, nor would it ever be, in my humble opinion.

Entry level / junior professionals - you are the next generation, the next force that pushes the economic pedestal forward for your country and industry, you have the energy and perspective, you have the internet and lot of free resources to upskill and you can understand industry trends well (or learn).. simply said, you are smart, vocal, capable and well armed.

First some historical reference:

During the economic downturn events (2000 dot com burst, 2008-09 financial crisis, Covid-19), for freshers/juniors (even seniors), I cannot deny that struggle was there, I am aware of many technologists to moved to marketing/data processing/front office/other roles to keep the house running; due to lay offs many professionals had to stay out of job for few months, but then eventually (even after an year), people got the relevant jobs - may not be in big companies, but in small ones, midsized ones, working as interns/trainees, faculties, part-time engineers and then eventually landing the kind of jobs they wanted or aspired to. It took time, but it happened; career toll? it took some months or year out of a career trajectory, but few months or year out of a 35-40 year career, can be caught up - looking at the long term.

Note: majority of working people I have known over the past 25 years are still employed, but they did need to pick up new skills or move into different roles

To the point about AI/automation impacting need for junior engineers:

Before AI, let's talk about previous automation spikes and what they did to IT jobs and need for juniors. Innovations like software test automation, robotic process automation (RPA), AI chatbots in support/customer facing phases forced professionals to pick new skills rather than eliminate their jobs - for majority of the roles (but some were effected e.g. reduction in IT support personnel head count or manual software testers asked to become test engineers etc.); again, only the professionals who did not adapt to new skills or aligned with new realities (incl. to increased productivity or performance expectations) were effected - and that too not on day one, but over a tenure. The need for entry level / juniors did not go away, junior hiring got delayed or recruitment numbers got reduced temporarily but definitely picked up later - let's call this the 'delay' effect.

AI is another form of automation that is much smarter than its predecessors. The first impact or theme, at least at this stage with Generative AI (Chat GPT, Gemini, Claude and others) is that with these chat tools at hand, people need to be a lot more productive and should be multipliers. So, if you see, the business demands are what? -> 'increased productivity or performance expectations'. I find this as a common theme repeated over and over again irrespective of the automation spike at play.

Another theme that AI has actually expedited (it was already growing) is a shift towards leaner organization hierarchy, increasing technical skills, currently trending as the need for more engineering skills and reduction in facilitation oriented roles. Whether we like this or not, this is happening and we must prepare/adapt. So, what could juniors/entry level staff do? Do more side / live projects to be job ready.

Yet another theme that will start taking shape is when Agentic AI becomes production ready, it could further impact facilitator roles in companies if the privacy and security concerns of Agentic AI are taken care of. But who would configure Agentic AI? of course, developers. And what could facilitator oriented roles do? Mesh more business or other skills relevant to the job or industry

AI will impact different IT companies in different ways, depending on their business models, segregation of roles, customer profiles, funding and more. But some things are less likely to change, in my humble opinion, like:

  • Need for engineers who are productive and multipliers (right attitude)
  • Need for engineers to oversee output of AI tools, this would be a technical function
  • Need for project managers to manage projects and programmes
  • Need for production support staff to man IT systems and tackle incidents/problems (if I were an IT production manager, I would not trust a solution from AI - at least at this point, I need to talk to a man)
  • Need for engineers to mentor other engineers, otherwise, the human connect will vanish
  • Need for Engineering leaders, not just talkers but, those who can walk the talk
  • Need for multiple skills - degrees would matter less, skills would matter more. And, this is not a new theme, its been there since a few decades at least in IT

What I would have done if I were a junior developer or fresher today

Being an entry level / junior is never easy in an unsettling economic or industry stage, like in IT. Yet, if I were there today, this is what I would have done:

1) Talked to experienced engineers (find on LinkedIn, Medium, dev.to etc.), taken their guidance for realistic projects and done practice
2) Checked college/university alumni and sought support (kept ego side)
3) Volunteered for freelance projects
4) Got into any IT role if possible (trainee, intern, tester, engineer, support) in any IT organization / get foot in the door
5) Created a smart CV covering projects, skills, volunteering, education
6) Done Network Network Network - one of the lifelines of career
7) Focused on learning and professional certification
8) Taken career guidance from experienced IT folks

At the end

I hope the articles resonates with someone, I would be more than happy to hear any criticism or views that would widen my own and everyone's understanding and to help each other. And if you ask me about AI impact, I believe the senior IT professionals are at a much higher risk than juniors.

Top comments (8)

Collapse
 
mcondon profile image
Micah

Despite the massive industry changes brought by AI, ultimately software development relies on quite a bit of human judgement. The best judgement often (but not always) comes from senior+ engineers, with years of hard won experience and learning. And where do these senior engineers come from? I'm pretty sure most of us started out as junior engineers.

Though hiring trends don't currently favor junior engineers, the need for experienced engineers is not going to disappear, and all experienced engineers start as inexperienced engineers

Collapse
 
shitij_bhatnagar_b6d1be72 profile image
Shitij Bhatnagar

Very well said, thanks for your comments. A world with just senior engineers is not sustainable, we shall retire or do business or something else, we need succession planning, continuity and a healthy workforce.

Collapse
 
gurpreet_bakshi_503a2918a profile image
Gurpreet Bakshi

Short answer: Yes—absolutely.
Long answer: we need them, but we need to use them correctly.

  • If organizations stop hiring juniors, they create a future skill vacuum.

  • Juniors question assumptions, adopt new tools faster, and are not biased by “we’ve always done it this way.”

  • Growing people internally leads to better retention and stronger ownership than hiring only laterally.

  • The real q to ask should not be
    “Do we need junior developers?”
    But
    “Do we have a system that can grow people?”
    If the answer is no, the problem isn’t juniors—it’s engineering culture and planning.

Collapse
 
shitij_bhatnagar_b6d1be72 profile image
Shitij Bhatnagar

Thanks for your comments :-)

Collapse
 
flowerwine profile image
wine flower

I agree with most of the points in the article, but it overlooks one crucial reality: the future simply won't require the same volume of junior developers we see today. The anxiety junior developers are feeling is entirely normal, and unfortunately, it’s not likely to improve—this shift is inevitable.

To put it into perspective, consider the evolution of manual labor. We used to dig trenches with shovels, but today we use excavators. The job of digging hasn't disappeared, but whereas it once took hundreds of people to complete a project, it now only takes a few.

The advancement of AI will never lead to the complete disappearance of developers, including those at the junior level. However, applications that previously required hundreds of people and years of work can now be completed by dozens of people in a matter of months. Development just isn't as labor-intensive as it used to be. That is the true source of anxiety for junior developers—not the fear that their roles will vanish entirely, but the fact that the industry no longer needs them in such massive numbers.

This text was translated by AI.

Collapse
 
shitij_bhatnagar_b6d1be72 profile image
Shitij Bhatnagar

Thanks for sharing your view, appreciate it. Picking with the last line of your comment 'This text was translated by AI', this is what AI should be doing for us - help in communication even if we speak different languages, yes, for a meaningful goal.

Now, the statement 'applications that previously required hundreds of people and years of work can now be completed by dozens of people in a matter of months' - this is only a worry in my view without a basis, otherwise, what is a real life example of this (apart from proof of concepts that are 95% throw away), what has been proven thus far and that too bug free, without security bias, without privacy lapses? I am yet to see a pragmatic, real life impact that can be generalized (and Agentic AI is growing, but again everything takes time). In real life, IT systems are built and maintained by humans; yes, some part of the system build (or test) can be done faster with AI's aid (and I shall come to that shortly), but high quality maintenance, releases, handing production incident, software extensions and more would always be done by humans - largely, AI's share in that will grow slowly only, if it does even.

Different industries, different type of IT companies could have unequal impacts of AI, so it is not possible to generalize anything, we need to see as it evolves - and this is not the case of bullock cart being replaced by automobiles.

The main anxiety about less hiring of junior developers - is something I cannot deny fully (there are unknowns) but I am unwilling to give in to one of the previous statements (on which I commented) that sound like 'weapons of mass destruction', we need to be pragmatic.

We must also not forget that, juniors armed with AI tools (productivity), with high quality side projects completed, internships, mentorship, strong fundamentals - are a win win in long term. Some seniors instead may more time to adapt to new trends (age, mental blocks - hey seniors - no offence mates :-)), but juniors would be quick to catch up, adapt and if I were a hiring manager, I would go for a mix of juniors and seniors - we need both in the industry.

And yes, if we need to be worried about something more than AI, it should be Robotics that can impact masses hugely, in my humble opinion.

Thanks once again for your comment (and sorry for longish response).

Collapse
 
hussaincode profile image
Mohammad Saddan Hussain

very informative article in this wave of AI.

Collapse
 
shitij_bhatnagar_b6d1be72 profile image
Shitij Bhatnagar

Thanks for your kind words Saddan :-)