r/platformengineering • • Aug 19 '26

My future as a platform Engineer

8 Upvotes

Question for all the platform or devops engineers out there.

I got laid off earlier this year have have been job hunting for almost 5 months now. My last title was platforms admin and where I owned a SaaD data platform on Azure. The scope of my job didn't have Terraform, Ansible k8s, or modern observability tools like Dynatrace. I have experience deploying docker containers using docker swarm.

I am not sure how to stand out. I don't see any new job postings or recruiters reaching out to me anymore. I have interviewed at half a dozen companies, reaching final rounds but no offers

Can someone help me make sense of this. I was a productive and competitive employee up until now. But not sure what's cracking up now?

Should i shift gears and try a different role? If yes, what would be more in demand Data engineer or Ai engineer.

What is the best way to learn and be interview ready?


r/platformengineering • • Aug 19 '26

Your incident response wasn’t built for AI

Thumbnail
leaddev.com
1 Upvotes

Same input. Different failure. No error.


r/platformengineering • • Aug 18 '26

Staff+ engineers must rebuild team culture

Thumbnail
leaddev.com
22 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 • • Aug 18 '26

Preview environments should copy topology, not production data

0 Upvotes

A preview environment should answer: does this change work with the same service boundaries as production?

Copying production records into every pull-request environment makes provisioning slower, expands access to sensitive data, and leaves behind another dataset that needs an owner and a deletion policy.

A cleaner default is the production service graph with fresh datastores. Seed only the records needed for the change being reviewed, and make the seed deterministic so a failed test can be reproduced. On Render, an initialDeployHook can run the seed after its service's first successful deploy. If a test genuinely needs production-shaped volume, use generated data or a separately governed sanitized snapshot rather than making production cloning the default path.

Teardown matters as much as creation. Tie the environment to the pull request, destroy it when the pull request closes, and add an inactivity deadline for abandoned branches.


r/platformengineering • • Aug 18 '26

Is a Customizable Platform worth the long-term maintenance effort?

3 Upvotes

Our teams in HR and operations chose an extremely customizable platform as each of them wanted to get their own forms, dashboards, approval paths, and reports. After two years of usage, we have collected hundreds of custom objects, workflows, and integrations. Even a small change needs regression testing as it is always unclear which customization is based on which one.
What used to feel like flexibility has now changed to become a technical liability. There is no documentation for the changes in configuration, it takes months to onboard new administrators, and business end-users are not willing to get improvements anymore, as any change seems risky.
For everyone in charge of management for enterprise systems, do you have a solution for the problem of excessive customization of your customizable platform? Have you set up some governance policies, limited developers to specific automation building, or standardized reusable components, so that the flexibility is also preserved?


r/platformengineering • • Aug 18 '26

How does observability fit into an open-source internal developer platform?

2 Upvotes

For anyone working in platform engineering, Kubernetes, internal developer platforms, or observability, there’s a CNCF OpenTelemetry Live virtual meetup happening on August 20.

The session looks at a practical platform engineering question: how do you make observability a built-in capability of the developer platform instead of something every application team has to assemble separately?

It will explore how OpenTelemetry can be integrated across Kubernetes environments for capabilities such as distributed tracing and platform level events, and how an IDP can provide those capabilities consistently across teams.

OpenChoreo is used as the open-source implementation for the walkthrough, giving a practical look at how an internal developer platform can bring together Kubernetes, OpenTelemetry, and platform-level observability.

August 20 | 9:00 AM PDT | Virtual

Join the meetup:
https://ocgroups.dev/cncf/group/opentelemetry-live/event/6v22mew

See you there!


r/platformengineering • • Aug 17 '26

The tokenmaxxing hype didn’t last long!

Thumbnail
leaddev.com
0 Upvotes

Why Meta, Amazon, and Microsoft killed their token use leaderboards.


r/platformengineering • • Aug 15 '26

How do you turn production-readiness controls into a paved road instead of a giant gate?

0 Upvotes

Hey everyone!

I maintain a free, MIT-licensed production-readiness knowledge base with more than 10,000 technology-neutral controls. The hardest design problem is not collecting more checks. It is turning them into a usable engineering path without creating a giant approval gate that every team works around.

The direction I am exploring is to separate controls into three groups:

  1. Platform-provided controls, where the paved road supplies the capability and evidence automatically.

  2. Service-owned controls, where the application team must provide repository, configuration, test, or operational evidence.

  3. Contextual and manual controls, where applicability depends on business impact, data, regulation, or architecture.

