Automation index
How much of a Revenue manager’s job can AI already do?
A pickup comes earlier. Raising the rate without emptying the hotel do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Revenue manager
27%
AI can already do 27% of this job.
#212 / 763
View rankingRevenue 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.
| Task | Share | AI | Points |
|---|---|---|---|
Pickup, competitors and the rate.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Channels, overbooking and the one left on the street.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Events, the holiday and not sleeping on the price.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Report, management and the staff cut.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Sales, the group and not giving the room away.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
A high rate and a full house, not empty.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
- pickup
- rates
- channels
- overbooking
- holidays
- groups
- competitors
- rooms
Sources for this job· O*NET 11-9081.00· ESCO/ISCO 1411
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