r/platformengineering • • 8h ago

Moving from CI work into Kubernetes roles?

2 Upvotes

In my role, I build reusable CI templates and policy gates, and we own code scanning and the artifact repository. My team also owns and runs the CI runners on Kubernetes.

I’d like to end up in a role with low-level Linux and Kubernetes work: nodes, scheduling, debugging production systems. Is that realistic from here, or would it be hard because of my current focus? Or more generally, how realistic is it to move from my delivery-focused work into runtime infrastructure roles or am I locked into the former?


r/platformengineering • • 22h ago

Moving coding agents from personal terminals into shared team channels: what we had to build

0 Upvotes

Disclosure: I work on AgentConnect. This is a write-up of how our own team uses it.

We’re fewer than ten engineers, running around thirty agents: one generalist for everyday engineering requests, plus specialists for cluster checks, alert investigation, code review, releases, upstream fork maintenance and customer support. Each specialist has its own repositories, tools, channels and schedules, with permissions scoped to its job.

Initially, everyone had their own scripts, schedules and credentials. We were duplicating the plumbing, and investigation context stayed in whoever’s terminal ran the task.

Moving agents into Slack threads made investigations visible to teammates, but introduced problems our first bots weren’t built for: picking up earlier messages, keeping workspaces separate, surviving restarts and preventing bots from triggering each other.

Permissions needed more than ‘can this person message the bot?’ We separated who can use an agent, which repositories and tools it can access, and who can read its sessions. Private-channel context and memory stay scoped to that conversation’s audience.

We kept the existing coding harnesses so engineers can reproduce channel behaviour locally. For fork maintenance, agents prepare changes and checks; people merge and publish.

Full write-up

For teams putting agents into operational workflows: how are you handling shared investigation context without making private conversations or privileged tools accessible to everyone?


r/platformengineering • • 1d ago

Are AI agents transforming Dev and Ops jobs differently?

0 Upvotes

I have the feeling that AI agents may not transform Dev and Ops jobs in the same way.

For Devs, writing code themselves is a central part of the job that is now being challenged. For Ops, it seems more like another level of abstraction, as the job is already largely about orchestrating automation.

I wonder if others share this view, or if I'm oversimplifying things.

I'm currently Ops, previously Dev.

Short essay here: https://cl3don.substack.com/p/dev-and-ops-facing-ai


r/platformengineering • • 1d ago

I built a free tool to find the minimum IAM role in Azure, AWS and GCP, plus a reverse lookup by action

Post image
4 Upvotes

Working in multi-cloud, I kept ending up with three tabs open, two reference docs, and still guessing whether a role was least-privilege or way too broad.

The hard part is never finding a role. It's knowing exactly what's inside it without reading hundreds of JSON/YAML policies. And the other way around: "which roles grant this specific action?" is surprisingly painful to answer.

So I built whatroledoineed.com:

- Intent-based lookup: pick a resource and what you want to do (read / write / assign / delete) and get the minimum role back
- Reverse search: type an action and instantly see which roles grant it
- Browse the built-in role catalogs of Azure, AWS and Google Cloud (in development) and inspect the actions each role includes

It's free and launched a few days ago (available in English and Spanish).

I'd love honest feedback from people who deal with IAM daily:
- Does the intent-based lookup return the role you'd expect?
- Is the reverse search useful in your workflow, or do you already solve this another way?
- Anything missing or wrong in the catalogs?

There's a feedback button inside the app too. Roast it if needed 🙂


r/platformengineering • • 3d ago

Claude Code touched a helper, two AI reviewers approved it, and our Kafka consumer fell over.

0 Upvotes

