Automation index
How much of a Naval architect’s job can AI already do?
A stability calc comes earlier. A ship that floats and does not break does not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Naval architect
25%
AI can already do 25% of this job.
#286 / 763
View rankingNaval architect
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 |
|---|---|---|---|
Stability, strength and hull forms.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Drawings, specs and class rules.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 32% | +5.1 |
Yard, sea trials and owner.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Systems, machinery and onboard safety.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
Rules, IMO and documentation.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 16% | +2.9 |
Sign a hull that will not break.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 25% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- building plans
- renders
- sign a project
- Stability, strength and hull forms
- Drawings, specs and class rules
- Yard, sea trials and owner
- Systems, machinery and onboard safety
- Rules, IMO and documentation
- Sign a hull that will not break
- ingeniero naval
Sources for this job· O*NET 17-2121.00· ESCO/ISCO 2144
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