IS WORK OVER?

Automation index

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

A datasheet comes earlier. It actually reading without leaving the bypass open do not.

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

Task comparison

Instrumentation 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
Datasheet, the range and the loop.
Estimate

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

16%40%+6.4
Field, the transmitter and the one that will not arrive.
Estimate

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

18%14%+2.5
Calibrate, the standard and not signing the drift.
Estimate

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

16%28%+4.5
Bypass, the valve and not leaving it open.
Estimate

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

16%22%+3.5
Process, the rush and not jumping to a yes.
Estimate

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

18%18%+3.2
That it reads, and not leaving the bypass open.
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

  • datasheets
  • instrument loops
  • transmitters
  • calibrate
  • standards
  • bypass
  • ranges
  • drift

Sources for this job· O*NET 17-3023.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. 397Control engineer22%
  2. 398Corrosion engineer22%
  3. 399Firmware engineer22%
  4. 401Facilities engineer22%
  5. 402Mechatronics engineer22%
  6. 403Mining engineer22%