IS WORK OVER?

Automation index

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

A tensile curve comes earlier. Picking the alloy so it does not fail in service do not.

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

Task comparison

Materials 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
Tests, metallography and the spec.
Estimate

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

18%48%+8.6
Shop, heat treatment and the part that fails spec.
Estimate

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

16%22%+3.5
Material choice, corrosion and fatigue.
Estimate

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

16%36%+5.8
Supplier, certificates and the doubtful batch.
Estimate

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

16%28%+4.5
The field failure and the root cause.
Estimate

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

18%14%+2.5
That it does not fail, and not swapping the material blind.
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

  • materials tests
  • metallography
  • choose alloys
  • corrosion
  • fatigue
  • heat treatment
  • failure analysis
  • batch certificates

Sources for this job· O*NET 17-2131.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. 181Packaging engineer27%
  2. 182Reliability engineer27%
  3. 183Lighting engineer27%
  4. 185QA automation engineer27%
  5. 186Renewables engineer27%
  6. 187Requirements engineer27%