Automation index
How much of a Secondary teacher’s job can AI already do?
A unit plan comes earlier. Them being quiet, working, and nobody left out, do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Secondary teacher
22%
AI can already do 22% of this job.
#471 / 773
View rankingSecondary 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.
| Task | Share | AI | Points |
|---|---|---|---|
Unit, criteria and the exam.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Classroom, the group and the one who blows it up.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Cover, the corridor and the fight.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Family, the report and not giving a 5 for quiet.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Staff, inspection and not dressing it.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
That they work, and nobody left out.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
- unit plans
- assessment criteria
- secondary cover
- corridors
- the report
- staff meeting
- schools inspection
- behaviour
Sources for this job· O*NET 25-2031.00· ESCO/ISCO 2330
IS WORK OVER?
Backend developer
27%
#153 / 773
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