Platform Engineering: Is This Where Traditional DevOps Is Heading?
Platform engineering is rapidly replacing traditional DevOps in major banks as scale, complexity, and hybrid skill demands outgrow legacy enablement models. Internal Developer Platforms and AI‑accelerated workflows are now reshaping how engineering teams operate, driving a new baseline for productivity, governance, and SME expectations.
Ben Dowdle
Senior Principal Consultant
ben.dowdle@caspianone.co.uk
Over the last few years, I’ve watched a shift take place inside the engineering organisations of major banks. This shift has now reached critical mass. DevOps, at least in the form most banks adopted it, is giving way to platform engineering. Not because DevOps failed, but because the scale, complexity, and expectations placed on engineering teams have evolved far beyond what traditional enablement teams can realistically support.
From my conversations with global investment banks to the expertise clients now request to the challenges SMEs talk about daily, the picture is clear that the future of engineering in financial services revolves around platform‑led delivery and Internal Developer Platforms (IDPs). DevOps hasn’t disappeared, but it is being absorbed into a broader, more capable model that revolves around developer self‑service, automation, and hybrid engineering knowledge.
What’s driving the shift from DevOps to platform engineering?
When I look back at the DevOps market of a few years ago, most opportunities centred around engineers coming from Linux or sysadmin backgrounds who were strong with tooling, configuration, and CI/CD. That model made sense when organisations were transitioning to the cloud or breaking broad service offerings into smaller, more focused projects. But banks now operate at a scale where that model simply doesn’t stretch far enough.
What I see consistently is that DevOps has become overwhelmed. If you double the number of developers, you don’t just double requests. You multiply them. Every app team wants environments, pipelines, security checks, observability, containerisation, and infrastructure patterns. A centralised DevOps group can only absorb so much before it becomes a bottleneck.
This is where platform engineering enters. Instead of enabling developers to react, platform engineers build the actual platform developers work in, such as automated governance, standardised pipelines, fully provisioned runtimes, templates, and shared tools.
IDPs support this shift, creating a consistent “operating system” for development that eliminates the constant duplication I’ve seen across banks. One team is reinventing a CI pipeline while another builds container scaffolding from scratch. Infrastructure sprawl becomes productised, repeatable, versioned, and maintained as an internal product.
Industry research reflects exactly what I’m seeing. Gartner projected that by 2026, 80% of large engineering organisations will have platform engineering teams, up from 45% in 2022. That tracks perfectly with the programmes of work coming across my desk; opportunities once labelled “DevOps Engineer” are now “Platform Engineer” or “Platform Developer.”
But the biggest reason for the shift is a convergence of expertise. Banks now want engineers who can code, automate, and understand infrastructure. Developers are expected to know containers, ops engineers are expected to write Python, and front‑end engineers are expected to understand cloud fundamentals. Platform engineering is the model that brings all of these expectations together.
How Are Internal Developer Platforms Reshaping Engineering?
Teams are moving away from ticket‑driven DevOps and toward platform‑led delivery, fundamentally rewriting how engineers interact with tooling, infrastructure, and each other. Internal Developer Platforms sit at the centre of this change. They redefine the relationship between developers and the environment in which they build. What used to be a patchwork of scripts, requests, and almost-tribal knowledge is becoming a consistent, self‑service experience that developers can rely on every day. The impact is tangible across productivity, governance, and team autonomy, and the following areas highlight where this change is most visible.
IDPs offer a true self‑service model
One of the most noticeable changes in banks is the desire to give developers an environment they can operate in without filing a ticket. I’ve heard this described as a “playground,” and it’s exactly what IDPs provide - a set of paved roads where developers can create services, spin up environments, deploy code, and roll back changes without involving multiple teams. Google Cloud frames IDPs as curated platforms providing “secure, well‑supported templates and automation” to reduce cognitive load. This aligns directly with what banks now expect their engineering teams to deliver.
Reducing friction and eliminating duplication
I’ve seen countless examples of teams inside the same bank solving the same operational problems independently. Without a centralised platform, fragmentation is inevitable. IDPs remove this by consolidating best practices into reusable assets such as infrastructure blueprints, deployment pipelines, policy‑as‑code, and observability hooks. CNCF highlights this as one of the primary benefits of platform engineering, reducing duplicated effort and giving back time to development teams.
Governance built in, not bolted on
In a highly regulated environment, compliance is not optional. Historically, this meant manual checks, approval chains, and a lot of interruption-driven work. What’s changing now is that compliance controls are being embedded directly into the platform. Google’s “shift down” approach, which advocates for pushing security, reliability, and efficiency responsibilities into the platform rather than onto individual developers, mirrors exactly what I see banks moving toward.
What Is A Platform Engineer Today?
A modern platform engineer is not just someone who knows Terraform and Kubernetes (although those skills still matter). They are developers who can build automation, infrastructure engineers who can program, and problem‑solvers who can create abstractions that empower thousands of other engineers. The most striking change I’ve seen in the market is this hybridisation.
Banks now expect platform engineers to:
Write production‑quality code in languages like Python or JavaScript
Understand containers, orchestration, IaC, CI/CD, networking, and cloud security
Build internal tools, portals, and templates
Work closely with developers to create intuitive experiences
Understand underlying systems well enough to debug them
One challenge I encounter frequently is the knowledge gap between new entrants to the industry and more traditional engineers. Many new engineers are strong with cloud tools, scripting, and AI‑generated code but often lack basic systems knowledge such as how networks work, how data centres operate, how to design resilient infrastructure. On the other hand, teams with strong infrastructure lineage sometimes lack programming fluency. Platform engineering sits at the intersection of both worlds. Industry guidance reinforces the need for this hybrid expertise, emphasising product thinking, developer experience, and cross-functional collaboration.
What Role Is AI Playing?
AI has become an unavoidable part of engineering and resourcing. In almost every bank I work with, engineers are now expected to use AI tools during technical assessments. The question is now, “Can you use AI as part of your workflow, validate the output, and deliver something robust?” This is a massive shift. A few years ago, engineers couldn’t use external tools during interviews. Now, those who don’t use AI intelligently are at a disadvantage.
A Microsoft-led experiment showed developers completed tasks 55.8% faster using GitHub Copilot. For banks, this changes what “good engineering” looks like. AI accelerates routine work, which means engineers are increasingly assessed on their ability to reason about systems, design architectures, and make judgement calls, not just write code quickly.
How Will Engineering Teams Evolve As Platform Engineering Becomes Standard?
Instead of multiple teams owning slivers of the delivery lifecycle, platforms bring everything together under shared tooling, shared automation, and shared controls. The traditional lines between development, operations, SRE, and infrastructure are blurring. I believe the clearest signal of the future is the way these responsibilities are converging.
This doesn’t remove the need for specialists. Far from it. Network engineers, security teams, and infrastructure experts are all still essential. But their expertise is increasingly expressed through the platform rather than through manual intervention. That’s what allows the model to scale.
Platform engineering also influences career development. Developers with an interest in automation naturally move toward platform roles. Infrastructure engineers are learning to code to stay relevant. Junior engineers, who increasingly arrive with strong AI-assisted programming ability, will need support in building foundational systems knowledge. CNCF’s maturity model describes exactly this type of organisational evolution as a shift from fragmented automation to an orchestrated platform that becomes the backbone of software delivery.
Why Is Platform Engineering Becoming The New Baseline for Modern Engineering?
Engineering teams are more hybrid, delivery expectations are higher, and AI has changed the baseline of what “productive” looks like. But at its core, this shift is about enabling developers. Platform engineering isn’t complexity for complexity’s sake, but creating an environment where developers can build, ship, and innovate at the speed the business now expects. Platform engineering has arrived because the realities of modern banking demand it. The world I work in today looks fundamentally different from the one I entered several years ago.
Caspian One - Powering the Talent Behind Modern Platform Engineering
As banks modernise their engineering organisations, the biggest challenge isn’t recognising the need for platform engineering; it’s securing the talent and capability to deliver it. That’s where Caspian One supports the institutions we partner with. We specialise in providing the hybrid engineers, niche specialists, and delivery teams required to build and scale Internal Developer Platforms, modern infrastructure, and data‑driven systems. Caspian One delivers expert consultants and managed teams across trading technology, data and analytics, AI‑enabled solutions, and the core infrastructure that underpins today’s financial markets.
Our model gives clients flexibility. Through Resource Augmentation, we embed highly skilled SMEs directly into engineering teams, enabling rapid scaling without long‑term overhead. For organisations needing end‑to‑end delivery, our Managed Outcomes offering provides structured project execution, governance, and measurable results. This includes work across data and analytics, application development, infrastructure uplift, and cybersecurity, all grounded in domain expertise across financial services technology.
Where platform engineering demands breadth, depth, and adaptability, Caspian One can ensure you get the right capability at the right time, helping engineering teams deliver at the pace modern platforms require.
Platform Engineering FAQs
What is platform engineering?
Platform engineering focuses on building internal platforms that give developers self-service access to infrastructure, deployment pipelines, and tools, reducing reliance on central DevOps teams.
What is an Internal Developer Platform (IDP)?
An Internal Developer Platform (IDP) is a self-service platform that provides developers with standardised tools, environments, and automation to build and deploy software faster.
Why are banks adopting platform engineering?
Banks are adopting platform engineering to reduce delivery bottlenecks, improve developer productivity, and embed governance and security directly into the software development process.
What experience do platform engineers need?
Platform engineers need a blend of software development, cloud infrastructure, automation, Kubernetes, Infrastructure as Code (IaC), and security knowledge.
How is AI impacting platform engineering?
AI helps platform engineers automate repetitive tasks, accelerate development workflows, and focus more on system design, architecture, and engineering decision-making.
Disclaimer: This article is based on publicly available, AI-assisted research and Caspian One’s market expertise as of the time of writing; written by humans. It is intended for informational purposes only and should not be considered formal advice or specific recommendations. Readers should independently verify information and seek appropriate professional guidance before making strategic hiring decisions. Caspian One accepts no liability for actions taken based on this content. © Caspian One, 2026. All rights reserved.
Read more or search for topics that matter most to you!
