Automation index
How much of a Surveyor’s job can AI already do?
A digital set-out and a drawing come earlier. Driving stakes in the wind, and the building lining up, do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Surveyor
24%
AI can already do 24% of this job.
#284 / 623
View rankingSurveyor
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 |
|---|---|---|---|
Process stations, GNSS and drawings.EstimateNo public source provides a precise figure. This is our estimate. | 20% | 45% | +9 |
Reports, volumes and deliverables.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 35% | +5.6 |
Measure in the field, stake and set out.EstimateNo public source provides a precise figure. This is our estimate. | 20% | 12% | +2.4 |
Coordinate with works and the site authority.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 15% | +2.4 |
Read the ground when the model lies.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 16% | +2.2 |
Owning a 3 cm error.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 14% | +2 |
| Total | 100% | 24% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- Process stations, GNSS and drawings
- Reports, volumes and deliverables
- Measure in the field, stake and set out
- Read the ground when the model lies
- Owning a 3 cm error
- topografo
- surveyor
- aparejador topografia
Sources for this job· O*NET 17-1022.00· ESCO/ISCO 2165
IS WORK OVER?
Mobile developer
28%
#92 / 623
View rankingMobile 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 |
|---|---|---|---|
Screens, API and offline state.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Store review, crashlytics and ANRs.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Real device, the notch and fragmented Android.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
CI, tests and the week's release.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the redesign and not breaking what people use.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it does not crash, and not ignoring the one-star.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 28% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- build apps
- ship to stores
- crashlytics
- offline state
- ANRs
- mobile tests
- fragmented Android
- store review
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2514