I've spent the last fortnight interviewing disappointed CTOs across London. Same story, different accent. They've hired a DevSecOps engineer who turned out to be nothing more than a developer with a security certificate and a generous interpretation of their CI/CD experience.
Thing is, the market's flooded with these halfway-house candidates. Since the 2025 NCSC guidance practically mandated DevSecOps adoption for critical infrastructure suppliers, we've seen a gold rush of developers rebranding themselves faster than you can say "shift left."
But here's the rub: genuine DevSecOps engineers are a different breed entirely. And most UK tech leaders are still using outdated assessment techniques that fail to separate the real deal from the well-intentioned pretenders.
The Security-Developer Divide Isn't What You Think
The most painful misconception I encounter when placing DevSecOps talent? That it's primarily about technical checklists.
Security isn't a feature, it's a mindset. When I'm evaluating candidates for US defence contractors (where the standards make UK banking look positively cavalier), I'm looking for someone who instinctively approaches architecture discussions with threat modelling already running in their head.
A developer who's done a few security courses will talk about implementing specific tools. A true DevSecOps engineer talks about attack surfaces, trust boundaries, and threat actors before they even mention a single tool.
But how do you assess this in an interview?
Beyond Tick Boxes: Diversity Recruitment Strategies That Actually Transform UK Workplaces
Master the Virtual Hot Seat: 7 Video Interview Techniques Recruiters Don't Tell You
AI Governance Careers Surge in 2026: Why This Role Will Define the Next Decade
The Scenarios That Separate Pretenders From Contenders
Forget the coding tests and security trivia. Here's what actually works:
- The Architectural Security Review
Instead of asking candidates to write secure code, show them a deliberately flawed system architecture diagram. Ask them to identify security concerns. The pretenders will spot the obvious OWASP Top 10 issues. The genuine article will question assumptions about trust boundaries, data flows, and identify subtle issues like insufficient logging or privilege escalation paths.
I placed a brilliant engineer at a London fintech last month who impressed them by identifying how their proposed architecture would fail compliance requirements they hadn't even considered yet. That's the difference.
The Pipeline Challenge
This is my favourite. Present candidates with a working CI/CD pipeline and ask them to evolve it for security without breaking developer workflow.
The real DevSecOps engineers won't just bolt on security tools. They'll consider:
- Where security checks create the most value with least friction
- How to handle false positives
- Ways to educate developers rather than just blocking their work
- The governance requirements for evidence and audit trails
In my experience placing candidates at financial services firms, this approach instantly reveals who understands security as a cultural practice rather than a technical checklist.
The Questions FTSE 100 Tech Leaders Actually Ask
Some of my clients at Britain's largest companies have entirely ditched the technical focus in first interviews. Instead, they're asking questions like:
"Tell me about a time when you had to convince developers to adopt a security practice they initially resisted."
The answer tells you volumes about communication skills, empathy, and whether they see security as a collaborative effort or a policing function.
Another brutal but effective question: "How would you respond if our CEO demanded we disable a security control to meet a critical deadline?"
You'd be shocked how many candidates give the textbook answer about "never compromising security" without acknowledging the business realities. The best candidates talk about risk management, compensating controls, and time-limited exceptions with proper governance.
Salary Benchmarks That Won't Make You Competitive in 2026
Let's be blunt. If you're still offering £85-95K for senior DevSecOps roles in London, you're wasting everyone's time. The market shifted dramatically after the National Cyber Strategy implementation deadlines hit.
Competent mid-level DevSecOps engineers are commanding £110-125K in the capital now. Senior roles with architecture responsibility? £140K minimum, often with equity that actually means something.
And if you're competing with US remote roles (which, let's face it, you are), add another 15-20%. I've placed three UK DevSecOps leads with US defence tech firms this year alone, all remote, all north of £160K equivalent.
The painful reality is that candidates with this hybrid skillset can name their price. The even more painful reality is that hiring the wrong person costs considerably more than paying market rate for the right one.
The Accidental Security Engineer Problem
A pattern I'm seeing with alarming frequency: companies hiring security-aware developers and expecting them to grow into full DevSecOps roles. Without training. Without mentorship. Without clear expectations.
It doesn't work. I've had to re-place too many of these "accidental security engineers" who were set up to fail.
If you're genuinely developing talent internally, you need a structured pathway. The best companies I work with pair junior DevSecOps engineers with security architects and give them cross-functional exposure to both security operations and development teams.
Without this deliberate approach, you're just rebadging developers and hoping security expertise will materialise through osmosis.
The teams who are doing this successfully? They're using security champions programs, regular threat modelling sessions, and brown bag security training to embed security thinking across their engineering organisation.
The Assessment That Actually Works
If I could recommend just one change to your DevSecOps hiring process, it would be this: focus on the interfaces.
How does your candidate interact with:
- Developers who don't understand security requirements
- Security teams who don't understand development constraints
- Product owners pushing for features over security
- Risk and compliance teams demanding evidence
The best DevSecOps engineers are translators and diplomats as much as they are technicians. They can speak the language of each group and find the path that satisfies everyone's needs.
So stop focusing exclusively on technical assessments and start evaluating communication skills, empathy, and the ability to influence without authority.
You can find technical competence. But finding someone who can make security part of your engineering culture rather than a bolt-on afterthought? That's the difference between checkbox compliance and actual security.
I've placed over 30 DevSecOps professionals in the last year alone, and I can tell you with absolute certainty: the ones who succeed aren't just the most technically proficient. They're the ones who can make security relevant, accessible, and valuable to everyone in the organisation.
And that's something your technical assessments probably aren't measuring at all.
What's your experience been? The market's evolving rapidly, and I'm always keen to hear what's working (and what's not) in DevSecOps recruitment.
Connor Walsh is a cybersecurity recruiter specialising in UK to US talent placement. Browse UK DevSecOps opportunities or explore The OHub's specialist security recruitment services for your hiring needs.
