r/platformengineering • • Oct 16 '26

DevOps is cooked.

312 Upvotes

Hear me out...

When I first saw the movie The Matrix, in the early scene where Neo is called into his boss's office and told that if he behaves well, he has a future at that no-name Corp., or otherwise he'll be fired, I joked and laughed, like, "Yeah, sure, a tech professional could just walk out into the opposite building, and they would beg him to join since everyone is looking to hire engineers."

Today, this scene is closer to reality than I'd like to admit. I personally know Senior DevOps engineers who are solid folks, and it took them 8 months to land a job at a salary that sucked. Our industry is not regulated, the barriers to entry and outsourcing are being lowered by AI, and we have a massive oversupply of engineers. This is just a reality.

Before tech, I worked in another industry that also experienced a major decline. I saw it coming and made a decision at the right time, before it became obvious. I moved to tech years ago and was lucky enough to become a staff engineer. Now I see the same pattern. I think we have 5 to 10 years before salaries in this field will be $70k-$80k for Senior Engineers in the US (which is around a 2x decline) you can do the math for other countries.

My advice is work on a backup plan now. Invest, save, but also learn a trade. I'm studying medicine this year. Fuck it. Six years of study while working remotely, and I'm opening my own dentistry clinic. I'm in my late 30s, but it's still better to have a plan. My wife is also changing careers to become a registered nurse.

This is my plan. You might think of something else, but my point is that it was a good ride. We did a lot of nice work and, IMHO, got easy money, but it's over, and it's time to move on.


r/platformengineering • • Jan 15 '26

We struggle to hire decent DevOps engineers

158 Upvotes

Idk if this is as widespread but I work for fairly large org and we struggle to hire competent engineers. Our pay (EU) is not a match to US colleagues but still fair around 110-115k EUR base and for that I'd expect some decent candidates.

Out of 100+ candidates you can throw to the bin 80 easily.. you get all sort of random candidates, marketing folks, hr, fresh grads, bootcamp folks all applying to a Senior DevOps role.

Remaining 10-15 .. those will look like Principal engineers on resume but will fold on first question like "can you explain what is systemd and when you'd use it".

We really end up with 3-4 decent candidates eventually. Usually those guys already work somewhere asking above our budget and Rightfully so.. and already have multiple offers/options.

So I don't get all this market is bad thing.


r/platformengineering • • Jan 17 '26

How a good job ad in tech should look like in 2026:

Post image
105 Upvotes

r/platformengineering • • Feb 22 '26

We need more of this

Post image
77 Upvotes

r/platformengineering • • Mar 19 '26

Top 15 DevOps tools that are mentioned on Linkedin Job posts in 2026

Post image
75 Upvotes

The source is hidden to avoid promo/self-promo.


r/platformengineering • • Mar 08 '26

Tech job market at its highest since recession

Post image
60 Upvotes

data: FRED and TrueUp


r/platformengineering • • Dec 07 '22

Cloud Technology Cheat Sheet (translating service names)

Post image
60 Upvotes

r/platformengineering • • Sep 03 '26

Engineers grieve a job that no longer exists

Thumbnail
leaddev.com
56 Upvotes

Something is happening in engineering teams that doesn’t show up in sprint velocity or deployment frequency. It shows up in resignation letters.


r/platformengineering • • Feb 14 '26

OpenShift > Kubernetes if your goal is Money

52 Upvotes

Hey,

I'm working as a consultant and recently realized that rates for Openshift are 20-30% higher on average than rates for the Kuberentes. I think K8s getting commoditized and OS is way better niche if you are after money.

Do you know any other "hacks" to get into specific niche or fat hourly rate?


r/platformengineering • • Aug 23 '26

My job title is "Platform Engineer". Buut what the heck is a platform eng?

47 Upvotes

From what I read online, it sounds like a combination of dev ops + some internal tools to make developer lives easier.

