Talent Radar · Cybersecurity: 73% of Indian firms still can't find the security talent they need.

Get the report

The AI/ML band split in two

By Kalaiselvi Ponnurangam · 9 min read

Key takeaways

  1. The AI/ML band bifurcated into two populations with different economics and different scarcity, each moving on its own supply.
  2. Traditional ML engineering has held roughly steady on a deep pool, while the applied-GenAI end has pulled away on the back of thin supply the market is racing to build.
  3. Price them as one band and you lose the top and over-pay the bottom: the worst of both errors in a single number. The fix is to price the proof behind the work.
01

One label, two labour markets.

“AI/ML” has become a band that describes two jobs pretending to be one. At one end sits established machine-learning engineering, feature pipelines, model training, MLOps, a deep, well-supplied talent pool whose price has behaved much as it did a year ago. At the other end sits applied generative work: people who've actually shipped retrieval systems, evaluation harnesses and agentic workflows into production, not just prototyped them. That pool is shallow, and the market has begun to price it accordingly.

The result is a band that split. The midpoint you quote now sits in a valley between two populations, describing neither. That's why the number feels simultaneously too high for the candidates you can find and too low for the ones you want.

The distinction matters because the market it sits inside isn't soft. India's Net Employment Outlook was +68% for Q2 2026, the strongest reading since 2008, yet 82% of employers reported difficulty finding the skills they need, according to ManpowerGroup's Employment Outlook Survey. High intent colliding with scarce supply is precisely the condition under which a single band fractures: demand pushes hardest against the thinnest part of the pool, and the price there detaches from the average.

DimensionTraditional ML engineeringApplied GenAI (in production)
The workFeature pipelines, model training, MLOpsRetrieval systems, evaluation harnesses and agentic workflows, shipped into production
Typical backgroundAnalytics and data-science pipeline; degree programmes, bootcamps, on-the-job MLOpsEmerged as a distinct role in roughly the last two years; few practitioners hold three years of it
SupplyDeep and well-supplied; India ranks first globally in AI skill penetration (Nasscom)Limited; the production-GenAI subset is a fraction of the ~16% of IT professionals who are AI-skilled (Deloitte–Nasscom)
Where supply sitsDistributed across major tech hubs and the wider analytics baseConcentrated in a few metros; LinkedIn's Economic Graph identifies Bengaluru as a generative-AI hub
Price behaviourRoughly steady; depth of supply holds the rateRe-pricing upward; Naukri's JobSpeak Index put the senior 20-plus-LPA band up about 16% over the year
Benchmark behaviourPublished market averages track the pool reliablyPublished averages understate the scarce end; the offer is set case by case
What moves the offerFair market rate for the skillDemonstrated production experience: the proof, not the title
Two labour markets under one label. Price them as one band and you lose the top and over-pay the bottom. Full band detail sits in Recruise's Talent Radar and Compensation Index.
02

Why the two ends diverged.

The traditional-ML end has been supplied for a decade. India built that bench through the analytics and data-science boom, and the pipeline that feeds it, degree programmes, bootcamps, on-the-job MLOps, is mature. Depth keeps price honest: when many capable people can do the work, no one candidate can hold a premium for long. That's why this end has stayed close to where it was.

The applied-GenAI end is younger than the pipelines that would supply it. The capability the market now wants, production retrieval, evaluation, agentic systems, barely existed as a job 2 years ago, so almost nobody has 3 years of it. Supply is a lagging function of demand here, and the lag is the whole story. The aggregate signals confirm the direction: the World Economic Forum's Future of Jobs Report 2025 places AI and big data at the very top of the fastest-growing skills to 2030, and LinkedIn's Economic Graph reports the global economy added roughly 1.3 million AI-related jobs in two years, with India (+40%) among the fastest-growing AI-hiring markets. The constraint is proven supply at the production end.

Two adjacent skills, two different clocks. One end is priced by a deep, settled pool; the other by a scramble for the few people who've actually shipped. A single band assumes one clock. There are two.

The pull at the top has a cost in the middle. As the proven-GenAI end runs ahead, the mid-tier of the band gets compressed against a ceiling that's climbing faster than their pay. A strong mid-level engineer sees the offers going to the production-GenAI hires and reads the gap on their own req before you do. That's how a splitting band quietly hollows out the people you were relying on to grow into it.

03

The scarcity is real, and it's measurable.

This isn't a story about a few hot job titles. The gap sits under the whole AI labour market. Deloitte and Nasscom estimate India's AI-talent demand will exceed 1.25 million by 2027, up from roughly 600,000–650,000 in 2022, against a shortfall of about 50% in 2024, with only around 16% of IT professionals AI-skilled. When barely 1 in 6 practitioners can do any AI work, the subset who've run generative systems in production, at scale, is a fraction of a fraction.

