IS WORK OVER?

Automation index

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

A test protocol comes earlier. Starting up without leaving an interlock jumped do not.

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

Task comparison

Commissioning 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
Protocol, the loop and the punch.
Estimate

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

16%40%+6.4
Plant, start-up and the one that is not ready.
Estimate

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

18%14%+2.5
Test, the trip and not jumping it.
Estimate

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

16%28%+4.5
Vendors, the one who does not come and the spare.
Estimate

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

16%22%+3.5
The client, the deadline and not signing half done.
Estimate

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

18%18%+3.2
Start up, and not leaving the interlock jumped.
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

  • test protocols
  • loops
  • punch list
  • start-up
  • trips
  • vendors
  • interlocks
  • not sign half done

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. 412Mechatronics engineer22%
  2. 413Mining engineer22%
  3. 414Bridge engineer22%
  4. 416Gas network engineer22%
  5. 417District heating engineer22%
  6. 418Safety engineer22%