Automation index
How much of a Book editor’s job can AI already do?
A reader’s report comes earlier. Backing a manuscript and getting it into bookshops do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Book editor
25%
AI can already do 25% of this job.
#220 / 623
View rankingBook 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 |
|---|---|---|---|
Readers’ reports, selection and rejection.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Work the text with the author: structure and tone.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 22% | +4 |
P&L, advances, contracts and the schedule.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 32% | +5.1 |
Coordinate copy-edit, layout, cover and press.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
List, bookshops and the life of the title.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The editorial bet and owning the book.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 25% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- edit books
- readers’ reports
- work manuscripts
- negotiate advances
- build the list
- coordinate layout
- choose the cover
- get it into shops
Sources for this job· O*NET 27-3041.00· ESCO/ISCO 2641
IS WORK OVER?
Mobile developer
28%
#92 / 623
View rankingMobile 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 |
|---|---|---|---|
Screens, API and offline state.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Store review, crashlytics and ANRs.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Real device, the notch and fragmented Android.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
CI, tests and the week's release.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the redesign and not breaking what people use.EstimateNo 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.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
- 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