NXH.
The knowledge layers of a Senior DevOps Engineer, from bottom to top: Foundations (Linux, networking, Bash, Python, Git); Cloud and IaC (AWS, Terraform/OpenTofu, Ansible); Containers and Orchestration (Docker, Kubernetes, Helm, Kustomize); Software Delivery (GitHub Actions, GitLab CI, Argo CD); Observability and Reliability (Prometheus, Grafana, OpenTelemetry, CloudWatch); Security and Governance (Vault, Trivy, Syft, Cosign, OPA); Platform and Leadership (Backstage, Cost Explorer, DORA metrics). Cross-cutting: automation, security, documentation, collaboration.
← Back to learning materials
Learning journey

Senior Platform Engineer Roadmap

The order I study in, from Linux to platform engineering. Each step links to its slide deck when the deck is ready.

16steps
7phases
14decks ready
Decks built14 / 16
Start the journey ↓

Study order

Linux → Networking → … → Platform Engineering. Go runs in parallel from K8s onward.

Deck readyPlanned
Phase 1

Foundations

4 / 4 ready
Phase 2

Containers & Orchestration

3 / 3 ready
Phase 3

Cloud & IaC

1 / 1 ready
STEP 7

Terraform & IaC A to Z

Ready
ModulesStatemoved / importPlan risk reviewPolicy as code (Checkov, Trivy)Repo layout per environment
Phase 4

Software Delivery

2 / 2 ready
STEP 8

CI/CD & Supply Chain Security

Ready
GitHub Actions + OIDCReusable workflowsDeployment strategiesRollbackSBOMcosignSLSA
STEP 9

GitOps: Helm & Argo CD

Ready
HelmKustomizeArgo CD app-of-appsSync wavesMulti-clusterMulti-environment
Phase 5

Observability & Reliability

2 / 2 ready
STEP 10

Observability

Ready
Prometheus & PromQLStructured logs & LokiOpenTelemetry tracesRED/USE dashboardsCloudWatch
STEP 11

SRE Practices

Ready
SLI/SLOError budgetsBurn-rate alertsOn-callIncident commandPostmortemsCapacityChaosDR drills
Phase 6

Security & Governance

1 / 2 ready
STEP 12

Kubernetes Security

Planned
RBACPod Security StandardsNetworkPolicyKyverno / GatekeeperSecrets with KMSFalcoCIS benchmark
Deck coming soon
Phase 7 · Goal

Platform & Leadership

0 / 1 ready
STEP 14

Platform Engineering

Planned
Platform as a productGolden pathsBackstageSelf-serviceMulti-tenancyDORA metricsRFCs / ADRs
Deck coming soon
Parallel track · from K8s onward

Go for Platform Engineers

STEP 15

Go for Platform Engineers

Ready
Go basicsCLIsAWS SDKclient-goA simple operatorTesting

Linux study plan

2 weeks × 4 hours a day.

Lab dayReview day

Week 1

  1. Day
    1
    1.1 Kernel and system basics
  2. Day
    2
    1.2 Shell (first half)
  3. Day
    3
    1.2 Shell (second half)
  4. Day
    4
    2.1 FilesystemLab 1
  5. Day
    5
    3.1 Users and permissionsLab 2
  6. Day
    6
    4.1 Processes and signals
  7. Day
    7
    Review week 1, redo all labsReview

Week 2

  1. Day
    8
    4.2 systemd, 4.3 PackagesLab 3
  2. Day
    9
    5 Performance (load, CPU, memory, OOM)Lab 4
  3. Day
    10
    5 Performance (I/O, USE, sar, benchmarks)
  4. Day
    11
    2.2 Storage operationsLab 5
  5. Day
    12
    3.2 Security hardeningLab 6
  6. Day
    13
    6 Networking, 8.1 Troubleshooting case studies
  7. Day
    14
    8.2 Practice and review: self-checks, glossaryReview