Automation index
How much of a Building surveyor’s job can AI already do?
A take-off and a log come earlier. Directing the build and signing the works do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Building surveyor
22%
AI can already do 22% of this job.
#368 / 763
View rankingBuilding surveyor
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 |
|---|---|---|---|
Quantities, valuations and cost control.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Working drawings and trade coordination.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Site, visits and safety.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Client, contractor and site team.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Quality, tests and the building book.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 16% | +2.9 |
Sign a build that will not fall.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 22% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- building plans
- renders
- sign a project
- Quantities, valuations and cost control
- Working drawings and trade coordination
- Site, visits and safety
- Client, contractor and site team
- Quality, tests and the building book
- Sign a build that will not fall
- arquitecto tecnico
Sources for this job· O*NET 17-3011.00· ESCO/ISCO 3112
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