Automation index
How much of a Switchboard operator’s job can AI already do?
A switchboard comes earlier. Putting the call through without hanging up on the one who waits do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Switchboard operator
27%
AI can already do 27% of this job.
#232 / 763
View rankingSwitchboard operator
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 |
|---|---|---|---|
Board, destinations and the shift.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
The call, the one who is out and the message.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Emergencies, the anger and not losing it.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Directory, changes and not putting through wrong.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The peak, the queues and not hanging up.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Put it through, and not hanging up on the one who waits.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
- switchboard
- destinations
- messages
- directory
- call queues
- emergencies
- telephony shifts
- extension changes
Sources for this job· O*NET 43-2021.00· ESCO/ISCO 4223
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