I was working with a CEO who was looking to hire a CTO.

Not a startup CTO. A serious operator, fifteen years in the role, had taken companies from zero to institutional scale across capital markets, been through full exit cycles including acquisitions, had worked at some of the most technically demanding firms in the industry. The kind of person you spend six months trying to find.

The first interview was run by the CPO.

It was the CPO's first C-level role.

Early in the conversation, the CPO mentioned the company was facing significant challenges around real-time data reconciliation across multi-chain environments, latency issues, on-chain and off-chain state mismatches at institutional volume. The kind of architectural problem that sits right at the boundary of what current infrastructure can handle. Serious, specific, exactly the kind of challenge the CTO was being hired to solve.

The CTO asked the obvious question. The one any serious technical leader asks before committing to a diagnosis: What specifically is breaking down, and why does the problem currently exist at the architecture level?

The CPO moved to the next question.

Not pivoted. Not said "let me bring in the engineering lead for that." but moved to a prepared question about cross-functional stakeholder management. The kind of question you find in thirty seconds on ChatGPT. Because that is where it came from.

The CTO knew immediately. Not that the role was wrong. That the process was.

Three weeks later they joined a competitor. They are now rebuilding exactly the infrastructure the original company claimed it desperately needed.

The founder still does not know why they lost them.

Here is what nobody in executive hiring wants to say out loud.

The behaviours that define an exceptional executive, the counter-questioning, the refusal to give easy answers, the intellectual pushback, the precision before commitment - intensify with experience. A candidate with fifteen years at C-suite level does these things harder, faster, and more instinctively than one with five. They have spent a decade and a half being right in high-stakes environments by gathering information before committing to a position.

And your interview process, run by someone without the depth to meet that behaviour, armed with prepared questions that expect sequential answers, gets worse at assessing people the more exceptional they become.

This is not a coincidence. It is a mechanism.

The better the candidate, the more precisely they trigger every failure mode in your process.

The CPO and the CTO in that room is not an edge case. It is the mechanism in its purest form. A first-time C-level executive, in their first senior role, sitting across from someone who has held that title for fifteen years and built and sold companies along the way. One of them was being assessed in that conversation. It was not the CTO.

They are still building confidence at the executive level. They have prepared for the interview. They give fluent, well-structured answers. They do not challenge the framing of the question. They make the interviewer feel competent.

Your process assesses them adequately. They pass.

Whether they are exceptional is a different question, one your process is not actually equipped to answer. But the interview feels productive, the feedback is positive, and the hire moves forward.

They have enough seniority to know that a bad question deserves a better question back. They begin to probe before answering. They push back on a premise that does not reflect reality. The interviewer starts to feel mild friction.

The feedback includes words like strong but slightly guarded. Or: impressive track record, just want to understand more about culture fit.

Your process is beginning to struggle. The candidate is good enough to challenge it. But not so obviously exceptional that the discomfort gets overridden.

They ask about the specific technical or commercial problem before proposing a solution. They counter a surface-level question with a precise one the interviewer cannot answer. They decline to perform certainty they do not have. They treat the interview as a bilateral assessment, because that is what it is.

The CPO in that room had prepared questions. The CTO had prepared something else entirely, a mental model for diagnosing infrastructure problems, built over fifteen years of being the person responsible when things broke at institutional scale. When the CPO described a technical challenge, the CTO did not hear a conversation topic. They heard an incomplete problem statement that required more information before it could be usefully addressed.

That is not a personality trait. That is fifteen years of engineering judgment operating exactly as it should.

The CPO experienced it as deflection. The feedback was immediate: hard to read, didn't seem fully engaged, not quite the right fit.

What actually happened: the process encountered someone operating at a level it was not built to assess, and it rejected the signal it could not decode.

The specific dynamic of that interview deserves to be examined precisely, because it reveals something the general "bad interviewer" framing misses.

A CPO is not an obviously unqualified interviewer for a CTO. That is what makes this version of the problem so persistent. They share a leadership table. They have a shared language around product and engineering. They have opinions about architecture decisions and technical roadmap. The assumption of qualification seems reasonable to the CPO, to the founder who made the call, possibly even to the CTO walking into the room.

But product depth and engineering depth are not the same thing. And the distance between them becomes visible the moment a serious technical conversation begins.

When the CPO described the data reconciliation challenges, they were not being dishonest. They understood the problem exists. What they could not do and this is the critical gap was answer why it exists at the structural level. That requires a different kind of depth. The kind that comes from having personally designed, broken, and rebuilt the systems in question.

The CTO's counter-question was not a test of the CPO. It was a fifteen-year technical operator doing due diligence on the company in real time. Before accepting a role, they needed to understand whether the problem was a data pipeline issue, an architecture decision made under the wrong constraints, a team capability gap, or something else entirely. The answer changes everything about how you approach it.

When the CPO moved to the next prepared question, two things happened simultaneously.

The CPO felt the discomfort pass and the conversation return to familiar ground.

The CTO concluded that the company did not understand its own most critical technical problem well enough to discuss it with the person they were trying to hire to solve it.

That is a due diligence conclusion. Drawn in real time. In your interview room.

If you cannot articulate the problem to a CTO candidate in an interview, the candidate has a reasonable basis to question whether you will be able to articulate it once they join. And the better the candidate, the more precisely they think, the more experienced they are at diagnosing technical complexity- the faster they reach that conclusion.