Python shop, Django plus a few Kafka consumers. Claude Code refactored a date parsing helper as part of a bigger PR. CodeRabbit and Greptile both reviewed it, no complaints, a human skimmed it, merged. Turns out that helper is also called inside our highest volume consumer and the new version does an extra db lookup per message. Consumer lag went vertical an hour after deploy. Nothing in the diff told anyone that function sits on a hot path, the reviewers read the diff and the diff looked fine. Someone on the platform team has been pushing hud because its PR check lists the functions a change touches with how much traffic they carry and who calls them, so the reviewer sees “this is called from the consumer” before merge. Haven’t rolled it out. How are others catching this, is it just better tests or do you actually feed production call data into review?


r/platformengineering • • 4d ago

Platform folks: who owns “prove what’s in our software” at your company?

0 Upvotes

Quick disclosure: grad student (NYU), doing a class case study with a software supply-chain startup. Not selling anything, just trying to learn.

I spent 8 years as a frontend-biased software engineer and never really owned this problem, but I’m now hearing it lands on platform teams a lot. Customers in healthcare, finance or the EU (CRA) ask for SBOMs or security evidence, a big CVE drops, or someone needs to swap out a deprecated library, and suddenly the question is “where is this used and can we prove it?”

Curious how it works on your team:

  • Is this actually the platform team’s job where you are, or does it sit with security?

  • When a customer or auditor last asked for evidence, how painful was it to pull together?

  • Has more AI-generated code made dependency tracking harder, or no real change?

Would love to hear real experiences (including if this never comes up for you or your team), the messy ones especially. Happy to share a summary of what I hear back here.


r/platformengineering • • 4d ago

Design review: a shell as the self-service interface to a platform, where every default is visible through explain. Is this a golden path or a footgun?

0 Upvotes

I'm designing Convoy Fleet Manager, a POSIX-like shell over Kubernetes, and I'd like platform engineers to review it before any code exists. The pitch to developers is "use the verbs you already know". The pitch to platform teams is "you set the defaults, and your users can always see them".

How it splits the work between the platform team and its users:

  • The platform owns the defaults. Storage classes, queues, packages, budgets, the release path, the provenance each environment requires, whether debugging is allowed: all of these are platform settings. Every command's explain prints the defaults it picked up and where each came from, so "why did my job land there" has an answer without a ticket.

  • Profiles are per environment. A test mount can accept images built in the cluster (provenance: session), while production accepts only CI-attested digests, refuses debug agents, and with release_diff=refuse refuses a release whose plan differs from where the digest last passed.

  • Groups own things, people act. Objects belong to groups, and processes run as svc:<group>. The person is recorded as the actor on every receipt.

  • Approvals are objects, not chat buttons. A policy (say, release to prod-*) creates an approval on the process. It pins the explain output it shows the approver, and only a different person can answer it, from their own session.

  • Cost is part of the plan. It's a band at plan time, a column in ps while running, and a receipt at the end that tightens the next estimate. Budgets are enforced at plan time, not discovered on the bill.

  • There's a typed escape hatch. Unknown commands still run, on one node, and explain says why. Nothing is blocked for lack of an annotation, but nothing gets parallelized by guessing.

It's design-only. The repo has 22 ADRs, nine workload walkthroughs and 24 persona-driven user stories (SRE, platform engineer, data engineer, ML engineer, auditor, app developer...). Their 181 findings have each been applied, drafted or accepted.

What I'd like from this community:

  1. Does a shell belong in an internal developer platform next to Backstage-style portals and golden-path templates, or does it undercut them?

  2. Is "every default is visible and attributed" enough governance, or do platform teams need defaults the user can't see?

  3. Who should own the command annotation database (which commands can be split, how their outputs merge): the platform team, the tool authors, or both?

  4. Would you hand the cost band and budget enforcement to a shell, or keep them in FinOps tooling?

  5. What's missing for you to offer this to your users?


r/platformengineering • • 4d ago

Is post release verification worth its own line item or is that just your APM again?

2 Upvotes

We took a chunk out of the New Relic bill this year by cutting custom instrumentation and dropping some boxes to infra only. Nobody complained for a while. Then a deploy went bad on one of the services we’d thinned out and we had almost nothing to go on, so it turned into a log reading exercise and a long night.

