Automation index
How much of a Data protection inspector’s job can AI already do?
A notice comes earlier. Walking into the file without leaving the data lying around do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Data protection inspector
27%
AI can already do 27% of this job.
#194 / 763
View rankingData protection 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 |
|---|---|---|---|
Notice, the file and the deadline.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Inspection, the processing and what is not there.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Breach, the notice and not delaying.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Fine, the test and not hunting the sole trader extra.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The director, the note and not leaking the file.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Walk into the file, and not leaving the data lying around.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
- files
- processing
- breaches
- notices
- data fines
- AEPD deadlines
- sole traders
- not leak files
Sources for this job· O*NET 13-1041.00· ESCO/ISCO 2422
IS WORK OVER?
Front-end developer
27%
#154 / 763
View rankingFront-end 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 |
|---|---|---|---|
Component, states and the design.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Accessible, the keyboard and the reader.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Contrast, the token and not leaving it dead.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Performance, the weight and not adding the extra library.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The designer, the pixel and not fighting for sport.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it works from the keyboard, and not leaving the contrast.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
- components
- accessibility
- keyboard
- contrast
- tokens
- front-end performance
- libraries
- write interface
Sources for this job· O*NET 15-1254.00· ESCO/ISCO 2513