When you map the inverse relationship honestly, the conclusion is uncomfortable.

Your process is not selecting for the best executive. It is selecting for the executive who is easiest to interview. Those are not the same person.

The candidate who answers every question fluently, never redirects, never makes the interviewer feel out of their depth, gives clean responses to imprecise questions, they perform well. They progress. They get hired.

What you discover twelve months later is that those same qualities, compliance with the frame, reluctance to push back, comfort giving answers without full information are exactly the qualities that limit them in the role.

The candidate who challenged the question, asked for clarification, refused to give a clean answer to a question that did not have one they failed your process. And they are somewhere else, demonstrating exactly the judgment you needed, for someone who could recognise it.

The mechanism that filtered them out is the same mechanism that should have let them through.

This pattern persists not because people are careless but because the incentives are almost perfectly designed to sustain it.

The person running the interview faces an asymmetric risk.

A bad hire is visible. It costs money, disrupts the team, and somebody gets blamed. A rejected great candidate is invisible. They disappear into the market. Nobody connects the exceptional executive at your competitor eighteen months later to the interview that filtered them out six months before that.

So the rational move, especially for someone new to the C-suite, still building their own credibility, not yet confident enough to sit with a candidate who outperforms them in the room is to reject anyone who creates uncertainty.

The CPO who moved to the next question was not being malicious. They were managing discomfort in the only way available to them. Passing through a candidate who made them feel out of their depth carried a professional risk. Rejecting them carried none because the false negative is never measured.

Now layer the quality gradient onto that incentive structure.

The better the candidate, the more uncertainty they create. The more they push back. The more precisely they probe. The higher the incentive to reject them. The inverse relationship is not accidental. It is baked into the structure of how the decision gets made and who bears the consequences of getting it wrong.

Digital Assets and Market Infrastructure is a small world with a genuinely constrained talent pool.

The executives who can lead institutional revenue, build compliant technology infrastructure at scale, or navigate market structure complexity across multiple jurisdictions while managing a high-performance organisation, globally, you are talking about hundreds of people, not thousands. The ones with fifteen years in the role, real exit experience, and digital asset-specific depth are fewer still.

Every one of them has options. Every one of them is being spoken to by your competitors.

When your process filters out the exceptional and passes through the comfortable, the cost is not just one bad hire. It is the compounding advantage your competitor builds with the person you rejected. The institutional relationships formed. The architecture decisions made correctly from day one. The engineering talent that joins because exceptional technical leadership is already in place.

The Recruitment and Employment Confederation puts the cost of a mis-hire at three times base salary. For a C-suite hire in this sector, that is a seven-figure number before you count anything else.

The false negative has no standard measure. In a market this small and this interconnected, it is arguably larger. And it scales directly with candidate quality because the better the candidate your process rejects, the better the candidate your competitor now has.

The CTO in that story is not an abstraction. They are a named person in a named company doing exactly what the original firm needed done. The founder who lost them is competing against the decision their process made.

Match interviewer depth to candidate depth.

A first-time C-level executive cannot assess a fifteen-year veteran of that role. Not because they are incapable as a person, because they have not yet accumulated the depth of pattern recognition, technical vocabulary, and executive judgment that the conversation requires. Putting them in that room is not their failure. It is a structural decision made above them that sets the process up to invert.

Before the next senior search begins, ask three questions honestly:

Does the person running the first interview have domain depth equal to or greater than the candidate they are assessing?

Have they hired at this level before, not managed the process, but sat in the room and made the call?

Can they answer the counter-question, not deflect from it?

If the answer to any of those is no, you have already identified where your process inverts. The solution is not to coach the interviewer. It is to change who is in the room.

That is exactly why Spearpoint Search and WorkInCrypto exist. Not to fill a vacancy any recruiter can run a process. But to bring the specific pattern recognition that comes from placing senior technical and commercial leadership across Digital Assets and Market Infrastructure through multiple market cycles. The ability to distinguish genuine depth from performed familiarity in a CTO candidate. To know what a great CRO answer sounds like in an institutional digital asset context versus a rehearsed one. To tell the founder, before the interview happens, what signal they should be looking for and what should concern them.

That capability does not come from a job description and a screening call. It accumulates over hundreds of senior conversations, across roles that got it right and roles that did not. It is precisely the depth your internal process lacks when the inversion happens.

Define signal before you go looking for it.

Before anyone speaks to a candidate, the hiring panel should agree on what exceptional actually looks like in this specific role. Not personality descriptors. Specific, observable behaviours tied to real strategic priorities.

When you define signal in advance, counter-questioning becomes evidence of strategic precision rather than evasion. Intellectual pushback becomes confidence rather than arrogance. The refusal to give clean answers to unclear questions becomes the integrity you are hiring for.

You cannot recognise a signal you have not defined. And if you have not defined it, your process defaults to comfort, which scales inversely with candidate quality.

Start measuring what you are missing.

Every company tracks failed hires. Almost none track rejected candidates who subsequently performed well elsewhere. That data makes the inversion visible. Ask consistently: where did the candidates we passed on go? What happened twelve months later?

The answer will be instructive. Probably uncomfortable. Definitely worth knowing.

Thank you for reading - see you next Friday,