What I can’t work out is whether the answer is buying back the instrumentation we cut, or buying something that watches the rollout itself. Harness and LaunchDarkly both do the guarded rollout thing off metrics you already send. Hud goes at it from the function side, so you aren’t picking metrics up front. Different money, different data leaving the building.

Has anyone actually swapped more APM for verify the deploy and been happy about it? Or did you end up paying for both anyway?


r/platformengineering • • 5d ago

Benchmarked 10 LLMs on writing reusable OpenTofu modules for AWS/GCP/Azure: open-source harness, data, and results

12 Upvotes

Just because AI-generated infrastructure passes tofu plan doesn’t mean it would survive an org’s compliance, cost, or scale requirements.

We had 10 models each write 9 reusable OpenTofu modules (90 total) across AWS (S3), GCP (Cloud SQL Postgres), and Azure (App Service). Almost everything planned cleanly. No syntax errors, very few failed plans. But:

S3 access log delivery was missed in 30 of 30 attempts. Every model, every time.

Cloud SQL would drop the database on removal in 24 of 28 attempts. Take the DB out of the inputs and your data goes with it.

25 of 90 attempts failed at least one mandatory security item. 6/30 S3 modules didn’t guarantee the public access block, 9/28 Cloud SQL modules didn’t require encrypted connections, and 10/28 App Service modules left basic-auth publishing on.

Only 32/90 fully validated their inputs, and 26/90 shipped docs containing false statements about what the module does.

Provider version constraints allowed the next major version in 19/30 AWS and 22/28 GCP modules.

How it was scored: 70% mechanical checks against real tofu plan output, 30% LLM judge grading against a published 14-section quality doctrine. Nothing was applied, only planned.

The obvious objection: the judge is Claude Opus 5.5, and Opus came out #1. Two things on that. First, the judge had to agree with a human grader on at least 6 of 8 modules in every section, and GPT-5.5 failed that calibration, so it wasn’t used. Second, if you rank by the mechanical score alone, the order doesn’t change. The top four (Opus 5.5, Fable 5.1, GPT-6 Astra, Sonnet 5.5) have overlapping confidence intervals, so treat them as a tie.

Some other things that stood out:

GPT-6 Luna came 6th with zero security failures, at about $0.005 per attempt.

Gemini 3.6 Flash failed security items in 8 of 9 attempts.

Kimi K3 was the best open-weight model (5th), but 4 of its 9 attempts had security failures.

Full disclosure: I work at Massdriver, which ran this. The harness is Apache-2.0 and the data is CC BY 4.0, so you can rerun it, add your own checks, or tell us where the methodology is wrong. We’d like to hear that.

Rankings: https://www.massdriver.cloud/llm-rankings

Methodology: https://www.massdriver.cloud/blogs/iac-bench-2026-10-methodology

Repo: https://github.com/massdriver-cloud/iac-bench/tree/2026-10

Raw results + generated code: https://github.com/massdriver-cloud/iac-bench/tree/2026-10/results/2026-10

Quality doctrine we graded against: https://github.com/massdriver-cloud/iac-bench/blob/2026-10/docs/good-opentofu.md

I’m curious whether these match what you’re seeing with AI-generated IaC in your orgs. What would you add to the checks?


r/platformengineering • • 5d ago

Practice Real Production Outages

0 Upvotes

Disclosure: I built this.

Most of us learn incident response live, in prod, with everyone watching. I wanted somewhere to practice first, so I built Outage Gym.

How it works: a small production stack runs on your laptop with Docker: a service, a Postgres database, real traffic that keeps coming, and dashboards. Something is broken. You find the root cause, ship a fix (code, database or both), and keep "support" updated in an #incident channel while the clock runs. The system itself confirms when it's actually fixed and stays fixed. Nobody tells you where to look.

First problem: it's the first week of term, thousands of students are logging in, and the student service starts to drag. Some pages never load. No deploy, nobody touched the servers. It takes about 30–60 minutes.

