What Does India’s Annual State of Hiring Report Reveal?

National employability in India has climbed to 56.35%, up from 54.81% a year ago, and 60% of the roles our clients are filling right now are replacements, not net new headcount. Those two numbers alone say more about the state of the Indian tech labour market than most 40 page decks we get asked to summarise for HR leadership. This piece is that walkthrough, built from the report data plus what we're seeing across 500+ live and closed mandates in our own pipeline.

Why Does India's Hiring Market Look Different This Year?

The headline shift in the latest data is that Indian hiring has moved from expansion to precision. Overall hiring intent in India sits at 11%, up from 9.75%. More roles are open, but the profile of who's hiring for what has changed sharply. AI adoption inside Indian employers has reached 44% implementation, and 72% of employers report genuine difficulty filling roles in AI, cloud, and data specifically. Not because candidates don't exist, but because the specific combination of skills, seniority, and delivery maturity employers now want is thin.

We've felt this directly. A mandate for five mid level backend engineers in Bengaluru used to close in three to four weeks. Today, the same mandate, same seniority band, same stack, takes five to seven weeks, because 50% of live postings in the Indian tech market are now asking for senior candidates, and only around 6% are entry level. The market has quietly become a senior heavy hiring market, and clients who built their timelines around fresher heavy sourcing get caught off guard.

Global Capability Centers (GCC) are a big part of why. India now hosts more than 1,850 GCCs employing close to two million professionals, with the sector's overall workforce expected to cross two million employees and its market value approaching $100 billion by 2030. When a Fortune 500 GCC opens a 200 person cloud engineering pod in Hyderabad, it doesn't just hire 200 people. It pulls senior engineers out of the mid market and startup pool across the city for the next two quarters, and every recruiter with an active mandate in that skill set feels the ripple.

Agentic AI tools have added a new layer this cycle too. Employers aren't just asking whether a candidate has used a large language model. They're asking whether that candidate can supervise an AI agent inside a real delivery pipeline, catch its errors, and own the outcome. That single shift in interview questions is one of the fastest moving signals we track, faster than any annual report can capture.

Where Is India's Talent Actually Concentrated, City by City and Skill by Skill?

The report data and our own placement history agree on this: Bengaluru, Hyderabad, and Pune remain the deepest pools for AI, cloud, and platform engineering, but the growth story is Tier 2 cities. Roughly 32% of hiring now happens in Tier 2 locations and another 20% in Tier 3, with cities like Indore, Coimbatore, Vadodara, and Kochi building genuine specialist depth. Indore in analytics, Coimbatore in engineering and IT services, Kochi in digital marketing and support functions. Senior professionals are moving back to these cities too. A Tier 2 hiring hub isn't a compromise anymore, it's a deliberate sourcing strategy for clients who want strong mid to senior talent without Bengaluru's compensation inflation.

On skills, three things stand out. First, demand for AI and data roles has grown roughly 30% year on year, concentrated in Tier 1 metros but spreading fast. Second, cloud platform preference has quietly shifted: in live postings, Azure now edges out AWS in raw mention count, which surprises most clients who assume AWS is still the default. Third, data analyst demand is running at roughly 3.5 times data scientist demand. The "sexiest job" narrative from a few years back hasn't matched what employers are actually posting.

What Indian engineers bring to the table is strong: deep hands on cloud certification density, genuine comfort working async across an 8 to 12 hour offset, and increasingly, practical GenAI tool fluency, since over 90% of Indian tech employees report already working with generative AI tools in some form. What they typically lack for our international clients isn't technical depth, it's exposure to production incident ownership and client facing communication under pressure.

We test for this specifically in our technical rounds by asking candidates to walk us through a real production issue they owned end to end, not a whiteboard problem. A mid size German fintech client we work with told us this single change in our screening process cut their post hire onboarding friction by roughly a third.

What Does India's Annual State of Hiring Report Mean for Your Compliance Setup in India?

India's four consolidated Labour Codes, the Code on Wages 2019, the Industrial Relations Code 2020, the Code on Social Security 2020, and the Occupational Safety, Health and Working Conditions Code 2020, replacing 29 older central labour statutes, with Central Rules. If your compliance documentation still references the old Payment of Gratuity Act or the Contract Labour Act by name, it's out of date, and that matters more now than it has in the past decade.

The change that catches clients out most often is the new wage definition: basic pay plus dearness allowance must now equal at least 50% of total CTC. Companies that historically structured offers with a low basic salary and heavy allowances to reduce PF and gratuity contributions now have to restructure, and if you're paying contractors or fixed term hires through an EOR, your EOR partner should already be running these numbers, not asking you to catch the discrepancy.

The second change worth knowing is that gratuity is now payable to fixed term contract employees on a pro rata basis from day one, with no five year minimum service requirement. That single change affects every contract to hire structure we run for clients, because it removes what used to be a cost advantage of short fixed term contracts.

This is where the contract versus full time hiring decision actually gets made. Full time employment still wins when a role is core to delivery, needs long term ownership, and benefits from institutional knowledge staying in house. Contract and fixed term hiring still make sense for defined scope work, seasonal surges, or when a client wants to test a market before committing to a permanent team. What's changed is that contract hiring is no longer the automatic cost saver it used to be, since pro rata gratuity now applies from the first day of the contract. Clients need to run both models against the new statutory math before defaulting to one or the other.

