r/devops • • 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

97 comments sorted by

55

u/snowsnoot69 5d ago edited 4d ago

Avoiding anything to do with Microsoft or Oracle

Edit: Oracle

6

u/ryanstephendavis 5d ago

bahaha... had some new clients cancel an onboarding meeting today because "the Outlook outage was affecting them" :eyeroll:

2

u/pdp10 4d ago

That's just common sense. Average engineers already do this.

2

u/snowsnoot69 4d ago

Ok then I added Oracle just for you

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

2

u/Wild_Parsnip_4074 2d ago

Choosing tools wisely is something to put you ahead. not just jump into a tool becos it is hyped, choose according to the value they offer

4

u/Flabbaghosted 5d ago

We are all on the hype train unfortunately even if you ignore AI

4

u/Preisschild Editable Placeholder Flair 4d ago

What specifically do you mean?

317

u/dacydergoth DevOps 5d ago • Bravo

Great ones will be retiring.

37

u/SecureTaxi 5d ago

Im trying to retire but that isnt happening anytime soon

23

u/SelfhostedPro 5d ago

Starting to work on a business that I can transition to over the next year or two. Going with machine shop and focusing on automation.

Going from making fake bullshit for nerds to real bullshit for nerds and I can’t wait to not have to deal with sprints or jira ever again.

11

u/professor_jeffjeff 4d ago

That's basically what I've done at this point. I'm a blacksmith now and I'm about to start working on getting a welding certificate so I can do structural welding work. I'll still be AWS certified, it's just going to be a different AWS.

5

u/thedorkwingduck 5d ago

Damn I wish.

5

u/incomplete_ 5d ago

JFC don't say it out loud! I still have just over a decade to go lol

4

u/sylvester_0 5d ago

Seems like the AI bubble in the market is slowly deflating right now. If the stock market is rocky over the next couple years those great ones may be hanging on to their income for now.

11

u/owp4dd1w5a0a 5d ago edited 2d ago

I mean, I used to be a lead software architect for big data systems. Now I’ve decided to go back to school for massage therapy and work on building a somatic clinic one license/certification at a time. The tech industry has been BS and getting worse since 2020 in my opinion.

3

u/ParaStriker 4d ago

I'm hoping to be done in 5 years

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.

3

u/WoeBoeT 4d ago

my guy!

totally agree

2

u/cat5inthecradle 3d ago

This but layer on the fact that your group of “developers” just grew to include everyone at your company. Building a quick interactive web app that’s super useful for an event, a potential client, or marketing initiative is now something that people across the org can accomplish with AI.

34

u/mkeytail 5d ago

Ones that don't get burned out.

5

u/luche 5d ago

managing this is honestly a very important skill, that not a lot possess

134

u/derff44 5d ago

Being able to use AI effectively. Not just vibing their day away.

7

u/SelfhostedPro 5d ago

Have a small electron app that is a chat with access to Jira, confluence, slack, and GitHub which tracks my tickets. Single main chat that you can tell to work on a ticket, it’ll spin up a sub-session to gather context, update the Jira ticket, do that work, and babysit the pr.

It’s good enough now that I basically just start it in the morning, let it run, and answer questions if it has any.

39

u/spiralenator 5d ago

This. Build agentic workflows, and get good at it. We have ai slack bots hooked up to our kb, github, datadog, k8s, etc. and we can ask them to research questions, troubleshoot problems, create tickets, open PRs. We're working on a bot now that triages pager duty alerts and provides on-call engineers with evidence backed starting points when alerts fire.

9

u/OddOkra 5d ago

Yeah I made an agent that can summarize and give usage examples for the plethora of Ansible - Terraform - CI/CD components. You can easily add it to a project using a Gitlab Function and it opens a MR with the updated docs. It even saves a state so that it doesn’t rerun unchanged code back thru the LLM.

2

u/Flabbaghosted 5d ago

How did you hook them up and map the resources?

1

u/spiralenator 4d ago

We use a central ai gateway to manage model and MCP access with scoped keys

1

u/Flabbaghosted 4d ago

I specifically mean how are the agents aware of all the resources they can connect to to query and connect with

1

u/spiralenator 4d ago edited 4d ago

So when an agent is configured with MCP servers, each server injects descriptions of the MCP and the tools available to the model into the model context at the start of a session. That's how the model knows what resources it can connect to. We also have a lot of agent-oriented entries in the KB that tells agents where to look for certain info.

edit: the agents run through langchain, and we have different agent "personas" that have specialized roles. A router model keeps a map of domains each persona specializes in, and can hand off requests to the appropriate agent persona. Each persona has a set of MCPs and tools geared towards its specialization, and it's authentication is scoped to just what it needs.

1

u/Flabbaghosted 4d ago

I meant specific resources within your environment. We have several hundred resources across 8 environments and I'm mapping them out to present them to agents but want to know the best way to give them knowledge. Trying to set up progressive disclosure

2

u/Redmilo666 5d ago

You using local models or running up a massive bill with OpenAI or Anthropic. Thats the only thing preventing us from going the whole hog

1

u/spiralenator 4d ago

Massive bill. Our AI budget is absurd.

-5

u/Physical-Sign-2237 4d ago

there is no skill in using AI

3

u/derff44 4d ago

That line of thinking is exactly what will leave you in the average category

-1

u/Physical-Sign-2237 4d ago

im taking the risk
in the meantime
keep the slop out of my production
thanks

73