Free to start: https://outage-gym.com


r/platformengineering • • 8d ago

AI makes content reproducible. I built a pipeline that does the same for the mobile architecture itself. Let’s talk about the future of development

0 Upvotes

AI has successfully automated a significant part of software creation. But what about the deployment and infrastructure stage? Here is a reproducible process that takes a technical specification and outputs a finished, standalone native mobile platform—independent apps for both iOS and Android driven by a unified backend — in about two hours.

This is strictly a Self-Hosted solution, not a SaaS or a drag-and-drop app builder. Every single output is a genuine native product with its own codebase, deployed directly onto the recipient's server under their absolute control.

There are two fundamental questions where I require raw feedback from engineers and practitioners:

  1. Does transitioning from the traditional "every app is a separate development project" model to a reproducible production pipeline reshape mobile engineering as a discipline?

  2. Does this level of structural automation threaten developers, or does it finally free them from routine to focus on building truly unique functionality?


r/platformengineering • • 8d ago

Career choices: Platform engineer vs Swe

4 Upvotes

Hey all,

I'm having trouble landing interviews. I know the job marker is bad but i also suspect my resume isnt selling me well. For context, i come from a SWE (backend focused) background. I lost my job early this year, and decided to upskill. I built projects while learning and I do use them in my portfolio. Ive been applying to devops and platform engineering jobs but all i get is rejections. I thought my 5yrs experience in SWE was an added advantage.

Granted, in those 5 years i haven't exclusively worked as a devops/platform engineer but my roles kinda overlapped and so occasionally have handled devops tasks. I have reframed my resume to reflect my devops experience and backend engineering but still i'm not landing interviews. Yeah sure i'm not senior level perfect in platform /devops engineering but i can make a good mid level.

Would it be better if i just completely ignore devops/ platform engineering and just apply to backend engineering.


r/platformengineering • • 9d ago

Preparing for a master’s dissertation on Platform Engineering / IDPs — where should I start?

3 Upvotes

Hi everyone! I’m starting a dissertation internship in February focused on Platform Engineering. The goal is to design and build an Internal Developer Platform (IDP) prototype for a development team.

The platform should provide self-service workflows for tasks such as creating projects from templates, provisioning infrastructure, and deploying applications. The dissertation will involve:

  • Researching Platform Engineering principles and Developer Experience.

  • Defining a use case and designing a modular architecture.

  • Building a prototype, potentially using Backstage, Terraform, and Kubernetes.

  • Enabling features such as project generation, deployment, and monitoring.

  • Documenting the platform and evaluating its usefulness and usability through developer feedback.

The focus is on reducing repetitive work and cognitive load through reusable components and golden paths. The tools mentioned in the proposal haven’t all been confirmed as mandatory.

My background: I code in Python and have used GitHub and GitLab, but I don’t have hands-on experience with Linux, Docker, Kubernetes, Terraform, or building internal platforms.

I have until February to build a foundation before the internship starts. I’m looking for a structured learning path with beginner-friendly explanations and practical exercises. I’m willing to pay for suitable training and have been considering KodeKloud and TechWorld with Nana’s DevOps Bootcamp.

For those working in this area:

  • What would you prioritise learning, and in what order?

  • Which course or learning path would you recommend for someone with my background?

  • What small practical project would help me connect these concepts?

  • What would you consider a realistic scope for an academic IDP prototype?

I’d appreciate any advice, especially from people who started with a similar background or have built an IDP!


r/platformengineering • • 10d ago

Our homegrown MCP gateway let a read only agent write, and nobody owned it.

2 Upvotes