So far, most of what I do is just backend work and a couple of self-serve features that reduce the friction of inter-departmental communication/requests.

I'm not building platforms to make developing code easier or for to help developers run their own code. Not a of docker or kubernetes or things like that that I find when I google "what is a platform engineer?"

i've asked AI, but it'll just agree with enough of my skepticism that it makes its answers unreliable.

The most dev-opsy thing I do is maybe update a terraform file or make tweeks to the testing we run on CI.


r/platformengineering • • Mar 26 '26

GitHub Copilot will train on your code by default starting April 24

45 Upvotes

I noticed this message today:

On April 24 we'll start using GitHub Copilot interaction data for AI model training unless you opt out, so starting from end of April, your prompts, code snippets, and context will be used to train their models by default.

They excluded enterprise users, but everyone else is included automatically. I personally don’t want any of my chats or codebase to be used to train their or any other model. I think this is a shitty way of conducting business, as they opted everyone in and not everyone will be checking their GitHub account to notice that.

Imo such things should have a hard Agree or Disagree prompt, and unless explicitly agreed, users should not be opted in. But hey, I’m not surprised, given they’re digging themselves into a hole with their shitty AI.. anyway just be aware of this.


r/platformengineering • • Aug 11 '26

Is "platform engineering" just DevOps with better branding, or is there a real difference?

34 Upvotes

I've been in enough job specs, conference talks, and internal debates over the last year to notice a pattern: half the "Platform Engineer" postings I read are describing exactly what a senior DevOps Engineer already did five years ago. The other half are describing something genuinely different: a dedicated internal product team building paved roads and self-service tooling for other engineers, with its own roadmap and its own users (the org's own devs).

I don't think this is just semantics, but I also don't think the distinction is as clean as the conference talks make it sound. Genuine question for people who've actually sat in both seats, not just read the thinkpieces:

Where do you draw the line? A few candidate answers I keep going back and forth on:

●      DevOps is a set of practices/culture (CI/CD, IaC, shared ownership of ops); platform engineering is a specific team/role that productizes those practices for internal consumers. Under this framing, "platform engineer" isn't a rebrand. It's what you call the person once the team gets big enough to need a dedicated builder instead of everyone doing their own DevOps.

●      Platform engineering is what happens when "you build it, you run it" quietly failed at scale, and someone had to become the paved-road team so product engineers could stop reinventing Terraform modules badly.

●      It's mostly branding, and a lot of "Platform Engineer" postings are just "Senior DevOps Engineer, but the title tests better in this hiring market."

What's made me second-guess my own take: at companies under maybe 40-50 engineers, I've basically never seen a real separation. It's the same 2-3 people doing both, and "platform engineering" there is just a slide in a deck, not an org reality. It seems to only become a real, distinct discipline somewhere past that scale, and I'm not sure where.

Curious where people who've actually lived through the transition, either building a platform team from scratch or watching DevOps quietly get relabeled, land on this. Real difference, or mostly vibes and a better-selling job title?


r/platformengineering • • Jan 13 '26

January 2026 job Market Trends

34 Upvotes

Hi Everyone,

I did analysis of recent job market trends (North America, Europe, Asia). I took 500 job posting from LinkedIn for Platform Engineer, DevOps, SRE titles and made a list of tools that were mentioned most of the time:

Format is: Tool Name (% of mentioned jobs/500) (% change since last 3 months)
hope this helps.
---

AWS 71% (-5%)

Python 70% (+1%)

Terraform 69% (-7%)

Kubernete 65% (-1%)

Docker 53% (+1%)

Bash 47% (+2%)

Azure 45% (-1%)

Jenkins 42% (+2%)

Ansible 38% (-6%)

GCP 31% (-1%)

CloudFormation 29% (+4%)

Linux 27% (-4%)

GitHub Actions 27% (-1%)

Grafana 26% (+2%)

GitLab 24% (0%)

Prometheus 24% (-3%)

