IS WORK OVER?

Automation index

How much of a History teacher’s job can AI already do?

A causes outline comes earlier. Them not cramming dates and knowing why it happened do not.

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

Task comparison

History teacher

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
Topic, sources and the outline.
Estimate

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

16%40%+6.4
Classroom, the debate and the one who drops the cliché.
Estimate

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

18%14%+2.5
Exam, the argument and not rewarding the crib.
Estimate

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

16%28%+4.5
Trip, the museum and getting them to actually look.
Estimate

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

16%22%+3.5
The family, the politics and not indoctrinating.
Estimate

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

18%18%+3.2
That they know why it happened, and not just the date.
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

  • historical sources
  • causes outlines
  • classroom debate
  • history exams
  • museum trips
  • not indoctrinate
  • cribs
  • argument

Sources for this job· O*NET 25-2031.00· ESCO/ISCO 2330

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. 463PE teacher22%
  2. 464Vocational teacher22%
  3. 465Golf professional22%
  4. 467Spanish language teacher22%
  5. 468Maths teacher22%
  6. 469Music teacher22%