18.11.26

Why Multi-Cloud Security Fluency Is Becoming a Core Requirement for Platform Engineering Hires

Job specs for platform engineers used to be fairly predictable: Terraform, Kubernetes, CI/CD, a cloud of choice, maybe a nod to "DevOps culture." We're seeing that template break apart in real time. Across live screenings this year, we're consistently hearing briefs that fold in security posture work, multi-cloud design, and AI-adjacent infrastructure as core requirements, not nice-to-haves bolted on at the end of a spec.

This isn't a hypothetical trend we've extrapolated from a market report. It's showing up in the actual language hiring managers use when they brief us, and in the way candidates describe their day-to-day work when we screen them. A Manchester-based fintech brief we worked recently asked for a senior platform engineer primarily based in AWS, with "pretty deep expertise" in Terraform, strong CI/CD pipeline management across Buildkite and GitHub Actions, and crucially, a "very kind of security-first mindset" because the environment is highly regulated and cloud security is "absolutely pivotal". That's not a security specialist role. That's a platform engineering role where security fluency is now assumed baseline competence.

For Heads of Engineering and Platform leads writing specs for 2026, this convergence changes what "qualified" looks like, and it changes how you need to screen for it.

Security Is No Longer a Separate Lane From Platform Work

The clearest signal we're tracking is that candidates themselves describe their roles as blurring platform engineering and DevSecOps, often without being prompted to frame it that way. One candidate working heavily in Azure described his remit as landing zone implementation, security posture assessment, and improvement, explicitly tied to a mature zero trust adaptation and "secure by design" programme, alongside automating manual processes, securing pipelines, and building infrastructure with Terraform. When we noted the overlap, he put it plainly: "these days the line between these roles are quite thin".

Security Is No Longer a Separate Lane From Platform Work — dcoded. Manchester tech recruitment

This isn't an isolated framing. Another candidate screened for an Azure platform engineering contract with a major UK investment bank described building Terraform infrastructure-as-code through Azure DevOps and GitHub Actions, with security "built along the code, along the pipelines," including validation and approval gates at every stage across test, dev, staging, and production environments, plus landing zone builds incorporating firewalls and Key Vault. Security wasn't a separate checklist item in his account. It was threaded through the pipeline architecture itself.

For hiring managers, the practical implication is this: a job spec that lists "Terraform" and "CI/CD" as skills and "security awareness" as a soft requirement is already behind what the market is producing. Candidates at the senior end are demonstrating security-by-design as a working method, not a compliance afterthought, and specs that don't test for this will under-screen for it.

A related shift sits alongside this one: multi-cloud fluency, which used to be a differentiator, is becoming table stakes for senior platform hires.

Multi-Cloud Fluency Has Moved From Differentiator to Baseline

Candidates increasingly present cross-cloud competence as standard rather than exceptional. In one screening, a candidate described himself as "equally AWS, Azure" with GCP competence as well, having worked end-to-end across multiple customers on both primary platforms. Another, interviewing for a senior platform engineer role at a Manchester fintech, described delivering Terraform code to build multi-cloud infrastructure spanning Azure, GCP, and AWS, exposing networking components to spoke workloads via hub and spoke architecture, and using Azure landing zones to support more robust DevSecOps pipelines for CI/CD.

Multi-Cloud Fluency Has Moved From Differentiator to Baseline — dcoded. Manchester tech recruitment

This pattern repeats across multiple live briefs we're working. A senior platform engineer role for a fintech organisation based in Manchester explicitly asked for strong experience in either AWS or GCP, alongside DevOps principles and the ability to contribute to original platform solutions, not just execute someone else's design. Another Manchester fintech brief required AWS and GCP experience because the business's legacy Azure systems were being migrated into a combined AWS-GCP environment, with the hiring need driven specifically by a lack of in-house GCP depth. A third brief for a senior platform engineer, head of platform, and junior platform engineer being hired simultaneously centred on AWS experience with legacy Azure systems slated for migration to a fully cloud-native platform.

What's notable here isn't just that multi-cloud experience appears in specs. It's that hiring managers are explicitly briefing for engineers who can design the migration path between clouds, not just operate within one. That's a materially different and harder screening bar than "has used AWS and Azure."

Alongside multi-cloud design, we're now seeing AI-infrastructure literacy enter the same conversations, often in the same breath as traditional pipeline tooling.

AI Infrastructure Is Entering the Platform Engineering Remit

