GCC estate grew, GCC hiring fell 28%
India's GCC estate keeps compounding — 2,117 centres, 3,728 sites, 2.36 million professionals and $98.4 billion in FY2026 revenue, up from $64.6 billion two years earlier, per NASSCOM-Zinnov. But the same research shows GCC hiring volumes falling roughly 28% between the first and second halves of FY2026, with redeployment and AI-assisted capability building replacing net recruitment. The article argues the operational scaffolding has not kept pace: monitoring stacks, alert thresholds and dependency maps are still inherited from headquarters, while India teams now own uptime outright. As expansion pushes into tier-2 cities, one campus becomes a primary site plus several thinner ones, multiplying non-uniform failure modes. Key signal: NASSCOM-Zinnov data cited in the piece puts India at 2,117 GCCs across 3,728 sites with 2.36 million employees and $98.4 billion FY2026 revenue — while GCC hiring volumes fell roughly 28% between H1 and H2 FY2026. For hiring leaders, this matters because this is the clearest articulation yet of the GCC paradox: headcount growth is decelerating while scope and accountability keep expanding. For CHROs and GCC heads, it means the next phase of value is not more engineers but differently skilled ones — operations, observability, SRE and platform talent who can own services end to end rather than execute tickets. It also reframes tier-2 expansion: cheaper real estate and talent come with thinner vendor benches and less mature connectivity, so operational risk rises precisely where cost pressure pushes you. TA leaders planning FY2027 should expect requisition mix to shift from volume engineering toward operations and reliability roles, even as total hiring stays flat. Teksands view: The GCC story everyone tells is scale. The story that matters for hiring leaders is the 28% volume drop against a still-growing estate — scope per engineer is rising, and the profiles that absorb that scope (operations, SRE, observability, platform) are not the ones most GCC TA teams are built to hire at volume. Tier-2 expansion makes it sharper: thinner vendor benches, less mature connectivity, more non-uniform failure modes. Treat operations and reliability hiring as a strategic pipeline, not a backfill category.
Key fact
NASSCOM-Zinnov data cited in the piece puts India at 2,117 GCCs across 3,728 sites with 2.36 million employees and $98.4 billion FY2026 revenue — while GCC hiring volumes fell roughly 28% between H1 and H2 FY2026.
Why it matters
This is the clearest articulation yet of the GCC paradox: headcount growth is decelerating while scope and accountability keep expanding. For CHROs and GCC heads, it means the next phase of value is not more engineers but differently skilled ones — operations, observability, SRE and platform talent who can own services end to end rather than execute tickets. It also reframes tier-2 expansion: cheaper real estate and talent come with thinner vendor benches and less mature connectivity, so operational risk rises precisely where cost pressure pushes you. TA leaders planning FY2027 should expect requisition mix to shift from volume engineering toward operations and reliability roles, even as total hiring stays flat.
The Teksands point of view
The GCC story everyone tells is scale. The story that matters for hiring leaders is the 28% volume drop against a still-growing estate — scope per engineer is rising, and the profiles that absorb that scope (operations, SRE, observability, platform) are not the ones most GCC TA teams are built to hire at volume. Tier-2 expansion makes it sharper: thinner vendor benches, less mature connectivity, more non-uniform failure modes. Treat operations and reliability hiring as a strategic pipeline, not a backfill category.
Got a tech role that's refusing to close?
Send us the JD. We'll tell you whether the problem is talent supply, compensation, location, process - or the JD itself.
