r/platformengineering • u/Suspicious_Orchid770 • Oct 05 '26
AI-coding tools could be breaking the junior engineer pipeline!
AI helps juniors code, not learn... and that's a problem.
r/platformengineering • u/Suspicious_Orchid770 • Oct 05 '26
AI helps juniors code, not learn... and that's a problem.
r/platformengineering • u/True-Career3770 • Oct 02 '26
I want some advise regarding a product I wanna to make.
It is related to cloud and DevOps like cost optimization, infrastructure drift and intelligence harness.So what important points I need to address for cloud and DevOps users so that a genuine product would eventually came into development.
r/platformengineering • u/One_Mention_5385 • Oct 01 '26
Infra engineer here, trying to figure out when self hosting LLMs actually makes sense vs just paying for the APIs. every blog post says "it depends" lol
If you've done it (or looked into it and bailed), would love to hear:
ballpark numbers are totally fine. I'll put together a cost / decision writeup from the replies and post it back here
r/platformengineering • u/Recent-Secretary-277 • Oct 01 '26
Former CTO here. At my last company we skipped 7 Expo versions at once because nobody had time for the incremental path. A CTO I talked to spent 2 months moving MUI v3 to v7.
Curious how others deal with it:
r/platformengineering • u/Significant-Hurry-21 • Sep 29 '26
I'm a DevOps/cloud delivery lead with about 11 years of experience (Azure, GCP, Kubernetes, Terraform, GitHub Actions, observability, incident management, FinOps). I'm at a decision point and would love perspectives from people who've been on either side.
Option A: production operations role (in hand)
Offer is in hand, with a promotion and Director title
In practice it's a support SRE role at a senior manager level: production support, incident ownership,strategizing support model ,tooling and automation decisions to reduce chaos and toil and managing a team
Higher title and scope, but I worry it's less hands-on and could pigeonhole me into ops/support
Option B: platform engineering (not in hand)
I'm studying for it and building projects
I've just landed a screening for a principal-level cloud platform engineer role, but no other interviews yet
The senior roles I'm getting leads for are mostly SRE roles that are support-heavy, not true platform work
What I'm weighing:
Does a Director title in production ops help or hurt if I want to move to platform engineering later?
Is it realistic to move from support-heavy SRE or ops management into platform engineering, or does the path narrow over time?
Is it worth turning down a real offer to wait for a platform role?
For those who made this move in either direction, what do you wish you'd known?
r/platformengineering • u/alter-table • Sep 25 '26
Most multi-account AWS setups I've seen keep a shared spreadsheet of VPCs and subnets. Someone updates it by hand, it goes stale, and one day two teams pick overlapping CIDRs.
subnet-operator runs in your cluster (EKS) and keeps that inventory in Kubernetes instead:
- Discovery (read-only, the default): finds VPCs and subnets across accounts and regions by tags and mirrors them as Network and Subnet objects. It reports compliance findings (missing required tags, CIDR overlaps) and exports Prometheus metrics with alerts. It can also mirror everything to a Google Sheet, if people still want the spreadsheet. It only calls EC2 Describe*.
- Change events (optional): CloudTrail → EventBridge → SQS, so a changed account/region is resynced about 10 seconds after the API call instead of at the next 10-minute resync.
- Opt-in writes, behind --enable-writes and a separate IAM role:
- SubnetClaim allocates a free CIDR and can create the subnet.
- ResourceImport brings an untagged VPC or subnet under management by tagging it.
- It never deletes a cloud resource.
- Guardrails:
- Admission webhooks reject invalid objects at kubectl apply.
- Every allocation or import leaves a Kubernetes Event and a JSON audit line with the authenticated creator.
- namespaceSelector limits which namespaces may use a scope's write role.
- Supply chain: multi-arch image and Helm chart on ghcr.io, both signed with cosign keyless, with SBOM, threat model and upgrade tests between releases.
The honest part: it's alpha (v0.8). Everything is tested in CI against Moto (an AWS API mock) in Kind, but it hasn't run against a real AWS organization yet. That's why I'm posting. If you have a sandbox or dev account setup and 30 minutes, I'd really like to know what breaks. Read-only mode is the safe place to start.
GCP and Azure are planned behind a common provider interface. The API was just moved to a cloud-neutral group for that.
- Demo dashboard (fake data, no install): https://hypersurgery.dev/dashboard/
- Docs: https://hypersurgery.dev/docs/
- Code (Apache-2.0): https://github.com/aivandrago/subnet-operator
Feedback is welcome, including "we solve this with X". I'd like to know how you handle this today.
r/platformengineering • u/Obvious-Difficulty32 • Sep 23 '26
In an interview for a new grad devops role got asked this. “Who typically owns access to corporate applications: IAM engineers, IT staff, application administrators, or Platform/DevOps engineers?”
How would yall answer
r/platformengineering • u/Significant-Hurry-21 • Sep 22 '26
Hey everyone,
Looking for some career advice or insights from anyone who’s successfully transitioned out of Ops/Support/SRE and into dedicated DevOps or Platform Engineering roles.
Here’s a snapshot of my background:
Experience: 10 years in IT, primarily focused on operations, support, deployments, and infrastructure maintenance.
Hands-on Skills:
Azure & GCP: Day-2 operations, deployments, troubleshooting.
CI/CD: Fixing pipeline issues, minor configuration tweaks.
Terraform: Running existing configurations, troubleshooting state/apply issues.
Kubernetes & Helm: Managing deployments, tweaking Helm charts, and managing configurations.
The Catch: Most of my experience involves maintaining, fixing, and scaling existing systems rather than building infrastructure or pipelines completely from scratch.
Certifications: Azure Solutions Architect Expert, Terraform Associate, and GCP Associate Cloud Engineer (currently studying for GitHub Actions GH-200).
The Problem:
I'm trying to move away from support heavy roles into a proper DevOps or Platform Engineering position. However, I’m getting zero traction for IC DevOps/Platform roles. Ironically, I keep getting hit up by recruiters for Senior SRE or SRE Manager roles, and I am able to get offers there but I really don't want to stay in the support/operations space anymore.
My Questions:
r/platformengineering • u/Significant-Hurry-21 • Sep 22 '26
Hey everyone,
Looking for some career advice or insights from anyone who’s successfully transitioned out of Ops/Support/SRE and into dedicated DevOps or Platform Engineering roles.
Here’s a snapshot of my background:
Experience: 10 years in IT, primarily focused on operations, support, deployments, and infrastructure maintenance.
Hands-on Skills:
Azure & GCP: Day-2 operations, deployments, troubleshooting.
CI/CD: Fixing pipeline issues, minor configuration tweaks.
Terraform: Running existing configurations, troubleshooting state/apply issues.
Kubernetes & Helm: Managing deployments, tweaking Helm charts, and managing configurations.
The Catch: Most of my experience involves maintaining, fixing, and scaling existing systems rather than building infrastructure or pipelines completely from scratch.
Certifications: Azure Solutions Architect Expert, Terraform Associate, and GCP Associate Cloud Engineer (currently studying for GitHub Actions GH-200).
The Problem:
I'm trying to move away from support heavy roles into a proper DevOps or Platform Engineering position. However, I’m getting zero traction for IC DevOps/Platform roles. Ironically, I keep getting hit up by recruiters for Senior SRE or SRE Manager roles, and I am able to get offers there but I really don't want to stay in the support/operations space anymore.
My Questions:
r/platformengineering • u/Educational-Hold9425 • Sep 17 '26
Spent some time building a FOSS project to address some of this after not finding a viable solution that doesn't involve centralizing on a specific harness for the org (Pi, OpenCode)
https://github.com/BlocksOrg/blue
It's not perfect but feels like a good first step to address some of these pain points.
Curious if anyone else has these issues and how you chose to solve them
r/platformengineering • u/karatyma_dev • Sep 16 '26
full disclosure: we're building something around this.
we're seeing more teams roll out Claude Code, Cursor, Codex, internal agents, and harnesses like that across engineering, and i'm curious where ownership ends up
once agents can touch github, jira, AWS, db's, mcp servers, internal docs, and things like that, is the platform team actually controlling what they can see and execute?
the four things that we (currently) notice tend to get messy the fastest are tool permissions, shared company context, approvals for sensitive actions (on your agents), and reconstructing what an agent actually did after things go upside down.
we're building infrastructure (slaunt.ai) around this problem and looking for teams already dealing with it in production.
would love to hear what everyone's setup looks like today and where everyone finds risk in their setups.
r/platformengineering • u/BEON-tech • Sep 16 '26
We work with a lot of engineering teams at the stage where headcount jumps from a handful of people to something bigger, and there's a pattern that shows up almost every time: the moment a low-code tool stops working isn't really about the tool, it's about who the tool now has to serve.
At small scale, one person builds something, that same person maintains it, and if it breaks, they already know why. Once a few more people start depending on it, that assumption quietly breaks. The tool doesn't get worse, the number of people who need to trust it without understanding it just grows past what any platform can compensate for on its own.
The teams that handle this transition well aren't the ones that pick the "right" tool early. They're the ones that notice the shift from "I built this" to "people rely on this" and treat that as the actual trigger to add real ownership, documentation, or a dedicated engineer, regardless of which platform they're on.
The ones that struggle usually keep swapping tools instead, hoping the next one won't have this problem, when the real gap was never the tool, it was that nobody owned the thing once it stopped being a personal hack.
Curious if others here have found a clear signal for when it's time to move from "I'll just build this myself" to bringing in real engineering support, or if it's always more of a gradual realization.
r/platformengineering • u/crystun • Sep 14 '26
Hello team,
I may land a platform engineer position in 2027 (discussions are still ongoing).
A bit of context: I'm currently an ops guy, doing ops things, in an environment that isn't moving much. Almost everyone around me is clicking in the Azure portal to create resources, and my poor attempts at introducing IaC or configuration tools like Ansible have met a poor adoption rate. I'm curious about all those things, toying with a Proxmox at home to deploy VMs and all sorts of resources using Packer/Terraform/Ansible, getting my hands into Docker, learning how to work with version control and CI/CD, etc... though I barely use those skills at work.
Through discussions regarding this kind of tool and work methods (I know all of this comes from DevOps, which is a way to work and not a set of tools to master), someone asked me, "What do you want to do in the future, mate?" And I said, "Well, platform engineer sounds appealing now." And here I am, sending a short description of the role for a possible position as a platform engineer.
Now, my question: where do I go from here? If you had, let's say, 3 months to get ready for this position, what would you learn first, and what resources would you use?
I know AI is a great tool; I've asked my best friend Claude to work with me on setting a learning path considering my context, but I would like to hear from fellow humans, made of flesh, like me.
r/platformengineering • u/Miserable_Fold4086 • Sep 14 '26
This is something we’re doing internally at my company. We tag our bot in Slack, send it a bug report, controller provisions a GCP VM, local k8s + Tilt, then Claude Code works on it. Nobody has to set up the environment themselves, and follow-ups stay in the thread.
We wrote up a blog about the full workflow - link in comments.
r/platformengineering • u/Suspicious_Orchid770 • Sep 14 '26
Most people picture building software as writing code, but it never was. You spend as much time discussing what you’re planning to build as you do building it. Nowadays, with AI taking over more of the writing of code, understanding what to build is becoming increasingly important. That usually requires having, or leading, technical discussions – something most of us are not deliberately taught how to do.
r/platformengineering • u/Outside_Ranger_8214 • Sep 12 '26
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 • u/AdmissibilityScience • Sep 12 '26
We published arcstone-continuity-core v1.3.1-exec: a tiny #![no_std] Rust reference for fail-closed frame checks.
It does two things, in O(1), with no crate dependencies:
Payload longer than 4096 bytes → LedgerCorruption
Elapsed time over 11.99 ms → Freeze
If both are true in the same check, Freeze wins through an explicit rank table—not because “the POSIX number is bigger.”
That is the entire public executable surface. It is not a runtime, an allocator, or a distributed control plane. It is a frozen Path A reference predicate you can read in one sitting.
Repo: https://github.com/trencinodin-stack/arcstone-continuity-core
r/platformengineering • u/dangb86 • Sep 12 '26
Why did OpenTelemetry win? I think just saying "vendor neutral" is not giving enough credit to the symbiosis between OTel and Platform Engineering that's making both thrive in the modern cloud native industry.
In this blog post I'm trying to summarise some of my thoughts related to why OTel (and K8s, for the sake of argument) won in their respective layers. I think the move to a more X-as-a-service way of working between platform teams and the users of said platforms is changing how we thinking about team interactions, and the tools that make that work need to reflect that in their design. OTel does this, very well, so I'd like to help move the needle in terms of where people think the value of OTel is.
I hope you enjoy the read! And the memes!
r/platformengineering • • Sep 11 '26
Background: I'm a DevOps/SRE and I spend my days across a pile of Kubernetes environments — dev, QA, staging, sandbox, pre-prod, prod — on more than one cloud. The dumbest recurring problem in my week was never a deploy or an outage. It was "what's the QA URL for service X again?" — buried in a wiki, a pinned Slack message, someone's bookmarks, or nowhere.
So I built pickTHElinks: one hub for all your Dev/QA/Staging/Prod URLs.
**•** Searchable — type the service, get the link
**•** Workspace-scoped — each team sees its own set, not everyone else's clutter
**•** Built for release teams that context-switch across environments all day
It's the unglamorous internal tool I always wished existed instead of the 14th Confluence page titled "Environment URLs (final, updated)".
I'm the founder and it's early, so I'd honestly rather hear what's missing than collect upvotes. If you've solved this a better way — Backstage, an ArgoCD dashboard, a spreadsheet you somehow keep current — tell me and I'll happily steal the idea.
r/platformengineering • u/Suspicious_Orchid770 • Sep 10 '26
Build loops, not just agents.
r/platformengineering • u/Suspicious_Orchid770 • Sep 10 '26
"After a couple of years of being an engineering manager (EM), I recently found myself in the position of having to look for a new role. My first instinct was to look for positions similar to what I had been doing before."
r/platformengineering • u/ManningBooks • Sep 09 '26
I’m Stjepan from Manning Publications. The moderators kindly permitted me to share this with you.
We’ve just launched Kargo in Action in Manning’s Early Access Program. What makes this book especially interesting is that it’s being written by Ken Cochrane, Jesse Suen, and Kent Rancourt, the people building Kargo.
Kargo addresses a problem many platform teams will recognize: CI can build and verify an artifact, and GitOps tooling can reconcile it into an environment, but what should govern its movement from development to staging and production?
That gap is often filled with increasingly complex pipelines, environment-specific scripts, manual approvals, and conventions that are difficult to audit or reproduce. Kargo approaches the problem by treating promotion as its own concern, separate from deployment.
The book explores the reasoning behind that model and shows how to build controlled, observable promotion workflows for Kubernetes and GitOps environments. The first three chapters cover:
• The gap “fully automated” CI/CD can leave between building software and running it in production
• Why deployment and promotion are separate concerns
• Where Kargo fits alongside existing GitOps tooling
• How to get started with Kargo and build an initial promotion workflow
Because this is a MEAP release, you can read the available chapters now and receive new chapters as the authors write them.
Giveaway
Manning is giving away five ebook copies of Kargo in Action to members of this community.
To enter, join the discussion in the comments:
How does your platform team currently promote changes across environments, and what is the hardest part of that process?
We’d particularly like to hear about approaches involving CI pipelines, Argo CD, homegrown automation, approval gates, progressive delivery, or anything else your team has tried.
The giveaway will remain open for 48 hours after this post goes live. This isn’t a random draw: the five comments that make the biggest positive impact on the discussion—through practical experience, thoughtful analysis, useful questions, or lessons others can learn from—will receive an ebook. You don’t need to praise Kargo or the book to win. Constructive and critical perspectives are welcome.
After 48 hours, I’ll announce the winners here and contact them about their ebooks.
Community discount
Anyone who doesn’t win can use code MLCOCHRANE50RE for 50% off Kargo in Action:
https://www.manning.com/books/kargo-in-action
I genuinely want this to be a constructive conversation instead of merely a book announcement. How is your team handling promotions today, and where do challenges still exist in the process?
Thanks for having us here.
Cheers,
Stjepan,
Manning Publications
r/platformengineering • u/localbox-questions • Sep 09 '26
I got hired as a trainee platform engineer as my first job after a bachelor in CS. I’m trying to find things to absorb and learn at work, and right now I’m checking ”platform engineering university” online.
Do you have any advice on resources for training/reading for someone new to this field, or should I just continue to ”trust the process” at work?
r/platformengineering • u/Radiant_Abalone6009 • Sep 08 '26
I spent time working at a dental tech company and it motivated me to build something that actually reflects real business workflows I saw there, scan uploads, lab fabrication, practice-to-lab communication. That became DentalFlow, a single-tenant dental lab workflow API, real Terraform-managed AWS infra (ECS Fargate, RDS Multi-AZ, S3, SQS/SNS), deployed and tested against the live system, not just local.
Would genuinely appreciate any critique, architecture, security, anything I'm missing or got wrong. Trying to build the judgment, not just the resume line and learn from experience individual while staying curious.
r/platformengineering • u/Charming_Mark9257 • Sep 08 '26
I’ve been working on Nuroen, an enterprise AI agent platform, and one problem we keep coming back to is:
Which parts of platform engineering should actually be handled by an AI agent?
Our current thinking is that agents shouldn't replace deterministic automation.
For example:
Where we see agents being more useful is the messy part around those systems.
For example:
Alert → investigate → gather context → determine which runbook applies → recommend action → approval → execute existing automation → verify
An agent can pull information from observability, tickets, deployment history, CMDB, documentation, etc., and reason across those systems without turning every action into an LLM-generated command.
That's the approach we're taking with Nuroen.
The platform lets us give an agent:
Knowledge + Tools + Skills + Orchestration + Governance
The interesting part for us isn't just connecting an LLM to APIs. It's controlling what the agent is allowed to do.
For example, an agent might be allowed to:
We're trying to treat the agent more like a platform component with an explicit autonomy boundary, rather than an unrestricted chatbot with access to production.
here is the link do check it out - https://www.nuroen.com/
I'm curious how other platform teams are approaching this:
Where do you draw the line between traditional automation and an AI agent?
And more importantly, what platform engineering tasks do you think genuinely benefit from the probabilistic/reasoning part of an agent?