Automation index
How much of a NDT technician’s job can AI already do?
An NDT procedure comes earlier. Seeing the defect without signing it sound do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
NDT technician
22%
AI can already do 22% of this job.
#493 / 773
View rankingNDT technician
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 |
|---|---|---|---|
Procedure, technique and the part.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Test, the indication and the one that hides.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Report, the size and not inflating.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Field, the scaffold and the access.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The welder, the rush and not signing it sound.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
See the defect, and a true report.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
- NDT
- ultrasound
- indications
- procedures
- scaffold
- test reports
- defect size
- access
Sources for this job· O*NET 51-9061.00· ESCO/ISCO 3119
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