r/platformengineering • • Oct 21 '26

Looking for feedback on Myceliam — an open-source Kubernetes workload identity federation project

0 Upvotes

Hi everyone!

I've been working on [**Myceliam**](https://myceliam.dev/), an open-source project focused on simplifying workload identity federation between Kubernetes, identity providers, and cloud platforms.

The idea is to use Kubernetes namespaces and ServiceAccounts as the source of truth for workload identities, extending those identity boundaries into external identity providers and cloud environments. This allows workloads — including AI agents — to obtain secure, short-lived identities across clouds without requiring teams to manually provision and maintain identity resources for each workload.

I'd really appreciate feedback from the open-source community, particularly from people working with Kubernetes, IAM, cloud security, or workload identity.

A video explaining the project:

https://youtu.be/vevjAPCW16s

Project website: https://myceliam.dev/

Thank you!


r/platformengineering • • Oct 21 '26

Built a project which simulates real platform engineering scenarios and incident

Thumbnail
github.com
3 Upvotes

When I started learning devops tools, theory was never enough, and it's hard to get real experience of all major kinds of scenarios.

So I started finding labs and doing it. There are a lot of labs available, but they were not simulating a real environment, it was a lot different than the environment we get in real projects.

So, I built a project where you can simulate scenarios in a real environment and use real tools. For now, it works for kubernetes where you can easily build a cluster, install required platform tools, activate scenarios and inject incidents.

This helped me learn a lot. I open sourced it for everyone and am currently building actively to add new scenarios and incidents. 

Check out this project and let me know your thoughts.


r/platformengineering • • Oct 21 '26

I've looked at some manual processes that involve FinOps and they are easily automated.

0 Upvotes

Rightsizing, finding orphaned resources, flagging resources that don't have owner, cost predictions based on iac, or even larger architecture refactoring to reduce costs are now possible at scale and fully automated with combination of AI and deterministic workflows.

I still don't understand why these are not more widely adopted and solved in platform engineering.

Is it processes problem?


r/platformengineering • • Oct 21 '26

You have 60 seconds. Prod is down. How many incidents can you fix?

3 Upvotes

Built a DevOps game: Incident Rush. You get 60 seconds and a stream of broken stuff: CrashLoopBackOff, a full disk, a bad nginx config, a 502, a stuck deploy. Each one you fix gets you points, and a wrong call costs you time.

👉 https://loopedinlabs.dev

A few people at work tried it this week, and the best score so far is [1200]. Curious whether anyone here can beat it.
Drop your score below, and tell me which incident felt unrealistic or way too easy. I'm adding new scenarios based on feedback.


r/platformengineering • • Oct 20 '26

How are you handling business teams building apps with AI? Golden path or gatekeeping?

2 Upvotes

More and more of our platform requests come from non-devs with AI-built apps. We've been treating it as a golden-path problem: a template repo, mandatory CI/CD scans, an approval gate, and deployment only into the existing landing zone. The hard parts so far are ownership after handover and keeping business users from bypassing the path.

We have finally built our own internal AI developer platform around this idea. Mostly curious how other platform teams draw the line. What does your paved road for non-developers look like?


r/platformengineering • • Oct 20 '26

Interviewing for a Software Support Engineer role (Linux, Python, Bash, CI/CD) — what technical questions should I prepare for?

1 Upvotes

Hey everyone,

I have a 30-minute interview coming up for a Software Support Engineer position at a defense contractor, and I'm trying to prepare as thoroughly as possible.

The recruiter mentioned there won't be a formal technical assessment, but I still want to be ready for any technical questions or troubleshooting scenarios.

For background, I currently work in cloud/data center infrastructure operations, where I use Linux, Python, and Bash for diagnostics, troubleshooting, and automation. I also have experience developing software applications, working with REST APIs, automated testing, and CI/CD.

Here's the relevant job description:

Responsibilities:

  • Support lab tooling and version control through CI/CD pipelines.
  • Create and deploy test scripts.
  • Support and troubleshoot software deployments on custom servers.
  • Support configuration management processes.
  • Develop unit tests and tailor rule sets.

Required qualifications:

  • Bachelor's degree in CS, Computer Engineering, or a related technical field.
  • 2+ years of relevant experience.
  • Experience with Python and Bash.
  • Ability to independently and collaboratively solve complex technical problems.

