Platform Engineer: market

Vacancy

an open job that cleared the quality gate and lists at least two technologies

Observed candidate

a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter

Matchable candidate

not counted yet

Window

jobs open at the moment the snapshot was built

Junior — rare (typical entry: DevOps Middle / Backend Middle + interest in internal-tooling). The Junior → Middle jump — after the first end-to-end IDP capability deployment (e.g. Backstage Software Templates for new-service scaffolding). Middle → Senior — multi-team platform ownership + DX metrics improvement track (e.g. reduce mean Time to First Deploy from 2 weeks to 2 days). Senior → Staff / Principal — org-wide IDP architecture + cross-team platform-as-product strategy. Career flow: DevOps Middle / Backend Middle (2-3 years) + interest → Platform Engineer Junior (1-2 years) → Middle (2-3 years) → Senior → either Platform Architect, DX Engineer specialisation, or Engineering Manager (Platform team).

Top 5: agile, devops, cloud, graphql, azure. IDP (Internal Developer Platform) tools: Backstage (Spotify open-source — dominates 2026 — CNCF incubating; the largest job market) — need to know React + TypeScript (frontend customisation) + Node.js (backend plugins) + Backstage entity model + Software Catalog + TechDocs + Software Templates + Kubernetes plugin. Port (commercial — best UX 2026 — competing with Backstage growing fast) — simpler to customise, Port-specific schema. Cortex (alternative — service catalog focus). Humanitec (platform orchestrator-focused — auto-deployment patterns). OpsLevel, Configure8. Self-service templates: Backstage Software Templates (cookiecutter integration) / Port Actions / custom CLI scaffolding (Yeoman / Plop / custom Go CLI). Service catalog: tracking all services + ownership + dependencies + maturity scoring (Backstage Software Catalog / Port / OpsLevel). Kubernetes ecosystem deep: foundation for platform — Crossplane (K8s-native IaC, provider-agnostic — best for platform abstraction), Argo CD (GitOps foundation), Tekton (pipeline platform), Knative (serverless platform). Platform abstractions: Crossplane Compositions (typed cloud-resource abstractions — example: "provision Postgres" = single API call expanding to RDS + IAM role + Secret + Network), Terraform modules + Spacelift / Atlantis (managed IaC), Kratix (platform-as-product framework — interesting newer entry 2024+). API gateway for platform APIs: Kong / Tyk / Apigee / AWS API Gateway. Developer portal: Backstage UI / Port UI / Cortex UI — single pane of glass for devs (service catalog + docs + actions + observability). DX (Developer Experience) metrics: DORA metrics (Deployment Frequency / Lead Time for Changes / Mean Time to Recover / Change Failure Rate — Google DevOps Research and Assessment framework), SPACE framework, DX surveys (developer feedback). Tools: Sleuth / LinearB / Faros AI / Swarmia / Code Climate Velocity. CI/CD platform: typically Tekton Pipelines (CNCF native) or Argo Workflows + Argo Events. Observability for the platform itself: platform adoption metrics + cost-per-team attribution + DX scores tracking. Languages: TypeScript primary (Backstage plugins) + Go for custom platform tooling + Python for automation.

DevOps Engineer — focus on CI/CD + cloud + K8s for a single team / product. Mid-team-level focus. See DevOps Engineer (general). SRE (Site Reliability Engineer) — focus on reliability + SLI / SLO + on-call + automation for toil reduction. Programming-heavy. See Site Reliability (SRE). Platform Engineer (this page) — focus on reusable self-service developer platform for the whole engineering organisation. Internal-product-thinking: developers = customers, platform team = product team. Day-to-day: build self-service capabilities (e.g. "one-click new service creation" via Backstage Templates), maintain service catalog + golden paths + paved roads. Programming-heavy (TypeScript + Go). Key distinction 2026: Platform Engineering — NOT just rebranded DevOps. Real distinction: platform-as-product mindset + DX metrics ownership + multi-team adoption strategies + internal-tooling product thinking. Difference from SRE: SRE owns reliability of services. Platform Engineer owns reliability + UX of the internal platform itself (which other teams use to deploy their services). Platform Engineer measures success not by infra uptime but by "how many minutes does a new engineer take to deploy their first service?" Difference from DevOps: DevOps Engineer is typically deeply embedded in a product team (CI/CD for one product). Platform Engineer works on cross-cutting infra used by 10+ product teams. Career-overlap reality 2026: 60-70% shared stack. Easy lateral moves DevOps Senior ↔ Platform Engineer (3-6 months). Smaller orgs: one person = both DevOps and Platform. Medium / Large (50+ engineers): separate roles.

