IS WORK OVER?

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

Technical 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.

TaskShareAIPoints
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
Total100%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

Front-end 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.

TaskShareAIPoints
Component, states and the design.
Estimate

No public source provides a precise figure. This is our estimate.

18%48%+8.6
Accessible, the keyboard and the reader.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
Contrast, the token and not leaving it dead.
Estimate

No public source provides a precise figure. This is our estimate.

16%22%+3.5
Performance, the weight and not adding the extra library.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
The designer, the pixel and not fighting for sport.
Estimate

No public source provides a precise figure. This is our estimate.

18%14%+2.5
That it works from the keyboard, and not leaving the contrast.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%27%

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

Skills and activities

  • components
  • accessibility
  • keyboard
  • contrast
  • tokens
  • front-end performance
  • libraries
  • write interface

Sources for this job· O*NET 15-1254.00· ESCO/ISCO 2513

Analyse my job

Jobs with similar scores

  1. 112Route planner28%
  2. 113Psychologist28%
  3. 114Parts clerk28%
  4. 116Land registrar28%
  5. 117Delivery driver28%
  6. 118Secretary28%