QA + DevOps = ?
QA + DevOps = ?
Gartner predicts that 80% of large software engineering organisations will establish platform engineering teams by the end of 2026.
Meet the role that doesn't yet have a clear title.
Some organisations call it Platform Engineer. Some call it Quality Engineer. Some are still posting it as DevOps or Senior QA. But the job description looks the same everywhere you find it:
Build reliable, automated delivery pipelines, with quality built in from the start.
This is what happens when two disciplines stop working in sequence and start working as one.
QA validated what developers built. DevOps shipped it to production. The handoff was the process.
QA ran regression cycles. DevOps triggered deployments. Quality happened between the two, in a window of time that shrunk every quarter.
Then delivery accelerated. The QA-DevOps boundary is now actively blurring. In mature teams, testing doesn't hand off to operations at deployment; it runs through the whole pipeline. The line between “running a test” and “monitoring a service” stops being meaningful.
The window between "code written" and "code in production" no longer fits a handoff.
The skills that were used to define two roles are now expected in one.
From QA: risk thinking, edge case instinct, coverage strategy, user behaviour understanding, knowing what can break, and why it matters when it does.
From DevOps: pipeline ownership, environment management, observability, platform thinking, building the infrastructure that makes quality accessible to the whole team by default.
What ties them together now: AI belongs in the platform, not just in the IDE. Centralising it early creates leverage, and retrofitting guardrails later is far more expensive.
Without this convergence, organisations run into the same predictable problems:
• Tests that exist but don't run automatically
• Pipelines that ship code no one has validated
• Quality gates that slow delivery instead of enabling it
• Two teams, both responsible for reliability, neither fully owning it
When code, test, and production metrics are siloed in different tools, the system as a whole cannot optimise itself.
What the Emerging Role Looks Like
Platform engineering teams now serve as a bridge between development and operations, integrating developer experience, security, and speed as one system.
The engineers who are most valuable now:
• Write automated tests and build the pipelines that run them
• Design quality gates and own the infrastructure they live in
• Think about user risk and system reliability simultaneously
• Shift effort from repetitive checks toward risk assessment and release readiness
• Use AI to generate tests, validate infrastructure config, and accelerate coverage
Refs: Gartner Platform Engineering Forecast; Capgemini/Sogeti World Quality Report 2025–26.