IS WORK OVER?

Automation index

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

A thickness map comes earlier. Stopping before the pipe goes, without painting over it, do not.

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

Task comparison

Corrosion 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
Thicknesses, the map and the coupon.
Estimate

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

16%40%+6.4
Plant, the pipe and the one that is thin.
Estimate

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

18%14%+2.5
Cathode, the protection and the one that will not take.
Estimate

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

16%28%+4.5
Shutdown, the coating and not painting over rust.
Estimate

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

16%22%+3.5
Operations, the rush and not leaving the thin one in service.
Estimate

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

18%18%+3.2
Stop before it goes, and not painting over it.
Estimate

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

16%12%+1.9
Total100%22%

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

Skills and activities

  • thicknesses
  • corrosion maps
  • cathodic protection
  • coatings
  • thin pipes
  • shutdowns
  • rust
  • coupons

Sources for this job· O*NET 17-2131.00· ESCO/ISCO 2145

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. 395Hydrologist22%
  2. 396Agronomist22%
  3. 397Control engineer22%
  4. 399Firmware engineer22%
  5. 400Instrumentation engineer22%
  6. 401Facilities engineer22%