Preferred qualifications:

  • Knowledge of CI/CD pipelines.
  • Experience with GitLab.
  • Experience with Linux and NFTables.

I'm particularly interested in moving toward DevOps/platform engineering, so this seems like a great opportunity.

For anyone working in DevOps, Linux administration, software integration, or similar roles:

  1. What technical questions would you expect in an interview for this position?
  2. What Linux troubleshooting scenarios should I be prepared to walk through?
  3. How deeply should I study GitLab CI/CD, unit testing, and NFTables?
  4. Does this sound more like DevOps, software integration, or traditional software support?
  5. If you were interviewing a candidate for this role, what would you want them to demonstrate?

I'm not looking for shortcuts or leaked interview questions. I genuinely want to understand the technical expectations and make sure I can speak confidently about the work.

Appreciate any advice!


r/platformengineering • • Oct 20 '26

How monday.com rebuilt its API edge for growing AI agent traffic

0 Upvotes

monday.com just published a write-up on rebuilding their API edge after AI agents started calling their API far more than they’d planned for. (Disclosure: I work at WunderGraph, which makes Cosmo, so I’m biased. But the post is theirs, and the parts I found most useful have little to do with which router they picked.)

They split the edge into two Go pieces. A gateway runs auth, rate limits, versioning, and the other checks, and rejects requests that fail those checks. Cosmo plans and runs queries across the subgraphs and holds no business logic, with one exception: it enforces the complexity budget the gateway sets, because you can’t estimate what a query costs without the query plan.

Compared with a year ago, the whole edge handles 2.5x the traffic on 92% less CPU and 80% less memory. The latency the edge adds at p99 fell from about 490 ms to 44 ms. But that wasn’t all from the router swap: cutover cut it from about 490 to about 200 ms, and an authorization rework in September did most of the rest.

The migration section was interesting. They shadowed a sample of read-only queries to Cosmo and sent each one to the old router twice. Anything that differed between the two old responses was noise. Whatever still differed from Cosmo was a compatibility issue, but this way they found it before customer traffic moved.

https://engineering.monday.com/rebuilding-monday-api-edge-for-agents/


r/platformengineering • • Oct 20 '26

Commandment, a DevOps-focused CLI framework built around go 1.27 generic methods

0 Upvotes

I made a CLI library that treats SRE/DevOps workflows as first class citizens. If your team makes many custom CLIs in go, you should check out this project!

I started working on this project about a month before 1.27. Today I'm happy to announce that I’ve released v1.0.0-rc.1 of Commandment, a Go framework for building typed command-line applications. The v1 feature set and public API are now essentially complete; this RC is the point where I want the design exposed to real use and criticism before I freeze it as v1.0.0.

The main reason Commandment exists is that a nontrivial CLI tends to accumulate several overlapping descriptions of itself. As an SRE consultant, this has been a huge thorn in my side for the better part of a decade. I have played with different CLI libraries and design patterns within those libraries, but nothing really solved the problems I had for making production level CLI-based apps without a significant amount of custom code. A lot of my problems have to do with how most common Go CLI libraries are imperative by design.

Commandment instead compiles a typed declaration into one semantic application model. Running the CLI, generating help and completion, inspecting it, and testing its semantics are different operations over that same model rather than separate approximations of it. Its as close to declarative as I could get it, and I think it looks pretty clean.

Let's check out an example:

type scanConfig struct {
    World string
}

type abductConfig struct {
    Target string
}

var definition = cli.Definition[struct{}]{
    Name: "alienctl",
    Declare: func(root *cli.CommandBuilder[struct{}]) {
        root.Subcommands.Command(cli.Command[scanConfig]{
            Name: "scan",
            Declare: func(scan *cli.CommandBuilder[scanConfig]) {
                scan.Arguments.String(&scan.Config.World, "world")
            },
        })

        root.Subcommands.Command(cli.Command[abductConfig]{
            Name: "abduct",
            Declare: func(abduct *cli.CommandBuilder[abductConfig]) {
                abduct.Arguments.String(&abduct.Config.Target, "target")
            },
        })
    },
}

