Automation index

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

A test comes earlier. Catching the real bug without painting a lying green do not.

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

Task comparison

IS WORK OVER?

27%

AI can already do 27% of this job.

#185 / 763

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

IS WORK OVER?

27%

#151 / 763

Backend developer

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

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