Site Reliability Engineer

☐ Linux Mastery · Required · 8 hrs

Processes, signals, file descriptors, networking stack, systemd, performance tools (top, vmstat, iostat, strace). SREs live in the terminal.

• Linux and Shell Scripting for Data Engineers (Data Engineering): https://chaduvuko.com/learn/data-engineering/linux-shell

☐ Networking Deep Dive · Required · 6 hrs

TCP/IP internals, DNS resolution, HTTP/2, load balancing, TLS. When production breaks, networking is often the cause.

• What is a Network? (Networking): https://chaduvuko.com/learn/networking/what-is-a-network
• The TCP/IP Model — How the Internet Works (Networking): https://chaduvuko.com/learn/networking/tcp-ip-model
• DNS — How Domain Names Become IP Addresses (Networking): https://chaduvuko.com/learn/networking/dns
• HTTP and HTTPS — The Protocol Powering the Web (Networking): https://chaduvuko.com/learn/networking/http-and-https

☐ Python or Go · Required · 8 hrs

Write automation scripts, tooling, and on-call helpers. Go is preferred at FAANG; Python works everywhere else.

• What is Python? Setup & Your First Program (Python): https://chaduvuko.com/learn/python/what-is-python-setup
• Functions — Defining, Parameters, Return Values (Python): https://chaduvuko.com/learn/python/functions

☐ Git & Infra as Code · Required · 3 hrs

Version-controlled infrastructure. Every config change should be a pull request.

• Git and Version Control for Data Projects (Data Engineering): https://chaduvuko.com/learn/data-engineering/git-for-data

☐ Docker & Containers · Required · 5 hrs

Container internals, namespaces, cgroups, image layers, runtime debugging. Know what K8s is running.

☐ Kubernetes · Required · 15 hrs

Scheduler, etcd, control plane, pods, deployments, services, HPA, RBAC, node troubleshooting. K8s is where SREs spend most of their day.

☐ Terraform · Required · 6 hrs

Infrastructure as Code for cloud resources. Reproducible, reviewable, rollback-able environments.

• Infrastructure as Code for Data Engineers (Data Engineering): https://chaduvuko.com/learn/data-engineering/infrastructure-as-code

☐ Observability Stack · Required · 10 hrs

Prometheus + Grafana (metrics), ELK / Loki (logs), Jaeger / Tempo (traces). The three pillars of observability.

• Data Observability — Metrics, Logging and Anomaly Detection (Data Engineering): https://chaduvuko.com/learn/data-engineering/monitoring-observability
• Monitoring and Observability (Apache Kafka): https://chaduvuko.com/learn/apache-kafka/monitoring-observability

☐ Alerting & On-call · Required · 5 hrs

Alertmanager, PagerDuty/OpsGenie, alert fatigue, runbooks, escalation policies. On-call without runbooks is chaos.

☐ Incident Response · Required · 5 hrs

Incident lifecycle, SEV levels, war room coordination, blameless post-mortems, corrective actions. How teams recover from production failures.

• Incident Response — From Alert to Recovery (Cybersecurity): https://chaduvuko.com/learn/cybersecurity/incident-response

☐ CI/CD & GitOps · Required · 6 hrs

GitHub Actions, ArgoCD, progressive delivery (canary, blue-green). SREs own the deployment pipeline.

• DataOps and CI/CD for Data Pipelines (Data Engineering): https://chaduvuko.com/learn/data-engineering/cicd-pipelines

☐ SLI / SLO / SLA · Required · 6 hrs

Define service level indicators, set realistic objectives, calculate error budgets. The language reliability engineers use to talk to the business.

☐ Capacity Planning · Recommended · 5 hrs

Load testing (k6 / Locust), resource forecasting, auto-scaling, graceful degradation. Plan for traffic spikes before they happen.

☐ Chaos Engineering · Optional · 5 hrs

Chaos Monkey, Litmus Chaos, controlled failure injection. Prove your system is resilient before production proves it isn't.