Automation index

How much of a Site reliability engineer’s job can AI already do?

A runbook and autoscale come earlier. The 3 a.m. incident without taking production down do not.

This percentage does not predict how many people will lose their jobs.

Task comparison

IS WORK OVER?

28%

AI can already do 28% of this job.

#103 / 763

Site reliability engineer

Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.

The time saving for each task is estimated separately.

Task	Share	AI	Points
SLOs, alerts and the runbook. Estimate No public source provides a precise figure. This is our estimate.	18%	52%	+9.4
Incident, war room and not making it worse. Estimate No public source provides a precise figure. This is our estimate.	16%	22%	+3.5
CI/CD, capacity and the error budget. Estimate No public source provides a precise figure. This is our estimate.	16%	40%	+6.4
Postmortem, toil and automating the repeated. Estimate No public source provides a precise figure. This is our estimate.	16%	28%	+4.5
The product that wants to ship and the SLO that will not allow it. Estimate No public source provides a precise figure. This is our estimate.	18%	14%	+2.5
Not taking production down, and signing the change. Estimate No public source provides a precise figure. This is our estimate.	16%	12%	+1.9
Total	100%		28%

Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low

IS WORK OVER?

27%

#151 / 763

Backend developer

Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.

The time saving for each task is estimated separately.

Task	Share	AI	Points
Endpoint, the contract and the test. Estimate No public source provides a precise figure. This is our estimate.	18%	48%	+8.6
Spike, the queue and the one that drops. Estimate No public source provides a precise figure. This is our estimate.	16%	40%	+6.4
Key, the secret and not leaving it in the repo. Estimate No public source provides a precise figure. This is our estimate.	16%	22%	+3.5
Migration, the rollback and not improvising in prod. Estimate No public source provides a precise figure. This is our estimate.	16%	28%	+4.5
Product, the deadline and not cutting the one that matters. Estimate No public source provides a precise figure. This is our estimate.	18%	14%	+2.5
That it takes the spike, and not leaving the key. Estimate No public source provides a precise figure. This is our estimate.	16%	12%	+1.9
Total	100%		27%

Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low