r/platformengineering • • Mar 15 '26

Someone tried to Hack our platform, but we use Golang

19 Upvotes

Someone created a guest account on our platform and started doing things outside typical use case.. we noticed errors in our API logs and once checked found a guest account had been hitting our endpoints with SQL injection payloads. MySQL sleep(15), Oracle DBMS_PIPE.RECEIVE_MESSAGE, PostgreSQL PG_SLEEP, XOR-based blind injection, double encoded quotes they tried it all :)

Last month we had around 2.7 million requests and close to 200k unique visitors and managing that with a team of 4 is not a trivial job, however our backend is written in Go so they were not able to bypass that.

Every single payload got stored as a useless entry in DB. Nothing was executed and nothing broke. The attacker’s “exploits” are now just junk entries sitting in the database with names like:

(select(0)from(select(sleep(15)))v)/*'+(select(0)from(select(sleep(15)))v)+'"+(select(0)from(select(sleep(15)))v)+"*/

In other words, the scanner failed to exploit anything but it still acted as a free penetration test.

We use Golang so Go's typed JSON deserialization acted as a security layer for us since json.Decode into structs silently rejected unexpected types and shapes.

there was only one place where we used map[any].. which still was not meaningful attack surface but allowed attackers to insert some junk into our db which is not fixed.


r/platformengineering • • Oct 06 '24

What Salary Should I Ask for as a Platform Engineer with My Experience

0 Upvotes

Hi All,

I’m currently working as a Platform Engineer, specializing in research and development in cloud computing, big data, and DevOps. I have about 19 months of experience, starting as a SysOps Engineer, moving to Site Reliability Engineer, and now in my current role where I optimize client environments.

I hold a Bachelor's degree in Science (Research), covering various tech topics, including AI, data science, and web design. My current salary is lower due to my limited experience, but I'm considering moving to a new company soon. I've had the opportunity to learn from experienced professionals with over 28 years in the tech industry, which has greatly enhanced my skills.

Given my background, what salary range should I aim for in my next role? Additionally, any tips on negotiating the best salary and acing interviews would be greatly appreciated!

Thanks for your insights!


r/platformengineering • • Jun 26 '26

The platform work nobody credits you for is the work that lets you add agents later

0 Upvotes

Platform teams get pushed toward the shiny layer — self-service, AI agents, automation — but the unglamorous foundation is what determines whether any of it holds. Scaling a pipeline taught me the leverage is all in the abstractions:

  • Golden paths only work if they're reproducible. No UI changes anywhere — GitHub, AWS console, Grafana. Everything as code, dashboards as JSON in the repo. If you can't rebuild an environment exactly, your "platform" is a set of conventions people drift away from.

  • Decouple the runtime early. We built around Helm/Kubernetes, then a database needed dedicated VMs and Helm couldn't follow — it only speaks K8s. One Ansible + Packer playbook that bakes both a container image and a VM AMI removed the lock-in. Terraform/Pulumi as the runtime abstraction matters more the bigger you get.

  • Abstract telemetry too. OpenTelemetry so apps emit to a standard interface, not to whatever backend you happen to run today. Swapping backends shouldn't touch app code.

My take: a platform that enforces a standard, monitors it, scales it, and lets parts be swapped out is exactly what makes agents viable. Build the engine first — once it's stable, an agentic layer that monitors and maintains it becomes the natural next step instead of a liability. Full write-up with the tradeoff tables exists, but I'm curious — where's your abstraction layer thinnest right now?


r/platformengineering • • Sep 10 '26

The engineer’s guide to building a software factory

Thumbnail
leaddev.com
1 Upvotes

Build loops, not just agents.


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 • • Mar 14 '26

DevOps market overcrowded. I might have a solution.

6 Upvotes

Hey Folks,

Another write from me, but I thought it might be worthwhile to share what I've recently discovered. So I had to hire a DevOps engineer and a few Data Engineers, and at first I thought that hiring DE would be a walk in the park. At the end of the day, how hard could it be? They have way fewer tools, no networking, no security, lighter programming, and in general the barrier of entry seemed lower. On the other hand, my perception was that hiring a solid Platform Engineer or DevOps would be very tough.

