Automation index
How much of a Information specialist’s job can AI already do?
Filing a PDF and a thesaurus come earlier. Retrieving what the house does not know it has do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Information specialist
31%
AI can already do 31% of this job.
#33 / 763
View rankingInformation specialist
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 |
|---|---|---|---|
Classify, index and describe holdings.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Thesauri, metadata and the internal search.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 52% | +8.3 |
Answer queries and retrieve what nobody can find.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Records policy, retention and destruction.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 22% | +4 |
Train people who file badly and people who do not file.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
The organisation’s memory, and not losing it.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 30% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- manage records
- index holdings
- classify archives
- retrieve information
- metadata
- thesauri
- retention policy
- internal search
Sources for this job· O*NET 25-4013.00· ESCO/ISCO 2622
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