Automation index
How much of a Funeral director’s job can AI already do?
A form and an obituary come earlier. Collecting someone and looking after the family do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Funeral director
22%
AI can already do 22% of this job.
#330 / 623
View rankingFuneral director
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 |
|---|---|---|---|
Paperwork, chapel, burial and cremation.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Collection, thanatopraxy and care of the body.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 12% | +2.2 |
The family, the wake, and what is and is not possible.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Notice, flowers, hearse and the minute-by-minute of the rite.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Cemetery, times and suppliers.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Dignity, legal times and owning the service.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 22% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- arrange funerals
- file death paperwork
- collect the deceased
- support the family
- thanatopraxy
- run the wake
- arrange cremation
- notices
Sources for this job· O*NET 39-4031.00· ESCO/ISCO 5163
IS WORK OVER?
Mobile developer
28%
#92 / 623
View rankingMobile 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 |
|---|---|---|---|
Screens, API and offline state.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Store review, crashlytics and ANRs.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Real device, the notch and fragmented Android.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
CI, tests and the week's release.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the redesign and not breaking what people use.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it does not crash, and not ignoring the one-star.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
- build apps
- ship to stores
- crashlytics
- offline state
- ANRs
- mobile tests
- fragmented Android
- store review
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2514