Automation index

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

A controller comes earlier. Watering the block without drowning the field do not.

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

Task comparison

IS WORK OVER?

22%

AI can already do 22% of this job.

#500 / 773

Irrigation technician

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
Flow, controller and the sector. Estimate No public source provides a precise figure. This is our estimate.	16%	40%	+6.4
Dripper, valve and the leak you cannot see. Estimate No public source provides a precise figure. This is our estimate.	18%	14%	+2.5
Filters, fertigation and the blockage. Estimate No public source provides a precise figure. This is our estimate.	16%	28%	+4.5
Field, pressure and the one that does not reach the end. Estimate No public source provides a precise figure. This is our estimate.	16%	22%	+3.5
The drought, the water turn and not fighting the flow. Estimate No public source provides a precise figure. This is our estimate.	18%	18%	+3.2
The block watered, and not drowning it. Estimate No public source provides a precise figure. This is our estimate.	16%	12%	+1.9
Total	100%		22%

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

IS WORK OVER?

27%

#153 / 773

Backend developer

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. 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
Total	100%		27%

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