IS WORK OVER?

Automation index

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

A core model comes earlier. Running the plant and not playing with reactivity do not.

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

Task comparison

Nuclear 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
Neutronics, thermal-hydraulics and the file.
Estimate

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

16%44%+7
Control room, tests and the set-point.
Estimate

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

16%22%+3.5
Licence, the regulator and the safety analyses.
Estimate

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

16%36%+5.8
Outage, reload and spent fuel.
Estimate

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

18%14%+2.5
The event, safety culture and the report.
Estimate

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

18%18%+3.2
Not playing with reactivity, and signing the analysis.
Estimate

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

16%12%+1.9
Total100%24%

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

Skills and activities

  • neutronics
  • thermal-hydraulics
  • nuclear licence
  • reload
  • safety analysis
  • control room
  • spent fuel
  • safety culture

Sources for this job· O*NET 17-2161.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. 310Museum educator24%
  2. 311Electrician24%
  3. 312Nurse24%
  4. 314Health inspector24%
  5. 315Interpreter24%
  6. 316Warehouse supervisor24%