IS WORK OVER?

Automation index

How much of a Community health worker’s job can AI already do?

A workshop and a leaflet come earlier. Reaching the person who never walks into the clinic do not.

This percentage does not predict how many people will lose their jobs.

Task comparison

Community health worker

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.

TaskShareAIPoints
Health map, workshops and the calendar.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
Street, doorway and the neighbour who does not come.
Estimate

No public source provides a precise figure. This is our estimate.

18%14%+2.5
Vaccines, screening and referring to the clinic.
Estimate

No public source provides a precise figure. This is our estimate.

16%32%+5.1
Data, report and the health table.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
The rumour, the distrust and not moralising.
Estimate

No public source provides a precise figure. This is our estimate.

18%18%+3.2
That they come, and not inflating workshop numbers.
Estimate

No public source provides a precise figure. This is our estimate.

16%14%+2.2
Total100%24%

Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low

Skills and activities

  • health workshops
  • health map
  • door-to-door
  • refer to clinic
  • screening
  • health table
  • community vaccination
  • health distrust

Sources for this job· O*NET 21-1094.00· ESCO/ISCO 3253

Backend 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.

TaskShareAIPoints
Endpoint, the contract and the test.
Estimate

No public source provides a precise figure. This is our estimate.

18%48%+8.6
Spike, the queue and the one that drops.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
Key, the secret and not leaving it in the repo.
Estimate

No public source provides a precise figure. This is our estimate.

16%22%+3.5
Migration, the rollback and not improvising in prod.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
Product, the deadline and not cutting the one that matters.
Estimate

No public source provides a precise figure. This is our estimate.

18%14%+2.5
That it takes the spike, and not leaving the key.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%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

Analyse my job

Jobs with similar scores

  1. 299Insurance underwriter25%
  2. 300Pest control technician25%
  3. 301Property manager24%
  4. 303Agile coach24%
  5. 304Software architect24%
  6. 305Biochemist24%