Automation index
How much of a Structural engineer’s job can AI already do?
A frame model comes earlier. Signing that it takes wind and quake do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Structural engineer
26%
AI can already do 26% of this job.
#250 / 763
View rankingStructural engineer
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 |
|---|---|---|---|
Model, combinations and the calculation annex.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Site, rebar and what was not poured that way.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Code, building regs and the sizing note.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 36% | +5.8 |
Pathology, the crack and shore or not.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
The architect, the deadline and not trimming the depth.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Sign that it stands, and not hiding the assumption.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 26% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- calculate structures
- frame model
- calculation annex
- building regs
- rebar
- structural pathology
- load combinations
- shore
Sources for this job· O*NET 17-2051.00· ESCO/ISCO 2142
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