IS WORK OVER?

Automation index

How much of a Robotics engineer’s job can AI already do?

A path and a twin come earlier. Putting the robot on the line without taking anyone with it do not.

This percentage does not predict how many people will lose their jobs.

Task comparison

Robotics 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.

TaskShareAIPoints
Paths, PLC and the cell twin.
Estimate

No public source provides a precise figure. This is our estimate.

16%48%+7.7
Cell, grippers and the cycle that will not close.
Estimate

No public source provides a precise figure. This is our estimate.

18%16%+2.9
Safety, fencing and CE validation.
Estimate

No public source provides a precise figure. This is our estimate.

16%32%+5.1
Maintenance, backups and the overwritten program.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
Production, takt and the robot that stops.
Estimate

No public source provides a precise figure. This is our estimate.

18%14%+2.5
That it takes nobody with it, and signing the cell.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%25%

Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low

Skills and activities

  • program robots
  • paths
  • robot cells
  • safety fencing
  • cell PLC
  • CE validation
  • grippers
  • takt

Sources for this job· O*NET 17-2199.00· ESCO/ISCO 2149

Mobile 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.

TaskShareAIPoints
Screens, API and offline state.
Estimate

No public source provides a precise figure. This is our estimate.

18%52%+9.4
Store review, crashlytics and ANRs.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
Real device, the notch and fragmented Android.
Estimate

No public source provides a precise figure. This is our estimate.

16%22%+3.5
CI, tests and the week's release.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
Product, the redesign and not breaking what people use.
Estimate

No 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.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%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

Analyse my job

Jobs with similar scores

  1. 231Civil engineer25%
  2. 232Petroleum engineer25%
  3. 233Production engineer25%
  4. 235Telecom engineer25%
  5. 236Electrical engineer25%
  6. 237Electronics engineer25%