The Explosion Of 'Ops' Roles - Unravelling The Common Thread In Modern Engineering
Barracuda, Tuesday, February 10th, 2026
Why every 'Ops' role shares a core purpose - and how to find it
Takeaways
- 'Ops' roles are proliferating rapidly in engineering, with new variants like DevOps, CloudOps, DataOps, and MLOps emerging every year.
- While the growing number of Ops roles initially seems innovative, it can lead to fragmentation, confusion and unclear ownership within teams.
- Despite their differences, all Ops roles share a common underlying purpose: helping engineering succeed in production reliably, securely and at scale.
- The main challenge is managing the complexity and finding the unifying thread - what truly connects all these roles - to ensure organizational success rather than chaos.
- Ops disciplines approach their shared goal from various domains such as code, infrastructure, data, ML models, security, cost, and platforms, contributing to a diverse operational ecosystem.
If you've been around modern engineering organizations, you've probably noticed a pattern: Every year, a new 'Ops' role emerges. DevOps, DevSecOps, CloudOps, DataOps, MLOps, FinOps, GitOps, PlatformOps, AIOps, ModelOps ... and the list keeps growing.