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

IS WORK OVER?

22%

AI can already do 22% of this job.

#415 / 773

Commissioning engineer

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
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
Total	100%		22%

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

IS WORK OVER?

27%

#192 / 773

QA automation engineer

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
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
Total	100%		27%

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