Hiring the Scarce 20%: AI, Cyber, Cloud and Data Talent for India GCCs

The talent shortage in India’s GCCs is narrower and sharper than it looks. Generalist software engineers, analysts and operations staff are available at scale in every major city. The hard part is the first ten people in AI and ML, IAM and cloud security, platform engineering and data, the roles that new global mandates depend on. Plan for those separately, or they will set the pace of the whole centre.

Key Takeaways

• The shortage is bifurcated. Volume roles fill; scarce roles stall the mandate.
• Time-to-fill is only half the delay. Notice periods push start dates out further, especially for senior hires.
• Scarce roles cluster in a few skill families: AI and ML, cybersecurity (especially IAM and PAM), cloud and platform, and data engineering.
• Bridge, don’t wait. A specialist pod can deliver against the roadmap while permanent hiring catches up, then transfer.
• Design for transfer from day one. Build-operate-transfer works when documentation, runbooks and hiring plans are part of the contract.

What the data says

The demand side is not in doubt. 1,200+ Indian GCCs now have AI and ML capabilities, and India’s GCCs hold about 28% of global GCC AI talent (Zinnov-Dell, September 2026). Supply is tighter. Across all Indian employers, not just GCCs, Quess Corp estimated a 51% demand-supply gap for AI talent in 2025, with GCCs accounting for about 23% of AI hiring.

The effect shows up in hiring speed. In a 2026 survey of GCC leaders, 58% of GCCs said they take more than 45 days to fill critical roles (Ceipal and People Matters). That is time to an accepted offer, before the candidate serves notice at their current employer.

Meanwhile the volume pipeline is deep. Telangana alone approved 1,16,877 undergraduate engineering seats for 2025-26, 83,622 of them in computer science and allied branches. Pune has about 550,000 IT and ITeS professionals, roughly 210,000 of them in GCCs (KPMG citing UnearthInsight). The constraint is not the number of engineers. It is the number of engineers who have already built and run production ML platforms, privileged-access programmes or multi-account cloud estates.

Why scarce roles miss their dates

Three effects compound:

1. Competition for the same people. A new GCC with an unfamiliar brand in India is bidding against established technology employers and older GCCs for a small pool of experienced specialists.
2. Notice periods. Experienced Indian technology professionals commonly serve notice periods measured in months. An offer accepted on day 50 can mean a start date after day 100.
3. Sequencing. The first AI or security leader usually has to be in place before their team can be hired, so delays cascade down the organisation.

The result is predictable: the mandate HQ approved for India starts a quarter or two late, while the generalist teams around it are fully staffed and waiting.

Plan scarce roles as a separate track

Treat scarce hiring as its own programme, with its own owner and its own risk register.

Skill family	Typical roles	Why it is scarce	Common bridge
AI and ML	ML engineers, MLOps, applied AI, evaluation engineers	Few people have run models and agents in production	AI platform pod
Cybersecurity	IAM and PAM engineers, cloud security, detection engineering	HQ control frameworks require experience the market is short of	Security engineering pod
Cloud and platform	Landing-zone architects, platform and SRE engineers	Needed before everyone else can work	Platform engineering pod
Data	Senior data engineers, data architects	Data platforms gate analytics and AI mandates	Data platform pod

For each scarce role, record the date the business needs the person productive, work backwards through onboarding, notice period and time-to-offer, and compare the result with today. Any role where that maths fails needs a bridge.

How a specialist pod bridges the gap

A pod is not a group of contractors added to your backlog. It is a small team with a lead, a defined outcome and a delivery plan: for example a 12-person AI platform team, an IAM and cloud-security bench or a 15-person data-platform pod. It delivers against your roadmap now, and its work is built to move into your captive.

Pods work best when three things are agreed up front:

• The outcome: a landing zone, an ML platform, an IAM rollout, not an hour count.
• The transfer path: timing, terms and what transfers (code, documentation, runbooks and, where people choose to move, the engineers themselves).
• The hiring plan alongside: the pod lead helps define and interview for the permanent roles that will take over.

Build-operate-transfer is already mainstream

Several of the centres in our India GCC Tracker use partner-built models from the start. Western Union’s AI-led Hyderabad GCC is being built with HCLTech on a build-operate-transfer basis. Carlsberg’s first IT GCC runs on a build-operate model with GSPANN, and Citizens Financial Group’s Hyderabad centre is built and operated by Cognizant. The lesson is not that every centre should outsource its build. It is that temporary partner capacity, designed to transfer, is a normal part of how GCCs ramp. A narrower pod for only the scarce skills keeps more of the centre captive from day one.

Make the rest of hiring boring

Scarce roles need special treatment precisely so that volume hiring can be run as a well-oiled process:

• Employer brand before job ads. Unknown foreign brands need an India story before they compete for engineers.
• RPO and background verification sized for the peak month, not the average.
• Campus partnerships in the catchment for graduate roles, which lower cost per hire and attrition.
• Compensation benchmarks by role and city, refreshed as the market moves.

Plan your own bridge

The free Scarce-Talent Bridge Planner shows which of your critical roles are likely to land after the date you need them, once notice periods are included, and sizes the pod that would cover the gap. Our specialist pods are delivered by Scutiger engineers using agentic delivery, with transfer terms agreed before they start. Our team has set up and scaled GCCs for global enterprises, so the pod plan and the permanent hiring plan are designed together.