Automation index
How much of a Station master’s job can AI already do?
A train graph comes earlier. Leaving on time without meeting on the same line do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Station master
23%
AI can already do 23% of this job.
#348 / 763
View rankingStation master
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 |
|---|---|---|---|
Graph, orders and the station log.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Platforms, the crossing and the late train.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Staff, shifts and the ticket-office gap.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 32% | +5.1 |
Incident, passengers and the PA.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Works, closures and leaving nobody on the platform.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
That they do not meet, and signing the graph.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 23% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- train graph
- orders
- platforms
- ticket office
- PA
- line crossings
- station shifts
- station logs
Sources for this job· O*NET 53-4031.00· ESCO/ISCO 4323
IS WORK OVER?
Backend developer
27%
#151 / 763
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