12 weeks · intensive
For whoever has a deadline
About 8 hours a week, in 1 cycle focused on the gaps that weigh most.
Career in 2026 and 2027
Platform Engineer
A platform engineer builds the internal tooling, pipelines and clusters that let product teams ship without becoming infrastructure experts. The platform is treated as a product whose customers are developers, measured by how fast and safely they can deliver.
Content reviewed on October 20, 2026
- Levels
- 3
- Skills mapped at Senior
- 14
What each level must prove
Senior
Accountable for the platform as a product: its portal, its interfaces, its supply chain and whether developers are measurably better off.
Beyond keeping tools running, the day includes deciding what the platform offers, talking to the teams that use it and arguing for investments with data. Compared with mid, you stop fixing individual requests and shape the interfaces and team structure that remove them.
Average score required: 75%
Self-Service Infrastructure
Why: Lets you design self-service with guardrails for cost, security and ownership, so teams can create environments freely without a forgotten, unsecured database appearing on the bill.
Developer Portal (Backstage)
Why: Lets you run a service catalogue in Backstage with owners, docs and links, so during an incident anyone can find who owns a failing service in seconds.
Kubernetes Operations
Why: Lets you set the upgrade cadence, tenancy model and policy for many teams' clusters, and plan version rollouts so an API removal does not break applications you do not own.
Helm Chart Design
Why: Lets you version a shared chart and manage its dependencies and upgrades, so changing a default does not silently alter the deployment of dozens of services.
Terraform Modules & State
Why: Lets you govern module versions and state layout across accounts, so a change to a shared network module is rolled out deliberately instead of breaking every consumer on the next apply.
GitOps (ArgoCD/Flux)
Why: Lets you structure repositories and promotion for GitOps across many teams, deciding who may change what, so drift and ownership disputes do not accumulate as you scale.
Build Optimization & Caching
Why: Lets you size shared build infrastructure and remote caches across the company and show the saved engineer-hours, which is how you justify the budget for it.
Artifact Management
Why: Lets you promote one signed image through environments from a controlled registry, so what ran in staging is what reaches production and a compromised dependency can be traced.
Centralized Logging
Why: Lets you decide retention, indexing and cost of the log platform for the whole company, so incident search stays fast without the log bill growing faster than the traffic.
Metrics & Dashboarding (Prometheus/Grafana)
Why: Lets you define a metric naming and cardinality standard, so a team adding a high-cardinality label does not overwhelm Prometheus and dashboards stay comparable across services.
Platform Team Topologies
Why: Lets you explain why the platform team provides services rather than taking tickets, and set its interaction with stream-aligned teams so it does not become a bottleneck for them.
API-First Platform Design
Why: Lets you expose platform capabilities through versioned APIs, so other teams can automate against them and you can change internals without breaking their scripts.
Internal Developer Platforms
Why: Lets you connect pipelines, infrastructure and docs into one internal platform, so a developer goes from idea to a running service through a single path instead of five tools.
Developer Experience Metrics
Why: Lets you pair DORA numbers with developer surveys to show whether the platform helps, and pick the next investment from evidence rather than from the loudest request.
Study for Platform Engineer: trails and practice exams
Each level of this career maps to a study trail. Read the full topic map for free, then measure your level.
Two ways to move up one level
40 weeks · regular
Alongside work
About 4 hours a week, in 3 cycles. Each cycle carries what was left from the previous one.
Frequently asked questions
What is Platform Engineer?
A platform engineer builds the internal tooling, pipelines and clusters that let product teams ship without becoming infrastructure experts. The platform is treated as a product whose customers are developers, measured by how fast and safely they can deliver.
What must each level of Platform Engineer prove?
Platform Engineer is mapped in 3 levels: Mid-level, Senior, and Expert. Open each level above to see the skills it must prove.
How long does the Platform Engineer plan take?
The plan has 2 paces: 12 weeks per level at about 8 hours a week (intensive) and 40 weeks per level at about 4 hours a week (regular).
How the plan works
AI tutor
A study session on each new topic, at your level.
AI school
Hands-on lessons on using AI in your career's daily work.
Assessments
Each requirement is proven by measurement, not by a checkbox.
Stage review
At the end of each cycle you see what moved and what carries over.
Find out which level you are at
A short diagnostic measures the skills you already have. The journey starts from there.