IS WORK OVER?

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

Army 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.

TaskShareAIPoints
Order, the map and the section.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
Field, the one who lags and the one who jumps.
Estimate

No public source provides a precise figure. This is our estimate.

18%14%+2.5
Live fire, safety and not playing brave.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
Logistics, the meal and the one that does not arrive.
Estimate

No public source provides a precise figure. This is our estimate.

16%22%+3.5
Command, the pressure and not dressing casualties.
Estimate

No public source provides a precise figure. This is our estimate.

18%18%+3.2
Get them all out, and not losing one.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%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

Backend 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.

TaskShareAIPoints
Endpoint, the contract and the test.
Estimate

No public source provides a precise figure. This is our estimate.

18%48%+8.6
Spike, the queue and the one that drops.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
Key, the secret and not leaving it in the repo.
Estimate

No public source provides a precise figure. This is our estimate.

16%22%+3.5
Migration, the rollback and not improvising in prod.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
Product, the deadline and not cutting the one that matters.
Estimate

No public source provides a precise figure. This is our estimate.

18%14%+2.5
That it takes the spike, and not leaving the key.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%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

Analyse my job

Jobs with similar scores

  1. 447Music therapist22%
  2. 448Notary22%
  3. 449Oceanographer22%
  4. 451Ophthalmologist22%
  5. 452Oncologist22%
  6. 453Dry cleaner22%