What does a Platform Engineer actually do?

KNOWN ALIASES / DISGUISES:

MARKET AVERAGE

$145,000

* Highly variable based on location, company size, and the actual scope of 'platform' responsibilities, often a rebranding of DevOps work with little pay increase.

"This compensation package ensures the perpetual availability of a human firewall against the inevitable collapse of poorly architected microservices."

[DIAGNOSIS]Constant on-call burden, thankless task of maintaining other teams' unstable services, and the perpetual redefinition of their 'platform' make them prime candidates for burnout and exodus.

"As a platform engineer, you design, install and maintain the essential platforms that propel software applications, allowing them to work efficiently and effectively."

OTIOSE TRANSLATION

Architect and steward the labyrinthine dependencies that enable other engineers to perpetually ship marginally functional code, ensuring optimal resource consumption for maximum shareholder value.

"A platform engineer oversees a company's software applications. They do more than just create software. They also deploy and maintain it. Their job is to make operations smoother, automate tasks and fix any problems that might stop the software..."

OTIOSE TRANSLATION

Assume custodial responsibility for the digital assets of the organization, perpetually optimizing the 'DevOps pipeline' to eliminate manual human intervention, thus accelerating the deployment of next quarter's inevitable refactor.

"Develop robust internal automation and tooling for ML workflow orchestration, resource scheduling, and platform operations, with a strong focus on software engineering best practices. Collaborate with ML researchers and applied scientists to understand infrastructure needs and build solutions that streamline their end-to-end experimentation. Evolve and operate our multi-cloud and hybrid (on-prem + cloud) environments, implementing monitoring, alerting, and incident response protocols. Participate in on-call rotation to provide support for platform services and infrastructure running critical ML jobs, driving root cause analysis and implementing preventative measures."

OTIOSE TRANSLATION

Construct elaborate Rube Goldberg machines to 'orchestrate' theoretical machine learning breakthroughs, while simultaneously being on-call 24/7 to resolve self-inflicted outages in a sprawling, multi-cloud environment, ensuring seamless data flow for the next quarterly AI initiative.

[10:00 - 11:00]

Triaging PagerDuty Alerts

Responding to critical alerts triggered by a non-critical application, often requiring a full context switch to debug someone else's code.

[13:00 - 14:00]

Platform Roadmap Alignment Sync

A cross-functional meeting where the platform team's efforts are 'aligned' with product goals, usually resulting in a list of new, unrealistic demands.

[15:00 - 16:00]

YAML Configuration Refinement

Meticulously adjusting indentation and variable names in configuration files, praying the next deployment doesn't break due to a misplaced comma.

"The issue is HR has no idea what any of these things are, they just go off of Salary.com or whatever, and apparently my salary was already within the salary of a Platform Engineer of equal level."

— r/devops

"My entire week is just writing YAML to glue together three different cloud provider services, then debugging why they refuse to talk to each other. We call it 'platform innovation'."

— teamblind.com

"They promised 'developer enablement' but it's really just me being on-call for every poorly written microservice, while Devs complain my 'platform' isn't magical enough."

— r/cscareerquestions