IS WORK OVER?

Automation index

How much of a Copy editor’s job can AI already do?

A checker and a first pass come earlier. Keeping the author’s voice and not inserting a typo do not.

This percentage does not predict how many people will lose their jobs.

Task comparison

Copy editor

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
Spelling, agreement and consistency.
Estimate

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

18%52%+9.4
Style, repetition and sentence rhythm.
Estimate

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

16%48%+7.7
Queries to the author, grey areas and the house style.
Estimate

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

16%28%+4.5
Second proofs, PDF and last-minute typos.
Estimate

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

18%22%+4
Deadlines with publisher, layout and translation.
Estimate

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

16%18%+2.9
Judgement, not over-rewriting, and the typo that remains.
Estimate

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

16%14%+2.2
Total100%31%

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

Skills and activities

  • copy-edit
  • spelling and punctuation
  • unify style
  • catch typos
  • house style
  • second proofs
  • author queries
  • avoid over-editing

Sources for this job· O*NET 27-3041.00· ESCO/ISCO 2641

Mobile 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
Screens, API and offline state.
Estimate

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

18%52%+9.4
Store review, crashlytics and ANRs.
Estimate

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

16%40%+6.4
Real device, the notch and fragmented Android.
Estimate

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

16%22%+3.5
CI, tests and the week's release.
Estimate

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

16%28%+4.5
Product, the redesign and not breaking what people use.
Estimate

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

  • 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

Analyse my job

Jobs with similar scores

  1. 29Admin assistant31%
  2. 30Biologist31%
  3. 31Cartographer31%
  4. 33Information specialist31%
  5. 34Epidemiologist31%
  6. 35Growth manager31%