SRE as a Beginner: How to Break In Without Getting Overwhelmed
Beginners often get stuck because they try to memorize 50 tools on Day 1. In reality, 80% of production
outages come down to DNS, expired SSL certificates, full disks, memory limits, or bad config pushes.
STARTING POINT // WHO CAN BECOME AN SRE?
Transitioning Into SRE & First 30-Day Survival Checklist
From SysAdmin / Support
Your Advantage: You already know Linux, OS troubleshooting, and networking.
Focus On: Python/Bash scripting, Git, Terraform
Infrastructure as Code, and Kubernetes.
From Software Developer
Your Advantage: You already know coding, Git, and APIs.
Focus On: Linux kernel/process metrics, DNS/TCP networking,
Docker, Kubernetes, and cloud IAM/VPCs.
From QA / Fresh Graduate
Your Advantage: Strong testing mindset and hunger to learn.
Focus On: Follow Stage 1 to Stage 4 below in exact order and
build 1 hands-on cloud monitoring project.
MENTAL MODEL // THE 5 HOPS
How a Web Request Travels (And Where Outages Happen)
THE #1 BEGINNER INTERVIEW QUESTION:"What happens when a user types a website URL into
their browser?"
Master these 5 hops and you can systematically troubleshoot almost any live production outage:
Step
What Happens
What Can Break (And What SREs Check)
1. DNS Lookup
Browser asks DNS for the IP address of example.com.
Domain expired or wrong DNS IP configured. Check with dig or nslookup.
2. HTTPS / TLS
Browser establishes a secure encrypted connection (Port 443).
TLS/SSL certificate expired! (One of the most common real-world outages).
3. Load Balancer
Traffic hits Cloud Load Balancer (AWS / Azure / GCP) or Nginx, spreading requests across servers.
Health check failing, returning 502 Bad Gateway or
503 Service Unavailable.
4. App Server / Pod
Your Python/Java/Go/Node.js container processes the user's request.
Container ran out of Memory (OOMKilled) or CPU is throttled, or a recent code bug crashed the app.
5. Database / Cache
App reads or saves data in PostgreSQL / MySQL / Redis.
Disk is 100% full, slow SQL query locks the table, or connection pool is exhausted.
INTERACTIVE ROADMAP
The 4-Stage SRE Learning Path (Check Off As You Learn)
0 of 12 topics completed (0%)
FOLLOW IN ORDER: Spend 2–3 weeks on each stage. Tick the checkboxes below as you master each
topic—your progress is saved automatically in your browser.
Stage 1: Linux Internals, Networking & Git (Weeks 1–3)
# 1. Check if the server hard disk is full (or out of inodes)
df -h && df -i
# 2. Check available RAM / Memory in Megabytes
free -m
# 3. See which process is using the most CPU & Memory
top
# 4. Watch live application logs as errors happen
tail -f /var/log/nginx/error.log
# 5. Search for "ERROR" inside a log file (case-insensitive)
grep -i "error" app.log
# 6. Check which network ports are open and listening
ss -tulpn
# 7. Test if an API URL is responding and inspect HTTP headers
curl -I https://reliableaiops.com
# 8. Check why a background systemd service failed or restarted
systemctl status nginx && journalctl -u nginx -n 50