IS WORK OVER?

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

Site reliability engineer

Where the time goes

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.

TaskShareAIPoints
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
Total100%28%

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

Skills and activities

  • SLOs
  • runbooks
  • handle incidents
  • error budget
  • autoscale
  • postmortem
  • reduce toil
  • reliability CI/CD

Sources for this job· O*NET 15-1244.00· ESCO/ISCO 2512

Technical writer

Where the time goes

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.

TaskShareAIPoints
Structure, API docs and the tutorial.
Estimate

No public source provides a precise figure. This is our estimate.

18%52%+9.4
Screenshots, versions and not leaving the old shot.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
The engineer who will not write, and extracting the how.
Estimate

No public source provides a precise figure. This is our estimate.

16%22%+3.5
Legal review, i18n and the changelog.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
Support, the tickets and what the doc misses.
Estimate

No public source provides a precise figure. This is our estimate.

18%14%+2.5
That it can be installed, and not documenting thin air.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%28%

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

Skills and activities

  • document APIs
  • product tutorials
  • screenshots
  • changelogs
  • extract knowledge
  • docs i18n
  • version review
  • support tickets

Sources for this job· O*NET 27-3042.00· ESCO/ISCO 2641

Analyse my job

Jobs with similar scores

  1. 100Photographer28%
  2. 101Tour guide28%
  3. 102Industrial engineer28%
  4. 104Tax inspector28%
  5. 105Inventory clerk28%
  6. 106Store manager28%