IS WORK OVER?

Automation index

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

A digital herbarium comes earlier. Identifying in the field without killing the population do not.

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

Task comparison

Botanist

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
Herbarium, keys and the specimen.
Estimate

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

16%40%+6.4
Field, the population and not collecting extra.
Estimate

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

18%14%+2.5
Survey, the habitat and the one that is lost.
Estimate

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

16%28%+4.5
Report, the works and the one who will not hear.
Estimate

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

16%22%+3.5
The glasshouse, the culture and not mixing labels.
Estimate

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

18%18%+3.2
Identify, and not killing the population.
Estimate

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

16%12%+1.9
Total100%22%

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

Skills and activities

  • herbarium
  • keys
  • populations
  • botanical surveys
  • habitats
  • collect
  • labels
  • the field

Sources for this job· O*NET 19-1022.00· ESCO/ISCO 2131

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. 370Language assistant22%
  2. 371Poultry farmer22%
  3. 372School librarian22%
  4. 374Chocolatier22%
  5. 375Forensic scientist22%
  6. 376Hotel concierge22%