AI changes the tasks first, the titles last
The role looks the same on the org chart. The work inside it doesn’t. Reading that gap early is the whole game.
Draft. Figures marked like this are illustrative and pending verification against Recruise placement data & Sachith sign-off before publication.
Key takeaways
- The role looks identical on the org chart. The work inside it doesn’t — AI changes the tasks long before it changes the title.
- Because the title is stable, the shift is easy to miss — you keep hiring the old profile for the new job.
- Reading that gap early, before the title catches up, is the whole game in staffing an AI-affected function.
The title is the last thing to move.
When AI enters an IT function, the sequence is almost always the same. First the tasks change — what the person spends their day doing quietly re-composes around what the model now handles. Then, much later, the title changes to describe the new reality. In between, there’s a stretch where the job on the org chart and the job being done have drifted apart, and nobody has written it down.
That stretch is where hiring goes wrong. The req still carries the old title and the old skills list, so you keep sourcing the profile that fit the job as it was. The candidate arrives competent for a role that no longer quite exists and short on the judgment the changed work actually needs — and the mismatch doesn’t surface until they’re in the seat.
“The title is the last thing to change and the first thing you hire against. That’s the whole error. Read the tasks, not the title, and you’re hiring for the job that exists.”
Sachith Rai · MD & Founder, Recruise
Read the task composition, not the label.
The way past it is unglamorous but reliable: look at the actual composition of the work before you write the req. What in this role is now assisted by a model, and what does that free the person to spend their time on instead? Usually the answer is that the routine share shrinks and the judgment share grows — which means the profile you want is more senior in instinct than the title implies, even if the title hasn’t moved.
This is a habit more than a technique. The centres that do it well interrogate the work behind every req in an AI-affected function rather than trusting the title to still mean what it meant a year ago. It costs a conversation up front and saves a mis-hire that’s expensive to unwind later.
The edge is in seeing it early.
Everyone eventually updates the title. The advantage belongs to whoever reads the task change before the title does and hires against the real job first. That head start compounds: you staff the changed work while the rest of the market is still hiring against the label, and your team is fit for the function as it actually operates rather than as the chart describes it.
So the discipline is simple to state and easy to skip. Before the next req in an AI-touched role, ask what the work has become, not what it’s still called. Get that right consistently and you’re always hiring one step ahead of the org chart — which, in a function AI is reshaping, is exactly where you want to be.
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.