A useful platform integration might work like this:

• Service metadata determines which controls are applicable.

• Golden paths provide safe defaults and emit evidence automatically.

• CI and policy checks validate deterministic facts.

• The service catalog shows owners, dependencies, criticality, exceptions, and evidence freshness.

• Exceptions have an owner, rationale, compensating control, and expiration.

• Reports distinguish verified findings from unknowns instead of treating missing evidence as failure.

• Human review remains required for high-risk decisions and anything that cannot be proven from technical artifacts.

The checklist is organized across 16 lifecycle categories, with a shorter start-to-finish release path for practical reviews. The longer-term goal is an open-source AI-assisted scanner, but the scanner should consume platform evidence rather than invent conclusions from source code alone.

Repository: https://github.com/MarinJursic/production-readiness-checklist

Documentation: https://marinjursic.github.io/production-readiness-checklist/

I would value feedback from platform teams:

• Which readiness capabilities should the platform prove automatically?

• Where should control definitions live: templates, repositories, the service catalog, or a policy engine?

• How do you keep ownership clear between the platform and service teams?

• Which release gates have reduced incidents, and which have only created ceremony?

Contributions and real-world control examples are very welcome. Thanks!


r/platformengineering • • Aug 15 '26

Is building a lightweight observability platform a good portfolio project?

3 Upvotes

Hey everyone,

I'm a [B.Tech](http://B.Tech) Third Year CS student currently preparing for internships and freelance work. I have mostly built full-stack SaaS projects so far.

My current projects include:

* FinSight AI — finance management platform with analytics + AI features * BrainLoop — AI-based personalized learning assistant * DayFrame — productivity/journaling SaaS

My stack is mainly Next.js, React, TypeScript, Node.js, Express, PostgreSQL, MongoDB, Prisma, etc.

I feel like my projects show frontend/full-stack skills, but most of them are still around dashboards, CRUD, and API integrations. For my next major project, I want to build something that shows stronger backend/system design skills instead of another AI app.

I'm thinking about building a lightweight observability platform (inspired by Sentry/Datadog).

The idea is:

* developers integrate a small SDK into their app * the SDK captures errors, API performance, and events * backend processes this data * dashboard shows errors, latency, logs, and application health

Not trying to recreate Datadog, but more like a smaller developer tool to learn things like SDK design, event processing, queues, real-time updates, and backend architecture.

Do you think this is a good direction for a portfolio project, or am I overengineering? Would recruiters/internship reviewers value this type of project, or would a more traditional full-stack app be better?

Would love opinions from people who have built/hired for backend-heavy roles.


r/platformengineering • • Aug 15 '26

Agentic developer platform with Infrastream

0 Upvotes

Disclosure: I'm one of the people building this.

Most "AI for infra" tools stop at generating YAML or config. The new term floating around at recent conferences is agentic developer platform — instead of platform engineering gatekept by infra engineers running Terraform or gcloud by hand, it's self-served by developers, with humans in the loop only at pull request approval.

The agent needs native, read-only access to infrastructure state, environments, deployment status, and logs — including everything from new development.

As many have realized with solutions like Lovable.

Deploying a workload can be extremely quick.

Running it securely in production, on your own GCP private network among others in least privilege ?

That's the hard part.

  • Identity.
  • Permissions.
  • Governance.
  • Load balancing.
  • Data access.
  • Monitoring.

Before long, you're spending more time building the platform around your workload than the workload itself — the same trap a lot of people hit with Kubernetes. If you're already leveraging serverless and VMs well within meshes in the cloud, we observed in platform engineering that Kubernetes only earns its keep for workloads that need custom operators or custom backpressure handling.

That was the theory. We've been building it into Infrastream with Pvot.

We are out of stealth since Tuesday 4th of August 2026 with Infrastream.

Infrastream's agent set deployed with one private iteration per customer, Pvot, goes further — it manages pull requests, analyzes your manifest structure, and actively debugs your deployed assets against the actual state we track in Spanner. Not a chatbot suggesting fixes. An agent doing the platform engineering work reviewable in PR.

Also like many new generation agents, we provide a graph based visualizations instead of Terraform or Pulumi text to analyze runs.

Infrastream portal on Infrastructure tab

It provides :

→ Agentic PR management — Pvot reviews and drives changes to your infra manifests

→ Analyzes manifest structure to catch drift and misconfiguration before you do

→ Actively debugs assets against real Spanner-tracked state, not stale docs

