IS WORK OVER?

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

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

Front-end 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
Component, states and the design.
Estimate

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

18%48%+8.6
Accessible, the keyboard and the reader.
Estimate

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

16%40%+6.4
Contrast, the token and not leaving it dead.
Estimate

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

16%22%+3.5
Performance, the weight and not adding the extra library.
Estimate

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

16%28%+4.5
The designer, the pixel and not fighting for sport.
Estimate

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

18%14%+2.5
That it works from the keyboard, and not leaving the contrast.
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

  • components
  • accessibility
  • keyboard
  • contrast
  • tokens
  • front-end performance
  • libraries
  • write interface

Sources for this job· O*NET 15-1254.00· ESCO/ISCO 2513

Analyse my job

Jobs with similar scores

  1. 182Reliability engineer27%
  2. 183Lighting engineer27%
  3. 184Materials engineer27%
  4. 186Renewables engineer27%
  5. 187Requirements engineer27%
  6. 188Security engineer27%