Automation index
How much of a Ship agent’s job can AI already do?
An ETA comes earlier. Clearing the ship without extra demurrage do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Ship agent
26%
AI can already do 26% of this job.
#241 / 763
View rankingShip agent
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 |
|---|---|---|---|
ETA, berth and port services.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 44% | +7 |
Clearance, crew and the crew change.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 36% | +5.8 |
The master, the terminal and the window clash.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 16% | +2.9 |
Invoices, disbursements and the owner’s account.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The inspection, the delay and not losing the slot.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
No extra demurrage, and the ship cleared.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 26% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- ETAs
- berths
- ship clearance
- crew changes
- disbursements
- terminal windows
- owner’s accounts
- port inspections
Sources for this job· O*NET 43-5011.00· ESCO/ISCO 3331
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