Role reference
Platform engineering roles: what each does and what each costs
Platform engineering is not one role. Six distinct titles live under the umbrella. Understanding what each does, when to hire each, and how they distinguish from adjacent roles is half of the headcount plan.
Across mature platform organisations, six job titles repeat. The boundaries between them are fuzzy in practice, especially at small scale where one engineer wears two or three hats, but the titles are useful for headcount planning and career progression.
Platform Engineer (generalist)
Loaded cost
$180k - $290k
ScopeBuild and operate shared capabilities other engineers depend on: infrastructure-as-code, CI/CD pipelines, service templates, deployment tooling. The foundational role on any platform team.
SkillsInfrastructure-as-code (Terraform, Pulumi, CDK), one major cloud provider at production depth, container orchestration, one CI platform, one observability tool, strong scripting.
Hiring signalThe first hire for most platform teams. Prefer senior with cross-company experience (small and large company backgrounds). Junior platform engineers struggle without a more senior IC to learn from.
Developer Experience (DevEx) Engineer
Loaded cost
$180k - $270k
ScopeFocus on the developer-facing surface of the platform: local dev environment, onboarding flows, internal CLI, documentation systems, developer portal, scaffolding templates.
SkillsFrontend or CLI tooling development, strong technical writing, user research skills, familiarity with developer-tool patterns, internal-product mindset.
Hiring signalBecomes a distinct role at 80+ product engineers. Below that the generalist platform engineer covers DevEx. Prefer engineers who have worked on developer tools as a product.
Site Reliability Engineer (platform-focused)
Loaded cost
$190k - $310k
ScopeReliability contract: SLO definition, incident response, capacity planning, observability backbone, on-call rotation leadership, post-incident review process.
SkillsStrong systems-level understanding, at least one production incident management role, observability tooling at depth, queueing-theory-adjacent capacity thinking.
Hiring signalFirst SRE specialist at 5-8 platform engineers. Often promoted from internal senior IC. Overlaps heavily with generalist platform engineer in practice.
Platform Engineering Manager
Loaded cost
$260k - $360k
ScopePeople management for 5-10 platform engineers, stakeholder alignment with product engineering leadership, platform roadmap ownership, quarterly planning, team hiring.
SkillsProven engineering management at similar scale, ability to hold the IC-vs-manager conversation credibly, stakeholder management, clear writing for executive communication.
Hiring signalNeeded around 6-8 platform engineers. Often promoted from within; external hires have higher failure rate because platform management needs deep stakeholder relationships.
Platform Engineering Director / VP
Loaded cost
$360k - $520k (plus equity)
ScopeCross-organisational platform strategy, CFO-facing budget ownership, VP-level stakeholder management, long-range capability planning, director-level hiring.
SkillsProven engineering leadership at 50+ direct and indirect reports, finance literacy, strong business-outcome framing of engineering work, executive presence.
Hiring signalAppears at 200+ product engineers. Almost always external hire with prior platform director experience. Often reports to VP or SVP Engineering.
Technical Program Manager (Platform)
Loaded cost
$180k - $260k
ScopeCross-team coordination for platform initiatives: golden-path rollouts, legacy migrations, compliance programmes. Non-engineering role but requires deep technical literacy.
SkillsTPM experience at a similar-sized engineering organisation, technical literacy (can read code, understand architectural diagrams), strong written communication, stakeholder-management discipline.
Hiring signalNeeded at 15+ platform engineers when the engineering manager is spending more than 30 percent of their time on cross-team coordination. Usually external hire.
Overlap with DevOps
The platform engineer versus DevOps engineer distinction is muddier than the trade press suggests. Historically, DevOps engineer meant an IC embedded in a product team running that team's infrastructure. Platform engineer means a centralised IC building shared capabilities. In 2026, many organisations use DevOps engineer as the job title and expect platform engineering scope from the hire, or use platform engineer title and expect DevOps-style embedded responsibilities.
The transition has been gradual (2020-2026) and is not complete. For hiring, the practical guidance is to read the job description closely and ignore the title. Ask the hiring manager about team structure: centralised or embedded, shared roadmap or team-specific, on-call for shared infrastructure or per-team.
Hiring sequence as the team grows
The order matters. A platform team of eight hired in the right order ships more value than a platform team of eight hired haphazardly. The following sequence works well for most mid-size organisations moving from zero to eight platform engineers.
- Hire 1. Senior generalist platform engineer. Someone who can cover CI, cloud, and infrastructure-as-code. Ideally with 5+ years of production experience.
- Hire 2. Second senior generalist platform engineer within 6-9 months, to eliminate single-point-of-failure risk and enable sustainable on-call.
- Hire 3. Mid-level platform engineer at 12-15 months, to expand roadmap capacity. Mid-level is the right level here because the seniors set direction and review work.
- Hires 4-5. Specialisation starts. One hire focused on CI/CD, one focused on observability and reliability (SRE overlap).
- Hire 6. Developer Experience engineer. The team has enough capability to serve; now it needs someone focused on the developer-facing surface.
- Hire 7. Engineering manager. With six to seven ICs, you need a dedicated manager; a tech lead role no longer scales.
- Hire 8. Fill the gap the team has identified after a year together. Often a second DevEx or a second SRE.
Past eight engineers, the platform starts to split into sub-specialisms and the hiring pattern becomes more organisation-specific.
Salary ranges by role
Detailed compensation by level and metro.
Team structure by scale
How these roles fit together at different org sizes.
The first hire
What to look for in the first platform engineer.
Frequently asked questions
What is the difference between a Platform Engineer and a DevOps Engineer?
In 2026 the two titles overlap heavily. DevOps engineer has historically meant individual contributors embedded in product teams running that team's infrastructure. Platform engineer means centralised contributors building shared capabilities for all product teams to consume. The scope is similar; the organisational model differs. Many organisations still use DevOps engineer as the job title and expect platform engineering scope. Salary tracks 5-10 percent above DevOps engineer for equivalent seniority.
When do you need a Developer Experience Engineer specifically?
Around 80 product engineers, when the developer-facing surface of the platform (onboarding, docs, dev environment, internal CLI) becomes big enough to need a dedicated owner. Below that, a generalist platform engineer can cover DevEx as part of their scope. A dedicated DevEx engineer is typically the third or fourth hire into a platform team, after the infrastructure-focused roles are filled.
What is the scope of a Site Reliability Engineer on a platform team?
Reliability. An SRE on a platform team owns production incident response, SLO definition, capacity planning, observability backbone, and the reliability contract between the platform and product teams. In some organisations SRE is a separate team that interfaces with platform; in others it is a sub-specialism within platform. The distinction matters for on-call rotation structure but not much for day-to-day technical work.
When do you need a Platform Engineering Manager?
Around 6 to 8 platform engineers. Before that, a senior IC who wants to grow toward management can lead the team as a tech lead. Above 8 engineers, a dedicated manager becomes necessary because the work of hiring, career development, stakeholder alignment, and roadmap ownership exceeds what an IC can cover part-time. Avoid hiring the manager before the team exists to avoid top-heavy platform functions.
Do small teams need a Technical Program Manager for platform?
No, typically not below 15 platform engineers. TPM role makes sense when the platform is running multi-team programmes (golden-path rollouts across dozens of product teams, multi-quarter migrations, compliance initiatives). For small teams, the engineering manager or director handles programme coordination. A dedicated TPM is the right hire when the EM is spending more than 30 percent of their time on cross-team coordination.