Disclaimer: I am no expert to define what AI will cause for sure in future, or to propose set-in-stone ideas to go beyond the disruption. You can go ahead and skip this article if you were looking for an expert opinion. This is just a rant, or at best, some speculations. Views are personal and do not necessarily reflect the opinions of my employer(s).
I am not addressing the Software Engineer crowd in this article (except for a section towards the end), but my fellow HRs, some of whom might be yet to start to follow the AI realm and how it is going to change the IT industry.
If you’ve been scrolling through your feed lately, you’ve likely felt the shift. It’s not just the quiet in the recruitment corridors; it’s the numbers screaming from the headlines. It was a week ago that Anish Aravind shared some thoughts in an HR WhatsApp group, after his recent acquaintance with Cursor/Opus, as to how disruptive things are going to be. I must agree that a majority of folks in the G&A functions, myself included, have not fully realised the changes that may happen to the Software Engineering field, and by extension to the talent schema in the IT industry, in a couple of years.
Earlier last week, reports surfaced that India’s top 5 IT giants (including TCS, Infosys, and Wipro) added a net total of just 17 employees in the first nine months of this fiscal year. You read that correctly. Seventeen. Compare that to the nearly 18,000 net additions in the same period last year. While it would be a statistical fallacy not to say that, though, it was TCS’s heavy negative headcount growth that resulted in the net growth being just 17, while the values of Infosys, HCL Tech, and Wipro remained higher than the last year. Tech Mahindra added hardly 1/5th of what they added during a similar period in the last financial year.
One could say that this is just playing with data; yes, it is. However, the larger picture is that there were fewer net jobs for our workforce in FY26; perhaps, more people lost their jobs, and many of them could be jobless as I write this. Imagine 5 big pools, and water receding in some of them. Fish in those ponds need water in other ponds to live in, which is clearly not available.

The Writing is on the Wall
We are seeing a convergence of validation from the very top of the tech food chain (who we assume know better than we do). While some of the AI developments/news could be written off as hype or exaggeration, it is becoming more and more evident that AI is, at least, costing many their jobs.
Just days ago, Dario Amodei, CEO of Anthropic, stated at the World Economic Forum that software engineering as we know it – the actual typing of code – could be “automatable” within just 6 to 12 months. He wasn’t speaking in hypotheticals; he noted that his own engineers rarely write code anymore. They edit it. They guide it.
Echoing this, Ryan Dahl, the creator of Node.js (a tool that literally defined modern web development during the 2010s), tweeted a sentiment that sent shivers down many spines: “The era of humans writing code is over.”

I wrote this much to tell my fellow HRs that ‘AI changing software engineering’ is not a hype. While one could argue that vibe coding isn’t equivalent to AI-assisted software engineering, the speed of change in this field is faster than the speed of light.
I Am Not Here to Fear-Monger
Now, before you panic-apply to law school or convince your children to abandon their CS degrees, let me put my HR hat on. This is not the end of the software engineer. This is the end of the ‘typist’ coder. Software Engineering could be a lot more than that (at least for now!).
We have been there before.
In the late 1970s and 80s, the corporate world relied heavily on the Typing Pool. Dedicated professionals spent their entire days physically striking keys on typewriters. When the personal computer and word processors arrived, there was mass hysteria: What will happen to the typists?. There were mass protests against computers (I have a personal opinion on this topic, which is political in nature; hiding it since the purpose of this article is different) since computers could cause a lot of people to lose their then jobs.
Did the job of creating documents disappear? No. It exploded. People evolved. Jobs evolved. Computers made lives easier. The task of typing became trivial, but the value of the work shifted to content, formatting, data analysis, and speed. It made humans more powerful and effective. The typists who adapted became Executive Assistants, Office Managers, and Data Analysts. They stopped worrying about ink ribbons and started worrying about output. It was a technological (r)evolution. We are, in my opinion and that of many others, at a similar juncture in the history of workforce (r)evolution.
The New HR Mandate: From Syntax to Strategy
Ryan Dahl hit the nail on the head in his analysis: That’s not to say SWEs (Software Engineers) don’t have work to do, but writing syntax directly is not it.
From a hiring perspective, the skills test is undergoing a radical upgrade. We are moving away from testing memory and towards testing judgment. A (super basic) example below:
- Yesterday (The Builder): The interview question perhaps was: Write a Python script from scratch to scrape data from this website and save it to a CSV. We paid for the hours spent struggling with HTML parsing libraries and handling exceptions.
- Today (The Architect): The prompt is, “Here is a script generated by AI that scrapes the data. It has a subtle security flaw that exposes our server IP and crashes on large datasets. Find the flaw, fix the logic, and optimise it for a distributed cloud environment.”
We are no longer hiring people to lay the bricks; we are hiring them to inspect the wall and to see how it fits in the entire architecture/strength of the building. The job will shift from production to verification & integration. Read this from Morgan Stanley.

