Automation index
How much of a Occupational physician’s job can AI already do?
A screening protocol comes earlier. Calling fit or not and facing the company do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Occupational physician
29%
AI can already do 29% of this job.
#65 / 763
View rankingOccupational physician
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 |
|---|---|---|---|
Screenings, protocols and the work history.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Fit notes, restrictions and PPE.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
The hard case, the one who cannot, and the company pushing.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Risk surveillance, sick leave and return.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Inspectorate, mutual and coordination with H&S.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Medical secrecy and signing fit for work.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 29% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- occupational screening
- fit for work
- health surveillance
- work restrictions
- return to work
- occupational medicine
- work history
- medical secrecy
Sources for this job· O*NET 29-1229.00· ESCO/ISCO 2212
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