Decision tree for IDP choice 2026: 1) Backstage (Spotify open-source 2020, CNCF incubating 2022) — market leader 2026 (~60% share). The largest niche for plugin development + custom integrations. Strengths: huge community (10K+ stars GitHub), 130+ official plugins, fully open-source, polyglot service support, Software Catalog + TechDocs + Software Templates all built-in, integrations with everything. Weaknesses: high implementation effort (typical Backstage rollout — 6-12 months engineering investment), requires React + TypeScript expertise for customisation, complex authoring of plugins, ongoing maintenance heavy. Use case: companies with 50+ engineers + dedicated platform team (3+ engineers) + want full ownership + open-source preference. 2) Port (commercial Israeli startup — founded 2022, rapid growth 2024–2026) — challenger leader with best UX. Strengths: dramatically simpler implementation (typically setup in 1-2 weeks vs Backstage 6-12 months), declarative blueprint model, beautiful UI, built-in Self-Service Actions, drag-drop service builders, native Slack / Teams integrations. Use case: companies with 20-200 engineers + want fast value + don't want to invest in a platform team of 3+ engineers. 3) Cortex (commercial — founded 2020, slightly older than Port) — service catalog focus. Strengths: best-in-class service catalog scoring + maturity tracking, focus on "production-readiness scorecards". Use case: organisations where the primary problem is tracking service quality across many teams. 4) Humanitec (commercial — platform orchestrator-focused) — different angle than IDP portal. Strengths: deep K8s automation + multi-environment deployment patterns + workload separation. Use case: heavily K8s-focused platforms where deployment automation is the primary need (vs service discovery). 5) OpsLevel, Configure8 — alternatives, smaller market share. 6) Self-built — companies sometimes build their own minimal IDP with (Hugo / Next.js static + custom API integrations). Default 2026 recommendations: Large enterprise / open-source preference / dedicated platform team → Backstage. Mid-market (20-200 engineers) / want fast value → Port. Service catalog quality primary need → Cortex or Port. K8s deployment automation primary → Humanitec. Backstage market 2026 — the largest job category, but Port jobs are growing fast.

Yes, 36% of Platform Engineer jobs are full-remote or hybrid. Platform work — cloud-based + internal-tooling = ideal for remote. Outsourcing shops — almost always remote on US projects. Russian companies — hybrid or remote after probation. International tech companies — full-remote standard. Big Tech — hybrid-standard. Backstage core-team contributors (CNCF community work) — full-remote by definition. Relocant hubs: Poland / Germany (Platform Engineering-friendly) / Canada / Serbia / Georgia / UAE. English for international Platform remote — must (Platform Engineering community is English-speaking — CNCF / Backstage Working Groups / KubeCon Platform Engineering Day).

Platform Engineer (general) — builds + maintains platform capabilities. Owner of technical implementation. DX (Developer Experience) Engineer — sub-specialisation focusing on developer productivity metrics + developer feedback loops. Day-to-day: 1) Quantify developer productivity (DORA + SPACE metrics measurement automation), 2) Developer survey design + analysis (qualitative feedback), 3) Identify friction points in developer workflow (e.g. "build takes 30 minutes", "test flakiness 15%", "time to provision dev environment 2 hours"), 4) Drive cross-team initiatives to reduce friction (sometimes implementing themselves, sometimes coordinating with other teams), 5) Onboarding optimisation (reduce time-to-first-PR / time-to-first-deploy for new hires), 6) Tooling standardisation decisions (recommend / mandate specific IDE / framework / build tool choices), 7) Developer documentation strategy (Backstage TechDocs / mkdocs / custom). Skills: technical (must understand the entire platform stack) + analytics (data-driven productivity measurement) + people (interview developers + extract real problems) + product-thinking (prioritise improvements based on impact). Programming light to moderate. Pay: DX Engineer comparable to Senior Platform Engineer. In US tech companies — DX Engineer became a sought-after role 2024–2026 thanks to high ROI (developer time = expensive). Career choice: Platform Engineer if implementing capabilities is more interesting than measuring. DX Engineer if data-driven productivity analysis + empathy for developer-pain-points + cross-team influence is interesting. Both are legitimate Senior+ paths. Famous DX Engineer voices 2026: Abi Noda (DX co-founder, ex-GitHub research lead — wrote SPACE framework paper), Lorin Hochstein (resilience engineering / chaos), Charity Majors (observability + DX overlap — Honeycomb).

