Automation index
How much of a Traffic engineer’s job can AI already do?
A microsim comes earlier. The junction not killing anyone without painting an extra lane do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Traffic engineer
27%
AI can already do 27% of this job.
#189 / 763
View rankingTraffic engineer
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 |
|---|---|---|---|
Counts, the model and the microsim.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Junction, the timings and the pedestrian.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Works, the diversion and not choking the neighbourhood.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Report, the councillor and not painting the miracle lane.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The crash, the figure and not hiding it.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That the junction does not kill, and not painting extra.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
- microsims
- counts
- junction timings
- pedestrians
- diversions
- councillors
- crashes
- lanes
Sources for this job· O*NET 17-2051.00· ESCO/ISCO 2142
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