IS WORK OVER?

Automation index

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

A crop map and a dose come earlier. Walking the farm and not ruining the harvest do not.

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

Task comparison

Agronomist

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
Maps, doses and fertiliser and irrigation plans.
Estimate

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

16%40%+6.4
Projects, subsidy files and paperwork.
Estimate

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

16%28%+4.5
Field, sampling and pests.
Estimate

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

18%14%+2.5
Farmer, co-op and administration.
Estimate

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

16%22%+3.5
Water, soils and sustainability.
Estimate

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

18%16%+2.9
Not prescribing a pesticide blind.
Estimate

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

16%14%+2.2
Total100%22%

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

Skills and activities

  • Projects, subsidy files and paperwork
  • Field, sampling and pests
  • Farmer, co-op and administration
  • Water, soils and sustainability
  • Not prescribing a pesticide blind
  • ingeniero agronomo
  • agronomist

Sources for this job· O*NET 17-2021.00· ESCO/ISCO 2144

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. 393Nature guide22%
  2. 394Ice-cream maker22%
  3. 395Hydrologist22%
  4. 397Control engineer22%
  5. 398Corrosion engineer22%
  6. 399Firmware engineer22%