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
IS WORK OVER?
Copy editor
31%
AI can already do 31% of this job.
#32 / 763
View rankingCopy 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.
| Task | Share | AI | Points |
|---|---|---|---|
Spelling, agreement and consistency.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Style, repetition and sentence rhythm.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 48% | +7.7 |
Queries to the author, grey areas and the house style.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Second proofs, PDF and last-minute typos.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 22% | +4 |
Deadlines with publisher, layout and translation.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
Judgement, not over-rewriting, and the typo that remains.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 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
IS WORK OVER?
Backend developer
27%
#151 / 763
View rankingBackend 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.
| Task | Share | AI | Points |
|---|---|---|---|
Endpoint, the contract and the test.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Spike, the queue and the one that drops.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Key, the secret and not leaving it in the repo.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Migration, the rollback and not improvising in prod.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the deadline and not cutting the one that matters.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it takes the spike, and not leaving the key.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 27% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- endpoints
- API contracts
- queues
- secrets
- migrations
- rollback
- backend tests
- write server code
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2512