IS WORK OVER?

Automation index

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

An occupancy forecast comes earlier. The house running without breakfast collapsing do not.

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

Task comparison

Hotel 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
Occupancy, rates and the forecast.
Estimate

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

18%48%+8.6
Shifts, complaints and the one who leaves staff.
Estimate

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

16%40%+6.4
Owner, the budget and not cutting breakfast.
Estimate

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

16%22%+3.5
Incident, the VIP and the one who floods the room.
Estimate

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

16%28%+4.5
The inspection, insurance and not dressing the log.
Estimate

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

18%14%+2.5
That the house runs, and breakfast standing.
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

  • occupancy
  • hotel forecast
  • shifts
  • complaints
  • VIP
  • breakfast
  • inspection
  • rates

Sources for this job· O*NET 11-9081.00· ESCO/ISCO 1411

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. 154Front-end developer27%
  2. 155Comic artist27%
  3. 156Headteacher27%
  4. 158Spa manager27%
  5. 159Thesis supervisor27%
  6. 160Sporting director27%