PowerShell 23% (+5%)

Git 21% (-7%)

GitHub 16% (+3%)

ELK Stack 15% (0%)


r/platformengineering • • Oct 07 '26

A reflection on the future of platform engineering

33 Upvotes

I think the history from traditional Ops to DevOps and then Platform Engineering is best understood as a dialectic driven mostly by technological change.

Traditional Ops concentrated infrastructure knowledge in a specialised team because operating infrastructure required direct administration. Automation, cloud and infrastructure as code changed that. DevOps emerged as the antithesis: operational ownership could move closer to development teams.
The operational work did not disappear, though. Much of its complexity was simply redistributed to developers.

Platform Engineering became the synthesis once cloud APIs, declarative systems and orchestration made it possible to encode operational knowledge into software and expose it through self-service. Operations could specialise again without returning to tickets and manual handoffs.

This is why I do not think the conceptual distance between the old sysadmin and the platform engineer is that large. The function is broadly similar. What changed was the technology through which that function could be organised and delivered.

AI may now be starting the next movement in the same dialectic. Agents do not necessarily need portals, fixed workflows or abstractions designed primarily for humans. They can discover tools, combine APIs and construct their own path through a system.

But this does not remove the need for a platform. It changes what the platform must provide. Instead of defining only human-oriented golden paths, it increasingly needs to expose machine-readable contracts, capabilities, relationships, constraints and evidence.

The next stage of Platform Engineering may therefore be less about building interfaces that hide complexity from developers, and more about defining the operational space within which agents can act without having to guess.


r/platformengineering • • 13d ago

Our coding agents went from ~65 to ~700 PRs a week, so we moved CI to our own server

Thumbnail
brunoj.com
31 Upvotes

r/platformengineering • • Sep 06 '26

Built a 3-node Talos Kubernetes homelab

Post image
31 Upvotes

I wanted a small environment where I could experiment with the parts of platform engineering that are harder to appreciate in a local single-node cluster, especially networking, HA, failure handling, GitOps, observability, storage, upgrades, and security.

So I built a 3-node bare-metal Kubernetes homelab using Talos Linux on refurbished mini PCs.

The setup includes:

  • 3 control-plane + etcd nodes

  • a shared Kubernetes API VIP for HA

  • DHCP reservations for predictable node IPs

  • per-node Talos machine configs

  • workloads scheduled on the control-plane nodes

  • failure testing by taking a node offline and verifying the API stays reachable

I documented the full setup, including the network design, Talos installation, config generation, bootstrap, validation, workload testing, and HA checks.

Everything is in the repo: https://github.com/prateekjaindev/homelab

Blog: https://blog.prateekjain.dev/building-a-3-node-highly-available-kubernetes-homelab-with-talos-linux-0372066fe49c?sk=4c66cf9181999f9db19ac3aacabcd8e8

I’m planning to use this next for Argo CD, Gateway API, observability, storage, secrets, and more platform-engineering experiments.

Would be interested to know what others here are using for their local platform engineering labs.


r/platformengineering • • Sep 12 '26

I built a FREE website to learn platform engineering concepts

28 Upvotes

I have built hamchops.com, for now it is completely FREE

It's a micro learning app focused on concepts that uses spaced repetition for reviews

Any feedback is welcome


r/platformengineering • • Feb 04 '26

Best books on Platform Engineering

25 Upvotes

I have some list here:
- TCP/IP Illustrated vol 1 Protocols
- Designing Data Intensive Applications
- SRE Book by Google
- Linux Programming Interface

anything else?


r/platformengineering • • Dec 22 '22

Deployment Patterns

Post image
25 Upvotes

r/platformengineering • • Aug 24 '26

What am I missing about Crossplane

24 Upvotes

I try to treat new tooling with a healthy dose of skepticism, being wary of jumping on things has served me well over the years. So it's a genuinely weird feeling when a tool's value is obvious to me in five minutes, and Crossplane is the first one in a while that confounds me.