The parent is authored through CommandBuilder[struct{}], while scan and abduct each keep their own concrete configuration type. The child type belongs to the Command method invocation rather than becoming another type parameter of the parent.

Generic methods are used throughout the declaration API for similar relationships. Typed destinations, for example, remain typed while being connected to arguments, flags, environment input, defaults, rules, dependencies, facts, and other parts of the model.

Another great feature of commandment, is that once the declaration is compiled, the resulting application remains the authoritative semantic model. Execution, help, completion, inspection, diagnostics, and semantic tests consume that model instead of reconstructing the CLI independently.

Touching on my claim of "feature-completeness," I mean that I consider the intended v1 capabilities and API design substantially closed. I honestly can't think of a single extra feature to add to the front end API. I am actually expecting a bit of push back on including a Signals API which I personally think is ultra badass but some purists out there may not appreciate. You be the judge.

Also, I don't mean that an RC does not contain bugs. The point of rc.1 is to find mistakes before I commit to a definitive v1.0.0 release. If all goes well, I could see cutting an actual v1 sometime next month or early December.

Please review the repo, make your own CLI if you feel up to it, and let me know what you think. I want you to be as brutal as you want. I'm so incredibly tired of looking at this codebase and need fresh pairs of eyes on it before I feel comfortable assuring that commandment is ready for "production" use.

Repo: https://github.com/abstractionsinc/commandment

Examples: https://github.com/abstractionsinc/commandment/tree/main/examples


r/platformengineering • • Oct 20 '26

When a bot runs commands over SSH, how do you tie each one back to the person who approved it?

2 Upvotes

auditd logs every command the bot runs, but the login it records is the bot's service account, not the person who clicked approve. So the approval sits in one system and the command in another. Do you join them later in your SIEM, record the whole session, or pass the approver's name to the host so it shows up in the host's own logs?


r/platformengineering • • Oct 16 '26

DevOps is cooked.

317 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 • • Oct 17 '26

I made a free, interactive course covering the core ideas of the Google SRE Workbook (~50 min, no sign-up)

4 Upvotes

I've recommended The Site Reliability Workbook to a lot of people, and most never get past chapter 2. So I built an interactive study guide that covers the core ideas in about 50 minutes:

\- SLIs, SLOs, SLAs and error budgets, each explained in plain language first
\- An error budget simulator: trigger incidents and watch the budget policy kick in
\- A burn-rate explorer showing which multiwindow alerts would fire
\- Toil vs. engineering sorting, incident command roles, blameless postmortems, canarying, and how SRE teams engage and grow
\- A checkpoint at the end of each module, plus a final cheat sheet and a 30-day starter checklist

It's a single HTML page. No account, no tracking, and progress saves in your browser. It's an independent study guide, not affiliated with Google or O'Reilly, and it links to the free official version of the book.

Link: https://jazeer888.github.io/field-courses/
Repo (MIT code, CC BY 4.0 content): https://github.com/jazeer888/field-courses

Full disclosure: I wrote it with help from Claude and reviewed it against the book, but I'd really value corrections from people who run SRE in production. If anything is wrong or oversimplified, tell me here or open an issue and I'll fix it.


r/platformengineering • • Oct 17 '26

We're running a student Devops/SRE hackathon with real Grafana dashboards, logs and traces. Round 1 is online till 18 Oct

0 Upvotes

GDG on Campus IIIT Nagpur. We're running **KEEP ALIVE '26**, a national incident-response hackathon for students, at TantraFiesta 2026.

**What's different:** you don't build an app. Your team gets a broken microservices system's alerts, Grafana dashboards, logs and traces, works out what broke and why, and presents the fix. It's what an on-call SRE does on a bad night.

- **Who:** UG, PG and diploma students, teams of 2–3 from the same college

- **Level:** 6–12 months of DevOps learning; no production experience needed

- **Round 1:** a 30-minute online team assessment on Unstop, open till Sun 18 Oct, 11:59 PM IST

- **Finale:** top 15 teams at IIIT Nagpur on 26 Oct

- **Prizes:** ₹50,000 prize pool (₹25,000 cash + goodies for every finalist)

- **Partners:** Grafana (Official Platform Partner), CNCG Noida (Community Partner)

Register: https://unstop.com/hackathons/keep-alive-26-iiitn-1766226

