IS WORK OVER?

Automation index

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

A jam log comes earlier. Leaving the office printing without inking the floor do not.

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

Task comparison

Printer technician

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
Log, count and the maintenance kit.
Estimate

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

16%40%+6.4
Jam, fuser and toner on the floor.
Estimate

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

18%14%+2.5
Network, queues and the wrong driver.
Estimate

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

16%32%+5.1
Contract, visits and the machine that is done.
Estimate

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

16%22%+3.5
The office at peak and not stopping invoicing.
Estimate

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

18%18%+3.2
That it prints, and not swapping the fuser blind.
Estimate

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

16%12%+1.9
Total100%23%

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

Skills and activities

  • jams
  • fuser
  • maintenance kits
  • print queues
  • toner
  • service contracts
  • drivers
  • copy counts

Sources for this job· O*NET 49-2011.00· ESCO/ISCO 7421

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. 357Radiation oncologist23%
  2. 358Rheumatologist23%
  3. 359Victim support worker23%
  4. 361Crime scene technician23%
  5. 362CCTV technician23%
  6. 363Aquaculturist22%