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

QA automation 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
Test, the selector and the flake.
Estimate

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

18%48%+8.6
Pipeline, the green and the one that lies.
Estimate

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

16%40%+6.4
Bug, the repro and not closing it blind.
Estimate

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

16%22%+3.5
Data, the environment and not sharing prod.
Estimate

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

16%28%+4.5
The developer, the rush and not skipping the one that fails.
Estimate

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

18%14%+2.5
Catch the bug, and not painting a lying green.
Estimate

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

16%12%+1.9
Total100%27%

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

Skills and activities

  • automated tests
  • selectors
  • flakes
  • QA pipelines
  • repro
  • environments
  • lying green
  • debug tests

Sources for this job· O*NET 15-1253.00· ESCO/ISCO 2519

Analyse my job

Jobs with similar scores

  1. 277Civil engineer25%
  2. 278Petroleum engineer25%
  3. 279Production engineer25%
  4. 281Telecom engineer25%
  5. 282Electrical engineer25%
  6. 283Electronics engineer25%