IS WORK OVER?

Automation index

How much of a Banquet manager’s job can AI already do?

A menu and a table plan come earlier. The service going out without the plate going cold do not.

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

Task comparison

Banquet manager

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
Menu, plan and the timing.
Estimate

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

16%40%+6.4
Set-up, staff and the one who is late.
Estimate

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

18%14%+2.5
Service, the toast and the one without a plate.
Estimate

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

16%28%+4.5
Kitchen, the pass and not working too far ahead.
Estimate

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

16%22%+3.5
The groom, the change and not mixing allergies.
Estimate

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

18%18%+3.2
The service goes out, and the plate hot.
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

  • table plans
  • banquet timing
  • set-up
  • toast
  • kitchen pass
  • allergies
  • floor staff
  • menus

Sources for this job· O*NET 35-1012.00· ESCO/ISCO 1412

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. 428Social integrator22%
  2. 429Heritage interpreter22%
  3. 430Court interpreter22%
  4. 432Table official22%
  5. 433Duty solicitor22%
  6. 434Radio host22%