State level Shops and Establishments Acts still run in parallel with the central Codes, and because labour sits on India's Concurrent List, a team in Bengaluru and a team in Mumbai can technically face different working hour and registration rules under the same company. The most common mistake we see international companies make is assuming one compliance template covers every Indian city they hire in.

Not sure where your current India hiring plan stands against these changes? Talk to our team and we'll walk through your compliance and hiring setup together.

What Are the 10 Numbers Every HR Leader Should Know From This Year's Report?

Every figure below is grounded in the latest published hiring and skills data.

Metric	Current Figure	What It Means for You
National employability rate	56.35% (up from 54.81%)	More screenable candidates per role, but competition for the top quartile is sharper
Overall hiring intent	11% (up from 9.75%)	More roles open industry wide; expect longer sourcing queues on senior reqs
Roles that are replacements, not new headcount	60%	Budget for backfill speed, not just net growth
AI adoption among employers	44% implementation	AI fluency is now a baseline screening filter, not a differentiator
Employers reporting difficulty filling AI, cloud, or data roles	72%	Build in longer lead time for these specific skill sets
Share of live postings asking for senior candidates	Around 50%	Entry level pipelines won't fill mid to senior mandates
Entry level share of live tech postings	Around 6%	Fresher hiring needs a dedicated, separate strategy
Hiring share in Tier 2 cities	32%	Tier 2 sourcing is now a cost and speed advantage, not a fallback
GCC workforce in India	Approaching 2 million	Expect more senior talent competition in metro hubs
India's share of the global AI talent pool	16% (heading to 1.25M specialists)	India remains the deepest AI bench globally, but it's getting expensive fast

Read this table before you set your next hiring timeline, not after your first requisition stalls.

How Do We Actually Use This Report in Live Hiring Mandates?

At AnjuSmriti Global, we rebuild our internal sourcing playbook against this report within the first two weeks of publication, because the skill demand shifts it captures show up in client mandates almost immediately afterward. Our standard timeline for a mid to senior technical role, from kickoff call to signed offer, currently runs 25 to 35 days for Tier 1 city hires and 20 to 28 days for Tier 2, both slightly longer than the 18 to 24 day benchmark we quoted clients a couple of cycles ago, directly because of the senior heavy market this data confirms.

A recent example: a mid size US based SaaS company, roughly 400 employees globally, came to us needing eight data engineers for a GCC style pod in Pune, with a hard deadline tied to a board reported delivery date. Our first candidate slate, sourced the way we would have a couple of years ago, came back thin. Strong SQL and Python candidates, but very few with production Spark or Airflow experience at the seniority the client needed, which matched exactly what the report shows about senior demand outpacing supply in data engineering specifically.

We nearly lost two weeks re scoping the search before we adjusted our sourcing radius to include Pune adjacent Tier 2 talent and reworked our technical screen to weight pipeline ownership experience over tool specific certifications. We closed all eight roles in 31 days against a 35 day deadline, and the client's own engineering lead told us the two Tier 2 hires ended up outperforming their Tier 1 counterparts in the first quarter. That near miss taught us to build the report's city and seniority data into our sourcing brief on day one now, not after the first candidate slate underperforms.

This is also where the full time versus contract question resurfaces in practice. For a board reported delivery date like the one above, most clients default to full time hires because they need people who'll still be there past the deadline. But for one off migrations, proof of concept work, or a six month capacity spike, a contract or fixed term structure gets you the same skill set faster, since contract candidates are often more open to short notice starts than someone leaving a permanent role. The right call depends on whether the work outlives the deadline, not just on cost.

What Do This Year's Numbers Mean for Your Hiring Budget?

Real INR numbers, based on current market data across our active mandates for backend and cloud engineering talent, the two role families most clients ask us to benchmark:

• Mid level (4 to 6 years): 18 to 28 lakh per annum CTC in Bengaluru/Hyderabad; 14 to 22 lakh in Tier 2 cities like Pune, Indore, or Coimbatore

• Senior (7 to 10 years): 32 to 48 lakh per annum CTC in Tier 1 metros; 26 to 38 lakh in Tier 2 cities

• Lead/Architect (10+ years): 55 to 85 lakh per annum CTC in Tier 1 metros; 45 to 65 lakh in Tier 2 cities

For a client hiring five mid level and two senior engineers through an EOR structure, total annual cost typically runs employer CTC plus employer PF and gratuity contributions (roughly 13 to 15% on top of CTC under the new wage definition), plus EOR service fees (commonly 8 to 15% of CTC depending on scope), plus our agency placement fee. Even after all of that, total cost of ownership for an India based team in this band typically lands at 45 to 60% of the equivalent US or Western European fully loaded cost.

This is the math AnjuSmriti Global runs for every client scoping an India based team, and it's a gap most clients reinvest directly into faster iteration cycles: more senior hires per budget dollar, dedicated QA capacity, or a second Tier 2 hiring hub rather than a single concentrated Tier 1 team.

