Automation index
How much of a Production engineer’s job can AI already do?
An OEE and a sequencer come earlier. Getting the shift out without stopping the line for nothing do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Production engineer
25%
AI can already do 25% of this job.
#233 / 623
View rankingProduction engineer
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 |
|---|---|---|---|
OEE, sequence and the shift plan.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Line, changeovers and the micro-stop.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Layout, times and the work standard.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 36% | +5.8 |
Supervisors, unions and the shift that turns.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
In-line quality and the batch that cannot ship.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Hit the plan, and not dressing the OEE.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 25% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- OEE
- sequence production
- changeovers
- layout
- work standards
- micro-stops
- shift plan
- in-line quality
Sources for this job· O*NET 17-2112.00· ESCO/ISCO 2141
IS WORK OVER?
Mobile developer
28%
#92 / 623
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