15.11.26
Why Experienced Data Leaders Are Choosing Contract Work Over Permanent Leadership Roles
We speak to dozens of senior data professionals every month, and a pattern keeps surfacing that most permanent hiring strategies haven't caught up with yet. Experienced engineers, architects, and even people sitting in permanent director-level roles are actively steering away from permanent leadership positions and back towards outside-IR35 contract work. This isn't a handful of outliers. It's a visible, recurring theme in our candidate conversations, and it has direct implications for any CTO or HR leader trying to build a Data or AI leadership team right now.
The instinct among hiring teams is often to assume contractors are contracting because they can't land a permanent role, or because they're holding out for a better offer. Our conversations tell a different story. Senior candidates with ten, fifteen, twenty years of experience are choosing contract work deliberately, for reasons that have nothing to do with employability and everything to do with how they want to structure their working life and their finances. Understanding those reasons is the difference between designing a hiring strategy that fights the market and one that works with it.
The Candidates Driving This Shift Aren't Who You'd Expect
These are not junior engineers testing the waters. One candidate we spoke with has around 20 years of data engineering experience and is comfortable quoting day rates from standard data engineering work right up to interim Head of Data and director-level positions, saying plainly that "so long as what they're asking matches how much they're paying, I'm happy to take a look at any role". This is someone who could credibly be hired into a permanent leadership seat, yet he's structured his entire working life around outside contracts.

Similarly, a data architect with experience spanning finance, public sector, and automotive sectors including Jaguar Land Rover was actively pursuing data architect contract roles the moment his current contract wrapped, telling us he would prefer to stay outside IR35 "but I am realistic" about the trade-offs. Another candidate, a backend developer with experience at an American firm earning £650 a day outside IR35 for three years, explicitly avoids inside-IR35 work altogether, saying it "wouldn't work out" with his tax position. These aren't candidates priced out of permanent roles. They're candidates who have run the numbers and chosen a different structure.
Why Senior Talent Is Opting Out of Permanent Leadership
The clearest signal in our conversations is that contract work functions as a funding mechanism for other ventures, not just a career choice. One contractor told us directly that he can "only really do outside contracts because I need to keep the money in the business" to fund a sports data platform he's building and back-end software work he's doing for sports bars in Liverpool. For this candidate, a permanent leadership role would actually work against his broader goals, since it would tie up the time and income flexibility he needs to run his own ventures.

Flexibility and control over monitoring and earning structure also come up repeatedly. One candidate, with roughly ten years of contracting experience, told us he wanted to "come back into the contract world because contract world can give my needs what I'm looking in the career" and specifically cited the ability to control his own "monitoring point of view," contrasting it with the regular but less adaptable nature of a permanent salary. Another candidate transitioning from permanent work described the appeal in similar terms: the earnings potential, the variety of organisations he'd get to work with, and crucially, the ability to "bank the work," take a few weeks off when needed, and then "start working again and try something new".
Financial Flexibility, Not Just Financial Upside
It's worth being precise about what "financial flexibility" means to these candidates, because it's not simply about chasing a higher headline rate. One candidate benchmarking a potential move into contracting had already modeled the numbers before even speaking with us, landing on a day rate that would "account for the risk" of leaving a stable permanent salary while still making "good money". That's a candidate thinking like a business owner about risk-adjusted return, not an employee comparing one salary figure to another.
Others are weighing geographic and lifestyle flexibility into the same calculation. One backend engineer, based outside London, told us he'd consider funding an Airbnb out of a higher day rate if a role required on-site presence, doing the maths on whether the rate justified the commute and accommodation cost. This is a level of financial modeling that permanent salary negotiations rarely surface, and it tells hiring leaders something important: these candidates are evaluating opportunities as a cost-benefit equation, not a status upgrade.
What This Means for Permanent Leadership Hiring Strategies
Employers designing permanent leadership hiring strategies for Data and AI programmes need to treat this as a supply-side constraint, not a recruitment inconvenience. When a candidate with director-level data engineering experience is comfortable quoting rates "right the way up to like interim, head of data", that's a direct signal that the permanent leadership market is competing against a parallel, often more attractive, contracting market for the exact same skill set.