It went on for three weeks in our ticketing system before anyone noticed, and when we did nobody could say who the agent belonged to or who it was acting for. Every agent reaches servers through an MCP gateway I wrote in Go over two weekends. It knows tokens and routes but nothing about owners, and now it fronts 23 servers through a yaml policy file nobody wants to own.
Classic case of not seeing the forest for the trees, we built agent access control around reachability and skipped AI agent identity.
A teammate mentioned in standup that the MCP spec now has enterprise managed authorization, which could remove some auth plumbing, though it does nothing for AI agent ownership.
I read newcore’s post The MCP Gateway Had a Good Run, and sure, a vendor would say identity matters more than routing, but it stung a little.
Then again, remember Simon Willison’s lethal trifecta post from last year? One agent with the wrong mix of tools is a problem no matter who owns it. For teams that sorted this out, did you give agents their own identity and owner before picking tooling, and what would you do differently? I feel pretty dumb asking, but appreciate any thoughts.


r/platformengineering • • 11d ago

Devenv local ci for Ai agent

0 Upvotes

Hello!

I've written a small series to explain how we moved from GitHub action to local ci with devenv with few tricks to make our bill lower and ci faster : https://etienne.deneuve.xyz/en/thinking/2026-10-09-ia-accelere-code-ci-doit-suivre-en/
I would love to have feedback on this !

How you manage this on your end ?


r/platformengineering • • 11d ago

Platform teams: what’s the rule your AI coding tools keep missing?

1 Upvotes

I’m a high school student researching a startup idea about AI agents and infrastructure changes. Not selling anything, no link.

Someone in r/kubernetes told me their AI adds the YAML for a new app but forgets to create the ArgoCD app. Nobody wrote that step down because “a human knows that since it’s logical.”

For those of you running platform teams:

  1. What’s a step or rule like that on your team, something everyone knows but isn’t written anywhere?

  2. Do you let AI tools change anything on their own yet? If so, how did you decide what?

Short answers help a lot.


r/platformengineering • • 13d ago

I built an open-source CLI that upgrades Terraform/OpenTofu providers across all your modules, and lets Terraform own the lock file

Post image
0 Upvotes

Keeping provider versions current across a lot of modules was a constant chore for me: bump a version, find out a shared module caps it, fix the constraint, regenerate lock files for every platform, repeat. Version bots can bump a number, but they don't understand dependency ceilings, constraint styles, or lock files that need hashes for every OS/arch.

So I built provlift, a small Go CLI (Apache-2.0):

  • provlift check: inventories every required_providers entry across all modules, shows what's outdated and why an upgrade is blocked (your own constraint vs. a module's ceiling)

  • provlift drift: finds version skew between modules

  • provlift upgrade: rewrites constraints with the smallest possible diff (keeps your ~> / range style and comments), then runs terraform init -upgrade → providers lock for each platform you list → validate. It never writes the lock file itself.

  • Major upgrades need an explicit --allow-major, and it can step one major at a time.

  • Example GitHub Actions workflow that opens one PR per provider.

Works with any registry provider (AWS, AzureRM, Google, GitHub, Kubernetes, private registries) and with OpenTofu (--terraform-binary tofu, uses registry.opentofu.org).

What it doesn't do (yet): module version upgrades are out of scope, Terragrunt config isn't evaluated, and .tf.json is reported rather than edited. It's early (v0.1.x), so expect rough edges.

I'd really appreciate feedback, especially on edge cases in your setups that it gets wrong. There are also good-first-issues if anyone wants to contribute.

GitHub: https://github.com/provlift/provlift
Docs: https://provlift.github.io/provlift/


r/platformengineering • • 13d ago

When technology is created: open the source code or preserve responsibility for its future?

0 Upvotes

On October 28, 2026, the head of Russia's Ministry of Digital Development stated the country's readiness to open the source code of domestic social networks, messengers, and video services to foreign partners, to demonstrate how they work, and to jointly adjust algorithms.

This is an important and timely initiative. It brings the question of technological openness far beyond the scope of professional discussions among IT specialists and developers. Now it becomes a question of international cooperation, trust, and the technological independence of countries, organizations, and individuals.

