Automation index
How much of a Pest control technician’s job can AI already do?
A protocol and a sheet come earlier. Treating without poisoning the people who live there do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Pest control technician
25%
AI can already do 25% of this job.
#254 / 633
View rankingPest control 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 |
|---|---|---|---|
Inspection, species and the treatment plan.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 32% | +5.1 |
Bait, apply, seal and look again.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Sheets, schedule and the certificate for the client.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Explain risks, times and what is not a miracle.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 22% | +4 |
Rules, biocides and waste.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
That the pest drops and nobody else pays.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
- pest control
- inspect infestations
- bait
- apply biocides
- seal entry points
- treatment certificate
- identify species
- not poison anyone
Sources for this job· O*NET 37-2021.00· ESCO/ISCO 7544
IS WORK OVER?
Technical writer
28%
#115 / 633
View rankingTechnical writer
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 |
|---|---|---|---|
Structure, API docs and the tutorial.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Screenshots, versions and not leaving the old shot.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
The engineer who will not write, and extracting the how.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Legal review, i18n and the changelog.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Support, the tickets and what the doc misses.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it can be installed, and not documenting thin air.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 28% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- document APIs
- product tutorials
- screenshots
- changelogs
- extract knowledge
- docs i18n
- version review
- support tickets
Sources for this job· O*NET 27-3042.00· ESCO/ISCO 2641