Hiring volume is tracking the same asymmetry. Naukri's JobSpeak Index recorded AI/ML roles growing around 45% over the year, far ahead of the roughly 8% for white-collar hiring overall, while the senior 20-plus-LPA band rose about 16%. Postings surge fastest exactly where the proven pool is thinnest, which is the mechanical definition of a market re-pricing at one end. And on the supply side, India ranks first globally in AI skill penetration, per Nasscom's State of Data Science and AI Skills report, a strength that's real but sits mostly at the practitioner layer, not at the production-GenAI edge that scarcity is concentrated in.

India has more AI talent, and more concentrated, than almost anywhere. The tension is that proven production-GenAI talent is scarce inside an otherwise deep market, which is precisely how one band comes to contain two prices.

04

The split hits GCCs first and hardest.

Global capability centres are where this concentrates. F500 India GCCs already hold more than 126,600 AI professionals, roughly 22.5% of the country's AI talent pool, according to ANSR's enterprise-AI workforce release. And LinkedIn's Economic Graph identifies Bengaluru specifically as a hub concentrating generative-AI roles. GCCs aren't dabbling at the edges of this market; they sit at its centre, which means they feel the fracture before anyone else does.

For a GCC building an AI function, the practical consequence is that the same requisition covers two hires the market prices differently. Staff the pipeline and the platform work from the deep pool at a fair rate. Staff the person who owns the generative system in production from a pool that barely exists, and be honest that this is a different negotiation. Run both through one band and the offer letter is wrong twice: generous to the hire you could have sourced cheaply, and short to the one you actually needed to win.

The parent organisation rarely sees this. It reads a single AI/ML budget line and a single market average and assumes they describe each other. They no longer do. The averages the market publishes are true and useless in the same breath: true about the pool, useless about the position.

Scarcity pools at the end the pipeline hasn't caught up to yet, and that's exactly the end a single number hides.

Kalaiselvi Ponnurangam · Practice Head – Talent Consulting & Advisory · Recruise

05

How to tell which market a role sits in.

The diagnosis lives in the proof behind the work. Ask three questions before you set a number. Has this person shipped a generative system into production, or prototyped one? Did they own the failure modes, the evaluation, the drift, the cost of a bad answer at scale, or hand them off? And is the scarce part of the role the modelling, which the deep pool supplies, or the production judgment, which it doesn't?

Where the answers point to pipelines, training and platform work, you're in the traditional-ML market: price it at a fair market rate, because depth of supply will hold that rate for you. Where they point to a live generative system with real users and real consequences, you're in the applied-GenAI market: the premium tracks demonstrated production experience. Two roles that read identically on a job board can belong to different labour markets, and the interview is where you find out which.

06

The fix is to price the proof behind the work.

The centres closing GenAI hires cleanly have quietly abandoned the single band. They ask the sharper question, has this person shipped generative systems into production, at scale, with the failure modes that teaches, and they price the answer. The premium tracks demonstrated production experience.

Do that and two things happen. You stop over-paying for traditional ML capability you can source at a fair market rate, and you free up the headroom to actually close the scarce end. Splitting the band is how you spend the same budget more accurately, and in a market where intent is at a post-2008 high but 4 in 5 employers can't find the skills, per ManpowerGroup, accuracy at the scarce end is the difference between an open req and a closed one.

Frequently Asked Questions

How should we benchmark GenAI roles against traditional ML roles?

Benchmark them as two separate labour markets. Traditional ML engineering, pipelines, training, MLOps, can be priced against a published market average, because it's supplied by a deep pool that holds the rate. Applied production-GenAI can't: the proven pool is thin, so the offer is set case by case against demonstrated production experience. Use the market average for the ML end and a proof-based benchmark for the GenAI end.

Why does a single AI/ML salary band mislead?

A single band averages two populations with different economics, so its midpoint describes neither. Traditional ML sits at one level on deep supply; applied GenAI has pulled away on thin supply. Quote the average and you over-pay the ML hire, who finds it generous, and under-pay the GenAI hire, who has already stopped reading. The number is true about the pool and wrong about the position.

How do we tell which market a specific role sits in?

Ask what proof sits behind the work. Three questions decide it: has the person shipped a generative system into production or only prototyped one; did they own the failure modes, evaluation, drift, the cost of a bad answer at scale, or hand them off; and is the scarce part of the role the modelling, which the deep pool supplies, or the production judgment, which it doesn't. Answers pointing to live systems with real users put the role in the applied-GenAI market.

Why do GCCs feel this split before other employers?

GCCs sit at the centre of India's AI workforce, so they hit the fracture first. F500 India GCCs already hold more than 126,600 AI professionals, roughly 22.5% of the country's AI talent pool, according to ANSR, and LinkedIn's Economic Graph identifies Bengaluru as a generative-AI hub. A single AI requisition at a GCC routinely covers both a deep-pool platform hire and a scarce production-GenAI hire, which one band prices wrong twice.

The Mandate Desk

One hiring pattern worth knowing, every ten days.

The Mandate Desk is our read on the senior GCC talent market — one signal that moved, the read behind it, and one thing worth doing. Written from live placement data.

Work with us

Have a senior seat to fill?

Tell us the mandate — the role, the level, the market. We’ll come back with what the market is really doing on it, and how we’d run the search.