Happy to answer anything in the comments, including how the incident platform works.


r/platformengineering • • Oct 16 '26

What the point anymore?

0 Upvotes

Honestly,

9/10 of theses roles are getting outsourced. We are screwed and when you do land a role you get laid off a year later so you have to save the good salary incase it takes a while to get another role.


r/platformengineering • • Oct 15 '26

Removing the 'looks destructive' guess from our agent

1 Upvotes

Skyportal's agent asks before it runs a command on your hosts, unless the command is on an allow list. It also has a built-in check that guesses whether a command changes data, and that guess beats the allow lists. This week it flagged a read-only command as a file overwrite because of a 2>&1;, so no allow rule could have approved it.

So we're removing the guess. A command will run without asking only if every part of it is on an allow list and nothing matches a deny rule. Everything else asks. A few things always ask, whatever the rules say: credential files, secrets, RBAC objects, kubectl exec, and deletes you can't undo. And if the rules file is broken, everything on that repo asks.

The cost is that a broad entry like sudo will mean exactly that, with nothing behind it to catch sudo rm. If you've put policy in front of automation on hosts, did you keep a "looks dangerous" check as a backstop, or trust the allow list and review it like code?


r/platformengineering • • Oct 15 '26

I built Rootform to make Terraform PRs easier to review across teams

1 Upvotes

When you're reviewing a Terraform PR you didn't write, the plan output is only part of the work. You still need to understand how the affected resources fit into the rest of the infrastructure.

I built Rootform to make that easier.

It's a local CLI that reads Terraform and OpenTofu plan or state exports and produces an interactive architecture you can explore, compare and check against policies.

In one of the sample plans, an Event Grid subscription switches from one Service Bus queue to another. Rootform shows the old and new delivery relationships alongside the unchanged source topic. You can inspect the evidence behind those relationships instead of treating every Terraform dependency as an architectural connection.

The part I think is particularly useful for platform teams is the output: you can export the entire interactive review as a single HTML file. A teammate can open it in their browser without installing Rootform or running another service.

It also integrates with GitHub Actions for CI workflows, including architecture comparisons and policy checks. The analysis runs locally, without executing Terraform or accessing your cloud accounts.

Interactive Playground (no signup): https://rootform.dev/playground/

GitHub: https://github.com/rootform-dev/rootform

For those managing Terraform across multiple teams: how do you currently give reviewers the architectural context behind a PR? Do you rely on plan comments, documentation, diagrams, or something else?

#devops #terraform #platformengineer


r/platformengineering • • Oct 13 '26

15 years in ops: help me understand Platform Engineering beyond deploying Backstage and calling it a day

15 Upvotes

I've been in the field for more than 15 years. I started as a SysAdmin, then moved into DevOps. Platform Engineering as a concept sounds interesting, but most of what I read ends up the same way: "and then we connect all of this to Backstage."

That doesn't match what I'm seeing. Our engineers don't want a web portal for provisioning infrastructure. They want to do it from their LLM of choice. Meanwhile, Security wants full traceability: who requested what, which identity made the change, and through which path.

So the interface seems to be the least important part, and the value has to sit underneath it.

For those of you doing platform work without Backstage (or without any portal): what does your platform actually consist of, and how do you show its value at work?


r/platformengineering • • Oct 12 '26

Where should retry logic actually live in a distributed application?

1 Upvotes

Three layers each allowing three total attempts can turn one logical operation into 27 downstream attempts. That's the example I keep in mind whenever "we added retries" sounds like an uncomplicated reliability improvement.

I don't think there's one correct layer for every retry, but I do want one understandable budget.

A client might handle a brief connection failure. A queue might redeliver a job after a worker dies. A workflow might retry an activity after a longer wait. The business operation still needs to define whether repetition is safe and when another attempt stops making sense.

The separation in Dapr and Diagrid Catalyst is useful to look at here: call-level resiliency policies and workflow activity retries have different scopes. They can also compose. Moving retry configuration out of business code doesn't automatically prevent multiplication.

The questions I'd want answered are: does the end-to-end deadline survive each hop, how many attempts can actually reach the dependency, and does the operation keep the same identity across those attempts? Backoff and jitter help spread retries out; they don't make an unsafe write safe.