I perceive this statement not as an occasion to compare various technological solutions, but as an invitation to a broader professional discussion.

For me, this conversation has direct practical significance.

This topic became a logical continuation of the discussion at the VII International Rospatent Conference "ERA IP 2025." During the specialized session "The Role of Intellectual Property in the Structure of Russian Exports," I publicly raised the question of how to protect domestic developments in the era of digital transformation and globalization. It was there that I first outlined the possibility of opening source code as a strategic step to ensure real independence and competitiveness. Today, this trend is moving from the realm of predictions into the plane of concrete decisions.

I created and patented Rezvov Mobile Software — an infrastructure technology for the reproducible creation of standalone native mobile products for iOS and Android.

This is not SaaS, not Low-Code/No-Code, and not an app builder. It is an Infrastructure Engine & Production Pipeline — an infrastructure core and production conveyor for standalone native mobile products for iOS and Android.

The main engineering result of the technology lies in the transition from developing each new mobile application and its server infrastructure as a separate long-term IT project to a reproducible technological process for obtaining a finished product.

On this basis, it is possible to create the necessary number of standalone native mobile applications, social networks, social business networks, and digital ecosystems. Each product can have its own purpose, brand, structure, and functionality, and can be deployed together with autonomous server infrastructure on the owner's server and under their control.

This is not a theoretical concept. For our own projects based on Rezvov Mobile Software, dozens of standalone mobile products have already been created and published in the App Store and Google Play.

That is why the question of opening the technology is not a philosophical reflection on the future for me. It is a decision whose consequences may prove irreversible.

What Exactly Does "Opening the Technology" Mean?

Opening source code can have completely different meanings.

One can fully publish the source code and hand over further development to the global engineering community.

One can open the code only for the mobile applications being created, while keeping the infrastructure core that ensures their reproduction protected.

One can provide access to source code for independent technical audit and security verification.

One can form an international network of partners who will implement, support, and develop the technology in different countries.

One can create an independent engineering council or other structure that will ensure transparency of development while preserving authorship, responsibility, and unified technical standards.

A combined model is also possible: open products, protected technological core, independent audit, and clear usage rules.

Which of these paths is correct — I am not yet asserting. That is precisely why I am bringing this question to open professional discussion.

Open Code Is Not Yet a Ready-Made Ecosystem

Publishing source code can increase trust, enable independent auditing, and accelerate technology development. But along with freedom comes responsibility.

Who will maintain the architecture?

Who will be responsible for security?

Who will ensure compatibility of new versions?

Who will prevent the emergence of incompatible forks and products of unknown quality?

Who will take responsibility if an open infrastructure technology is used for purposes other than originally intended?

Source code can be opened with a single decision. Creating a sustainable system of development, trust, and responsibility around it is significantly more complex.

What Will Happen to the Mobile Development Market?

There is another question that cannot be ignored. If the creation of standalone native mobile products becomes a reproducible technological process, the very economics of mobile development changes.

But does this mean a threat to the developer profession? Or, on the contrary, does the technology free specialists from the repeated performance of routine work and redirect their efforts to where human knowledge is truly necessary: architecture, security, integration, domain logic, and the development of new functions?

Once, the industrial conveyor did not destroy the engineering profession. It changed the content of engineering work and made complex products accessible to millions of people.

Perhaps today a similar transition is beginning in the production of mobile software. But I do not want to answer this question alone.

This conversation did not arise today. The question of how a reproducible engineering architecture should exist and be distributed after its completion, I have consistently raised in my previous publications on LinkedIn. In the article from September 22, "Reshaping the Mobile Development Market: Are Billions in Revenue from the Existing Model Under Threat?" there was a detailed analysis of how an automated conveyor "breaks" the old Big Tech economics, freeing business and science from months of paying for repetitive stages. Later, in the material "After Launch: Which Model of Technology Dissemination Is More Effective", I first proposed that the community openly discuss this fork in the road: whether to fully move to Open Source, coordinate processes through an international network of independent partners, or seek a fundamentally new model. Today, in light of recent statements by regulators, this topic has moved from the realm of predictions into the plane of concrete actions.

