The Science of Hiring: what AI changed about the senior bench
A working GCC head on which decisions they now hand to AI, which they kept, and how the team changed.
Draft. Figures marked like this are illustrative and pending verification against Recruise placement data & Sachith sign-off before publication.
Key takeaways
- In this episode, a working GCC head walks through which decisions they now hand to AI — and, more tellingly, which they deliberately kept.
- The team didn’t shrink the way the headlines predicted. It changed shape — fewer producers, more people who own quality and direction.
- The clearest lesson: AI raised the bar for the senior bench, because the work that’s left is the work that needs judgment.
What our guest handed to AI — and what they wouldn’t.
In this episode of The Science of Hiring, we sit down with a GCC head running a sizeable IT centre and ask the question most panels skip: not what AI can do, but what they actually let it do. The honest answer is a line drawn carefully. Drafting, first-pass triage, and the repetitive scaffolding of the work went to the model. The decisions with downstream consequence — who to trust, what to ship, where to escalate — stayed with people, on purpose.
What makes the conversation useful is that the line wasn’t drawn by policy. It was drawn by experience, one workflow at a time, and our guest is candid about the places they got it wrong before they got it right. That trial-and-error is the part no vendor deck captures, and it’s the spine of the episode.
“The most useful thing our guest said wasn’t what they automated. It was what they refused to — and why that refusal changed who they needed to hire.”
Sachith Rai · MD & Founder, Recruise
The team changed shape, not size.
The expectation going in was that AI would thin the team. What actually happened, our guest explains, is that it changed the team’s composition. The junior-heavy production layer got leaner, but the demand for people who could set direction, own quality, and hold the standard the parent expects went up. The centre didn’t need fewer people so much as a different distribution of seniority.
We dig into what that meant for hiring in practice: harder searches at the senior end, a re-think of what an entry-level path even looks like when the model does the entry-level work, and a bench that has to be stronger because there’s less routine work to grow into. It’s a more demanding org to staff, not an easier one.
Listen for the hiring implications.
The through-line of the episode is that AI didn’t lower the skill bar in this centre — it raised it, and concentrated it. When the routine work is handled, what’s left is the judgment, and judgment is expensive to hire and slow to grow. Our guest is frank that they underhired at the senior level early and spent the following year catching up.
If you run a GCC or plan its hiring, this is the conversation to sit with. It’s a practitioner describing, without hype, how a real team moved through the change — and where the hiring plan needed to move first for the rest to work.
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.
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.