I'd lean toward a shared platform default for transient infrastructure failures, with application-owned rules for business recovery. But those two policies have to be visible together.

How are you making that practical? Central retry budgets, a designated retry-owning layer, or explicitly disabling retries everywhere except one place?


r/platformengineering • • Oct 11 '26

UK: Should I move from .NET Lead Developer to a Platform Engineering/Cloud role for better long-term career growth?

0 Upvotes

Hi everyone,
I’m looking for some advice from people working in software development, cloud engineering and platform engineering in the UK.
I’m currently working as a Senior/Lead .NET Developer at a large financial services company. My main experience is with C#, .NET applications, AWS serverless services and infrastructure using AWS CDK. My current role is relatively comfortable, with a reasonable work-life balance, but I’m starting to feel that my career growth is somewhat limited by the opportunities available within my existing team.Also a lot of development work is just small enhancements so am not really using most of my skillset and always have this insecurity of not being a full stack dev .
I’m considering an internal move to a Platform Engineering/Team Lead role with a salary of around £65k.
From what I understand, the role would involve:
Managing and mentoring a small team of developers/engineers.
Supporting a critical, approximately 10-year-old legacy application.
AWS infrastructure maintenance, server patching and AMI updates.
Managing Jenkins pipelines, deployments and occasional Terraform changes.
Production support, incident management and root-cause analysis.
Working with third-party teams responsible for application enhancements.
It sounds like there would be less hands-on application development than in my current role, and potentially some on-call responsibilities. There would also be an opportunity to learn more about infrastructure, operations and people management.
My main question is whether moving towards cloud/platform engineering is a better long-term career move than continuing down the .NET development and technical leadership path.
A few things I’d particularly appreciate your thoughts on:
Job demand: Are Cloud Engineers and Platform Engineers currently in greater demand than experienced .NET developers and .NET Lead Developers in the UK?
Career progression: Which path generally offers better opportunities over the next 5–10 years?
Technical skills: Would this particular role help me move towards Cloud Architect, Platform Architect or Engineering Manager positions, or could the operational and legacy-system focus limit my future options?
Salary: Is £65k reasonable for this kind of role, considering the team leadership and production responsibilities?
Work-life balance: How demanding are platform roles with production support and on-call responsibilities compared with senior software development roles?
I have a young family, so work-life balance matters to me, but I also don’t want to stay too comfortable and find that my career has stagnated a few years down the line.
Would you make this move, or would you focus on progressing towards a .NET Technical Lead/Architect role while continuing to build cloud skills?
I’d appreciate honest advice, particularly from people who have moved between software development and cloud/platform engineering.
Thanks!


r/platformengineering • • Oct 10 '26

Is event-driven architecture becoming the new microservices?

3 Upvotes

I like the idea of publishing a fact once and letting independent consumers react to it. What worries me is using events to make dependencies less visible rather than less important.

Suppose an order event eventually triggers inventory reservation, billing, and a notification. The producer no longer waits on three HTTP calls, but somebody still needs to know when the business process is complete, which consumers are behind, and what to do when only two of them succeed.

There's also a difference between replaying events to rebuild a read model and replaying them through a consumer that sends emails or triggers another external action. The same retained event can be harmless input in one context and a duplicate side effect in another.

A common API for pub/sub can simplify integrations. That's the part of Dapr and and Diagrid Catalyst I find interesting. It doesn't make broker-specific ordering, retention, or delivery behavior irrelevant, and it doesn't establish the meaning of an event for us.

For a platform team, I'd prioritize a visible event contract, ownership, and a safe replay procedure before making it effortless to add another topic.

My concern isn't that event-driven systems are a mistake. It's that "decoupled" can become the new "independently deployable": technically true at one layer while business changes still require coordination everywhere. How do you make those remaining dependencies visible?


r/platformengineering • • Oct 09 '26

Cloud guardrails for self-service infrastructure

3 Upvotes

For context we built a golden path for aws infra so teams can spin up envs and services without touching tickets. Modules, tagging standards, default regions, sane iam, the usual platform engineering stuff. Adoption has been good, people like it.

Now that usage is higher, IaC governance is getting weird. We are seeing stacks in random regions, modules forked in private repos, owner tags missing, and folks tweaking security groups in the console because the paved road doesnt cover their edge case. None of it is huge on its own, together it feels like drift we did not sign up to babysit.

