How the Talent Shortage Is Reshaping GCC Strategy
For twenty years the primary reason to build a capability centre was cost. That has changed, and the change is more consequential than it first appears. For a growing number of companies the reason is now access: they cannot hire the senior engineers they need in their home market at any price they are willing to pay, within any timeframe that keeps the roadmap alive.
This is not a rebranding of the same decision. A centre built for cost and a centre built for access are structured differently, staffed differently, measured differently and scoped differently. Building one while thinking about the other is a reliable way to get a centre that satisfies nobody.
This guide covers what changed, why the shortage sits where it does, and what a centre built for access looks like in practice.
Key points
- Access to capability has replaced cost as the primary driver for many companies
- The shortage is concentrated at senior level, not across engineering generally
- A centre built for access must be senior heavy, which inverts the cost logic
- The roles must offer ownership, because senior candidates select on the work
- Retention becomes the central operational concern rather than recruitment cost
What actually changed
Three things happened close together. Demand for senior engineering rose sharply as software moved deeper into every industry. Remote work removed the geographic constraint that had previously kept local markets somewhat insulated, which meant every company could suddenly compete for the same people. And the supply of genuinely senior engineers, meaning people with a decade or more of production experience, could not respond, because seniority is produced by time rather than by training.
The result is that in many markets a senior engineering role now stays open for two or three quarters. The effective cost of that is not the salary you did not pay; it is the roadmap that did not move, and that cost is usually much larger and almost never measured.
Once leadership recognises that arithmetic, the capability centre conversation changes character. It stops being a question about margin and becomes a question about whether the plan is executable at all.
The shortage is narrower than it looks
Treating this as a general engineering shortage leads to the wrong response. There is no shortage of capable engineers in absolute terms, and there is a growing surplus at the junior end as tooling makes entry level work easier to automate.
The constraint sits specifically at the level of people who can own a system: make architectural decisions, absorb ambiguity, operate what they build and be trusted without supervision. That population grows only as fast as engineers accumulate a decade of experience, and no amount of hiring intensity changes it.
This matters because it determines the shape of the response. Hiring more people does not help if the missing capability is judgement. Hiring five mid level engineers in place of one senior engineer usually makes the situation worse, because they generate work that requires the judgement you do not have.
Relative supply pressure by seniority band
Illustrative representation of supply pressure rather than measured research. The pattern is the point: the constraint is concentrated at the top and eases sharply below it.
What changes when access replaces cost
A centre built for access is a different design from a centre built for cost, on almost every dimension. The table below sets out where they diverge, because the divergence shows up as a series of specific decisions rather than as a change in stated intent.
| Decision | Centre built for cost | Centre built for access |
|---|---|---|
| Primary objective | Reduce cost of known work | Acquire capability that cannot be hired locally |
| Seniority mix | Minimised to lower average cost | Deliberately heavy, because seniority is the point |
| Size | Large enough to amortise fixed costs | As small as the capability requires |
| Work assigned | Well specified, transferable | Ambiguous, requiring judgement |
| Success measure | Cost per FTE | Whether the roadmap moves |
| Retention priority | Moderate; roles are replaceable | Critical; each departure is a capability loss |
| Role design | Defined scope, clear instructions | Ownership of outcomes |
| Competition | Other offshore providers | Every company hiring the same seniority band |
The last row is the one most often missed. A centre built for access competes for candidates against every well funded company in that market, not against other outsourcing options.
Why the roles have to be real
If you are building a centre to access senior talent, you are competing for exactly the people who have the most options. They are not evaluating your offer against unemployment; they are evaluating it against several other offers, most of which are also well funded.
Senior engineers in every market select on the work. Specifically they ask what they will own, whether they will be able to make decisions, whether the problems are interesting, and whether they will be treated as capable adults or as remote capacity. A role that fails those tests will not attract the people the centre exists to attract, regardless of compensation.
This is the most common reason access oriented centres underperform. The company recognises it needs seniority, budgets for seniority, and then scopes roles as offshore support because that is the familiar template. The strongest candidates identify this in the first interview and decline.
A named system or outcome the person will own, not a stream of work. This is the single most effective differentiator in a competitive senior market.
What they can decide without asking. Senior candidates ask this directly and interpret a vague answer as a negative answer.
Genuine technical or domain difficulty. Senior engineers leave for interesting work more often than they leave for money.
Who else is here and what have they done. The first senior hire is the hardest, and every subsequent one gets easier if the first was strong.
Retention becomes the main operational concern
In a cost oriented centre, attrition is a recruitment expense. In an access oriented centre it is a capability loss, and the two require entirely different responses.
If the centre exists because you could not hire this capability elsewhere, then losing a senior engineer means losing capability you cannot readily replace, along with the accumulated context that made them productive. The cost of that departure is far larger than the recruitment expense, and it is rarely accounted for as such.
The practical implication is that scope design becomes a retention strategy. Senior engineers leave when the work stops being interesting, which usually means ownership was withdrawn, scope narrowed, or decisions quietly moved back onshore. Retention at this level is mostly a governance question, not a compensation question.
- Track regretted attrition among senior engineers separately from total attrition
- Treat withdrawn ownership as a retention risk, because it is the most common trigger
- Ensure the work continues to grow in scope rather than plateauing after year one
- Keep the senior population large enough that individuals are not isolated
- Review whether decision authority has quietly migrated back onshore
How to build for access
The sequence differs from a cost oriented build, and the differences are concentrated at the start.
Identify the specific capability gap
Not headcount. Which decisions cannot currently be made, and which systems cannot be owned. This determines everything downstream.
Size to the capability, not to a cost threshold
Access oriented centres are usually small. There is no reason to reach a headcount that fixed cost amortisation would once have demanded.
Design the role before the market search
What will they own, what can they decide, why is the problem interesting. Doing this after the search starts means competing on compensation alone.
Hire the first senior person carefully
The first hire sets the ceiling for everyone after them and is your strongest recruiting asset. It is worth waiting for.
Protect the scope
The centre exists because of the capability. Narrowing the work to fit a delivery need will lose the people it was built to attract.
Access and cost require different centres,If you cannot hire the seniority you need, a centre designed to minimise cost per head will not solve the problem. It will reproduce it in another location, at a slightly lower price.
Frequently asked questions
Is this just a justification for offshore hiring?
It is a description of a change in why companies do it. The distinction matters practically: a centre built to reduce cost and a centre built to access capability differ in seniority mix, size, scope and measurement. Building one while intending the other is the source of most disappointment.
Does the talent shortage affect all engineering roles?
No, and treating it as general leads to the wrong response. Junior supply is comfortable and increasing; mid level is adequate. The constraint is concentrated at senior and above, where the population grows only as fast as engineers accumulate experience.
Why not just pay more locally?
Because compensation competition redistributes a fixed population rather than increasing it. If every company in a market raises offers, the same engineers move between the same companies at higher cost and the roles stay hard to fill. Widening the geography is the only lever that changes supply.
Will AI tooling resolve the shortage?
It reduces demand for junior and routine work substantially, and has already done so. It does not produce senior judgement, and by increasing the number of systems that reach production it arguably increases demand for the people who can keep them working.
How small can an access oriented centre be?
As small as the capability requires, which is often six to fifteen people. The old headcount thresholds existed because fixed costs demanded amortisation, and those costs have fallen enough that a small senior team is now viable.
What is the biggest mistake in building for access?
Scoping the roles as offshore support while budgeting for senior salaries. The strongest candidates identify this immediately and decline, and the centre ends up with people who accepted a role the best candidates rejected.
How do we compete for senior talent in a market where we have no brand?
On the work. A specific, interesting problem with genuine ownership competes effectively against a recognisable brand offering a narrow role. The first senior hire is the hardest; after that the team itself becomes the recruiting argument.
Does this change how we should measure the centre?
Yes. Cost per FTE is close to meaningless for a centre built for access, because it was never the objective. Measure whether the roadmap moves, whether systems are owned locally, and whether senior people stay.
Sources & further reading
- NASSCOM — https://nasscom.in/
- Deloitte — https://www.deloitte.com/
- McKinsey & Company — https://www.mckinsey.com/
- Everest Group — https://www.everestgrp.com/
Build where the seniority actually is
Hexominds builds capability centres designed around access to senior talent, with the ownership those candidates select for.