Questions to the Professional Community

I am addressing programmers, developers, architects, heads of IT teams, departments, and technology companies.

  1. What model of opening and distributing infrastructure technology can bring the greatest benefit while preserving security, manageability, and responsibility for the end result?

  2. What should be opened: the source code of created products, the infrastructure core of the technology, or only interfaces, standards, and mechanisms for independent audit?

  3. Can patent protection and an open development model not contradict but complement each other?

  4. Is the engineering community ready not only to receive access to the technology but also to participate in its verification, support, and further development?

  5. How will the role of the developer change if a significant part of creating a mobile product shifts from individual development to a reproducible production process?

  6. Who, in that case, should own the rules for technology development: its creator, the international community, an independent council, or a network of professional operators?

I have already raised this question in my previous publications, considering Open Source, international partnership, and other possible models. Today, the initiative publicly announced by the Ministry of Digital Development has given this topic a new and timely context.

I am not announcing the opening of Rezvov Mobile Software and am not offering the community a pre-prepared answer.

I am proposing to discuss the decision before it is made.

Because opening source code means providing access to the past labor of the creator. But opening an infrastructure technology designed for reproducing new digital products means influencing their future.

How can this step be taken so that the technology serves people, develops the engineering profession, and creates independence without losing responsibility?

This is the question I am bringing to professional discussion today.


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 • • 14d ago

Can't find platform engineer roles locally

5 Upvotes

Hi, I'm very passionate about platform engineering but my local market seems to only have DevOps roles.

I'm a DevOps engineer with 3+ YOEs.

Are there platform engineering roles that are fully remote? Or do I need to search for relocation opportunities?

I have been trying with the relocation opportunities for a while but it feels impossible, not getting past the ATS at all, even if the job description said visa sponsorship available, selecting that in the application results in an instant reject.

I would like to hear any advice or tips you can offer to help me make my job search more fruitful.

Below is a quick summary of my experience:

I have hands-on experience running and managing multiple production EKS clusters, running a fleet of microservices in a gitops environment and building an internal developer platform with Backstage.

Also designing DevSecOps pipelines that adheres to best practices, ensuring that code moves from source to production smoothly and securely, following build once promote many through multiple environments and multiple quality gates.

In addition I have strong development experience with Python, typescript(nodejs) and go.

I do have AWS and k8s certificates, in addition to Backstage certificate and CNPA (Platform Engineering Associate).


r/platformengineering • • 14d ago

Hunting for remote job

3 Upvotes

Hello everyone !

I am cloud and devops engineer with 6.4 years of experience designing and deploying continuous integration/deployment pipelines and cloud design for several companies.

Currently open to work on any remote job part time or full time , not to worry about payroll.

Ask me more questions if you want to and happy to clarify more

Regions I am looking are Europe and North America

Thanks in advance !

Pay range 100k USD to 250k

Desired pay minimum 100k USD


r/platformengineering • • 15d ago

What would a small software team consider a fair price for outsourced application deployment and CI/CD setup?

0 Upvotes

I'd like to understand how startups, SaaS companies, and software development agencies approach this.

Consider a team that already has a working web application but doesn't have a dedicated DevOps engineer.

An external engineer is brought in to establish a repeatable deployment workflow.

The engagement includes:

- Linux VPS setup and application hosting configuration.

- Docker containerization, where appropriate.

- NGINX reverse proxy and HTTPS configuration.

- GitHub Actions CI/CD pipeline.

- Automated deployment verification and health checks.

- A documented rollback and recovery procedure.

- Technical documentation and handover.

The scope is limited to one application, one server, and one deployment environment.

