The roles AI is quietly creating inside GCCs
Not the ones in the headlines. The senior seats that appear when a function moves from doing the work to governing it.
Draft. Figures marked like this are illustrative and pending verification against Recruise placement data & Sachith sign-off before publication.
Key takeaways
- The AI headlines are about jobs disappearing. The quieter story inside GCCs is about senior seats appearing that didn’t have a name eighteen months ago.
- These roles surface at the moment a function shifts from doing the work to governing it — setting the guardrails, owning the model risk, deciding what stays human.
- They are hard to fill because they don’t map to an existing ladder — you’re hiring for judgment and standing, not a tool stack.
The roles worth watching aren’t the ones being cut.
Every quarter the coverage is about the same thing: which jobs AI is taking. Inside the GCCs we recruit for, the more consequential movement is in the opposite direction. As a function automates the routine layer of its work, it discovers it now needs someone to govern that layer — and that someone sits higher, not lower, than the roles being displaced.
We’ve watched a handful of these seats appear across a dozen centres in the last year. A data-quality owner who exists because a model now depends on the input. An evaluation lead who owns whether the assisted output is good enough to ship. A governance seat that didn’t report to anyone because the org chart hadn’t caught up to the fact that it needed to exist.
“The jobs AI removes are visible on day one. The jobs it creates are senior, unnamed, and six months late to the org chart. Those are the ones our clients underhire for.”
Sachith Rai · MD & Founder, Recruise
Governing work is a different hire from producing it.
When a team moves from executing a task to overseeing a system that executes it, the skill that matters changes underneath the title. The producer optimises for output. The governor optimises for where the output can be trusted, where it must be checked, and who carries the consequence when it’s wrong. Those are not the same person, and they rarely come from the same shortlist.
This is why so many of these seats stay open. Centres try to promote the strongest producer into the governance role and find the instinct doesn’t transfer. The candidate who fits is usually someone who has held accountability for a system at scale before — and knowing where to find that person, rather than the best engineer, is the whole search.
Hire for the seat the function is about to need.
The centres getting ahead of this aren’t waiting for the role to become obvious. They read where their own automation is heading, name the governance seat before the gap becomes painful, and hire into it while there’s still time to onboard properly rather than under fire.
If your AI programme is maturing and your senior structure looks identical to eighteen months ago, that gap is the signal. The org chart lags the work — and the firms that close the lag early are the ones that don’t stall at the point where governance was supposed to already exist.
One pattern worth knowing, every week.
The Signal is our weekly read on the senior GCC talent market — one chart, one pattern, no noise. Written from live placement data.
More from Recruise Insights.
Most GCC AI pilots stall at the same place. Here's why.
We've mapped GenAI rollouts across the GCCs we work with. The failure mode is consistent — and it isn't the technology.
GenAI hires aren't the same as AI/ML hires. Most JDs miss it.
Three distinct profiles are being confused for one. The mis-hire rate is predictable. The fix is upstream of recruitment.
Hiring for judgment when everyone can use the tools
When the skill is commodity, the differentiator is knowing where to apply it. How to assess for that.