◆ Computer Science

What a site reliability engineer sre
really does.

20 tasks, each one witnessed by the sources that watched the job — and behind every one, a prompt you can use tonight.

20evidenced tasks
435,370in the US (2025)
$116,580median pay / year
7systems it runs on
This is what one task looks like here
Configure hardware and software
Provision the five new rack servers, install the OS, configure network…2 sources agree

The shape of the day

tap a movement to see its tasks

Which one is you, right now?

Pick the moment · no score, no sign-up
Which moment is you right now?
Whichever you pick, the task behind it opens below.

The work, task by task

20 tasks
Hands on the work14
Configure hardware and software+
Provision the five new rack servers, install the OS, configure network interfaces, apply the standard monitoring agent and kernel tuning, and hand over inventory and runbook to operations with signatures from facilities and security today.
escojd2 agree
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
Hardware testing methods+
Run the rack-level hardware test suite on the new server nodes, record voltage, current and temperature readings against the acceptance thresholds, log failures with photos and serial numbers, and send a concise daily summary to Procurement and Data Center Ops by 5pm.
esco
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
Implement software solutions+
Install the new service binaries on the staging cluster, wire the health checks and metrics collectors, run the integration test suite until green, record failures with logs and stack traces, then brief Dev and QA by EOD Thursday.
jd
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
Design system architecture+
Draft the redundant region layout that meets our five‑9s availability target, specify instance types, failover paths, and the monitoring boundaries, then circulate the diagram and risk notes to Architecture and Ops by Tuesday noon.
jd
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
Provide technical support+
Take the priority ticket for the failing service, reproduce the error on a support sandbox, gather logs, traces and configuration diffs, apply the workaround, and update the incident with steps and owners within two hours.
jd
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
Analyze system performance+
Run the 24‑hour performance report for the payment service, compare CPU, memory and latency against the SLOs, highlight regressions with corresponding deploy IDs, and send a one‑page summary to Product and Engineering by 9am Monday.
jd
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
Collaborate with cross-functional teams+
Prepare the postmortem draft for last week's outage, include timeline, telemetry screenshots, root causes, action owners and RFCs, then run it past Platform, Security and Product and request comments by Friday COB.
jd
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
Manage database systems+
Check the production database cluster for replication lag and slow queries, apply the agreed configuration standard, rotate the oldest backup set, and report any anomalies to the platform lead by 11:00 so remediation can be scheduled before the daily deploy.
jd
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
Watch and assess4
Keep the record2

What the work runs on

named inside the evidenced tasks
5 tasksLinuxruns and automates hardware test suites and captures instrument data on servers
5 tasksJIRAtrack defects and record test results for other teams
4 tasksCiscoobserves router and switch traffic, export flow data and alerts for analysis
4 tasksMicrosoft Officeformats, reviews and circulates formal technical procedures and runbooks
2 tasksVMwaremodels virtual instance placement and failover in the proposed architecture
2 tasksSQL Serverqueries time‑series and transaction tables to produce performance summaries and correlated deploy data
1 taskWindowshosts the support sandbox and reproduces customer-facing service issues and diagnostics

The same task, four heights

this page is height one

Can AI actually do this job?

the honest answer

It can

where it genuinely helps
  • Explain the theory behind the work
  • Draft, tidy and structure your writing
  • Rehearse a hard conversation before you have it
  • Build a study plan that fits your gaps

It cannot

where it stops, completely
  • Be in the room where a site reliability engineer sre actually works
  • Carry the responsibility when the call is wrong — that weight stays yours
  • Notice what no one wrote down: the hesitation, the thing left unsaid
  • Live with the outcome

What the work pays

two countries, two different measures

United States

this exact occupation · BLS 2025
  • $116,580 a year — the middle: half earn more, half earn less
  • The lowest tenth earn near $55,940; the top tenth near $188,470
  • 435,370 people employed in this occupation

India

the occupation GROUP, not this job · PLFS via ILOSTAT 2025
  • ₹38,298 a month — the median for Professionals, the group this work sits in
  • India publishes pay by broad occupation group, so this covers many jobs besides this one. It is a shape, not a salary.
read this carefullyThese two numbers are not comparable and must not be converted into each other. One is a yearly figure for this job alone; the other is a monthly figure for a whole family of jobs. What travels between them is the pattern, not the amount: experience lifts pay almost everywhere.

Where the evidence lives

open any of it yourself

Close to this work

12 nearby
Computer ScienceFrontend Developer26 evidenced tasks Computer ScienceUi Developer26 evidenced tasks START Computer ScienceSales Engineer26 evidenced tasks Computer ScienceFreelance Web Developer26 evidenced tasks Computer ScienceTest Automation Engineer21 evidenced tasks Computer ScienceProduct Manager Tech21 evidenced tasks Computer ScienceApp Store Publisher21 evidenced tasks Computer ScienceBackend Developer20 evidenced tasks

Questions people actually ask

You spend time fixing live problems, writing automation, and digging into system logs. Morning often starts by checking alerts from monitoring tools, then triaging incidents and running postmortems after problems are fixed.

Afternoons usually involve deploying changes with CI/CD, improving system architecture, meeting with developers about reliability, and documenting procedures in JIRA or Confluence. Expect interruptions for on-call rotations and vendor coordination for hardware like Cisco or VMware.

You’ll use Linux daily for servers and containers, and sometimes Windows for legacy apps. For virtualization and private clouds, VMware is common; Cisco gear appears in networking tasks.

For tracking work and documenting procedures you’ll use JIRA and Microsoft Office. For databases you’ll manage SQL Server, and you’ll monitor systems with network and performance tools while reading assembly drawings or blueprints when hardware is involved.

The U.S. Bureau of Labor Statistics (BLS) reports 435,370 employed in this area with a median pay of $116,580 per year. The lowest tenth earn about $55,940 and the top tenth about $188,470, according to BLS.

Use these as a broad band—actual pay varies by company, location, and your skills with systems like VMware, Cisco, Linux, and SQL Server.

Yes, use AI for drafting scripts, explaining logs, or suggesting configuration fixes, but always verify outputs. Treat AI like an assistant: run suggested scripts first in a test environment (VMware or a Linux VM) and review changes before production.

Don’t let AI change live systems or handle sensitive credentials. Keep documentation and JIRA tickets for any AI-assisted change, and use monitoring to quickly detect regressions after deploying suggestions.

Designing resilient system architecture under real constraints is hardest: it combines software, hardware, networking, and trade-offs. It requires thinking ahead for failure modes and recovery procedures.

Improve by studying real outages, practicing chaos testing in a controlled lab, learning measurement instruments and monitoring, and reading blueprints and assembly drawings for hardware. Work with cross-functional teams and write postmortems to learn from incidents.