Automation index
How much of a Landscape architect’s job can AI already do?
A planting plan comes earlier. A garden you can live in that does not die in August do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Landscape architect
24%
AI can already do 24% of this job.
#277 / 633
View rankingLandscape architect
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 |
|---|---|---|---|
Plan, species and the irrigation.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 44% | +7 |
Works, levels and the tree that will not fit.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 16% | +2.9 |
Soil, climate and not planting what will not last.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 32% | +5.1 |
Client, maintenance and what they will not water.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
August, the drought and the yes to xeriscape.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it is lived in, and not dying in August.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 24% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- planting plans
- species
- garden irrigation
- xeriscape
- works levels
- soil
- garden maintenance
- trees
Sources for this job· O*NET 17-1012.00· ESCO/ISCO 2162
IS WORK OVER?
Technical writer
28%
#115 / 633
View rankingTechnical writer
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 |
|---|---|---|---|
Structure, API docs and the tutorial.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Screenshots, versions and not leaving the old shot.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
The engineer who will not write, and extracting the how.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Legal review, i18n and the changelog.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Support, the tickets and what the doc misses.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it can be installed, and not documenting thin air.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
- document APIs
- product tutorials
- screenshots
- changelogs
- extract knowledge
- docs i18n
- version review
- support tickets
Sources for this job· O*NET 27-3042.00· ESCO/ISCO 2641