Automation index
How much of a Development cooperation officer’s job can AI already do?
An agreement and a frame come earlier. Aligning with the southern partner and not imposing the project do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Development cooperation officer
26%
AI can already do 26% of this job.
#258 / 763
View rankingDevelopment cooperation officer
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 |
|---|---|---|---|
Agreements, alignment and the SDGs on the card.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 48% | +7.7 |
Follow-up, missions and reports to the agency.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 36% | +5.8 |
The local partner, the counterpart and the disagreement.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 16% | +2.9 |
Budget, currency and what stays in management.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The context that shifts and reworking the approach.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Not imposing, and accounting on both sides.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
- cooperation agreements
- align with SDGs
- agency reports
- southern partners
- monitoring missions
- hard-currency budget
- counterparts
- accountability
Sources for this job· O*NET 19-3094.00· ESCO/ISCO 2635
IS WORK OVER?
Backend developer
27%
#151 / 763
View rankingBackend 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 |
|---|---|---|---|
Endpoint, the contract and the test.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Spike, the queue and the one that drops.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Key, the secret and not leaving it in the repo.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Migration, the rollback and not improvising in prod.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the deadline and not cutting the one that matters.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it takes the spike, and not leaving the key.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
- endpoints
- API contracts
- queues
- secrets
- migrations
- rollback
- backend tests
- write server code
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2512