Learning path
Platform Engineer learning path: everything to study, topic by topic
Comprehensive Platform Engineer assessment covering developer experience, container orchestration, infrastructure as code, CI/CD platform design, observability, and platform strategy.
Short answer
To learn Platform Engineer, work through 7 modules and 35 topics in the order they build on each other. It starts with Developer Experience, then moves on to Container Orchestration and Infrastructure as Code. Use the map as a checklist, or measure your level and study only what is missing.
What you will study
Topics are grouped by module. Open one to see its objectives and key concepts.
1 · Developer Experience5 topics
Golden Paths & Templates
Opinionated starter templates, project scaffolding, cookiecutter generators, and standardized development environments that accelerate onboarding and reduce cognitive load
Objectives
- Design golden paths that balance developer autonomy with organizational standards
- Create project templates that encode best practices without over-constraining teams
Key concepts
- golden paths
- project scaffolding
- cookiecutter templates
- starter kits
- dev containers
- standardized environments
- inner-loop optimization
Self-Service Infrastructure
Internal tooling that allows developers to provision infrastructure, databases, and environments without filing tickets or waiting for operations teams
Objectives
- Build self-service infrastructure with appropriate guardrails and cost controls
- Balance developer velocity with governance and security requirements
Key concepts
- self-service portals
- infrastructure catalogs
- guardrails vs gates
- approval workflows
- resource quotas
- cost controls
- audit trails
Developer Portal (Backstage)
Building and operating internal developer portals using Backstage or similar tools to unify service catalogs, documentation, and developer tooling in one place
Objectives
- Design a developer portal that consolidates tooling and improves service discoverability
- Implement Backstage plugins and software templates for team-specific workflows
Key concepts
- Backstage
- service catalog
- software templates
- TechDocs
- plugin architecture
- entity model
- catalog-info.yaml
Documentation-as-Code
Treating documentation as code with version control, CI/CD pipelines for docs, automated API documentation, and living documentation strategies
Objectives
- Implement documentation pipelines that keep docs in sync with code changes
- Design a documentation strategy that scales with organizational growth
Key concepts
- docs-as-code
- MkDocs
- Docusaurus
- OpenAPI/Swagger
- ADRs
- living documentation
- doc linting
- automated API docs
Developer Productivity Metrics (DORA/SPACE)
Measuring developer experience and platform effectiveness using DORA metrics, SPACE framework, and custom developer satisfaction surveys
Objectives
- Implement DORA metrics to measure platform team effectiveness
- Use the SPACE framework to capture multi-dimensional developer productivity
Key concepts
- DORA metrics
- deployment frequency
- lead time for changes
- change failure rate
- MTTR
- SPACE framework
- developer satisfaction
- cognitive load
2 · Container Orchestration5 topics
Kubernetes Operations
Day-2 Kubernetes operations including upgrades, node management, RBAC, resource quotas, namespace strategies, and cluster maintenance
Objectives
- Perform zero-downtime Kubernetes cluster upgrades
- Design RBAC policies and namespace strategies for multi-team clusters
Key concepts
- cluster upgrades
- node pools
- RBAC
- resource quotas
- limit ranges
- namespace strategies
- PodDisruptionBudget
- drain and cordon
Helm Chart Design
Designing reusable Helm charts with proper templating, values hierarchies, chart dependencies, and release management
Objectives
- Design reusable Helm charts with proper parameterization and defaults
- Compare Helm and Kustomize for Kubernetes manifest management
Key concepts
- Helm templates
- values.yaml
- chart dependencies
- hooks
- release management
- chart repositories
- Helmfile
- Kustomize vs Helm
Multi-Cluster Management
Managing multiple Kubernetes clusters across regions, cloud providers, or environments with fleet management, federation, and consistent policy enforcement
Objectives
- Design multi-cluster strategies for high availability and disaster recovery
- Implement consistent policy enforcement across a fleet of clusters
Key concepts
- cluster federation
- fleet management
- multi-region
- Rancher
- Anthos
- cluster API
- GitOps multi-cluster
- cross-cluster networking
Custom Operators
Building Kubernetes operators using the operator pattern, custom resource definitions (CRDs), controller-runtime, and reconciliation loops for platform automation
Objectives
- Design a Kubernetes operator to automate a complex operational workflow
- Implement reconciliation loops with proper error handling and status reporting
Key concepts
- operator pattern
- CRDs
- controller-runtime
- reconciliation loop
- finalizers
- admission webhooks
- operator SDK
- level-triggered vs edge-triggered
Service Mesh (Istio/Linkerd)
Implementing service mesh for traffic management, mTLS, observability, and resilience patterns in Kubernetes environments
Objectives
- Evaluate when a service mesh adds value versus unnecessary complexity
- Configure traffic management policies for canary deployments and fault injection
Key concepts
- Istio
- Linkerd
- sidecar proxy
- mTLS
- traffic management
- virtual services
- destination rules
- circuit breaking
3 · Infrastructure as Code5 topics
Terraform Modules & State
Designing composable Terraform modules, managing remote state, state locking, workspaces, and multi-account infrastructure patterns
Objectives
- Design composable Terraform modules with clean interfaces and versioning
- Manage Terraform state safely across teams and environments
Key concepts
- Terraform modules
- remote state
- state locking
- workspaces
- module registries
- variable validation
- output composition
- state migration
GitOps (ArgoCD/Flux)
Implementing GitOps workflows with ArgoCD or Flux for declarative, git-driven infrastructure and application deployment
Objectives
- Implement GitOps workflows that ensure infrastructure matches the desired state in Git
- Design ArgoCD application hierarchies using the app-of-apps pattern
Key concepts
- ArgoCD
- Flux
- declarative deployment
- sync policies
- app-of-apps pattern
- drift detection
- sealed secrets
- image automation
Policy as Code (OPA/Kyverno)
Enforcing organizational policies using OPA/Rego, Kyverno, or Sentinel for admission control, infrastructure compliance, and governance automation
Objectives
- Design policy-as-code frameworks that enforce security and compliance at deploy time
- Write and test OPA/Rego or Kyverno policies for Kubernetes admission control
Key concepts
- OPA
- Rego
- Kyverno
- Sentinel
- admission controllers
- policy libraries
- compliance automation
- policy testing
Infrastructure Testing
Testing infrastructure code with unit tests, integration tests, contract tests, and compliance scanning to catch issues before deployment
Objectives
- Implement a multi-layer testing strategy for infrastructure code
- Balance test coverage with the cost of ephemeral test environments
Key concepts
- Terratest
- terraform validate
- tflint
- Checkov
- InSpec
- kitchen-terraform
- plan testing
- ephemeral environments
Crossplane & Control Planes
Using Crossplane to build custom cloud control planes, composing cloud resources as Kubernetes custom resources, and creating platform APIs
Objectives
- Design Crossplane compositions that abstract cloud complexity into platform-level APIs
- Evaluate Crossplane vs Terraform for infrastructure management in a platform context
Key concepts
- Crossplane
- compositions
- composite resource definitions
- providers
- managed resources
- platform APIs
- control plane pattern
- Kubernetes-native IaC
4 · CI/CD Platform5 topics
Pipeline Design Patterns
Designing CI/CD pipelines with proper stage ordering, parallelism, shared libraries, and pipeline-as-code best practices
Objectives
- Design CI/CD pipelines with appropriate stage ordering and quality gates
- Create reusable pipeline libraries that reduce duplication across projects
Key concepts
- pipeline-as-code
- shared libraries
- stage ordering
- parallel execution
- quality gates
- pipeline triggers
- monorepo pipelines
- fan-in fan-out
Build Optimization & Caching
Optimizing build times through caching strategies, incremental builds, parallelization, and build infrastructure tuning
Objectives
- Implement caching strategies that reduce CI pipeline duration by 50% or more
- Design build systems that scale with monorepo growth
Key concepts
- build caching
- remote caches
- incremental builds
- layer caching
- dependency caching
- Bazel
- Turborepo
- parallel compilation
Artifact Management
Managing build artifacts, container registries, package repositories, artifact promotion, and supply chain security
Objectives
- Design artifact management workflows with proper promotion and security scanning
- Implement software supply chain security using signing and SBOMs
Key concepts
- container registries
- package repositories
- artifact promotion
- immutable artifacts
- SBOM
- artifact signing
- Sigstore/Cosign
- vulnerability scanning
Progressive Delivery (Canary/Blue-Green)
Implementing progressive delivery strategies including canary deployments, blue-green deployments, feature flags, and automated rollback
Objectives
- Design progressive delivery pipelines with automated canary analysis and rollback
- Choose the right deployment strategy based on risk tolerance and infrastructure constraints
Key concepts
- canary deployments
- blue-green deployments
- feature flags
- Flagger
- Argo Rollouts
- traffic splitting
- automated rollback
- analysis templates
Multi-Environment Promotion
Managing artifact and configuration promotion across dev, staging, and production environments with proper governance and audit trails
Objectives
- Design multi-environment promotion pipelines with proper governance controls
- Implement ephemeral environments for pull request validation
Key concepts
- environment promotion
- configuration management
- environment parity
- promotion gates
- approval workflows
- environment branching
- config drift detection
- ephemeral environments
5 · Observability Platform5 topics
Centralized Logging
Building centralized logging platforms with structured logging, log aggregation, retention policies, and searchable log storage
Objectives
- Design a centralized logging platform that scales with organizational growth
- Implement structured logging standards that enable effective troubleshooting
Key concepts
- ELK stack
- Loki
- Fluentd/Fluent Bit
- structured logging
- log levels
- log retention
- log correlation
- log-based alerting
Metrics & Dashboarding (Prometheus/Grafana)
Implementing metrics collection with Prometheus, building Grafana dashboards, and designing metric hierarchies for infrastructure and applications
Objectives
- Design Prometheus metric hierarchies that balance detail with cardinality control
- Build Grafana dashboards that surface actionable insights using RED and USE methods
Key concepts
- Prometheus
- Grafana
- PromQL
- metric types
- labels and cardinality
- recording rules
- dashboard design
- RED/USE methods
Distributed Tracing (OpenTelemetry)
Implementing distributed tracing with OpenTelemetry for request flow visibility, latency analysis, and root cause identification across microservices
Objectives
- Implement OpenTelemetry instrumentation for end-to-end request tracing
- Design sampling strategies that balance observability with cost
Key concepts
- OpenTelemetry
- traces and spans
- context propagation
- sampling strategies
- Jaeger
- Tempo
- instrumentation
- baggage
SLO-Based Alerting
Designing alerting systems based on SLOs and error budgets instead of threshold-based alerts, reducing alert fatigue and improving incident response
Objectives
- Design SLO-based alerting that replaces noisy threshold alerts with actionable signals
- Implement multi-window burn rate alerts for early and accurate incident detection
Key concepts
- SLO-based alerting
- error budgets
- burn rate alerts
- multi-window alerts
- alert fatigue
- severity classification
- escalation policies
- on-call optimization
Cost Attribution & FinOps
Implementing cloud cost visibility, resource tagging, showback/chargeback models, and FinOps practices for platform teams
Objectives
- Implement cost attribution models that give teams visibility into their cloud spend
- Design FinOps practices that balance cost optimization with engineering velocity
Key concepts
- FinOps
- cost attribution
- resource tagging
- showback vs chargeback
- reserved instances
- spot instances
- cost anomaly detection
- unit economics
6 · Platform Strategy5 topics
Platform Team Topologies
Applying Team Topologies concepts to platform engineering: stream-aligned teams, enabling teams, complicated-subsystem teams, and platform teams
Objectives
- Apply Team Topologies to design an effective platform organization
- Identify the thinnest viable platform that reduces cognitive load for stream-aligned teams
Key concepts
- Team Topologies
- stream-aligned teams
- enabling teams
- platform teams
- cognitive load
- team interaction modes
- thin platform
- thinnest viable platform
API-First Platform Design
Designing platforms as products with well-defined APIs, versioning, backward compatibility, and developer-centric documentation
Objectives
- Design platform APIs that treat internal developers as first-class customers
- Implement API versioning and deprecation policies that minimize disruption
Key concepts
- platform as product
- API versioning
- backward compatibility
- API contracts
- platform SDKs
- developer documentation
- API governance
- deprecation policies
Multi-Tenancy & Isolation
Designing multi-tenant platform architectures with proper isolation, resource fairness, noisy neighbor prevention, and security boundaries
Objectives
- Design multi-tenant isolation strategies that balance security with operational efficiency
- Implement resource fairness mechanisms that prevent noisy neighbor problems
Key concepts
- multi-tenancy models
- namespace isolation
- network policies
- resource quotas
- noisy neighbor
- fair scheduling
- blast radius containment
- tenant onboarding
Platform Adoption & Migration
Driving platform adoption through migration strategies, change management, incentive design, and measuring adoption success
Objectives
- Design migration strategies that move teams to the platform without disrupting delivery
- Measure platform adoption and use data to drive improvement
Key concepts
- migration strategies
- strangler fig pattern
- adoption metrics
- change management
- incentive design
- migration tooling
- brown-field vs green-field
- platform evangelism
Build vs Buy Platform Decisions
Evaluating build vs buy decisions for platform components, vendor assessment, total cost of ownership, and strategic technology bets
Objectives
- Apply structured frameworks to build vs buy decisions for platform components
- Evaluate total cost of ownership including hidden costs of both building and buying
Key concepts
- build vs buy analysis
- total cost of ownership
- vendor lock-in
- open-source evaluation
- managed services
- strategic vs commodity
- Wardley mapping
- switching costs
7 · Expert Platform5 topics
Internal Developer Platforms
Building and operating Internal Developer Platforms using Backstage or Port, integrating pipelines, infra, and documentation
Objectives
- Design and implement an IDP using Backstage or Port with self-service workflows
- Integrate CI/CD, infrastructure, and documentation into a unified developer platform
Key concepts
- Backstage
- Port
- software catalog
- scaffolder
- tech docs
- platform APIs
- self-service workflows
Developer Experience Metrics
Measuring and improving developer experience using DORA metrics, SPACE framework, and developer satisfaction surveys
Objectives
- Implement DORA metrics tracking and connect them to platform engineering improvements
- Apply the SPACE framework to measure developer experience across multiple dimensions
Key concepts
- DORA metrics
- SPACE framework
- deployment frequency
- change failure rate
- MTTR
- developer satisfaction
- toil measurement
Platform as Product Strategy
Treating the internal developer platform as a product: product management, roadmaps, user research, and platform adoption
Objectives
- Apply product management principles to the internal developer platform
- Define the thinnest viable platform and build a roadmap driven by developer user research
Key concepts
- platform product management
- platform roadmap
- user research with devs
- platform adoption
- platform metrics
- thinnest viable platform
Paved Road Patterns & Golden Paths
Designing golden path templates and paved roads that balance standardization with developer autonomy
Objectives
- Design golden path templates that embed security, observability, and compliance by default
- Define escape hatch mechanisms that preserve developer autonomy while maintaining platform guardrails
Key concepts
- golden path
- paved road
- template library
- escape hatches
- cognitive load
- platform contracts
- compliance by default
Platform Observability
Implementing observability for the developer platform itself: API usage metrics, pipeline health, and capability adoption tracking
Objectives
- Design observability for the platform itself with SLOs and adoption metrics
- Build feedback loops that connect platform telemetry to platform roadmap decisions
Key concepts
- platform telemetry
- capability adoption
- pipeline health metrics
- error budget for platform
- platform SLOs
- usage analytics
- feedback loops
Levels: Junior, Mid, Senior, and Expert
Explain it in your own words
Graded by AI · no account · 1 questionNo options to guess from: you write, the AI grades against the topic's rubric and tells you what level your answer reads at.
Already studying Platform Engineer?
The assessment measures topic by topic, and your plan skips what you already know.
Open to read. An account is only needed to be measured.
Frequently asked questions
Where should I start studying Platform Engineer?
Start with Developer Experience: Golden Paths & Templates, Self-Service Infrastructure, and Developer Portal (Backstage). The map orders topics by what they depend on, so each one prepares the next.
How long does a full Platform Engineer assessment take?
A full assessment of this path takes about 50 minutes. Study time depends on where you start; a diagnostic shows which topics you can skip.
Do I need an account to use this page?
No. The map, objectives and key concepts are open. You only need an account to be measured, get your gap by topic and receive a plan.