IS WORK OVER?

Automation index

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

An OEM code comes earlier. Giving the part that fits, not the lookalike, do not.

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

Task comparison

Parts clerk

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
Catalogue, equivalents and the code.
Estimate

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

18%52%+9.4
Counter, the waiting shop and the doubt.
Estimate

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

16%22%+3.5
Stock, urgent orders and the one that is late.
Estimate

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

16%36%+5.8
Returns, warranties and the wrong part.
Estimate

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

16%28%+4.5
The mechanic, the blurry photo and not selling blind.
Estimate

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

18%14%+2.5
The one that fits, not the lookalike.
Estimate

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

16%12%+1.9
Total100%28%

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

Skills and activities

  • parts catalogue
  • OEM equivalents
  • shop counter
  • urgent orders
  • returns
  • part warranties
  • parts stock
  • part codes

Sources for this job· O*NET 41-2022.00· ESCO/ISCO 4321

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. 111Demand planner28%
  2. 112Route planner28%
  3. 113Psychologist28%
  4. 115Technical writer28%
  5. 116Land registrar28%
  6. 117Delivery driver28%