Automation index
How much of a Sports physiotherapist’s job can AI already do?
A return-to-play protocol comes earlier. Calling Sunday and not burning the player do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Sports physiotherapist
22%
AI can already do 22% of this job.
#389 / 763
View rankingSports physiotherapist
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 |
|---|---|---|---|
Injury, the test and the note.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Pitch, the move and the one who lies about pain.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Gym, the load and not rushing.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Sunday, the coach and not yielding.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The press, the rumour and not leaking.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
If they play Sunday, sign it. And not burning them.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
- return to play
- injury notes
- gym load
- sport-specific move
- Sunday clearance
- the coach
- not yield
- not leak
Sources for this job· O*NET 29-1123.00· ESCO/ISCO 2264
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