IS WORK OVER?

Automation index

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

A load curve comes earlier. Cutting the bill without leaving the process in the dark do not.

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

Task comparison

Energy 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
Energy audit, curves and the saving potential.
Estimate

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

18%48%+8.6
Contracts, tariffs and the power market.
Estimate

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

16%36%+5.8
Plant, meters and what the meter misses.
Estimate

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

16%22%+3.5
Efficiency projects and the real payback.
Estimate

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

16%28%+4.5
The board, the CAPEX and the no to the project.
Estimate

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

18%14%+2.5
Save for real, and not selling green smoke.
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

  • energy audit
  • load curves
  • power tariffs
  • energy efficiency
  • CAPEX payback
  • plant metering
  • power market
  • real savings

Sources for this job· O*NET 17-2199.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. 177Automation engineer27%
  2. 178HVAC engineer27%
  3. 179Cost engineer27%
  4. 181Packaging engineer27%
  5. 182Reliability engineer27%
  6. 183Lighting engineer27%