Automation index
How much of a PE teacher’s job can AI already do?
A stock session comes earlier. Getting them actually moving without getting hurt do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
PE teacher
22%
AI can already do 22% of this job.
#463 / 773
View rankingPE teacher
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 |
|---|---|---|---|
Session, aims and the kit.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Yard, the group and the one who will not.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Injury, protocol and calling home.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Assess, the report and not giving a 10 for quiet.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Staff, the rain and not leaving them in the corridor.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
That they move, and not getting hurt.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
- PE sessions
- the yard
- injury protocol
- assess PE
- sports kit
- staff meeting
- groups
- the report
Sources for this job· O*NET 25-2031.00· ESCO/ISCO 2330
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