What is platform engineering, and how does an internal developer platform (IDP) change the DevOps operating model?
Quick Answer
Platform engineering productizes the paved road: a dedicated team builds self-service golden paths (templates, pipelines, environments, observability defaults) that product teams consume, replacing both 'central ops ticket queues' and 'every team reinvents infrastructure'. The IDP is the product; developers are its customers; 'you build it, you run it' stays — but on rails the platform provides.
Detailed Answer
The problem it solves: pure 'every team owns everything' DevOps scales badly — 30 teams make 30 Terraform patterns, 30 alerting philosophies, and 30 sets of security mistakes, while cognitive load crushes product engineers. The platform team's answer is golden paths: a service scaffold that generates repo + CI/CD + deployment manifests + dashboards + on-call wiring in minutes, self-service infrastructure (databases, queues, environments) via catalog or API with security/compliance baked in, and defaults that make the right thing the easy thing. Key operating-model shifts: the platform is a product with a roadmap, user research, and adoption metrics (not a mandate — internal teams choosing it is the health signal); product teams still own their services in production (the platform reduces their cognitive load, not their accountability); and escape hatches are explicit — teams can leave the paved road but then own what they build. Failure modes worth naming: the rebranded-ops-team that still runs a ticket queue, the ivory-tower platform nobody asked for, and mandating adoption instead of earning it. Backstage-style portals, scaffolding, and scorecards are common furniture, but the portal is the least of it — the paved road underneath is the product.
Code Example
# a golden path, concretely $ platform create service --template go-api --name payments-refunds ✓ repo + CODEOWNERS ✓ CI/CD from org template (OIDC, scans) ✓ helm chart + env overlays ✓ dashboards, SLO + burn-rate alerts ✓ on-call rotation wired ✓ registered in service catalog # 20 minutes to a deployable, observable, on-call-ready service
Interview Tip
'The platform is a product, adoption is voluntary, and accountability stays with service teams' — those three clauses distinguish platform engineering from a renamed ops team, which is exactly the confusion interviewers test.