Automation index
How much of a Technical writer’s job can AI already do?
A doc skeleton comes earlier. A human installing the product without ringing do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Technical writer
28%
AI can already do 28% of this job.
#115 / 733
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
IS WORK OVER?
Commissioning engineer
22%
#387 / 733
View rankingCommissioning 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 |
|---|---|---|---|
Protocol, the loop and the punch.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Plant, start-up and the one that is not ready.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Test, the trip and not jumping it.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Vendors, the one who does not come and the spare.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The client, the deadline and not signing half done.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Start up, and not leaving the interlock jumped.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
- test protocols
- loops
- punch list
- start-up
- trips
- vendors
- interlocks
- not sign half done
Sources for this job· O*NET 17-2199.00· ESCO/ISCO 2149