Talent Radar · Cybersecurity — India needs 250K+ security pros by 2028; supply covers about a third.

Get the report
Perspectives

Stop hiring for the org chart you have. Hire for the one AI is drawing.

Most senior reqs describe a role that’s already changing shape. Sachith Rai on what the market gets wrong about future-proofing a leadership bench.

By Sachith Rai 6 min read
A colleague presenting to a coworker at a table

Draft. Figures marked like this are illustrative and pending verification against Recruise placement data & Sachith sign-off before publication.

The argument

  1. Most senior reqs describe the org chart you have, not the one AI is already redrawing underneath it.
  2. Future-proofing a bench isn’t about hiring ‘AI people’ — it’s about hiring leaders who can operate a role whose shape is still moving.
  3. Write the req for the seat in eighteen months, and you’ll disqualify some of today’s obvious candidates — which is the point.
01

The req is a photograph of a role that’s moving.

Open most senior job descriptions in a data or AI-adjacent function and you’re reading a careful description of how the role works today — the team it manages, the process it owns, the deliverables it’s accountable for. The trouble is that AI is redrawing exactly those things while the req sits in the market. The team that role manages is about to be smaller and more senior. The process it owns is about to be half-automated. You’re hiring against a snapshot of a role that will look materially different by the time the person is a year in.

This isn’t a call to chase every shiny signal. It’s a warning that the most confident, most specific reqs — the ones that read as rigorous because they nail today’s role in detail — are often the most brittle. They select precisely for fitness to a job that’s dissolving.

“A job description is a bet on what the role will be. Most are a bet that it’ll stay exactly as it is — which, in any function AI is touching, is the one thing we can be sure it won’t.”

Sachith Rai · MD & Founder, Recruise

02

Future-proofing is a trait, not a skill list.

The market’s reflex is to future-proof by bolting AI keywords onto the req — hire someone who’s ‘used the tools,’ who lists the right frameworks. That’s hiring for today’s tooling, which will be obsolete faster than the role. The thing actually worth selecting for is a disposition: the ability to lead a function whose definition keeps shifting, to redesign the work as the tools change, to hold judgement steady while the mechanics move.

That leader looks different on paper. They may not have the deepest command of the current stack, because they’ve spent their career adapting to three previous ones. What they have is a track record of walking into a role, watching it change under them, and reshaping it rather than defending its old form. In a moving org chart, that’s worth more than mastery of the version that’s about to expire.

03

Write the req for the seat in eighteen months.

The practical discipline is to draft the role not as it is but as you honestly expect it to be a year and a half out — smaller team, higher leverage, more ambiguity, more of the leader’s value in framing problems rather than running known processes. Then hire against that. It’s uncomfortable, because it will disqualify candidates who are perfect for today’s version and unremarkable against tomorrow’s. That discomfort is the signal you’re doing it right.

Hiring for the org chart you have feels safe and precise. It just quietly locks your leadership bench to a structure AI is dismantling. The centres that will still have the right leaders in place when the dust settles are the ones drawing the future chart now — and staffing that one, not the one on the wall today.

The Signal · Weekly

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.