Automation index
How much of a Army officer’s job can AI already do?
An operations order comes earlier. Getting the whole section out without losing one do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Army officer
22%
AI can already do 22% of this job.
#450 / 773
View rankingArmy officer
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 |
|---|---|---|---|
Order, the map and the section.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Field, the one who lags and the one who jumps.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Live fire, safety and not playing brave.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Logistics, the meal and the one that does not arrive.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Command, the pressure and not dressing casualties.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Get them all out, and not losing one.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
- operations orders
- sections
- the map
- live fire
- meals
- casualties
- command
- field safety
Sources for this job· O*NET 55-1015.00· ESCO/ISCO 0110
IS WORK OVER?
Front-end developer
27%
#157 / 773
View rankingFront-end 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 |
|---|---|---|---|
Component, states and the design.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Accessible, the keyboard and the reader.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Contrast, the token and not leaving it dead.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Performance, the weight and not adding the extra library.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The designer, the pixel and not fighting for sport.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it works from the keyboard, and not leaving the contrast.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
- components
- accessibility
- keyboard
- contrast
- tokens
- front-end performance
- libraries
- write interface
Sources for this job· O*NET 15-1254.00· ESCO/ISCO 2513