Roadmap: 1) Solid DevOps base — Linux + Docker + Kubernetes (CKA) + IaC (Terraform) + one cloud + CI/CD. Platform Engineering builds ON TOP of the DevOps stack. 2) Software engineering skills — Backstage and custom platform tooling are software engineering applied to infra problems. Backend Middle level in one language (Go primary for CLI tools, TypeScript + React for Backstage). 3) Backstage deep — most marketable IDP skill 2026. Resources: Backstage Documentation (backstage.io) + Backstage YouTube channel + "Developer Platforms with Backstage" Eli Goldberg book. Set up a Backstage instance on your own infra. Create a custom plugin (e.g. integrate a company-specific dashboard). Contribute a small fix to Backstage core. 4) Crossplane — second-most marketable platform skill. Learn Compositions (typed cloud-resource abstractions). Set up Crossplane on a K8s cluster, define a composition for "provision Postgres" (abstracts RDS + IAM + Secrets). 5) ArgoCD mastery (Platform-deployed apps + ApplicationSets for multi-tenancy). 6) Tekton Pipelines — CNCF pipeline platform (alternative to Jenkins + GitLab CI for platform-native CI/CD). 7) DORA metrics setup — implement automated tracking for Deployment Frequency / Lead Time / MTTR / Change Failure Rate (can use tools — Sleuth / LinearB / Faros AI or custom). 8) SPACE framework reading — paper "The SPACE of Developer Productivity" Forsgren / Storey / Maddila / Zimmermann / Houck / Nagappan (free PDF). 9) Service catalog design — Backstage Software Catalog / Port blueprints — entity modelling for your real org structure. 10) Self-service templates — Backstage Software Templates (cookiecutter-based) — create a template for a new microservice (including K8s manifests + CI/CD + observability + service catalog entry). 11) Advanced pet project: full IDP setup (Backstage + Crossplane + ArgoCD + custom Software Templates + DORA metrics dashboard) — document as portfolio. 12) Platform Engineering community engagement: KubeCon Platform Engineering Day (CNCF), Internal Developer Platform community (internaldeveloperplatform.org), platformengineering.org community. Must-read books: "Team Topologies" Skelton / Pais (canonical for understanding platform teams + interaction modes), "The Phoenix Project" Kim + sequel "The Unicorn Project" (DevOps + Platform context), "Accelerate" Forsgren / Humble / Kim (DORA metrics origin), "Developer Platforms with Backstage" Goldberg. Courses: Backstage Working Group videos (free YouTube), internaldeveloperplatform.org learning paths, Humanitec Academy (free platform engineering courses). DevOps Middle / Backend Middle + interest → Platform Engineer Junior — 4-10 months.

62 active open Platform Engineer positions — growing internal-developer-platform specialisation. Geography: Russia / Poland / remote. The real market is broader thanks to the international remote segment. Time to close a Senior Platform Engineer role — 5-10 weeks (longer than general DevOps due to specialisation + Backstage / Port expertise requirement). Platform Engineering as a category is growing fastest 2024–2026 per DORA / Puppet State of Platform Engineering reports.

A Senior Platform Engineer owns the full cycle of IDP architecture + DX optimisation + technical leadership. Software engineering at Backend Senior level: TypeScript + React mastery (for Backstage plugin development) + Go primary (for custom platform tooling) + Python for automation. Backstage mastery deep: plugin authoring (frontend React components + backend Node.js plugins), Software Catalog entity model deep, TechDocs setup advanced, Software Templates advanced (custom Yeoman generators), Catalog Processors for custom entity sources, Permission Framework for multi-tenant Backstage. Or Port / Cortex equivalent expertise in an alternative IDP. Crossplane mastery: Compositions design (typed cloud-resource abstractions), custom Provider development if needed, multi-cloud abstraction patterns. Kubernetes platform mastery: ArgoCD ApplicationSets for multi-tenancy + multi-cluster, Tekton Pipelines advanced, Knative for serverless platform offering. Self-service templates design: scaffolding mastery (Backstage Software Templates / Port Actions / custom CLI), enabling new-service-creation from idea to production in minutes. Service catalog architecture: entity model design for real org structure, ownership tracking automation, dependency tracking automation, maturity scoring. DORA metrics mastery: automated tracking implementation (from raw git + deployment data to dashboard), monthly metrics review meetings, target setting + improvement initiatives ownership. SPACE framework application: design + run developer surveys, qualitative feedback synthesis, action items prioritisation. Developer interview skills: extract real problems vs surface complaints (5-Whys methodology), identify cross-cutting themes. Multi-team adoption strategy: "platform-as-product" — design product launch for new platform capabilities (private beta → internal launch → adoption metrics tracking). Cross-team coordination: work with 10-20 product teams using the platform — manage feedback + feature requests + breaking changes + deprecation cycles. System design for platforms: design IDP architecture on a whiteboard for a engineers org, multi-region considerations, blast radius limitation. Cost-attribution for platform: per-team chargeback / showback dashboards, platform team budget defence vs ROI. Soft: ADRs writing for platform decisions, technical writing (platform documentation + onboarding materials), executive communication (platform value reporting to CTO / VP Engineering), product roadmap planning, hiring + mentoring Junior / Middle Platform Engineers. English for Senior+ MUST — Platform Engineering community (KubeCon Platform Engineering Day / Backstage Working Groups / platformengineering.org) is English-speaking. Optional bonus: open-source contributions to Backstage / Crossplane / ArgoCD / Tekton — sharply increase market value (the market is small + community-driven hiring).