Automation index
How much of a Tax inspector’s job can AI already do?
A data match comes earlier. Sitting across from the taxpayer and signing the adjustment do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Tax inspector
28%
AI can already do 28% of this job.
#104 / 763
View rankingTax inspector
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 |
|---|---|---|---|
Data matching, returns and sampling.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Requests, minutes and the proposal.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
The visit, the second till and what is not in the sheet.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Objections, appeals and the tax tribunal.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The team, deadlines and the file that slips.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
A fair adjustment and signing the minute.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
- match tax data
- raise assessments
- request papers
- visit taxpayers
- adjust tax
- objections
- tax tribunal
- tax inspection
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