Automation index
How much of a Electronics engineer’s job can AI already do?
A schematic and a layout come earlier. A board that works first time does not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Electronics engineer
25%
AI can already do 25% of this job.
#283 / 763
View rankingElectronics 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 |
|---|---|---|---|
Schematic, simulation and PCB layout.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Firmware, tests and bench.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 32% | +5.1 |
Vendors, prototypes and certifications.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Debug EMC and field faults.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
Documentation, versioning and quality.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 16% | +2.9 |
Not sending a blind board to manufacture.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 25% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- Schematic, simulation and PCB layout
- Firmware, tests and bench
- Vendors, prototypes and certifications
- Debug EMC and field faults
- Documentation, versioning and quality
- Not sending a blind board to manufacture
- ingeniero electronico
- electronics engineer
Sources for this job· O*NET 17-2072.00· ESCO/ISCO 2152
IS WORK OVER?
Backend developer
27%
#151 / 763
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