For most of the last decade, hiring a CTO at a Gulf bank came down to one question, asked in different forms across a handful of interviews: what have you shipped? Boards wanted a track record — a core migration delivered, a mobile platform launched, a legacy system decommissioned without an outage that made the news. The CV that answered that question well got the offer.
That question hasn't gone away. But it's no longer the one that decides the outcome. In the searches we're currently running, it's usually settled early — most shortlisted candidates can point to something real they've built. What separates who gets the offer is a different set of questions entirely, and they're being asked by people who didn't used to be in the room.
Who's actually in the interview now
Five years ago, a CTO search was largely an IT and executive committee conversation. Today, on the mandates we're placing, it's common for the final interview panel to include someone from risk, someone from the board's technology or audit committee, and — increasingly — someone whose role is specifically about AI governance. That composition tells you what the job has actually become.
The CTOs getting hired now aren't being tested on whether they can deliver a platform. They're being tested on whether the board can trust them with the decisions that come after it's delivered.
Three things boards are screening for now
Risk fluency, not just delivery fluency. A board member on one recent panel put it directly: "I don't need someone to tell me the migration will work. I need someone who can tell me, honestly, what happens to our regulatory position if it doesn't." Candidates who default to delivery-confidence language, without acknowledging what could go wrong and how it's controlled for, are increasingly screened out at this stage — not because they lack ability, but because they haven't shown the judgment the seat now requires.
A credible position on AI oversight. Every board we work with is asking some version of the same question: who is accountable when a model makes a decision that affects a customer or a regulatory filing? CTOs are no longer expected to be AI specialists, but they are expected to have a clear, considered answer for how AI-driven systems get governed inside their organisation — not a slide, an actual position they can defend under questioning.
Vendor and ecosystem management at board level. Fewer banks are building everything in-house. That means the CTO's real job increasingly involves managing an ecosystem of vendors, cloud providers, and fintech partners — and being able to explain to a board, in commercial terms, why that ecosystem is structured the way it is.
What this means for how you position yourself
If your CTO narrative is still built primarily around delivery — "I shipped X, I migrated Y" — it's worth rebuilding it before your next conversation. The strongest candidates we're seeing lead with governance and judgment, and use delivery track record as supporting evidence, not the headline.
That's a genuine shift in what the room wants to hear, not just a change in interview style. Boards aren't asking these questions because it's fashionable. They're asking because the accountability for a CTO's decisions now sits closer to the boardroom than it used to.