Automation index
How much of a Football coach’s job can AI already do?
A lineup and a clip come earlier. Going out to compete without breaking do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Football coach
22%
AI can already do 22% of this job.
#386 / 763
View rankingFootball coach
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 |
|---|---|---|---|
Lineup, plan and the opponent clip.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Train, the one who is late and the one who hides.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Match, the changes and the one who boils.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Dressing room, the ego and not losing the group.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The board, the parents and not picking the son under pressure.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Compete, and not breaking.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
- lineups
- opponent clip
- training
- changes
- dressing room
- parents
- pick the side
- match plan
Sources for this job· O*NET 27-2022.00· ESCO/ISCO 3422
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