Automation index
How much of a Sporting director’s job can AI already do?
A squad map comes earlier. Signing without breaking the dressing room do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Sporting director
27%
AI can already do 27% of this job.
#149 / 623
View rankingSporting director
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 |
|---|---|---|---|
Squad, wages and financial fair play.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Signings, scouting and the one who does not fit.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Coach, the project and the one who burns.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Board, the fans and not selling smoke.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The injury, the window and not papering over.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Sign well, and not breaking the dressing room.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
- squad
- signings
- fair play
- scouting
- wages
- the project
- dressing room
- the window
Sources for this job· O*NET 27-2022.00· ESCO/ISCO 3422
IS WORK OVER?
Technical writer
28%
#115 / 623
View rankingTechnical 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.
| Task | Share | AI | Points |
|---|---|---|---|
Structure, API docs and the tutorial.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Screenshots, versions and not leaving the old shot.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
The engineer who will not write, and extracting the how.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Legal review, i18n and the changelog.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Support, the tickets and what the doc misses.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it can be installed, and not documenting thin air.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 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