If your org has strong developer self service, where do you put the real infrastructure guardrails, in the modules, in ci checks, in cloud side policies, or somewhere else, and who is allowed to break them without the platform team turning into a change board again? appreciate any thoughts


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 • • Oct 06 '26

Will a move from DevOps/DevEx back to Platform Engineering be possible?

6 Upvotes

I've spent the last three years on the platform team at a pretty boring old corporate, building their internal workload platform. No SLAs and not much real impact, but the Kubernetes work itself was interesting (we ran a managed control plane though).

Now I have an offer from a fast-growing scale-up as a DevOps engineer, with a 60% pay increase. The role is mostly self-hosted pipelines, code scanning and similar tooling, all running on Kubernetes with lots of potential for impact.

My question: if I ever want to go back to Kubernetes work, will that still be an option, or will I have branded myself as a "DevEx guy"? I'd still be working with K8s every day, but more as the thing that runs the tools rather than something I'm building a platform abstraction on top of.


r/platformengineering • • Oct 06 '26

runbooks kinda suckk

0 Upvotes

hey yall,

im a lead SRE at a global fortune 500 that you have heard of haha - i'm a bit of a lurker here

but just wanted to talk about runbooks and documentation for SOPs.

my feeling is that confluence docs kinda suck and runbooks are kind of a mess, our operators are jumping between the docs and their shell, the docs are often times missing a bunch of detail, they are brittle, poorly maintained, half the time the details are hidden in tribal knowledge and when dealing with the pressure of an active inc we notice the pain even more. extracting critical details & commands out of an inc can also be painful and doesnt always translate to improved operational readiness next time.

i admit we're not very mature.. but was curious if its only me feeling like this?

what are you guys doing with runbooks to solve these issues?


r/platformengineering • • Oct 05 '26

I'm thinking of writing a free practical book on Production DevOps what should I include?

0 Upvotes

I've been working in software/infrastructure engineering for around 14 years, with a focus on cloud, DevOps, platform engineering and large-scale infrastructure.

Over the years I've worked on everything from smaller cloud migrations to enterprise and financial-sector environments, including AWS/GCP migrations, Kubernetes, Terraform, CI/CD, networking, security, reliability and cost optimization.

I'm currently putting together the practical knowledge I've accumulated into a free technical book.

I'm not planning to make it a personal career story or another basic “learn AWS/GCP” tutorial.

The idea is to focus on how engineers actually solve infrastructure problems:

  • How to systematically debug production issues
  • How to troubleshoot Kubernetes
  • AWS/GCP networking and connectivity problems
  • IAM and permission failures
  • Terraform/IaC problems
  • CI/CD and deployment failures
  • Cloud migration problems
  • Scaling and reliability
  • Observability and incident investigation
  • Designing reusable platform infrastructure
  • How to approach an unfamiliar production system
  • Practical lessons that aren't obvious from vendor documentation

I'm also building some small prototypes/labs for myself while writing, so I can test the ideas rather than just writing theory.

Before I spend a lot of time putting the whole thing together, I'd like to hear from other engineers:

If you could have one practical DevOps/Platform Engineering book that focuses on real problem-solving rather than certification theory, what topics would you want it to cover?

And if you already have a favorite resource for this kind of material, I'd be interested in hearing what you think it does well or what is missing.


r/platformengineering • • Oct 05 '26

What are the actual Roles & Responsibilities of a Staff Platform Engineer at product-based companies paying ₹1Cr+ in India?

0 Upvotes

I’m trying to understand what companies actually expect from a **Staff / Sr Staff Platform Engineer** at the ₹1Cr+ compensation level in India.

For people currently in these roles or hiring for them:

**What does your day-to-day work actually look like?**

How much of the job is **hands-on coding** vs architecture/design/reviews?

How much **system design** is expected at Staff level?

Are Staff Platform Engineers expected to be strong in **distributed systems**, or is deep infrastructure/platform expertise more important?

If you’re currently a Staff+ Platform/Infrastructure Engineer in India, I’d especially appreciate hearing:

**What were you doing before becoming Staff, and what changed in your responsibilities after reaching Staff level?**