Automation index
How much of a Camera operator’s job can AI already do?
A schedule and an overlay come earlier. The shot you have to nail does not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Camera operator
18%
AI can already do 18% of this job.
#556 / 633
View rankingCamera operator
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 |
|---|---|---|---|
Schedule, lists and overlays.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 32% | +5.1 |
Frame, follow and not lose focus.EstimateNo public source provides a precise figure. This is our estimate. | 22% | 10% | +2.2 |
Kit, cards and backups.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
Director, light and sound.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Knees, shoulder and long days.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 16% | +2.6 |
Not wiping a full card.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 14% | +2 |
| Total | 100% | 18% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- Schedule, lists and overlays
- Frame, follow and not lose focus
- Kit, cards and backups
- Director, light and sound
- Knees, shoulder and long days
- Not wiping a full card
- camara
- operador de camara
- camera operator
Sources for this job· O*NET 27-4031.00· ESCO/ISCO 3521
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