After 3 weeks of searching, I got dozens of high-quality DevOps candidates, while I had to repost the ad in multiple locations just to get a few decent Data Engineers. This was something I didn't expect. Now I'm not saying to pivot, but as Platform Engineers we already know so much that adding a few tools and practices like building data pipelines, writing solid SQL, working with Spark, using data warehouses like Snowflake/BigQuery, and orchestrating jobs with tools like AWS Glue or Airflow under our belt would substantially widen our marketability.


r/platformengineering • • Jan 25 '23

Copying from LinkedIN: Learning or launching a career in Cloud Computing and DevOps does not have to be a struggle by Amrut Patil

0 Upvotes

Learning or launching a career in Cloud Computing and DevOps does not have to be a struggle.
- By Amrut Patil via LinkedIN

Just subscribe to these 3 YouTube channels:

  1. TechWorld With Nana
    Nana is more focused on the latest trends in the DevOps world.

She puts out actionable content on how to use different DevOps and CI/CD tools using hands-on projects.

I like the fact that occasionally she will share her industry insights and what DevOps tools or skills should one be learning to begin a career in DevOps.

Her content is suitable for both beginners and experts in the DevOps industry.

2. ILyas In The Cloud
ILyas is more focused on AWS Cloud architecture and solutions.

He puts out awesome videos on best practices and architecture patterns in the Cloud. He will also share his experience and provide guidance on how to prepare for AWS certifications and launch a career in the cloud.

His content is suitable for beginners in the cloud, solution architects, and people interested in cloud computing in general.

3. Cloud With Raj
Raj is more focused on AWS Cloud, DevOps & career development.

He is a Senior Solutions Architect at Amazon Web Services and has helped thousands of people get started in the cloud. He is also a course instructor with multiple AWS Cloud courses on Udemy.

I like Raj's teaching style where he can break down complex architectures into simple understandable parts. He also puts out content about practical hands-on projects and how to apply best practices to your cloud solution.

So, save yourself $1000s studying Cloud Computing & DevOps in college or boot camps and just binge on these YouTube channels.


r/platformengineering • • Oct 15 '26

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

0 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 • • 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 • • Jan 17 '26

Does AI actually have a place in our Platform Engineering or are we just chasing the hype?

2 Upvotes

As platform engineers, we’re usually the ones tasked with cleaning up the mess when a new technology is rushed into production.

So, I wanted to get your honest take on a few things I’ve been chewing on:

The "Support" Bot: Everyone talks about an LLM for dev docs. Does that actually help you, or would you rather we just fixed the search bar in our Backstage/Portal?

The "Auto-Sizer": There’s a lot of talk about AI-driven cost optimization and K8s right-sizing. Is that something you’d actually trust to touch your production HPA settings?

The "YAML Generator": Is anyone using AI to generate manifests or Terraform? I’m worried about the "technical debt" of code that no one actually wrote or fully understands.

What do you all think? Is there a specific "papercut" in your daily workflow that you think AI could actually solve? Or are we better off sticking to robust, predictable automation for now?

I’m curious if anyone here has tried implementing something small that actually stuck. Let’s hear the good, the bad, and the "please don't do this."


r/platformengineering • • Jul 26 '26

How are Infrastructure Engineers using Claude Code/Codex in production?

2 Upvotes

Curious how other infrastructure/platform engineers are using AI agents (Claude Code, Codex, etc.) in their day-to-day work.

We're at a GPU compute hosting company and have connected our internal tools (Grafana, NetBox, internal APIs, etc.) through MCP. Instead of manually jumping between dashboards, we ask the agent things like:

  • Which GPUs are available at a specific site?

  • Show rack/device information.

  • Summarize alerts from Grafana.

  • Correlate data across systems.

  • Help troubleshoot infrastructure issues.

It's becoming more of an infrastructure copilot than just a coding assistant.

For those working in cloud, HPC, AI infrastructure, or compute hosting companies:

  • What MCP servers or internal tools have you connected?

  • What workflows have saved you the most time?

  • Any surprising use cases beyond writing code?

Looking for real-world ideas to improve our workflows.


r/platformengineering • • Jul 27 '26

If your goal is Platform Engineering, would you start in Backend or DevOps today?

3 Upvotes

Hi! I’m looking for some career advice from people working in DevOps, SRE, or Platform Engineering.

