IS WORK OVER?

Automation index

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

A logframe comes earlier. Being there when it goes wrong, and doing no harm, do not.

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

Task comparison

Aid 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
Forms, logframe and the indicators.
Estimate

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

16%44%+7
The field, local partners and what the spreadsheet misses.
Estimate

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

18%14%+2.5
Donor reports and the paperwork.
Estimate

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

16%32%+5.1
Security, evacuation and the call to stay.
Estimate

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

16%22%+3.5
Community, conflict and not replacing the local.
Estimate

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

18%18%+3.2
Do no harm and owning the project.
Estimate

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

16%12%+1.9
Total100%23%

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

Skills and activities

  • logframe
  • field work
  • justify projects
  • local partners
  • mission security
  • aid indicators
  • donor reports
  • do no harm

Sources for this job· O*NET 21-1093.00· ESCO/ISCO 2635

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. 335Nursing assistant23%
  2. 336Cardiologist23%
  3. 337Museum curator23%
  4. 339Dermatologist23%
  5. 340Art director23%
  6. 341Occupational trainer23%