Contract and fixed term structures carry the new pro rata gratuity obligation described above, which we now build into every cost projection we send clients, since it typically adds 3 to 5% to what used to be a "gratuity free" short term contract cost. It's still often the right structure for defined scope work, but it's no longer the automatic budget shortcut it used to be, and any hiring plan that treats contract and full time cost the same way as they did a few years back will be underbudgeted from day one.

Conclusion

Over the next 12 to 18 months, expect the senior talent squeeze in AI, cloud, and data roles to tighten further before it loosens. GCC expansion alone is projected to push India's specialised talent workforce past two million by 2028, and that pace of absorption isn't slowing. What we're seeing in live mandates right now backs this up: clients who used to open a single req and wait are increasingly asking us to build a 90 day pipeline instead, sourcing ahead of need rather than reacting to it. Reading India's annual state of hiring report closely isn't an academic exercise for us. It's the difference between a hiring plan that survives contact with the market and one that doesn't.

If your India hiring plan was built on older timelines or older compliance assumptions, now is the time to revisit it.

Talk to our team and we'll walk you through what the current data means for your specific roles and cities.

---

Interesting Reads:

How Do Gig Worker Rules Apply to Contractors in India?

What Roles and Costs Go Into Building an AI Team in India?

What Red Flags Should You Watch for When Vetting an India EOR?

FAQs

1.Does the report account for contract and gig workers, or only permanent employees?

Yes, the latest edition is notably more gig and contract aware than earlier editions, reflecting that project based hiring grew roughly 38% in the past year and the gig and freelance workforce is projected to reach 23.5 million workers by 2030. The Social Security Code now formally recognises gig and platform workers for social security purposes for the first time, though state level contribution rates and scheme mechanics are still being finalised.

2.Why is senior hiring outpacing entry level hiring so sharply?

Roughly half of all live Indian tech postings ask for senior candidates, while only about 6% are tagged entry level, an eight to one ratio in favour of experience. Two forces drive this: GCCs and enterprise clients scaling delivery teams that need day one productivity, and companies tightening graduate intake in favour of roles with faster ROI. Fresher hiring now needs a dedicated pipeline and timeline separate from your core technical hiring plan, since treating them as one funnel is the most common planning mistake we see.

3.Why has Azure moved ahead of AWS in Indian job postings?

Azure edges out AWS in raw mention count across live Indian tech postings, which surprises most Western clients who assume AWS remains dominant. Our read, based on client conversations, is that this tracks enterprise and GCC hiring specifically: large Indian GCCs tied to Microsoft aligned parent organisations, BFSI clients with existing Azure infrastructure, and government adjacent contracts have scaled hiring faster than pure play startups.

4.How does the new 50% wage rule affect what I pay an Indian contractor through an EOR?

Under the new uniform wage definition, basic pay plus dearness allowance must equal at least 50% of total CTC, which affects how PF and gratuity contributions are calculated even when your total offered CTC stays the same. In practice, this usually means a slightly higher statutory contribution base than under the old structure, since many employers previously kept basic salary artificially low. A properly run India payroll outsourcing partner should already be restructuring pay slips to this definition without requiring you to renegotiate the offer.

5.Which cities are the strongest alternatives to Bengaluru for senior technical hiring?

Hyderabad and Pune remain the closest Tier 1 alternatives with comparable senior talent density, while Indore, Coimbatore, and Vadodara are the Tier 2 cities showing the fastest growth in gig and specialist availability. Pune in particular has strong overlap with Bengaluru on cloud and data engineering seniority bands at a meaningfully lower compensation baseline. We increasingly recommend clients open Tier 2 searches in parallel with Tier 1 rather than sequentially, since sequential search costs two to three extra weeks on a senior mandate.

6.How does gratuity now apply to short fixed term contracts?

Gratuity is now payable to fixed term employees on a pro rata basis from day one of employment, removing the previous five year minimum service threshold entirely. This directly affects the cost math on short fixed term or project based contracts, which used to be structurally cheaper partly because gratuity rarely applied. We now build pro rata gratuity into every fixed term cost estimate we send clients, typically adding 3 to 5% to what the contract would have cost under the old rules.

7.Is India still cost competitive for AI hiring specifically?

India currently holds about 16% of the global AI talent pool, with specialist numbers projected to reach 1.25 million by 2027, which keeps India structurally ahead on raw AI talent depth. But 72% of employers report real difficulty filling AI, cloud, and data roles, which tells you the easy hiring era for AI talent in India is over. Clients building AI engineering teams should expect to pay closer to senior band rates even for mid level AI specialist roles right now.

8.How should a Finance Head use this report to set next year's India hiring budget?

Beyond headcount, the report's most budget relevant data points are the 60% replacement hiring share, the 11% overall hiring intent, and the new wage definition rules affecting PF and gratuity math. Together these tell you that budget needs to account for backfill velocity, not just growth, and that statutory contribution costs per hire are structurally higher than they were a couple of years back. We typically recommend Finance Heads build a 10 to 15% contingency into per hire cost projections to absorb the combined effect of senior heavy hiring and the revised wage definition base.