IS WORK OVER?

Automation index

How much of a Office receptionist’s job can AI already do?

A diary comes earlier. Greeting without losing the visitor in the lobby do not.

This percentage does not predict how many people will lose their jobs.

Task comparison

Office receptionist

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
Diary, visitors and the lobby.
Estimate

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

16%40%+6.4
Calls, the one who is out and the message.
Estimate

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

18%14%+2.5
Parcels, the urgent and not signing blind.
Estimate

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

16%28%+4.5
Access, the one without an appointment and not letting them through.
Estimate

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

16%22%+3.5
The peak, the mood and keeping calm.
Estimate

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

18%18%+3.2
Greet, and not losing the visitor.
Estimate

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

16%12%+1.9
Total100%22%

Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low

Skills and activities

  • visitor diary
  • lobby
  • messages
  • parcels
  • access
  • switchboard
  • appointments
  • sign-ins

Sources for this job· O*NET 43-4171.00· ESCO/ISCO 4226

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. 476School psychologist22%
  2. 477Educational psychologist22%
  3. 478Cheesemaker22%
  4. 480Stage manager22%
  5. 481Watchmaker22%
  6. 482Book restorer22%