This has a few concrete implications. First, assuming that experienced candidates will naturally gravitate to permanent roles for stability is increasingly unsafe. Several candidates we've spoken with aren't opposed to permanent work in principle. One data engineer told us he's "generally interested in both" permanent and contract, and would consider a fixed-term or permanent role if the salary justified it, while another said he's "okay to" consider a permanent role despite being contract-focused, so long as the remit matches. The door isn't closed, but it isn't the default either, and the terms matter more than the employment type itself.
Second, the inside versus outside IR35 distinction isn't a technicality, it's often the deciding factor in whether a candidate engages at all. Multiple candidates in our conversations were explicit that they'd only consider outside-IR35 arrangements, with rates inside IR35 effectively discounted by half in their own calculations once tax and business overheads are factored in. A permanent leadership hiring strategy that doesn't account for this parallel market, and doesn't understand why candidates are pricing contract work the way they are, risks losing exactly the senior talent it needs most.
Building a Hiring Strategy That Accounts for This Dynamic
Treating this supply-side shift as noise rather than signal is the most common mistake we see in permanent leadership searches. The candidates choosing contract work over permanent leadership roles are often the strongest technical operators in the market, the ones who could plausibly do either job well. A hiring strategy that only courts candidates actively seeking permanent roles is, by definition, only fishing in half the pool.

Practically, this means a few things for CTOs and HR leaders building out Data and AI leadership capability. Run parallel tracks rather than sequential ones: if your strongest candidate for a Head of Data or VP Engineering role is contract-first, consider whether an interim or fixed-term structure could de-risk the hire for both sides while you build the case internally for a permanent offer. Understand that day rate quotes from experienced candidates, often in the £500 to £1,000+ range depending on seniority, reflect risk-adjusted thinking, not inflated expectations. And recognise that candidates weighing contract versus permanent decisions are frequently doing so because contract work is funding something else, a business, a project, a different kind of career flexibility, not because they've been rejected elsewhere.
What We're Seeing in Practice
In our own conversations, this dynamic shows up constantly as a tension between what the client wants (a permanent hire to build durable capability) and what the strongest available candidate wants (contract flexibility to fund other priorities). One client's data engineering vacancy, for instance, was pitched at £500 to £550 a day, and the candidate's only real question was whether that was inside or outside IR35, because that answer determined whether the conversation continued at all. These aren't edge cases. They're the normal shape of a conversation with senior data talent in the current market.
For employers, the takeaway isn't that permanent leadership hiring is impossible, it's that it needs to be designed with this candidate psychology in mind from the outset. That means being upfront about IR35 status early in the process, being realistic about how day-rate benchmarks compare to the permanent package you're offering, and being willing to structure interim or fixed-term arrangements as a bridge when a strong candidate isn't ready to commit to permanent terms outright.
Designing Around the Market as It Actually Behaves
The data and AI leadership market isn't short of capable people, it's short of capable people who want the permanent structure on offer. That's a solvable problem, but only if hiring strategies are built around how senior candidates are actually thinking about risk, flexibility, and income, rather than around an assumption that permanence is always the more attractive offer. We see these conversations every week, and the pattern is consistent enough that it should be shaping hiring strategy, not just recruitment tactics.
If you're building a permanent leadership hiring strategy for a Data or AI programme and want to understand how this supply-side dynamic is likely to affect your search, talk to us. We run contract and permanent hiring in parallel for exactly this reason, and we can tell you, before you go to market, whether your ideal candidate profile is more likely to be found on an outside-IR35 contract than in your permanent pipeline.
Latest News
How to Assess Real-World Medallion Architecture Experience During Technical Screening
The technical screening questions a Manchester data recruiter uses to separate genuine bronze/silver/gold medallion ownership from peripheral experience.
How to Verify Hands-On Kubernetes and Private Endpoint Security Skills When Hiring Platform Engineers
A Manchester recruiter's screening guide for platform engineer hires: questions that reveal real AKS, Terraform and private endpoint security depth.
Who Should I Hire for a Microsoft Fabric Implementation Project?
A Manchester recruiter's FAQ on hiring Microsoft Fabric data engineers, Power BI leads and architects, with real medallion architecture screening insight.