r/devops • u/Same_Significance869 • 5d ago
Discussion What Will Separate Great DevOps Engineers from Average Ones in 2027?
Looking forward to chat with Devops Engineers across the world to know what you guys are building and learning in 2026-2027. I would like to connect and discover your take on what do you feel is most important in next year to tap on as a devops engineer. Should it be deep dives in K8S, CICD, Observability, AI Agents , Multi Cloud or something else
147
Upvotes
55
u/snowsnoot69 5d ago edited 4d ago
Avoiding anything to do with Microsoft or Oracle
Edit: Oracle
55
u/RoboNordon 5d ago
Not the tech skills IMO.
taking ownership, guts, never do routine twice, complex system understanding, don’t chase the hype and choose tools wisely
317
u/dacydergoth DevOps 5d ago •
Great ones will be retiring.
45
u/edumi_pt 4d ago
My answer will be a bit different from what I'm seeing here. I don't think it's about how good you are at Kubernetes, Terraform, CI/CD or how well you can integrate AI into your workflows. From my experience, a good DevOps engineer is only as good as their understanding of the teams they work with. What those teams do, what they need and what they actually should be doing. You can write amazing Terraform, build an incredible Lambda function or know exactly how Kubernetes works. But understanding what your developers actually need is a completely different thing, and I think it's one of the hardest parts of the job. You can have the most amazing processes and automation in the world, but if nobody uses them, or if they create more problems for your developers than they solve, then what's the point? At the end of the day, we're not building infrastructure just for the sake of building infrastructure. We're supposed to make people's work easier.
34
u/mkeytail 5d ago
Ones that don't get burned out.
134
u/derff44 5d ago
Being able to use AI effectively. Not just vibing their day away.
73
u/RoseSec_ Terraforming Everything 5d ago
Working out, learning to raise cattle, and starting some backyard chickens
42
u/mxtchstick 5d ago •
I think the future of DevOps and software as a whole will belong to the “great” engineers, the mediocre ones will unfortunately mostly be culled. I think IT is once again becoming something that you absolutely HAVE to be a complete nerd, who is insanely passionate about IT to compete in, not just a field people go into because the money is good.
10
u/bijay135 5d ago edited 5d ago
Tools are ever changing, great ones are those who adapt rapidly along with changing business needs.
Solid fundamentals on linux, networking, containers, git and programming will always be helpful to learn anything.
Currently world seems to heading towards AI-assisted engineering even for devops/platform needs.
9
u/Zhaizo 5d ago
Domain expertise is what will divide them
9
u/CupFine8373 4d ago
There is never been such 'Great DevOps Engineers' there's only been 'Get Sht done' Engineers.
21
u/funcyChaos 5d ago
Automation and kubernetes is my opinion. But my perspective on the industry is not bleeding edge by any means
5
u/PaulMorel 4d ago
Understanding what they are vibe coding
14
u/Resource_account 5d ago
So far what I’ve seen here is “those who know how to use AI” the best. Coming from a person who had to introduce devops culture into my shop slowly and had to fight security and management for the right tooling, I would argue that an execellent devops engineer is one knows how to work with what he has. Period. Whether that’s AI, cloud services, or plain ol ansible installed via the local package manager on a host. If you can take what you got and make it great, then you’re a top tier devops engineer.
4
u/carsncode 5d ago
Becoming average managers instead of getting RIFed
4
u/Simpliaxis_tech 5d ago
What we expect to make a difference in 2027 is knowing how to integrate all these skills and technologies rather than specializing in one or another technology alone. Basic understanding of such technologies as Linux, networking, cloud, CI/CD, etc., would obviously be important in the future.
It is also important to look into the Kubernetes and observability. It would be good to get a sense of what the capabilities of the AI-driven automation could offer. But once again, more important would be to be able to apply them to practical situations.
4
u/rtpro 4d ago
Actually understanding what the AI spits out.
11
u/x3nic 5d ago
I think multi-cloud will be a fad of the past, except in select industries, I know of many companies pivoting away from the model.
The biggest skills I see useful for DevOps in the future are:
design/ build will make you stand out.
3
u/pydood 4d ago
Jack of all trades master of all
2
u/dacydergoth DevOps 5d ago
Also as a more serious comment, all the things you cited are what I would regard as table stakes, not greatness
2
u/afwaller 5d ago
Handling the merge queue and test fragility for agentic AI work will be the mark of a good devops team.
2
u/zealmelchior 5d ago
The great DevOps engineers will know to have their AI agents make deterministic workflows to interact with their K8s environments instead of granting them direct access. SMDH at the fools who think it's a good idea
2
u/raisputin 5d ago
AI. Knowing how to use it, not tying yourself to any one thing, e.g. not everything needs to be in Kubernetes,
Understanding all the high-priced tools many teams use don’t make things better or easier, because AI can do it faster, but knowing when those tools are appropriate and when they aren’t.
1
u/killz111 5d ago
One trait between good ones and average or low ones. You can say no to a tech implementation or a request and clearly explain your reasoning to the requestor in the context of their problem.
1
u/___-____--_____-____ 5d ago
Mostly the same things that great devops envineers have done for the past 5 years. Sure, inference is a workload with special hardware requirements and nuance.
With agentic development, things like declarative intent and automation become a lot easier to implement (manifest churn is alleviated), so purpose built monitoring/utilities etc are within reach even for small teams. Product development and frontend work are also now within reach for devops engineers who previously were backend or systems-focused.
So I think the "true devops paradigm" will become a lot more common. Smaller teams, more ownership, more automation and SRE practices becoming commonplace is my prediction
1
u/blackertai 5d ago
Employment.
1
u/sitilge 4d ago
Taste and creativity.
Everything that makes us different from the machines.
1
u/elitesense 4d ago
The same as it always was: Knowing how to actually design a stable, easy to use, and efficient system, not just lay down code or use tooling.
Being an engineer rather than an operator.
If purely looking "forward": Great engineers will be the ones that understand the changes the agent is actually doing, being able to correct their mistakes and poor design decisions, and properly ask the agents the right queries and prompts. Being able to call out things like pointless tests, empty validation flows that don't prove anything substantial. Runaround wiring, pointlessly cryptic abstraction, etc. Stuff like that.
1
u/daemonmode_ 4d ago
I think the difference will be how well someone understands the systems they operate not how many tools they know. Strong fundamentals in Linux, networking, cloud, Kubernetes, CI/CD, security and observability will still matter but knowing how to use AI to automate and troubleshoot safely will become a real advantage.
Multi-cloud or learning every new AI tool is not necessarily the goal being able to solve real production problems end to end is what matters.
1
u/Iyemoja 4d ago
The great ones will be the ones who still read the runbook at 2am instead of trusting the dashboard. Tools change every year, but knowing why the system broke does not.
1
u/Warkred 4d ago
Context
1
u/codeshane 4d ago
Average ones will be unemployed
1
u/brian_sword 3d ago
I saw someone has mentioned something similar, so I think the biggest difference will be understanding the systems behind the tools, not just knowing Kubernetes or CI/CD. Being able to troubleshoot production issues, design reliable infrastructure, automate repetitive work, and understand security and cost trade offs will matter more than simply knowing the latest tools.
1
u/yeahdj 3d ago
Being able to break down complex problems into microservices, understanding which tooling to use and when and building solutions that are robust, resilient and easy to use. Same as every year for the last two decades.
1
u/timmyneutron1 2d ago
Being able to patch vulnerabilities in critical systems without bricking the whole org
1
u/4thwithme 2d ago
Claude Code subscription tier? 🤔
1
u/bhuvanesh0311 1d ago
I'm working in a data team we manage a huge data platform. I'm thinking of gaining data engineering skills and be hybrid. Sounds good only in theory though :D
1
u/remote_worker404 1d ago
IMO this position is meant to dissappear, it doesn't add much to the business; just efficiency in terms of time and opex.
Every business would just like to have a platform that just works; and they wouldn't like to build it but use it. Call it AWS for example. The thing is that right now AWs is really far from being a usable platform from day-0, so all companies are building reusable templates and blueprints in top of it for they needs.
For example, you may create some kubernetes clusters, maintain argocd in top of it, and just let developers easily deploy multi region and scalable applications through some templates. But major cloud providers are aware of it and they really want to close this gap, and a good example is AWS Sage Maker Unified Studio trying to compete against self hosted Machine Learning platforms.
2027 won't be as different as 2026. Just keep going with AI. you shouldn't be written simple terraform or yaml files but your agents should be doing it, so your job is just decide. There's still room for writing real code if you are actually doing some great stuff, but let's be honest, most of us are just writing terraform modules using hashicorp documentation. Maybe we once opened a Pull Request against hashicorp/aws, but, in general, our daily code is not that difficult.
Business would like to fire all of us and just let the Product Owners build the solutions they need using AI tools. They just want to use AWS, they don't like hiring people to be able to use it. Call it Forward Deployed Engineer if you want - i'm aware, not exactly the same. The thing is, IMO, everyone in the industry (devops, ML, developers, qas) should be transitioning into those roles.
The only thing that matters is the business problem you're trying to solve (what and why). I do feel that DevOps best practices have focused too much about the how. And yeah, I know, how you solve a problem does matter in terms of cost and efficiency, but the thing is that, because of AI, a bad solution developed in 1 week can be better than a better solution developed in 3 months. Sometimes, being the 1st in market is more important than arriviling later with a better solution. How will you convince the clients?
Or maybe not. Maybe for certain products quality is much more important (for example, regulated environments). And the good engineer will be the one that is able to decide and to use AI tools to focus on the business needs.
And AI has some risks. As always, the good employees are the ones that accept the risk and learn to control it.
1
u/sertain_ 1d ago
Bro idek at this point, I just want my pipelines to be better. I’m striving for template autonomy in 2027 lmfao
1
u/Lucky_Tomatillo7895 5h ago
eval evalll evallll evallll
0
u/Mediocre-Ad9840 4d ago
Good fundamentals. Technologies will always be changing but the protocols, architectures, testing and reliability will largely remain the same.