What This Means for Your Career (For Software Engineers)
If you are in IT or any sector feeling the AI ripples, here are my thoughts:
- Stop Competing with the Machine: You cannot out-type an LLM. You cannot out-memorise. Stop trying.
- Start Managing the Machine: The most valuable employees in 2026 will be the ones who can act as “Product Managers” for AI agents. The ability to verify, audit, and architect AI output is the new “coding.”
- Soft Skills are Now Hard Skills: As technical barriers lower, your ability to understand business context, negotiate requirements with stakeholders (including thinking from customers’ points of view), and lead ethical implementation becomes your moat.
The Tech Wreck headlines are scary, yes. But a lot of people will indeed lose jobs in the ripple unless they adapt. The new way is efficient, fast, and inevitably different. Remember: the typewriters were gathering dust, but the office was busier than ever.
What This Means for HRs
Well, this section is not about how HRs can save their jobs because of AI replacing them 😂, but on what they need to focus on as far as the workforce is concerned:
1. Skills are the New Currency
Companies are pivoting from task-based hiring to skill-based workforce development. Roles that work with AI (e.g., prompt engineering, AI governance, ethical oversight, agent orchestration) are expanding rapidly. Try to understand this change and learn how it works.
2. Learning & Upskilling Must Be Strategic
AI automation increases demand for complementary skills, viz., human strengths like complex problem-solving, emotional intelligence, creativity, and cross-disciplinary fluency. You might want to invest in your workforce’s skillsets around this area.
3. Entry Points are Shifting
Fresh grads/junior engineers face the first disruption, but this isn’t a shutdown of opportunity. It’s a shift in how entry-level experience is gained. Organisations must redesign career ladders so new talent can contribute where humans add the most value.
4. Workforce Planning must be Dynamic
Organisations need to balance automation with human potential: using AI to augment roles, not just eliminate them. According to international research, the biggest potential gains come from redesigning workflows, not simply automating tasks. HRBPs have a greater role to play in this aspect, to work with the C-level in effective and meaningful workforce planning.
Learn More about These
To understand the broader economic context of these job numbers, I recommend watching this discussion on the job crisis vs job opportunity debate: 1.2 Billion Youngsters vs 400 Million Jobs (thanks, Jaseen Jamaluddin, for sharing this with me). This video is highly relevant as it features World Bank President Ajay Banga discussing the macro-economic challenge of creating jobs for the next generation in the age of AI, providing the “big picture” behind the hiring slowdowns we are seeing in news headlines.
A few other resources are given at the bottom of this article, besides the references.
References
- Times of India: Tech wreck: Job cuts at TCS drag Big 5 IT companies’ net hiring to 17 in 9 months
- Ryan Dahl (Creator of Node.js): The era of humans writing code is over
- Dario Amodei (CEO, Anthropic): Comments at World Economic Forum, Jan 2026
- Morgan Stanley: How AI Coding Is Creating Jobs
More Resources
- Sundeep Teki: Impact of AI on the 2025 Software Engineering Job Market
- IMF: AI Will Transform the Global Economy. Let’s Make Sure It Benefits Humanity
- Business Insider: DeepMind and Anthropic CEOs: AI is already coming for junior roles at our companies
- The Times of India: Why Nvidia CEO Jensen Huang says engineers “shouldn’t code at all”: Here’s what he thinks matters more
- Your Story: Adopt AI or risk becoming obsolete: GitHub CEO Thomas Dohmke
- GitHub CEO Thomas Dohmke: On Copilot and the Future of Software Development
- An Interesting Discussion on Reddit, about Dahl’s Opinion
Also published on LinkedIn.
Join the HR Community by HRBro®: www.hrbro.com















