Automation index
How much of a Power engineer’s job can AI already do?
A short-circuit study comes earlier. The disconnector not blowing without working live do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Power engineer
22%
AI can already do 22% of this job.
#421 / 773
View rankingPower 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.
| Task | Share | AI | Points |
|---|---|---|---|
Study, the short-circuit and selectivity.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Substation, the disconnector and the lockout.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Switching, the five rules and not skipping them.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Fault, the relay and not resetting blind.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The operator, the rush and not working live.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
That it does not blow, and not working live.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 22% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- short-circuits
- selectivity
- disconnectors
- five rules
- relays
- substations
- lockouts
- not work live
Sources for this job· O*NET 17-2071.00· ESCO/ISCO 2151
IS WORK OVER?
Backend developer
27%
#153 / 773
View rankingBackend 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.
| Task | Share | AI | Points |
|---|---|---|---|
Endpoint, the contract and the test.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Spike, the queue and the one that drops.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Key, the secret and not leaving it in the repo.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Migration, the rollback and not improvising in prod.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the deadline and not cutting the one that matters.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it takes the spike, and not leaving the key.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 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