Automation index
How much of a Geomatics engineer’s job can AI already do?
A point cloud comes earlier. The axis being where it is without signing metres of drift do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Geomatics engineer
22%
AI can already do 22% of this job.
#422 / 773
View rankingGeomatics 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 |
|---|---|---|---|
Station, the base and the cloud.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Field, the axis and the one that moved.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Model, the drift and not hiding metres.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Works, the setting-out and going down to see it.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The contractor, the rush and not signing the drift.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
That the axis is there, and not signing metres.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
- point clouds
- total stations
- axes
- setting-out
- drift
- bases
- geomatics
- the field
Sources for this job· O*NET 17-1022.00· ESCO/ISCO 2165
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