Automation index
How much of a Virologist’s job can AI already do?
A PCR comes earlier. Isolating the virus without contaminating the lab do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Virologist
22%
AI can already do 22% of this job.
#400 / 633
View rankingVirologist
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 |
|---|---|---|---|
PCR, cultures and the report.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Isolate, biosafety and the one that breaks.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Outbreak, sequence and the one that does not fit.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Public health, the note and not delaying.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The clinician, the antiviral and not jumping.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Isolate, and not contaminating.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 22% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- virus PCR
- cultures
- biosafety
- sequence outbreaks
- isolate virus
- public-health notes
- antivirals
- P3 lab
Sources for this job· O*NET 19-1022.00· ESCO/ISCO 2131
IS WORK OVER?
Mobile developer
28%
#92 / 633
View rankingMobile 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 |
|---|---|---|---|
Screens, API and offline state.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Store review, crashlytics and ANRs.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Real device, the notch and fragmented Android.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
CI, tests and the week's release.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the redesign and not breaking what people use.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it does not crash, and not ignoring the one-star.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
- build apps
- ship to stores
- crashlytics
- offline state
- ANRs
- mobile tests
- fragmented Android
- store review
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2514