Automation index
How much of a Web developer’s job can AI already do?
A layout and a component come earlier. A site that loads and does not die on a Friday does not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Web developer
26%
AI can already do 26% of this job.
#244 / 763
View rankingWeb 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 |
|---|---|---|---|
Layout, components and API consumption.EstimateNo public source provides a precise figure. This is our estimate. | 20% | 48% | +9.6 |
Accessibility, performance and technical SEO.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 32% | +5.1 |
Design, product and the client who changes their mind.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Deploys, incidents and monitoring.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
Tests, code review and documentation.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 16% | +2.6 |
Not shipping a half-change on a Friday.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 26% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- write code
- programming
- software development
- coding
- debug code
- Layout, components and API consumption
- Deploys, incidents and monitoring
- Tests, code review and documentation
- Not shipping a half-change on a Friday
- desarrollador web
Sources for this job· O*NET 15-1254.00· ESCO/ISCO 2513
IS WORK OVER?
Front-end developer
27%
#154 / 763
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