When I first saw Terraform the problem it solved was immediately obvious.  HCL is not without its faults, but it sits in a useful middle ground between something like YAML and a full programming language. Drift is the one problem I've never seen solved cleanly, but adding friction to fight it (review/plan gates, etc.) gets you most of the way there. Not perfect, but controllable.

Terragrunt solved the "apply everything" problem by letting you split dependencies into independently-applicable DAGs. Made immediate sense.

On Pulumi. I don't personally believe general-purpose programming languages are the right abstraction for describing infrastructure, but I get the appeal: it's an escape hatch from HCL turning into a minefield as things scale.

Crossplane is where I'm getting stuck. To run it in production you generally need a Kubernetes cluster, which people often stand up with. Terraform. Then there's templating. Using Crossplane in practice seems to mean also standing up Helm or Kustomize on top of it. Adding a single new variable feels far more convoluted than the equivalent in Terraform. And once you need any real logic, you're reaching for Go to write a custom function/provider, which slows the whole loop down even further.

And yet, everyone who's actually used it in anger seems to swear by it. Which makes me suspect that I'm missing some context that makes all of the above worth it once you're in that world.

So, genuinely: what I am not getting about Crossplane? If you have any YouTube videos, short-form content, or articles that made it click for you (beyond the official docs), I'd appreciate the pointers.


r/platformengineering • • Aug 25 '26

Are we building Internal Developer Platforms at the wrong abstraction level?

23 Upvotes

I've been thinking we might be approaching Internal Developer Platforms from the wrong abstraction level.

The move from traditional Ops to DevOps to Platform Engineering looks, to me, mostly like a consequence of technological change. Traditional Ops concentrated operational knowledge in a specialized team, because operating infrastructure required direct, manual administration: the thesis. Automation, cloud, and infrastructure as code changed that. DevOps pushed operational ownership closer to development teams: the antithesis. Platform Engineering became the synthesis once declarative systems and orchestration made it possible to encode that operational knowledge into software and expose it through self-service.

AI might be starting the next turn in that cycle. Agents don't necessarily need portals or predefined workflows because they can discover capabilities, combine APIs, and construct their own path through a system. That doesn't make platforms less important. It changes what they need to expose.

Instead of only providing golden paths for developers, platforms increasingly need to expose machine-readable capabilities, contracts, relationships, constraints, and evidence.

Which raises a question: should all of that knowledge live inside the platform? Maybe not. Maybe the service should own its operational contract, while the platform provides the capabilities to act on it (decoupling the contract from any particular IDP, Kubernetes setup, or deployment tooling underneath).

This is the direction I've been exploring with a side project (Pacto): not another IDP, but a contract layer above them. I'm not sure it's the right abstraction yet, but making the operational model portable feels more interesting to me than building another platform around it. Thoughts?


r/platformengineering • • Aug 18 '26

Staff+ engineers must rebuild team culture

Thumbnail
leaddev.com
23 Upvotes

A year or two ago, the engineering/cross-functional team was a tight-knit, high-performing group. We had one or two goals we all worked on each sprint and we broke down work so that we could operate in parallel.

When someone was stuck and needed help, there was always somebody ready to jump to their aid and keep them moving. Team meetings were upbeat, fun, and productive. We were regularly paying down tech debt while our experiments gathered data. The vibe was helpful and collaborative.

Now, thanks to AI, we are shipping more than ever. We have as many goals every sprint as engineers. Rather than parallelizing work on one feature or experiment


r/platformengineering • • Dec 16 '25

Moving from software to platform engineering

23 Upvotes

Has anyone made the shift from software engineering to platform engineering? I’m curious as to the reasons why and what was done to make that transition.

A few reasons for switching I can think of:

  • higher salaries

  • less risk of AI replacement

  • more immune to the recent software layoffs

  • interested in end-to-end delivery

  • want to work on internal facing products rather than external

