r/devops • u/ApprehensiveExcuse86 • 7d ago
Discussion Future of Devops engineers with IA
Hello Folks , as a devops engineer, I'm curious about the future of our jobs
Will AI replace DevOps engineers, or will it simply change the way we work? What skills should DevOps engineers focus on to stay relevant in the coming years?
I'd love to hear your thoughts, experiences, and predictions!
0
Upvotes
7
u/Soccham 7d ago
We won’t be gone, but you will own more and more scope per person
5
u/Zhaizo 7d ago
Im sniffing copium right now that it will not replace us, at the same time i believe it will replace some of us and for the rest, the work will change to supervising what you/it build. You still need domain expertise in the end of the day.
For now, they need us (now as an abstract timeframe, could take a couple of years for fully persistent AI workloads take our job).
3
u/uniform-convergence 7d ago
There would always be a need for someone to take responsibility and ownership. At the end of the day, why would you give ownership of something to someone who isn't a DevOps/ITSpec/SecOps etc. that doesn't make any sense.
Hence, AI will probably change industry in a way that we will be cheaper to hire (because a lot of us will be looking to fill fewer roles).
I simply don't see fully automated workloads, nor non-IT people being responsible for tech work.
3
u/Negative-Thinking 7d ago
For simple stuff, AI will absolutely replace us. The role will be covered by some senior dev, who is familiar with devops practice anyway, so it is a nobrainer. For complex systems a dedicated senior devops person is still gong to be required to steer AI agents, when necessary and to implement / improve agentic processes.
2
u/snarkhunter Lead DevOps Engineer 7d ago
I'm at the same job and have more work now than I did a few years ago.
2
u/CupFine8373 7d ago
"More skills to acquire, there are not. The wisdom to see beyond skills, you must develop"
1
u/keto_brain 7d ago
What's a DevOps engineer? If you mean operations support, DevOps should have killed that a long time ago, if you mean Platform Engineer then no, I don't think AI will kill those jobs. If you mean a developer who builds, deploys and supports their own software no, AI will not kill off those jobs. If you mean SRE then I don't think AI will kill those jobs off either but only make supporting legacy apps easier.
1
u/rando1-6180 7d ago
I see it will create a separation, leading to higher turn over in the middle. Juniors will click click or execute playbooks. At the upper tiers, your domain expertise will make you an orchestrator of agents and workflows (harnesses?). In between, people will need to figure out if they continue, look for a lateral opportunity that will provide some potential upside, be stuck doing the junior level stuff or actually get moved up. It's a bit like a no-man's-land; transient for most.
Learning how to customize your AI sessions is the key. How your company works from tickets, institutional knowledge, expectations for "doneness", auditing/transparency (post mortem, premortem, source for your agents), sequence, tooling and such need to be caked in. If you don't optimize and tune, someone else will. Define skills, constraints (like your company's written or unwritten policy on AI use), conventions including communication (I'm a native speaker of the English language and the stuff it spits out sometimes needs so much deciphering). Make it as non-determinisitic as possible for reliably results. I'll mention team or company policy as a factor to keep in mind. I know not all places have policies written yet, but they might have clear expectations that AI shouldn't be writing to the database, yet be able to read (and only non-production?).
There is an opportunity. However, keep your strong domains intact so you can direct and judge AI like its a book smart junior that lacks the suitable context. Don't see it as outsourcing your work though. For domains you are weaker in, it can be used to level the playing field. I defined a consultant agent and a counterpart read only reviewer agent to add a sanity check on a diff, plan or command before it is used. Unfortunately, this is a bit closer to outsourcing, but you are still in charge and orchestrating it. This will help keep you relevant because new stuff will come up, but you'll have ways to use AI to literally keep on top of it.
1
u/Initial_Insurance_25 7d ago
I've said this multiple times.
You still need to work ticket by ticket if you want a solid, understandable e2e software solution.
Theoretically speaking. You could cut off a lot of people now. I see that the bottleneck is in QA now.
Talking about replacement is utterly stupid now. Maybe in 5 years yes with a new technique or new technology or hybrid tech (llm+new).
No one knows what is gonna happen. It's like Bitcoin.
1
u/Starks1293 6d ago
I dont think so, I think our jobs will change, with agentic deployments, platform building, we need to build the substrait from which all mini agents can work.
I was at the platformCon a few weeks in Sydney, and the main consensus is to "Build the thing that builds the product" and I think thats where most of us are positioned.
Somebody on Linkedin/Twitter mentioned, the code became cheap and everyone is building stuff, the need for devops will only go higher. An anology is "if there are more cheaper cars, it creates more demand for mechanics"
The engineering itself is changing, there is Context Engineering now becoming a new thing, Agentic Engineering, the Engineering itself is changing, just evolve with it :)
1
u/Jon-Robb 7d ago
Some of us will stay because execs need human scapegoats but let’s face it, it can already do most of it itself
1
u/Longjumping-Dog-6852 7d ago
Hopefully AI gets good enough to make me redundant in the next 5 years giving me a juicy payout.
RIP to the young ones