Automation index
How much of a Property developer’s job can AI already do?
A development model comes earlier. Putting the building up and selling it without rows do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Property developer
27%
AI can already do 27% of this job.
#174 / 623
View rankingProperty 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 |
|---|---|---|---|
Land, licence and the model.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Works, the builder and the one who is late.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Sell, the plan and the one who reserves.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Bank, the facility and the one that is cut.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Neighbours, the objection and not hiding the impact.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Put it up and sell without rows.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
- land
- licences
- development model
- sell units
- development finance
- objections
- reservations
- the build
Sources for this job· O*NET 11-9021.00· ESCO/ISCO 3334
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