Platform Engineer

The journey

1. Practised under observation

   1. 01The platform seat and the paved-road thesisWhy this role exists: cognitive load as the real constraint, the platform as a product, and the honest history of what internal platforms get wrong.Practised under observation

      MilestoneDiagnoses the platform problem

      The waiting, the tickets and the expertise a team needs are mapped from watching rather than from guessing, and the obvious problem to solve turns out not to be the one you chose.

2. From here, milestones are verified rather than practised.

   Verified against a real task

   1. 02The orchestration substrateThe engine most platforms run on, operated as a multi-tenant foundation rather than as one team's cluster.Verified against a real task

      MilestoneOperates the substrate, multi-tenant

      One team cannot reach another team's work or eat their capacity, an upgrade happens without the tenants noticing, and your own team's workloads get no exception the tenants cannot have.

   2. 03Infrastructure as code as a platform capabilityProvisioning turned into a service, with modules designed for consumption by other teams and state and policy managed at organisational scale.Verified against a real task

      MilestoneProvisioning, productized

      Documentation is enough for a team you have never spoken to to provision real infrastructure, and a breaking change reaches them with a version, a warning and a way across.

   3. 04Developer experience and golden pathsThe heart of the seat: the paved road designed from real developer pain, with the safe path made genuinely the fastest one.Verified against a real task

      MilestoneThe paved road, measured

      Somebody who has never seen this goes from nothing to a running, observable service without asking you, and the compliant route is genuinely the quickest one rather than the mandated one.

   4. 05Self-service, portals and platform interfacesThe platform as a system engineers operate themselves, with self-service provisioning, a service catalogue, and the interfaces through which capability is consumed.Verified against a real task

      MilestoneSelf-service, end to end

      Nothing here needs a ticket to your team, and a team reaching outside its scope is stopped by the platform rather than by a conversation.

   5. 06Building the platform as softwareThe half of this seat that is genuine software engineering, with platform components designed, built, tested and released with the rigour demanded of product teams.Verified against a real task

      MilestoneThe platform, engineered

      Your own tests catch the fault before a tenant does, a fix reaches the services already generated and you say plainly how many it did not reach, and a rollout stops at the first tenant it hurts.

   6. 07Operating the platform: reliability, security and costThe platform in production: a system whose outage is an outage for everybody, secured as a shared trust boundary, and priced so its users know what they consume.Verified against a real task

      MilestoneOperated as everyone's dependency

      The platform can be down without the business being down, and every team can see what its own use of this costs.

   7. 08The Platform Engineer in the organizationAdoption is the job, with a platform earned rather than mandated and a roadmap driven by users who could always walk away.Verified against a real task

      MilestoneAdopted, funded, and honest about it

      Teams use this because they chose to, the value you claim traces to something you measured, and an offer to make it compulsory is turned down because a mandate would hide the answer.

3. 1. Capstone

      A platform engineers choose

      A complete internal platform for a realistic engineering organisation, proposed by you and approved by an instructor, built under observation, from the platform assessment through a multi-tenant substrate, a productised module library, a measured golden path and self-service interfaces to operating the platform and earning its adoption.

      Defence

      You walk an instructor through your own platform: who your users are and what you watched them struggle with, whether they would use it if it were optional and what your evidence is, how a team that does not fit leaves and what their exit taught you, and what the platform costs, who pays for it and what it saves. The credential is not awarded if you cannot account for your own work.

   2. Credential

      High-assurance credential

      Evidence that you can build an internal product engineers would choose without being told to, and measure it by how much faster everybody else ships. It does not claim seniority, and it does not oblige any employer to accept it.

      See how proof works