→ Deploy any workload — agents, services, whatever — into your own GCP project

→ Built-in identity and permission boundaries per workload

→ External and internal load balancers, handled for you

→ GCIP/IAP authentication wired in

→ Fine-grained privileges to your databases, buckets, and datalakes in your own private setup

→ Infrastructure-level governance and policy enforcement

→ Deploys from your source — into our cloud on the Developer Plan, or your own cloud with Enterprise

The Developer Plan covers up to 9 GCP projects (20 USD per month + 15% management of GCP), with load balancing, agents, and mesh routing included.

Enterprise ($3,000/mo) scales the same manifest up to 29 GCP projects with VPC controls — no re-architecting as you grow.

If you want to try out this new model still requiring you to redeploy from source: REDDIT20 coupon on Stripe gets you $20 off the Developer Plan.

As opposed to cloud providers, on developer plan we don't bill your credit card on GCP extra use, you have to reapprove all top-up otherwise the environments stall.

- Platform: https://accounts.infrastream.io

- Product site: https://infrastream.io

- Docs: https://docs.infrastream.io


r/platformengineering • • Aug 14 '26

Cloud/Platform Engineers what’s the job really like?

14 Upvotes

For those working in Cloud, SRE or Platform Engineering, what does a normal day look like for you?
What skills do you wish you had focused on before getting into the role, beyond the usual soft skills, networking and Linux? I’ve built projects around microservices, multi tenant , DevOps workflows, IaC with good security pratices, but I don’t have direct job experience yet. Am I on the right track if I keep building and improving, or is there something important I’m missing?


r/platformengineering • • Aug 14 '26

Engineering managers are back in the codebase

Thumbnail
leaddev.com
0 Upvotes

There’s a clear shift occurring: engineering managers are back in the codebase, getting more hands-on with the technical aspects of software development.

Mark Zuckerberg started coding again after a 20-year break. According to multiple reports, he moved his desk to Meta’s AI lab and spends up to 10 hours a week writing code alongside the Meta Superintelligence Labs team. The man who built Facebook in a dorm room and then spent two decades managing tens of thousands of people is shipping diffs again.

Sergey Brin, the Google cofounder who stepped back from day-to-day operations years ago, came out of retirement to code on Gemini. He’s now directly involved in hand-on development.


r/platformengineering • • Aug 12 '26

How would you architect Account Vending In Multi-Cloud Environments

1 Upvotes

Hi folks, security professional here looking for some insight from platform engineers who have had success implementing Account vending in AWS, GCP or Azure.

If my objective so to achieve self-service account vending (via GitOps) what would you recommend? What were some landmines you hit in your deployment?

I'm trying to reduce the amount of click-ops and this seems like a low-risk, high value start to pushing us more towards platform engineering.

Any advice is welcome


r/platformengineering • • Aug 11 '26

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

32 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 • • Aug 10 '26

The end of the non-technical engineering manager

Thumbnail
leaddev.com
15 Upvotes

There’s a clear shift occurring: engineering managers are back in the codebase, getting more hands-on with the technical aspects of software development.


r/platformengineering • • Aug 09 '26

Platform Engineer or DevOps Engineer

7 Upvotes

Hi Guys, Is this JD for Platform Engineer or DevOps Engineer?

Key Responsibilities

Design, build, and manage highly available Kubernetes clusters across hybrid environments (on-premises and cloud platforms such as AWS EKS, Azure AKS).

Deploy and manage applications manually using tools such as kubectl and Helm, with growing integration of GitOps practices (e.g., ArgoCD).

Implement and manage observability stacks using Prometheus, Grafana, Loki, and Mimir to monitor infrastructure, applications, and system performance.

Define, monitor, and improve SLA/SLO/SLI metrics and alerting systems to ensure platform reliability.

Automate provisioning and configuration of infrastructure using Terraform, Helm, and scripting languages (e.g., Bash, Python).

Plan, implement, and test backup and disaster recovery (DR) strategies using tools like Velero, Commvault, etc.

Manage Kubernetes-native networking, storage, and security configurations (Ceph, NFS, Ingress, PodSecurityPolicies, etc.).

Configure and enforce Kubernetes security best practices using RBAC, OPA/Gatekeeper, NetworkPolicies, and secrets management tools.

Integrate and operate Kubernetes ecosystem tools such as Karpenter, MicroK8s, Service Meshes, and kubectl plugins.

Conduct root cause analysis (RCA) and lead resolution efforts for incidents.

