Automation index
How much of a Welding engineer’s job can AI already do?
A WPS comes earlier. The bead holding without signing an extra overlap do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Welding engineer
22%
AI can already do 22% of this job.
#419 / 773
View rankingWelding 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 |
|---|---|---|---|
WPS, the coupon and the qualification.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Shop, the bead and the one who skips the procedure.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
NDT, the fail and not hiding it.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Site, the position and the wind.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The client, the rush and not signing the extra overlap.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
That the bead holds, and not signing the overlap.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
- WPS
- coupons
- welder qualification
- beads
- NDT
- positions
- overlaps
- welding procedures
Sources for this job· O*NET 17-2141.00· ESCO/ISCO 2144
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