Automation index
How much of a Headteacher’s job can AI already do?
A timetable comes earlier. The school not falling over on Monday without hiding the clash do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Headteacher
27%
AI can already do 27% of this job.
#156 / 763
View rankingHeadteacher
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 |
|---|---|---|---|
Timetable, quotas and the staff.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Family, the complaint and the one that reaches inspection.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Behaviour, the sanction and not hiding it.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Budget, the club and not leaving a hole.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Inspection, the figure and not dressing it.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That Monday holds, and not hiding the clash.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
- school timetables
- quotas
- behaviour
- sanctions
- school budget
- inspection
- family complaints
- senior staff
Sources for this job· O*NET 11-9032.00· ESCO/ISCO 1345
IS WORK OVER?
Backend developer
27%
#151 / 763
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