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?

28%

AI can already do 28% of this job.

#115 / 623

Technical writer

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. Estimate No public source provides a precise figure. This is our estimate.	18%	52%	+9.4
Screenshots, versions and not leaving the old shot. Estimate No public source provides a precise figure. This is our estimate.	16%	40%	+6.4
The engineer who will not write, and extracting the how. Estimate No public source provides a precise figure. This is our estimate.	16%	22%	+3.5
Legal review, i18n and the changelog. Estimate No public source provides a precise figure. This is our estimate.	16%	28%	+4.5
Support, the tickets and what the doc misses. Estimate No public source provides a precise figure. This is our estimate.	18%	14%	+2.5
That it can be installed, and not documenting thin air. Estimate No 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

IS WORK OVER?

24%

#257 / 623

Agile coach

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
Boards, metrics and the cadence design. Estimate No public source provides a precise figure. This is our estimate.	16%	40%	+6.4
The real retro and the elephant in the room. Estimate No public source provides a precise figure. This is our estimate.	18%	14%	+2.5
Train, unblock and the manager who will not let go. Estimate No public source provides a precise figure. This is our estimate.	16%	32%	+5.1
Scale, dependencies and fake agile. Estimate No public source provides a precise figure. This is our estimate.	16%	28%	+4.5
Conflict, power and not selling extra frameworks. Estimate No public source provides a precise figure. This is our estimate.	18%	18%	+3.2
That they stop faking it, and not inflating velocity. Estimate No public source provides a precise figure. This is our estimate.	16%	14%	+2.2
Total	100%		24%

Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low