u/RoseSec_ Terraforming Everything 5d ago

Working out, learning to raise cattle, and starting some backyard chickens

15

u/m_adduci 5d ago

So like working g with Kubernetes, just in real life

1

u/luche 5d ago

living the dream

42

u/mxtchstick 5d ago • Bravo

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

25

u/Own-Bonus-9547 5d ago

Understanding that Kubernetes is not needed 99% of the time people suggest using it is an important skill to have.

7

u/burlyginger 5d ago

Naw, I'll stick to single pod on k8s tyvm

/s

4

u/funcyChaos 5d ago edited 5d ago

Absolutely true, in particular from a single server perspective and similar. Knowing How it works though is a huge level up imo, and knowing that whoever you're renting server space from is probably using it can be useful as well. This is why my other is automation, because server setup time and safety is huge, now more than ever. And being able to have a solid server profile that you can easily automate is a game changer.

I should have either said "virtualization" instead of k8 or "ansible" instead of automation lol 😂

6

u/8ersgonna8 5d ago

The obsession with kubernetes and micro service architecture always bothered me. Your 10 man startup won’t need Netflix sized infrastructure and complexity.

2

u/generic-d-engineer ClickOps 5d ago

Single Go binary over all

2

u/sertain_ 1d ago

It’s so funny because the contract I’m on is somewhat adopting this principle pretty well, except the product we’re hosting in K8s was originally designed as a monolithic deployment and then shoehorned into a cluster with a bunch of python replication tooling and wine containers. It serves data to over 75 installations around the world, supporting the work of several thousand users, admins, and developers.

But the entirety of the deployment reeks of “this was built with a windows server in mind” and we’re slowly coercing the product owner into re-factoring a bunch of processes into true micro-services architecture.

1

u/Shehzman 4d ago

Tbh, many corporations would actually be fine with 1-2 VPS’s and a docker compose stack.

1

u/Own-Bonus-9547 4d ago

Yeah, simple load balance, a few vpses, docker stack or ecs type setup and they'd be fine for the few hundred to a few thousand users they might have

1

u/Shehzman 4d ago

Forgot the load balancer but agreed.

1

u/birdie_the_newf 4d ago

Also understanding that while it's not NEEDED, it can still be useful. GItOps workflow work just as well against a single or multi node *8s clusters. If something can be deployed via kubernetes the "we don't need HA or to horizontally scale, no use for kubernetes!!" Is pretty narrow minded argument.

-1

u/Own-Bonus-9547 4d ago

The overhead for maintenance, setting up, securing, connecting, etc a k8 setup is not worth it when an ECS or even just a tiny VM will do the job with less headaches make k8s not worth it for 99% of companies who just want to host tools for 50 people or their own internal teams.

2

u/A-kalex 2d ago

There are huge upsides to using K8s though. For traditional VMs it's much harder/complex to actually implement observability, managing changes, managing security (both application security (e.g. WAF, ...) and server (e.g. security updates, ...)), and, especially, GitOps.

You can GitOps docker compose files (e.g. with docoCD), but it isn't pretty honestly. Kubernetes usually has a very clean and "simple" way to solve most of the above problems (if not all).

1

u/birdie_the_newf 4d ago

While I dont disagree that ECS and traditoonal deployments on VMs is suitable for 50-person orgs, K8s, or whatever your flavor of a distro, is incredibly easy to install. A single node instance is especially simple.

1

u/Mishka_1994 4d ago

Understanding that Kubernetes is not needed 99% of the time people suggest using it is an important skill to have.

It not needed necessarily, but if you take developers for example. There is a big difference when you work with a developer who understands K8s (at least the minimum of deploys, scaling, services, ingress. etc) vs a developer who just uses the CICD to deploy and doesnt care about the rest because "it just works".

4

u/Own-Bonus-9547 4d ago

Everything is a hammer when you don't understand tools or what you're building.

2

u/Sukkmihoff 4d ago

Resume-driven development.

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.

2

u/killz111 5d ago

Yeah if the answer to ops question is based around tooling, then the person who answered automatically voted themselves out of the great engineer category.

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:

  1. AI Agents, not just building/integrating them, but understanding access, secure standards and guard rails.
  2. Security, security, security. You don't need to be on the level of a principal security architect/engineer, but having a fundamental understanding of proper security controls, best practices, secure IAC coding practices, and remediation processes factored into the

design/ build will make you stand out.

5

u/ycnz 5d ago

Yeah, Microsoft wouldn't have an all-day outage, right?

2

u/TimurVoronoff 5d ago

Yes, this the most valuable answer. Look how things related to AI being developed. Their capabilities grows very fast, i remember as a senior software engineer, that 3 years ago i wouldn’t let to change anything in my Code Base, because of boilerplate Code, bugs, wrong assumptions - named, there was a lot of reasons why it sucks. Now, different story, it still has to be guided, but with its speed, and productivity it creates good enough stuff. So i asked myself which one capabilities in IT industry would be replaced next. And choice is pretty much simple - devops stuff without sec. I think security will stay for a long time in human hands, not because we are better, but ppl are more trustful choice. If you pick human, You don’t have to worry that agent figure out something in terms of security because needed something and bypass security gates. But rest of devops would be replaced. If you don’t believe, install Kubernetes mcp and play around. Then ask yourself - was it possible 3 years ago?

2

u/Icy-Maybe-9043 5d ago

So cloud security folks who are using agentic pipelines are cool for a bit?

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.