IS WORK OVER?

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

Switchboard 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.

TaskShareAIPoints
Board, destinations and the shift.
Estimate

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

18%48%+8.6
The call, the one who is out and the message.
Estimate

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

16%40%+6.4
Emergencies, the anger and not losing it.
Estimate

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

16%22%+3.5
Directory, changes and not putting through wrong.
Estimate

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

16%28%+4.5
The peak, the queues and not hanging up.
Estimate

No 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.
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

  • switchboard
  • destinations
  • messages
  • directory
  • call queues
  • emergencies
  • telephony shifts
  • extension changes

Sources for this job· O*NET 43-2021.00· ESCO/ISCO 4223

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. 229Grants officer27%
  2. 230Ombudsman officer27%
  3. 231Dairy technician27%
  4. 233Telemarketer27%
  5. 234Treasurer27%
  6. 235Trader27%