I'm interested in understanding the commercial side of this:

  1. Would you consider outsourcing this work, or would you prefer your developers to handle it internally?

  2. Which of these deliverables would provide the most value to your team?

  3. What would make you comfortable trusting an independent engineer with this work?

  4. Would you prefer a one-time fixed-price engagement or ongoing maintenance support?

  5. What would you consider a reasonable budget for this engagement in the Indian market?

I'm particularly interested in responses from founders, CTOs, engineering managers, SaaS operators, and software agency owners.

Actual purchasing experiences and budgets would be especially useful. I'm interested in realistic expectations, including reasons why you wouldn't outsource this work.


r/platformengineering • • 17d ago

Advice on how to prepare for an upcoming platform engineering role as a graduate

4 Upvotes

Hi, I’m a recent CS grad and I just got an offer for a platform engineering position and I start in 4 days. How can I prepare for this role?

They did say they will teach me everything I need to know, but I just want to be a little prepared so I know what to expect on day 1.

Can anyone offer advice on what to brush up on? Should I know any languages or technologies? Any roadmap I should use to prep my brain for learning?

Thank you!


r/platformengineering • • 17d ago

Hi everyone! I’m struggling to put my CV together. Could anyone help me with it?

0 Upvotes

DevOps Engineer

Linux | Docker | Kubernetes | GitLab CI/CD

Professional Summary

DevOps Engineer with approximately 3 years of experience in Linux server administration, Docker, GitLab CI/CD, and automation using Bash and Python. Additionally, 1 year of experience as a Python Developer, working with Django, Flask, and PostgreSQL.

Work Experience

Python Developer | Vavsynergy

2024–2025

  • Developed and maintained applications using Django and Flask with PostgreSQL databases.

  • Automated repetitive tasks using Python scripts.

  • Fixed bugs, optimized code, and deployed updates to servers.

DevOps Engineer / Systems Administrator | Vikant

2023–2024

  • Administered Linux servers and Windows Server environments.

  • Managed Docker containers, Docker Compose, and GitLab CI/CD pipelines.

  • Configured Nginx and network settings.

  • Analyzed logs and diagnosed CPU, RAM, and disk-related issues.

  • Administered the CRM database and maintained and improved the company website.

  • Configured email delivery.

  • Key achievement: Improved website stability and reduced server load through code optimization and configuration improvements.

DevOps Engineer | Ukrtools

2021–2023

  • Administered Linux servers and deployed and maintained applications built with Python and Django.

  • Worked with Docker and GitLab CI/CD.

  • Developed Bash scripts to automate routine tasks.

Technical Skills

  • Operating Systems: Linux, Ubuntu Server, Windows Server

  • Containerization: Docker, Docker Compose, Kubernetes

  • CI/CD & Automation: GitLab CI/CD, Bash, Python

  • Infrastructure & Web Servers: AWS, Nginx

  • Programming & Databases: Python, Django, Flask, SQL, PostgreSQL

Education

Computer Science (Specialization 122)
College of Food Industry, Kamianets-Podilskyi
2021–2024

Languages

  • Ukrainian: Native

  • Polish: B1 (Intermediate)

  • English: A1 (Beginner; able to read technical documentation)

Additional Information

  • Currently learning Rust.

  • Winner of competitions focused on Linux-based server development.


r/platformengineering • • 17d ago

Free Webinar: Why Platform Engineering Needs Domain-Driven Design | Nov 18

0 Upvotes

Ajay Chankramath, author of Effective Platform Engineering and Domain-Driven Platform Engineering, is hosting a free 45-minute webinar on applying Domain-Driven Design (DDD) principles to platform engineering.

Topics covered:

  • Why one-size-fits-all platforms fail

  • Using bounded contexts to define platform boundaries

  • The four-layer platform service taxonomy

  • Applying ubiquitous language to bridge infrastructure and business domains

  • Aligning platform architecture with Conway's Law

Date: November 18, 9 AM ET
Duration: 45 minutes, including Q&A
Format: Free, online

Know More: Why Platform Engineering Needs Domain-Driven Design