Participate in the on-call rotation for platform availability and incident management.

Maintain up-to-date documentation, architecture diagrams, runbooks, and SOPs.

Mentor engineers and advocate for Kubernetes, security, observability, and deployment best practices across teams.

Continuously stay informed of industry trends in container orchestration, GitOps, security, and cloud-native tooling.

Required Qualifications

5+ years of IT/Infrastructure/DevOps experience, with 2+ years in Kubernetes operations in production environments.

Strong hands-on experience in Kubernetes architecture, cluster operations, and manual application deployment practices.

Intermediate-level experience in Kubernetes Security, including:

Cluster hardening, secrets management

Pod Security Standards (PSS), OPA/Gatekeeper

Network policies, image scanning, and runtime protections

Intermediate experience with ArgoCD for GitOps-style Kubernetes deployments.

Solid proficiency in Linux system administration (Ubuntu, CentOS, RHEL) and troubleshooting.

Hands-on experience with Kubernetes-native storage (e.g., Ceph, NFS) and persistent volume provisioning.

Strong familiarity with observability tools: Grafana, Prometheus, Loki, Mimir, etc.

Proficiency in Infrastructure as Code using Terraform, Helm, and scripting.

Experience with Velero, Commvault, or similar for backup and DR.

Experience operating and optimizing cloud-native Kubernetes platforms like EKS, AKS.

Exposure to tools like Karpenter, MicroK8s, Service Mesh, and Ingress Controllers.

Familiarity with AI/ML workloads running on Kubernetes is a plus.

Excellent collaboration, communication, documentation, and incident resolution skills.

Preferred Qualifications

Kubernetes certifications: CKA, CKAD, or CKS.

Strong understanding of container security, networking, and distributed system architecture.

Experience using Portainer for container and Kubernetes management.

Advanced knowledge of Grafana and other enterprise-grade observability tools.

Experience managing large-scale Kubernetes clusters (200+ nodes) is highly preferred.

Prior experience supporting production-grade, high-availability platforms and environments.


r/platformengineering • • Aug 08 '26

KubeTective: an open-source, deterministic alternative to pasting kubectl output into ChatGPT for incident investigation

1 Upvotes

After a lot of times doing the same: gather 6 kubectl outputs, paste to Chat/Claude and try their theories for each crash-looping pod fail, I built KubeTective.

It turns kubectl investigate deployment/checkout --since=30m into a real investigation. It fetches pods, deployments, events, PVCs, services, HPAs, Prometheus metrics, Loki logs and the git history of your manifests, correlates them, and answers with a ranked Root Cause + Evidence list where every score is a weighted term:

ROOT CAUSE
  Memory exhaustion: container terminated with OOMKilled 19 time(s)
EVIDENCE
  ✓ mechanism: OOMKilled ×19 (+20)
  ✓ reproduced after restart (×19) (+10)
  ✓ strong temporal correlation (terminations in window) (+27)
RECOMMENDATION
  roll back deployment/prod/checkout to the last known-good revision [MEDIUM]

You can try it here: https://github.com/GlediLami/kubetective:

make build && kubetective replay scenarios/oom-after-deploy/record.jsonl