I'm 25 and just starting my software engineering career. Over the past few months I've explored backend development, DevOps, Platform Engineering, Linux, cloud, networking, Docker, CI/CD, and related topics.

The more I learn, the more I realise that what genuinely interests me is systems, infrastructure, reliability, automation, deployments, and understanding how software runs in production. If I could choose purely based on interest, I'd like to end up in Platform Engineering or SRE.

At the same time, I'm trying to be realistic. Given today's hiring market, AI's impact on junior roles, and the fact that I'm starting at 25, I'm not sure what the smartest entry point is.

Right now I'm considering two paths:

  1. Start as a backend engineer (probably ASP.NET Core), build strong software engineering fundamentals, and transition into Platform Engineering later.

  2. Focus directly on Platform/DevOps skills like Linux, Docker, Kubernetes, networking, cloud, CI/CD, Terraform, and Go, and aim for an infrastructure-focused role from the beginning.

For those of you already working in DevOps, SRE, or Platform Engineering:

- Which path would you recommend today, and why?

- Is a backend software engineering role still the best foundation for Platform Engineering, or has the industry changed enough that it's reasonable to start directly in infrastructure/cloud?

- If you were starting over in 2026 with my goals, what would you do differently?

I'm not looking for the easiest path or the highest salary. I just want to make the best long-term decision while maximising my chances of landing my first engineering role.

I'd really appreciate hearing about your experiences and what you've seen in the industry.

Thanks in advance!


r/platformengineering • • Jan 19 '26

Tech Leads, DevOps/SRE/Platform - what are your salaries?

0 Upvotes

How much do you guys make and what’s the size of the organisation?

Also interesting to know how much experience you got.


r/platformengineering • • Jun 08 '26

Multicloud K8s SME in California or Colorado needed ASAP

0 Upvotes

Compa is a Series B startup with a role we're turning over rocks for - SWE, Core Infrastructure. This is staff level, awesome visibility and impact opportunity for someone with a startup appetite. The full job posting is below.

$200K – $225K / Hybrid / Offers Equity / Full-Time

Compa is a venture-backed AI startup revolutionizing the future of compensation.

In a dynamic job market with hiring challenges, accountability, and the rise of AI, companies need the best data to stay ahead of industry changes, competition, and costs. Compa has developed the premier real-time compensation data platform, delivering top-tier compensation intelligence to leading enterprise teams.

Compa is a compensation intelligence company built to augment enterprise compensation teams in the era of AI.

Our customers include the world’s biggest companies: NVIDIA, Stripe, DoorDash, Open AI, TMobile, Moderna, Workday, Ulta, Target, and more.

Locations:

Compa headquarters are located in Irvine, California, with growing sites in Denver, Colorado and San Francisco, California. We’re a collaborative, curious, and driven team that values transparency, ownership, and continuous learning and prioritizing in person work where possible.

The Role:

As a Staff Software Engineer on the Core Infrastructure team at Compa, you will own and lead infra and platform engineering projects across Compa’s products, systems, AI/ML, and data warehouse.

In this role you will:

  • Design, build, and maintain core infrastructure across cloud, data, and AI/ML systems

  • Own and drive the evolution of Compa’s Kubernetes-based platforms that give engineers reliable environments

  • Work on scaling and automation of infrastructure services and tooling

  • Raise the bar on reliability and observability (SLIs/SLOs, monitoring, incident response)

  • Design and improve CI/CD pipelines, deployment workflows, and infrastructure automation

  • Drive major company initiatives like multi-cloud support and customer-managed encryption keys

  • Lead platform engineering efforts that reduce toil and improve developer velocity

  • Act as a technical leader and multiplier by setting direction and helping others level up

  • Partner with leadership on what we build next and why

Minimum Qualifications:

  • 8+ years of industry experience in a software engineering role working on infrastructure, platforms, or backend systems

  • Deep, hands-on experience with managed Kubernetes platforms (e.g., EKS, GKE, AKS), including cluster architecture, networking, scaling, and upgrades

  • Strong coding skills in Python, focused on building infrastructure and backend tooling

  • Experience designing, building, and operating systems on multi-cloud infrastructure across AWS, GCP, and/or Azure

  • Experience managing infrastructure across cloud boundaries, including identity, networking, data considerations, traffic routing, and failover strategies

  • Deep understanding of networking, operating systems, cryptographic protocols and distributed systems fundamentals

  • A passion for enabling teams to build fast while building safely through well-designed proactive detection mechanisms and tooling

  • Comfortable in a startup: high ownership, fast pace, and ambiguity