And things that I think would be important to learn:

  • Terraform

  • Kubernetes

  • containerization

  • CI/CD

  • public cloud

Anything I missed from my lists? Would love to hear about some of your experiences.


r/platformengineering • • 25d ago

[Hiring] SRE / Platform Engineers, remote US/EU/APAC: Go operators, multi-cloud Kubernetes, core banking

22 Upvotes

I'm the hiring manager for the SRE / Platform team at FIS Modern Banking, and I'm hands on: I write code and ship to production every week, and most recently that's been operators, cluster networking fixes and observability. When something breaks in prod, I'm in it with the team. The technical interview is with me and the team (small team).

We're building the global infrastructure under FIS's next generation of core banking. If it's down, people don't get paid and cards get declined, so reliability isn't a nice-to-have here.

It runs on AWS, Azure and GCP. That doesn't mean a separate copy in each cloud: it can run as one system spread across all three, so if a whole cloud goes away, the bank keeps running. We set recovery targets in minutes for that kind of failure, and a big part of the job is building the drills that prove them.

Some of what the team has built or is building right now:

- Kubernetes operators that run the stateful core of the platform: databases, credentials, backups and restores, reconciled continuously instead of run once and forgotten.

- Disaster recovery for the ledger, with continuous replication, verified backups and restore drills on a schedule.

- Autoscaling that works across clusters and clouds as one fleet, instead of each cluster scaling on its own.

- Networking across clouds and regions, plus the controllers that fill the gaps the cloud providers leave.

- A control plane for production operations, where every action is a signed, reviewed and audited command.

- Verification that, after a failover, every financial transaction is accounted for across every system it touched, with the evidence to show a regulator.

Everything is declarative and goes through GitOps. Observability is built in from the start, and every alert has a runbook.

You don't need to have done all of this. I'm looking for people who are strong in at least one of these areas:

  1. **Go and Kubernetes operators:** you've written controllers, you understand reconciliation, and you've debugged a finalizer that wouldn't let go.

  2. **Platform engineering:** Terraform, Helm, GitOps, and you care about what actually renders and what drifts in production, not just what passes CI.

  3. **Networking:** CNI, routing, cloud interconnects, DNS. If you've chased a packet across clouds, I really want to talk to you.

Multi-cloud experience is a big plus but not a requirement. If you're strong in one area and curious about the others, you'll learn the rest here quickly.

You'll own real production systems from day one, with real customers and real money moving through them. The team is small, so what you build ships and gets used.

**The practical stuff:**

- Location: remote, across the US, Europe and APAC

- Level: senior, open to staff for the right person

- Type: full-time

- Interviews: one technical interview with me, then a chat with HR about compensation and logistics. That's it.

- On-call: we're moving to follow-the-sun, which is why I'm hiring across three regions. Until each region is staffed, we share an on-call rotation. Every hire in a new time zone takes nights off the rotation for everyone.

If this sounds like you, DM me. A link to something you built or a short note on an incident you debugged is worth more to me than a CV.


r/platformengineering • • Mar 25 '26

Platform Engineering / DevOps transition

22 Upvotes

Hi everyone,

I have a background in software engineering and technical project management and I’m trying to transition into Platform Engineering / DevOps.

I’m currently planning a 3–6 month roadmap (cloud, CI/CD, Kubernetes, basic platform tooling) and I’m also considering a bootcamp to build a portfolio.

I’d appreciate any suggestions for:

• Specific Platform Engineering / DevOps bootcamps or courses (preferably online or EU‑friendly) that include hands‑on projects and a certificate.

• Which certifications (e.g., cloud‑DevOps, platform‑focused, or vendor‑neutral) are taken seriously in Platform Engineering roles.

• Whether paying for an intensive bootcamp is worth it versus a cheap or self‑paced course + strong personal projects for someone with my background.

Any recommendations (courses, programs, or even “red flags” to avoid) are very welcome.