IS WORK OVER?

Automation index

How much of a Strength and conditioning coach’s job can AI already do?

A load GPS comes earlier. Getting them ready without breaking them in the gym do not.

This percentage does not predict how many people will lose their jobs.

Task comparison

Strength and conditioning coach

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
Load, GPS and the microcycle.
Estimate

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

16%40%+6.4
Gym, the pattern and the one who cheats.
Estimate

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

18%14%+2.5
Rehab, the injured and not rushing the return.
Estimate

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

16%28%+4.5
Report, the manager and the fight over minutes.
Estimate

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

16%22%+3.5
The peak, pre-season and not grinding them.
Estimate

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

18%18%+3.2
Ready, and not broken.
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

  • load
  • training GPS
  • microcycles
  • rehab
  • movement pattern
  • pre-season
  • reports to the manager
  • the gym

Sources for this job· O*NET 29-9091.00· ESCO/ISCO 3423

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. 456Fire investigator22%
  2. 457Fishmonger22%
  3. 458Order picker22%
  4. 460Adult-education teacher22%
  5. 461Prison teacher22%
  6. 462Science teacher22%