Preferred Qualifications:

  • Experience working with monitoring and observability tooling (e.g., Prometheus, Grafana, Datadog, OpenTelemetry) to operate systems at scale

  • Strong understanding of DevOps + SRE practices (CI/CD, infrastructure as code, observability, incident response)

  • Working knowledge of security principles (IAM, secrets, encryption, least privilege)

  • Exposure to MLOps

  • Experience working at early-stage startups


r/platformengineering • • Sep 22 '26

10 YOE in Support/SRE trying to break into Platform Eng / pure DevOps—getting stuck in support loops. Advice?

0 Upvotes

Hey everyone,
Looking for some career advice or insights from anyone who’s successfully transitioned out of Ops/Support/SRE and into dedicated DevOps or Platform Engineering roles.
Here’s a snapshot of my background:
Experience: 10 years in IT, primarily focused on operations, support, deployments, and infrastructure maintenance.
Hands-on Skills:
Azure & GCP: Day-2 operations, deployments, troubleshooting.
CI/CD: Fixing pipeline issues, minor configuration tweaks.
Terraform: Running existing configurations, troubleshooting state/apply issues.
Kubernetes & Helm: Managing deployments, tweaking Helm charts, and managing configurations.
The Catch: Most of my experience involves maintaining, fixing, and scaling existing systems rather than building infrastructure or pipelines completely from scratch.
Certifications: Azure Solutions Architect Expert, Terraform Associate, and GCP Associate Cloud Engineer (currently studying for GitHub Actions GH-200).
The Problem:
I'm trying to move away from support heavy roles into a proper DevOps or Platform Engineering position. However, I’m getting zero traction for IC DevOps/Platform roles. Ironically, I keep getting hit up by recruiters for Senior SRE or SRE Manager roles, and I am able to get offers there but I really don't want to stay in the support/operations space anymore.
My Questions:

  1. How do I bridge the gap from "fixing/maintaining" to "building from scratch"? Is the lack of end-to-end greenfield building what's holding me back in interviews?

  2. Are bootcamps worth it for someone with 10 YOE? Or would my time be better spent building a comprehensive end-to-end portfolio project (e.g., full gitops pipeline, custom terraform modules, internal developer platform pattern) from scratch?

  3. Has anyone made a similar jump? What was the single most impactful thing that helped you shift your narrative from Ops/Support to Platform/DevOps?

  4. Appreciate any advice, project recommendations, or resume tips!


r/platformengineering • • Jun 16 '26

Looking for guidance from DevOps engineers or freshers who recently cracked interviews

1 Upvotes

Hi everyone,

I am currently preparing for Junior DevOps Engineer roles and I am feeling stuck because I have never worked in a real DevOps environment.

I am studying concepts, watching tutorials, and learning tools like Linux, Docker, Kubernetes, AWS, Jenkins, Terraform, etc., but my biggest confusion is understanding what interviewers actually expect from a fresher.

For example, when I answer a question such as:

"Your Linux server disk suddenly becomes 100% full. How would you troubleshoot it?"

I can give an answer based on what I have learned, but I have no idea whether an interviewer would think

• "This answer is good enough for a fresher."

• "This candidate doesn't have practical knowledge."

• "Let's move to the next question."

​

What I am looking for is someone who has either:

Recently given multiple DevOps interviews as a fresher and understands the interview pattern, or

Is currently working as a DevOps Engineer and can explain what interviewers actually look for in junior candidates.

I have many similar doubts where I know the theory but struggle to judge whether my answers are interview-ready.

If anyone is willing to help, review answers, or share insights about how DevOps interviews are evaluated, I would be extremely grateful.

Thank you!


r/platformengineering • • Sep 01 '26

AI made me a better engineering leader

Thumbnail
leaddev.com
1 Upvotes

AI made me a better engineering leader, not by writing my code faster, but by sharpening the parts of the job that were never about code in the first place.


r/platformengineering • • May 28 '26

FinServ / fintech / crypto SREs: what would actually make your observability stack feel sane?

0 Upvotes

Hey folks,

