IS WORK OVER?

Automation index

How much of a EV charger installer’s job can AI already do?

A single-line diagram comes earlier. A legal charger that actually charges at night do not.

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

Task comparison

EV charger installer

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
Single-line, power and the certificate.
Estimate

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

16%40%+6.4
Conduit, cable and the board that will not take it.
Estimate

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

18%14%+2.5
Configure, app and load balancing.
Estimate

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

16%28%+4.5
Residents, the bay and the neighbour who objects.
Estimate

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

16%22%+3.5
The electrical inspection and the inspector.
Estimate

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

18%18%+3.2
That it charges at night, and not tripping the main.
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

  • EV chargers
  • single-line
  • load balancing
  • electrical certificate
  • wire the bay
  • charger app
  • charge board
  • residents

Sources for this job· O*NET 47-2111.00· ESCO/ISCO 7411

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. 424Forestry engineer22%
  2. 425Geotechnical engineer22%
  3. 426Welding inspector22%
  4. 428Social integrator22%
  5. 429Heritage interpreter22%
  6. 430Court interpreter22%