Careers › IT & Cloud Infrastructure › Site Reliability Engineer
For students and early-career professionals
Site Reliability Engineer
Keeps large systems fast and available by automating operations and monitoring.
13 chapters · About 3 months · 15–30 min a day
Start this plan free → Chapter 1 is free.
What's in the plan
Practice 17 practice tasks Tasks from the real work of the job, 10 to 30 minutes each
Projects 2 projects you keep SLOs, error budgets, and a planned game-day exercise Self-hosted service with metrics, logs, and alerts
Interview 20 interview questions Practise your answers, with feedback
People 4 people to reach Who they are, with 4 messages ready to send
Also: choose your route in (8 credentials compared, none required) and 3 life skills courses.
Skills
15 skills, and what you'll learn in each
Each skill is a few short lessons, then practice. You rate yourself at the start and again at the end.
Core to the job
Chapter 2
Monitoring Fix a noisy alert and rank alerts by user harm
What you'll learn
Metrics logs traces Four golden signals Actionable alert Service level objective Practice
Tune a noisy alert from a fake on-call week20 min Chapter 2
Incident response Build an incident timeline from logs and write plain updates
What you'll learn
User impact first Mitigate before root cause Blameless post-mortem Incident command roles Practice
Write a blameless post-mortem for a small incident30 min Analyze How a Company Communicates During an Outage15 min Chapter 2
Keeping services reliable Write a rule that pauses releases after too many failures
What you'll learn
Error budget policy What the number misses Toil budget Production readiness Controlled failure Practice
Read the Growth Curve and Say When You Run Out of Room30 min Chapter 5
Cloud platforms Read a cloud bill and find which services cost most
What you'll learn
Core cloud services Identity and permissions Service tradeoffs Cloud cost drivers Well-Architected review Practice
Find 3 wasted cloud resources from a sample bill20 min Forecast capacity for a growing service25 min Chapter 5
Infrastructure as code Read server-building code and find where the real setup differs
What you'll learn
Desired state Plan diff State file Module boundary Configuration drift Practice
Read a Terraform Config and Describe What It Builds15 min Chapter 6
Linux Manage files and who can open them using short commands
What you'll learn
Filesystem map File permissions Pipes and filters Process signals Practice
Solve 5 Linux command-line puzzles25 min
9 more in the plan
Containers Package an app to run the same on another machine Ch 5 What you'll learn
Container image Stateless processes Desired state Service exposure Tenant separation Reusable chart Practice
Read a Dockerfile and Explain What Each Line Does15 min Scripting Write a script that checks disk space and warns you Ch 6 What you'll learn
Script arguments Error handling Input checks Readable scripts Practice
Write a Script That Checks Disk Space and Warns You20 min Git Save clear changes to a project's history and request review Ch 6 What you'll learn
Change states Short-lived branches Merge conflict Useful commit message Pull request review Practice
Practise a small Git branching workflow30 min Problem solving Test each possible cause of a problem instead of guessing Ch 7 What you'll learn
Problem vs symptom Clean problem splits Root cause Deciding under uncertainty Practice
Separate the Problem from the Symptom10 min Critical thinking Spot a weak assumption and ask where numbers come from Ch 7 What you'll learn
The hidden assumption Argue the other side The base rate Fact vs inference Wanting it to be true Practice
Spot the Weak Link in an Argument10 min Communication Rewrite an update for two different readers, cutting extra lines Ch 8 What you'll learn
Lead with the point Match detail to the reader Said versus heard Specific feedback Practice
Write a Six-Line Delay Message10 min Working with others Contribute to group work, ask for help and credit teammates Ch 8 What you'll learn
Early team friction Clear ownership Challenge ideas, not people Lead or follow Practice
Write a Request That Makes It Easy to Say Yes10 min Adapting to change Try a new tool and describe how you handled change Ch 8 What you'll learn
Change vs your response The messy in-between Not there yet Real change vs a feeling Documenting infrastructure work Write a task guide and draw how system parts connect Ch 9 What you'll learn
Runbook purpose Decision record Document type Current version Practice
Audit one runbook and update it20 min Write a runbook for one repetitive task25 min
Your plan
Chapter by chapter. 13 chapters, in this order. Chapter 1 is free.
1 ~1 wk See what site reliability engineer work involves Start Free
2 ~1 wk Keep services reliable and handle outages Skills
3 1–2 wks Plan reliability targets and a failure drill Project
4 ~1 wk Talk to a working reliability engineer People
5 ~1 wk Run apps in the cloud with code Skills
6 ~1 wk Script routine tasks on the command line Skills
7 ~1 wk Find the cause before you fix it Skills
8 ~1 wk Communicate and work together through change Skills
9 ~1 wk Document infrastructure work others can follow Skills
10 1–2 wks Capstone: host a monitored service with alerts Project
11 ~1 wk Answer the questions interviewers ask Interview
12 ~1 wk Decide how you will get in Decide
13 on your timeline Send your first applications Apply
The job
What a Site Reliability Engineer does Keeps online services reliable and fast by automating operations, watching system health, and fixing issues before users are impacted.
The work Design reliability goals and error budgets with product and engineering teams Build automation to reduce manual work in deployments, scaling, and recovery Set up monitoring, logging, and alerts to spot problems early Diagnose outages using metrics and traces, then restore service quickly Coordinate incident response, run post-incident reviews, and track fixes Improve system performance, capacity, and cost through tuning and planning Teach teams safer release practices and reliability-friendly design patterns A typical day Review dashboards and overnight alerts, then prioritize reliability work Work on automation or infrastructure changes, then test in staging Join incident calls when needed and communicate status to stakeholders Review upcoming releases and add checks, rollbacks, and runbooks Write post-incident notes and plan follow-up tasks with engineers Tools Cloud platforms: AWS, Azure, Google Cloud Containers: Docker, Kubernetes Infrastructure as code: Terraform, Ansible CI CD: GitHub Actions, GitLab CI, Jenkins Observability: Prometheus, Grafana, OpenTelemetry Logging: Elasticsearch, Splunk Programming: Python, Go, Bash
Ways in
There is more than one route. Ways to study Computer science or software engineering degree or diploma Information technology or networking diploma with strong Linux practice Cloud and DevOps training programs with hands-on labs Self-taught path using open-source projects and home lab practice How people get their first job Start in IT support or systems administration and learn automation Apply for DevOps or cloud engineering internships focused on operations Build a portfolio with monitoring, incident runbooks, and IaC examples Earn a cloud fundamentals certification and complete practical labs Contribute to open-source reliability tooling or documentation Life skills in this plan: Networking · Job interviews · Job search
How the work is changing
What AI is doing to this role How AI is changing this role · one of 6 tasks we track
Build and run monitoring and alerting Sped up a lot
What AI does Datadog and Dynatrace spot odd patterns and point at the cause.
Still yours You pick what to measure and what a good day looks like.
Reviewed September 2026
In the app · Premium
The rest is in the app
How AI affects the other 5 tasks Whether this job is growing or shrinking How hard the first job is to get Similar roles that are easier to get into Updated every month, with sources
See it in the app →
How we rate a job →
Already working
Already a Site Reliability Engineer? Plan your move to Senior Site Reliability Engineer: 12 chapters that end with a strong case for your next review.
Grow in the role →
Other roles in IT & Cloud Infrastructure
Questions
Questions about this plan How long does it take to become a site reliability engineer with Welica? The plan is 13 chapters, 3 months at 15 to 30 minutes a day. You can go faster or slower; the plan moves with you.
Do I need a degree? Not always. Common routes are computer science or software engineering degree or diploma, information technology or networking diploma with strong Linux practice, cloud and DevOps training programs with hands-on labs, or self-taught path using open-source projects and home lab practice.
What is free? Chapter 1, See what site reliability engineer work involves, is free for good. Premium unlocks the rest of the plan.
Start the Site Reliability Engineer plan. Chapter 1 free. About 15 to 30 minutes a day.
Already have an account? Sign in