IS WORK OVER?

Automation index

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

An MTBF comes earlier. It not dropping at three without hiding the spare do not.

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

Task comparison

Reliability 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
Data, MTBF and the Pareto.
Estimate

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

18%48%+8.6
Failure, the cause and not patching twice.
Estimate

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

16%40%+6.4
Spare, the critical and not hiding it.
Estimate

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

16%22%+3.5
RCM, the plan and the one that is not done.
Estimate

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

16%28%+4.5
Production, the rush and not running the tired one.
Estimate

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

18%14%+2.5
That it does not drop at three, and not hiding the spare.
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

  • MTBF
  • Pareto
  • root causes
  • critical spares
  • RCM
  • failures
  • maintenance plans
  • not patch twice

Sources for this job· O*NET 17-2112.00· ESCO/ISCO 2141

Requirements 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
Workshop, the actor and the requirement.
Estimate

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

18%48%+8.6
Conflict, the loudest and not swallowing it.
Estimate

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

16%40%+6.4
Criterion, the test and not leaving it vague.
Estimate

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

16%22%+3.5
Change, the impact and not hiding it.
Estimate

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

16%28%+4.5
The project lead, 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 is needed, and not the loudest one's.
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

  • requirements
  • actor workshops
  • acceptance criteria
  • change impact
  • backlog
  • tests
  • not swallow the loudest
  • ambiguity

Sources for this job· O*NET 15-1299.00· ESCO/ISCO 2511

Analyse my job

Jobs with similar scores

  1. 174Cost engineer27%
  2. 175Energy engineer27%
  3. 176Packaging engineer27%
  4. 178Lighting engineer27%
  5. 179Materials engineer27%
  6. 180Renewables engineer27%