English for Platform Engineers: The Vocabulary You Need

IDP, golden path, paved road, developer experience — the vocabulary platform engineers use when designing, pitching, and evolving internal developer platforms.

Platform engineering sits at the intersection of infrastructure and product — you are building a product whose customers are other developers. That means you need vocabulary not just for the technical work, but for selling the vision internally, writing RFCs, and explaining trade-offs to leadership. Getting the language right shapes how your platform is adopted.


The Platform Itself

IDP (Internal Developer Platform) The collection of tools, workflows, and self-service capabilities a platform team builds for product engineers. Note: do not confuse with IDP (Identity Provider). In context, say “internal developer platform” on first use. Phrase: “We’re building an IDP so teams can deploy without opening a ticket.”

Golden path The recommended, supported way to do something — the path the platform team has paved, tested, and documented. It is not mandatory, but it is the path of least resistance. Phrase: “Follow the golden path for service creation — it gives you CI, observability, and secret management out of the box.”

Paved road Often used interchangeably with golden path. The metaphor is explicit: the platform team paved the road, you still choose whether to drive on it. Some teams distinguish them — the paved road is the golden path plus the guardrails that keep you on it.

Scaffolding Auto-generated project skeletons or boilerplate that conform to the golden path. Engineers run a command and get a ready-to-deploy service structure. Phrase: “The scaffolding CLI generates the repo, Dockerfile, Helm chart, and Grafana dashboard in under two minutes.”

Self-service The ability for product engineers to provision infrastructure, configure environments, or deploy services without filing tickets or waiting for the platform team. This is the core value proposition of a mature IDP. Phrase: “Self-service is the goal — if they’re asking us to click things, we’ve failed.”


Developer Experience and Metrics

Developer experience (DX) The sum of all experiences a developer has while working with your platform — how fast they can onboard, how clear the documentation is, how painful debugging is. Poor DX leads to shadow IT (teams building their own solutions). Phrase: “DX surveys show that local environment setup is the biggest pain point.”

Cognitive load The mental effort required to understand or operate a system. High cognitive load slows teams down and causes errors. A platform’s job is to reduce cognitive load by hiding complexity behind good abstractions. Phrase: “We abstracted the Kubernetes manifests into a simple YAML spec — the goal was reducing cognitive load for app teams.”

Platform team The team responsible for building and maintaining the IDP. Also called infra product team or developer productivity team in some organisations. A platform team treats product engineers as customers and uses product management practices (roadmaps, user research, OKRs).

SLA for internal platforms Service Level Agreements apply to internal platforms too. Phrase: “Our IDP SLA commits to 99.5% availability of the CI/CD pipeline and a P95 build time under 8 minutes.” Tracking and publishing SLAs signals that the platform team is accountable.


Culture and Adoption

Dogfooding Using your own platform to build your own services — “eating your own dog food.” Platform teams that dogfood discover pain points before product engineers do. Phrase: “We dogfood the IDP for our own monitoring stack — if it hurts us, we fix it before shipping.”

Developer journey The sequence of interactions a developer has with the platform — from first onboarding to deploying in production to debugging an incident. Mapping the developer journey reveals friction points. Phrase: “The developer journey from account creation to first deploy should take under 30 minutes.”

Toil Repetitive, manual operational work that scales linearly with platform growth and provides no lasting value. Automating toil is a primary platform engineering motivation. Phrase: “Rotating certificates manually is pure toil — we’re replacing it with cert-manager.”


Real Phrases from Platform Teams

  • “Let’s keep the golden path opinionated but escapable — teams can deviate if they accept the support burden.”
  • “The scaffolding doesn’t enforce structure, but it nudges teams toward it.”
  • “We need to reduce time-to-first-deploy as our north star DX metric.”
  • “The platform’s job is to make the right thing the easy thing.”

Practice: Read the CNCF Platforms White Paper and notice how these terms appear in context. Then write a one-paragraph pitch for an IDP feature you would build, using at least five of the terms above.