IS WORK OVER?

Automation index

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

A schematic comes earlier. The arm not taking a finger, and actually starting, do not.

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

Task comparison

Mechatronics 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
Schematic, the PLC and the loop.
Estimate

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

16%40%+6.4
Cell, the arm and the one that will not stop.
Estimate

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

18%14%+2.5
Commissioning, the interlock and not jumping it.
Estimate

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

16%28%+4.5
Cycle, the time and not inflating the figure.
Estimate

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

16%22%+3.5
The operator, the guard and not leaving them blind.
Estimate

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

18%18%+3.2
That it does not take a finger, and starts.
Estimate

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

16%12%+1.9
Total100%22%

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

Skills and activities

  • PLC
  • loops
  • robot cells
  • interlocks
  • commissioning
  • guards
  • cycle times
  • not jump the interlock

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

Backend 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
Endpoint, the contract and the test.
Estimate

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

18%48%+8.6
Spike, the queue and the one that drops.
Estimate

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

16%40%+6.4
Key, the secret and not leaving it in the repo.
Estimate

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

16%22%+3.5
Migration, the rollback and not improvising in prod.
Estimate

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

16%28%+4.5
Product, the deadline and not cutting the one that matters.
Estimate

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

18%14%+2.5
That it takes the spike, and not leaving the key.
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

  • endpoints
  • API contracts
  • queues
  • secrets
  • migrations
  • rollback
  • backend tests
  • write server code

Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2512

Analyse my job

Jobs with similar scores

  1. 409Firmware engineer22%
  2. 410Instrumentation engineer22%
  3. 411Facilities engineer22%
  4. 413Mining engineer22%
  5. 414Bridge engineer22%
  6. 415Commissioning engineer22%