Automation index
How much of a Fibre technician’s job can AI already do?
An OTDR comes earlier. Splicing in the chamber so the customer can browse do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Fibre technician
22%
AI can already do 22% of this job.
#495 / 773
View rankingFibre 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 |
|---|---|---|---|
Route, OTDR and the splice log.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Chamber, splice and the fibre that breaks.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 12% | +2.2 |
CTO, drop and the customer who sees no light.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Pole, façade and the missing permit.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Rain, the cover and not leaving the chamber open.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
That they can browse, and not leaving a dirty splice.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
- splice fibre
- OTDR
- chambers
- CTO
- drops
- fibre strands
- poles
- splice logs
Sources for this job· O*NET 49-2022.00· ESCO/ISCO 7422
IS WORK OVER?
Front-end developer
27%
#157 / 773
View rankingFront-end 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 |
|---|---|---|---|
Component, states and the design.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Accessible, the keyboard and the reader.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Contrast, the token and not leaving it dead.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Performance, the weight and not adding the extra library.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The designer, the pixel and not fighting for sport.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it works from the keyboard, and not leaving the contrast.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
- components
- accessibility
- keyboard
- contrast
- tokens
- front-end performance
- libraries
- write interface
Sources for this job· O*NET 15-1254.00· ESCO/ISCO 2513