Platform engineering briefs are starting to reference AI tooling as part of the day-to-day stack rather than treating it as a separate AI engineering concern. In one screening for an Azure platform engineering contract, the candidate described automating subscription landing zones while also noting that the organisation has "some Copilot licenses as well," woven into the same conversation about GitHub Enterprise and Azure DevOps workflows. This is a small detail, but it's telling: Copilot governance and licensing is starting to live inside the same operational remit as pipeline and landing zone work, not in a separate AI platform team's job description.

AI Infrastructure Is Entering the Platform Engineering Remit — dcoded. Manchester tech recruitment

This matters for how specs get written. If Copilot usage, governance, or AI tooling integration sits inside the platform engineer's actual working environment, as it clearly did in this candidate's recent role, then a job spec that treats AI infrastructure as "out of scope" for the platform hire is likely to misjudge what the successful candidate will actually be doing once they start. We'd argue this is the leading edge of a broader pattern: platform teams are increasingly the ones responsible for hosting, securing, and governing the infrastructure that AI tooling runs on, even when the organisation hasn't yet created a dedicated AI platform function.

Where this convergence becomes most consequential is in how hiring managers assess it, because screening for three disciplines at once requires a different kind of technical interrogation than screening for one.

Why Screening Criteria Need to Catch Up Faster Than Job Specs

The convergence we're describing creates a specific risk for hiring managers: specs are starting to reflect the new reality, but screening processes often lag behind. It's relatively easy to add "security mindset" or "exposure to AI tooling" as a line item in a job advert. It's much harder to actually verify, in a live screening conversation, whether a candidate who claims Terraform and AWS experience can genuinely reason about zero trust architecture, pipeline security gates, or how Copilot governance intersects with their infrastructure.

Why Screening Criteria Need to Catch Up Faster Than Job Specs — dcoded. Manchester tech recruitment

This is precisely the gap Dcoded's technical screening approach is built to close. Our consultants probe for the mechanism behind the claim, not just the keyword on the CV. When a candidate tells us they've worked with Terraform or AWS, we're asking what the landing zone actually looked like, how security was built into the pipeline stages, and where the hub-and-spoke or multi-cloud design decisions were made, because that's where the real signal lives. Jay Guney, Dcoded's Founder & MD, has described building a formal qualification standard internally, bringing in technically expert "judges" from client organisations to help calibrate how Dcoded assesses candidate claims against the standards clients themselves work to, precisely because keyword-matching a CV against a job spec doesn't surface whether someone can actually do zero trust design, multi-cloud migration planning, or secure pipeline engineering.

For Heads of Engineering writing 2026 specs, the practical takeaway is to build the same interrogation into your own interview loops. Don't just ask whether a candidate has touched AWS, Azure, and GCP. Ask them to walk through a specific landing zone or migration decision and explain the trade-offs. Don't just ask whether they've worked with CI/CD tooling. Ask where security validation sits in their pipeline and why. The candidates who can answer in the kind of operational detail we're hearing in live screenings, describing hub and spoke architecture, approval gates across environments, or zero trust maturity stages, are the ones genuinely operating at the convergence point this trend describes.

What This Means for Writing 2026 Job Specs

Treat security and AI-infrastructure literacy as integrated platform engineering competencies, not adjacent specialisms to be hired separately later. The evidence from our live screenings points to a few concrete adjustments worth making now.

First, specify the multi-cloud reality rather than naming a single platform. Several of the briefs we're currently running involve organisations migrating between clouds, Azure to AWS and GCP, legacy Azure to cloud-native, and the engineers best suited to these roles are the ones who've actually designed and executed migrations, not simply maintained a single-cloud environment.

Second, name the security expectation explicitly and test for it. "Security-first mindset" should translate into interview questions about pipeline validation gates, landing zone design, and zero trust principles, the kind of detail candidates in our screenings volunteer unprompted when it's genuinely part of their working practice.

Third, don't assume AI-infrastructure responsibilities sit outside the platform remit. If your organisation has rolled out Copilot or is building AI agent hosting capability, your platform engineers are likely already touching governance and licensing questions in practice, even if the job spec hasn't caught up.

The Takeaway for 2026 Hiring

The platform engineering hire you write a spec for today will, in practice, be expected to reason across cloud architecture, security posture, and AI infrastructure simultaneously, because that's already how the strongest candidates we're screening describe their current roles. Specs that still separate these into "platform" versus "security" versus "AI" are likely to either attract the wrong candidates or under-test the right ones.

We're tracking this convergence in real time because it shows up every week in our screening calls, not because it's a theoretical prediction about where the market is heading. If you're writing platform engineering specs for 2026 and want a second opinion on whether your screening criteria actually catches candidates operating at this intersection, talk to us about how we structure technical screening for exactly this kind of hire.

Why Multi-Cloud Security Fluency Is Becoming a Core Requirement for Platform Engineering Hires

Latest News