Automation index
How much of a Tactical analyst’s job can AI already do?
A clip comes earlier. The manager using it, and it not being noise, do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Tactical analyst
27%
AI can already do 27% of this job.
#137 / 763
View rankingTactical analyst
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 |
|---|---|---|---|
Video, tags and the report.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Opponent, patterns and the one who hides.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Preview, the dressing room and not drowning them.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Live, the tablet and the change.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The manager, the ego and not contradicting in public.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it is used, and not being noise.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
- tag video
- opponent patterns
- preview
- bench tablet
- tactical reports
- dressing room
- changes
- data noise
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