Automation index
How much of a Table official’s job can AI already do?
A scoresheet comes earlier. Clock, fouls and not wrecking the result do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Table official
22%
AI can already do 22% of this job.
#432 / 773
View rankingTable official
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.
| Task | Share | AI | Points |
|---|---|---|---|
Sheet, clock and the protocol.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Fouls, the warning and the one who argues.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Timeout, the scoreboard and not jumping it.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The referee, the table and not contradicting.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The crowd, the shove and keeping calm.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
A clean result, and the sheet signed.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 22% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- scoresheets
- clock
- fouls
- timeouts
- scoreboard
- the table
- protocol
- warnings
Sources for this job· O*NET 27-2023.00· ESCO/ISCO 3422
IS WORK OVER?
Backend developer
27%
#153 / 773
View rankingBackend developer
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.
| Task | Share | AI | Points |
|---|---|---|---|
Endpoint, the contract and the test.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Spike, the queue and the one that drops.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Key, the secret and not leaving it in the repo.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Migration, the rollback and not improvising in prod.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the deadline and not cutting the one that matters.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it takes the spike, and not leaving the key.EstimateNo 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
Skills and activities
- endpoints
- API contracts
- queues
- secrets
- migrations
- rollback
- backend tests
- write server code
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2512