Skip to content
Unverified — AI-generated content. Help verify this page

Platform Engineer Learning Path

A structured 12-week journey through the Knowledge Vault for platform engineers. This path goes deeper than the DevOps path into Kubernetes advanced topics (CRDs, operators, admission webhooks), GitOps, FinOps, observability tools, API gateway patterns, storage systems, and developer experience. Platform engineering is the evolution of DevOps -- building self-service platforms that abstract infrastructure complexity.

Who This Is For

  • DevOps engineers evolving into platform engineering
  • Infrastructure engineers building internal developer platforms
  • SREs who want to shift from reactive to proactive platform building
  • Anyone designing self-service infrastructure for engineering teams

Prerequisites

  • Basic Linux command line and networking (TCP/IP, DNS, HTTP)
  • Experience with Docker and basic Kubernetes concepts
  • Some experience with at least one cloud provider (AWS, GCP, Azure)
  • Comfortable with at least one programming language

Total estimated time: ~55 hours across 12 weeks

Learning Progression


Week 1-2: Linux Internals

Estimated reading time: 4 hours


Week 2-3: Containers Deep Dive

Estimated reading time: 4.5 hours


Week 3-4: Kubernetes Core

Estimated reading time: 5 hours


Week 4-5: Kubernetes Advanced (CRDs, Operators, Webhooks)

Estimated reading time: 6 hours

This is where platform engineering diverges from basic DevOps. Master the extension points that let you build platform abstractions on top of Kubernetes.

Checkpoint

After this section you should be able to: build custom CRDs and operators for platform abstractions, implement admission webhooks for policy enforcement, configure GitOps with ArgoCD/Flux, and understand CNI networking internals.


Week 5-6: Infrastructure as Code

Estimated reading time: 6 hours


Week 6-7: CI/CD & GitOps

Estimated reading time: 5 hours


Week 7-8: Networking, Service Mesh & API Gateway

Estimated reading time: 5 hours


Week 8-9: Observability Stack

Estimated reading time: 6 hours

Comparisons:


Week 9-10: Security & Compliance

Estimated reading time: 5 hours


Week 10: SRE Practices & FinOps

Estimated reading time: 5 hours

SRE

FinOps

Checkpoint

After this section you should be able to: define SLOs and error budgets, implement FinOps practices with cost allocation and optimization, run chaos experiments, and reduce toil systematically.


Week 11: Storage Systems & Advanced Topics

Estimated reading time: 4 hours


Week 12: Developer Experience & Capstone

Estimated reading time: 4 hours

Platform Engineering & DX

Engineering Practices

Comparisons


What You Will Be Able to Do After This Path

  • Build custom Kubernetes operators, CRDs, and admission webhooks
  • Implement GitOps with ArgoCD/Flux for declarative infrastructure
  • Design FinOps practices with cost allocation and optimization
  • Build comprehensive observability stacks with metrics, logs, and traces
  • Manage API gateways and service meshes at scale
  • Design storage systems and multi-region architectures
  • Build internal developer platforms with golden paths and self-service
  • Apply SRE practices: SLOs, error budgets, chaos engineering

Total Progress

This path contains approximately 100 pages. The Kubernetes advanced section (CRDs, operators, admission webhooks, GitOps) is the differentiator from the DevOps path. Budget 12 weeks at 5 hours per week.

"What I cannot create, I do not understand." — Richard Feynman