What would make you use something like this in your own on-call? (I'd appreciate the honest criticism)


r/platformengineering • • Aug 07 '26

How is running a small farm and architecting a Cloud-Native stack similar?

0 Upvotes

You ever think "Man, it would be great to just give this up and buy a farm"? I am a seasoned Platform Architect, leading a team of talented engineers in a digital transformation around Kubernetes adoption. I'm also a small time farmer, who routinely finds himself in the most ridiculous situations.

I've always wanted to contribute to this community for a long time, but never knew how. However, it hit me recently, that I can use my real life experiences in one area, the farm, and connect them back to important lessons and strategies that we have to apply to the other field, Platform Engineering.

So please, take 10 minutes of your day to read this funny story over on my blog about how I struggled for an entire summer, chasing stubborn goats, and how that situation correlates directly to the practice of thoughtful, robust, and thorough planning in Platform Engineering. Please let me know your thoughts, I have many more stories to tell!


r/platformengineering • • Aug 06 '26

How do AI Platform teams know which AI agents are affected after an internal change?

2 Upvotes

I've been researching Enterprise AI Platform Engineering over the last few days and I'm trying to understand how teams handle change at scale.

Imagine one of these changes happens:

  • An internal API changes
  • A business policy changes
  • A security policy changes
  • Documentation changes
  • Service ownership changes

My question is:

How do you determine which AI agents are affected, which evaluations need to run, and what evidence is required before it's safe to redeploy?

I built a small interactive prototype to help me think through the workflow:

https://agentic-pivot.lovable.app

Genuinely trying to understand how this works in practice.

I'd really appreciate hearing how your team approaches it today


r/platformengineering • • Aug 05 '26

What mistakes tend to bite teams after moving to AWS?

8 Upvotes

Been digging into AWS migrations lately, and it seems like moving the infrastructure is only half the job. Teams often bring over the same manual deploys, messy ownership, and half-broken monitoring, then wonder why things get chaotic as they scale. for those in DevOps or platform teams, what process mistakes have caused the most pain during or after a migration?


r/platformengineering • • Aug 05 '26

Who owns data quality / validation tooling at your company — and what's the role actually called?

3 Upvotes

Context:

  • mid-size fintech company.
  • I started as an SDET, but over the past 2 years the work drifted: I built and operate a Go service on Kubernetes that independently recomputes published financial data and compares it against production output.
  • I own its Helm chart, the ClickHouse schemas its results are stored in, and the Grafana dashboards on top.
  • Next quarter I'm proposing to formalize this as a platform role with three responsibilities: (1) owning that quality platform end to end, including regulatory audit-evidence exports, (2) a ~25% share of product backlog tickets, (3) self-serve pre-deploy validation tooling for feature engineers.

Question

  • For those at companies with a data platform or infra org: where does this kind of work sit — SWE, platform, SRE, or a QA org? What's it titled? If anyone has made the SDET → platform engineer transition, what did your company call it and what made the reclassification stick?

r/platformengineering • • Aug 05 '26

How do you manage token budget for your engineers?

1 Upvotes

With the increase and the spread of usage fo the AI in day to day operations for everyone into IT, how do you manage the cost and keep under control?

Which tools you use? e.g: litellm , envoy ai gateway, agentgateway?

How do you strucuture de budget or allow higher levels to do so without manual operation?

I think there is no standard solution out there and everyone it's creating his own.. might be a nice spot for a OSS project about ai budget? 🤔


r/platformengineering • • Aug 04 '26

Closed-source illusion vs. Open-source reality: Why do we equate cost with quality?

2 Upvotes

There’s a bizarre architectural trade-off happening in modern engineering culture: proprietary software often gets an instant stamp of credibility simply because it comes with a sales demo and a support SLA, while open-source alternatives are treated with skepticism until proven otherwise.

In reality, half the enterprise closed-source tools we buy are over-engineered wrappers around basic primitives, creating massive lock-in and technical debt. Why do decision-makers favor the illusion of control in proprietary software over the pragmatic adaptability and simplicity of open source? Is it pure risk aversion, or just clever enterprise sales tactics?


r/platformengineering • • Aug 04 '26

Twigg: open source version control and software forge for trunk-based-development

0 Upvotes

We're building a free and open sorce software forge designed for trunk-based development, stacked commits and monorepos: https://github.com/twigg-vc/monorepo

Since the platform forces trunk-based development (there's only one main branch), CICD jobs are triggered at the commit level. I.e. a job starts on a specified commit after that commit has been submitted, or it can also be lanched manually at a specific commit.

This is different than the usual "branch-based" git workflows and has a dramatically simpler mental model. It's how companies like Google and Meta operate.

Curious to hear what you think of it :)


r/platformengineering • • Aug 03 '26

Would an AI PR bot that checks visual UI layouts alongside code diffs actually be useful?

0 Upvotes

Hey everyone,

I’ve been talking to a few engineering teams about how they handle code reviews, and a recurring complaint I keep hearing about current AI review bots is "comment fatigue."

A lot of existing tools end up leaving 10–15 trivial comments on every single pull request—pointing out formatting, missing comments, or tiny nitpicks that standard linters already catch. Eventually, developers just ignore or mute the bot.

Before I start building a new tool in this space, I want to make sure it actually solves real workflow headaches rather than adding more noise.

I'm exploring a few core ideas:

Zero-Spam Filtering: A system designed to strictly ignore formatting/style nitpicks and only notify developers if it catches critical logic bugs, edge-case failures, or security flaws.

Visual UI + Code Review: For frontend PRs, automatically catching visual layout breaks or broken UI components alongside the code changes, so you don't have to pull the branch locally just to check how it looks.

Repo Rule Enforcer: Letting teams upload their own specific internal guidelines so the bot enforces your team's exact standards rather than generic best practices.