I'm a founder working on observability infrastructure aimed at FinServ, fintechs(including crypto and AI) , and data-heavy enterprises. We have a functional product and small private betas lined up. Before we go any wider, I want to hear from SREs and platform engineers running production observability in regulated industries, because our own pain isn't necessarily yours.

Quick context on where we're coming from. My CTO has 8 years at a top US bank running Splunk, Grafana, and Datadog pipelines at petabyte scale. Our third co-founder is an SRE lead with 15 years across F500s. I'm a Fortune 500 tech lead and personally sign off on our observability bill every quarter. So we are operators, not consultants showing up with a deck.

Honest takes I'd love on any of these:

  • What is the single most frustrating thing about your current observability stack in 2026?

  • Where does compliance or audit posture force tradeoffs you wish you didn't have to make? Data deletion to manage cost, retention compromises, data-residency constraints, anything else?

  • What would you never give up about your current tooling and UI (Datadog, Splunk, Grafana, Elastic, whatever it is for you)?

  • If a tool could meaningfully cut your observability bill but required migrating off something you currently use, would you do it? Where's your line?

  • For regulated industries specifically, what does "audit-grade integrity" actually look like in practice? What do your auditors require?

  • One feature you'd consider a "must have" before evaluating anything new, versus a "nice to have"?

Also: what's a question you wish vendors would ask before showing up to pitch you?

I will respond to every comment. Happy to share what we're building in DMs if anyone wants the detail, but I'm deliberately not posting links here because this is a question post, not a launch.

Thank you.


r/platformengineering • • Sep 08 '26

Built and deployed a real AWS project cloud/ platform engineering

1 Upvotes

I spent time working at a dental tech company and it motivated me to build something that actually reflects real business workflows I saw there, scan uploads, lab fabrication, practice-to-lab communication. That became DentalFlow, a single-tenant dental lab workflow API, real Terraform-managed AWS infra (ECS Fargate, RDS Multi-AZ, S3, SQS/SNS), deployed and tested against the live system, not just local.

Would genuinely appreciate any critique, architecture, security, anything I'm missing or got wrong. Trying to build the judgment, not just the resume line and learn from experience individual while staying curious.

https://github.com/keusuanl/DentalFlow


r/platformengineering • • Jun 09 '26

PEngEx - Platform Engineer Experience

3 Upvotes

After years managing software and platform teams something dawned on me this week.

As platform engineers we spend a lot of time making things better for other teams and people and collectively refer to that as DevEx or DX. However we don't really spend too much time focussed on ourselves - in every business I've worked in, platform teams (like most teams) have had their fair share of friction and pain points and I personally have never really consciously focussed on what I'm coining PEngEx.

I'm curious if other leaders actively think about PEngEx and how they approach it outside of the usual metrics, toolchains and workflows


r/platformengineering • • Feb 05 '26

We quit our jobs to build this - open source AI SRE

8 Upvotes

My cofounder and I worked infra at Roblox. On-call sucked. The worst part was always the first 20 minutes - just trying to gather enough context to start debugging.

So we built an AI that does that part. Alert comes in, it checks logs, metrics, deploys, runbooks, and posts what it found in Slack.

The thing that actually makes it work: it reads your codebase and Slack history first, so it knows how your system is wired together. Not just generic "check your logs" advice.

Just open sourced it: github.com/incidentfox/incidentfox

Would love to hear people's thoughts!


r/platformengineering • • Sep 14 '26

We built a small in-house software factory: a bot in Slack provisions a dev VM, fixes small bugs and create PRs with auto-recorded demo of a fix.

5 Upvotes

This is something we’re doing internally at my company. We tag our bot in Slack, send it a bug report, controller provisions a GCP VM, local k8s + Tilt, then Claude Code works on it. Nobody has to set up the environment themselves, and follow-ups stay in the thread.

We wrote up a blog about the full workflow - link in comments.


r/platformengineering • • Oct 10 '26

Is event-driven architecture becoming the new microservices?

2 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 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?**


r/platformengineering • • Apr 11 '23

Platform Engineering Survey Results are Here!!

0 Upvotes

Hey everyone! Thank you to the people who responded to our survey the other month about the state of platform engineering. We had a total of 2289 real responses, and we analyzed the data and put together this website for you all to see. Thanks again!

https://survey.seaplane.io/admin/index