November 11, 2026
Source: Xist4 case study, A Major UK Global Bank (London) - Xist4
Sometimes a role is hard to fill because the market is tight.
Sometimes it is hard to fill because the brief is fuzzy, the process drags, and everyone acts surprised when a great candidate disappears like a magician in Canary Wharf.
This one was a bit of both.
A major UK global bank needed a Senior Platform Engineer to strengthen its Azure platform as adoption scaled across the organisation. Sounds straightforward on paper. In reality, it was the kind of role that looks simple until you get close enough to smell the complexity.
The bank had already tried twice. Twice, candidates got to offer stage and were lost. Not over money alone, which is usually where people lazily point the finger. Meanwhile, delivery milestones started to slip, demand kept piling up, and the platform team was left carrying a vacancy that was getting heavier by the week.
That is the hiring problem worth talking about, because this is where a lot of firms get it wrong. They think the challenge is finding talent. Often, the real challenge is being hirable to the talent you say you want.
Let us start with the obvious bit. This was not a standard cloud role.
The remit covered automation, networking, multi-region reliability, and building self-service capability for development teams. That alone narrows the field. Then layer in the need for technical depth, practical delivery experience, and the judgement to operate in a regulated, complex environment.
Now your talent pool is not small. It is properly skinny.
The market does have Azure engineers. What it does not have in abundance is senior engineers who can handle:
Those are not box-ticking skills. That is a blend of architecture, delivery, operational maturity, and political intelligence.
In plain English, the bank did not need someone who had read the menu. It needed someone who had cooked the meal during a fire drill.
The biggest clue in this case was not that the role was difficult. It was that the bank had already reached offer stage twice and still missed.
That changes the diagnosis.
If you cannot attract candidates, your problem is top-of-funnel. If you can get to offer stage and still lose, your problem is deeper. Usually it sits in one of three places:
In this case, the reasons were not purely about money. That matters.
A lot of firms still behave as if senior engineers are vending machines. Insert compensation, receive acceptance. That is not how strong candidates think, especially at this level.
Senior engineers care about whether the role has real ownership. They care about whether they will shape platform patterns or spend twelve months pushing a boulder uphill through committee. They care about whether the process itself reflects a serious, competent employer.
If your recruitment process feels muddled, candidates start to assume the internal environment is muddled too. Fair or not, that is how the game works.
This is the bit leaders sometimes underestimate.
An unfilled senior platform role is not merely a vacancy on an org chart. It creates drag in lots of expensive places at once.
Here, delivery milestones started to slip. The platform team was struggling to keep pace with demand from security, resilience, and environment requests. The gap left by the vacancy was becoming harder to absorb.
That is what a high-impact hiring problem looks like.
The damage tends to spread quietly:
And because this was a bank operating in a regulated environment, the stakes were not just speed. They were resilience, governance, and the ability to scale Azure adoption without wobbling every time demand increased.
When firms leave roles like this open for too long, they are usually not saving money. They are just moving the cost somewhere harder to see.
There is a pattern I see all the time.
A business needs someone exceptional. It writes a broad brief. It stuffs in every technical requirement. It talks vaguely about transformation and impact. Then it wonders why the right people are not biting, or why they go cold later.
Senior engineers are not seduced by fluff. They want to know what they are walking into.
In this case, the hiring manager wanted a recruitment partner who understood what senior engineers actually look for in a role, not just someone who could keyword-match a CV. That says a lot.
The issue was not simply access to candidates. It was understanding candidate motivation well enough to translate the role properly.
For engineers at this level, the compelling parts were things like:
That is a very different conversation from listing tools and hoping for chemistry.
If your pitch to a senior platform engineer sounds like a procurement checklist, you should not be shocked when they treat your offer like one.
Here is my slightly spicy take: your hiring process is not admin. It is your product.
Candidates experience your business through it. And senior candidates are very good at reading between the lines.
This bank had already seen what happens when communication goes quiet and processes move too slowly. Those are not harmless glitches. They are trust killers.
At offer stage especially, silence creates space for doubt. Doubt is where competing opportunities win.
For hard-to-find technical hires, process quality matters because candidates are usually assessing more than one role at once. They are comparing not just pay, but pace, clarity, seriousness, and how well the opportunity has been framed.
If your interview journey feels clunky, candidates start imagining what delivery inside the business will feel like. If scheduling is messy, sign-off is slow, or the story changes halfway through, they make a very reasonable leap: this might be painful on the inside too.
Not exactly the message you want to send when you need someone to improve resilience.
If you are trying to hire a senior infrastructure, cloud, platform, or cyber professional, this case offers a few useful lessons.
First, diagnose the right problem.
If you are losing people at offer stage, stop blaming the market alone. Look at process design, role positioning, communication, and pacing.
Second, sharpen the brief.
Be precise about the technical scope and the real outcomes attached to the role. Great candidates want substance, not hand-waving.
Third, sell what actually matters.
At senior level, ownership and impact often matter as much as package. Sometimes more.
Fourth, audit your process like a candidate would.
Ask yourself:
Fifth, treat delay as risk.
Not inconvenience. Risk.
Because in a competitive market, delay is rarely neutral. It usually benefits someone else.
If you are wrestling with a tough technical hire right now, put these questions to your team:
The answers are usually revealing. Occasionally mildly humiliating. Which, to be fair, is still useful.
This case was never just about a scarce Azure skill set.
It was about what happens when a business needs a high-calibre engineer in a high-stakes environment, but the role, process, and candidate experience are not tight enough to land them first time.
Two failed searches proved the point. The vacancy was not only hard to fill. It was becoming expensive to leave unresolved.
That is the real hiring problem for many firms. Not a total lack of talent, but a gap between the calibre they want and the hiring approach they are using to go and get it.
If you want senior technical people who can operate at scale, in complexity, under pressure, your hiring process needs to do the same.
Anything less, and you are not recruiting. You are hoping. And hope, lovely as it is, has a dreadful track record in infrastructure hiring.