Automation index
How much of a Geotechnical engineer’s job can AI already do?
A borehole comes earlier. Calling whether the building stands without hiding the clay do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Geotechnical engineer
22%
AI can already do 22% of this job.
#425 / 773
View rankingGeotechnical 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 |
|---|---|---|---|
Borehole, the sample and the report.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Field, the water table and the one that was not read.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Foundations, the clay and not hiding it.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Slope, the factor and not signing the one that slips.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The architect, the rush and not jumping to a yes.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
If it stands, sign it. And not hiding the clay.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 22% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- boreholes
- water table
- clays
- foundations
- slopes
- soil samples
- geotech reports
- factors of safety
Sources for this job· O*NET 17-2151.00· ESCO/ISCO 2142
IS WORK OVER?
Backend developer
27%
#153 / 773
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