Automation index
How much of a Tax officer’s job can AI already do?
A data match comes earlier. Assessing what is there without inventing a crime do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Tax officer
27%
AI can already do 27% of this job.
#224 / 763
View rankingTax officer
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 |
|---|---|---|---|
Match, the return and the gap.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Notice, the deadline and the one who will not answer.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Minute, the facts and not stretching them.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Garnishment, proportion and not sinking extra.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The boss, the target and not hunting for sport.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Assess what is there, and not inventing the crime.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
- data matches
- tax returns
- notices
- minutes
- garnishments
- facts
- tax-office deadlines
- not stretch facts
Sources for this job· O*NET 13-2081.00· ESCO/ISCO 3352
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