IS WORK OVER?

Automation index

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

A diagnosis and a spare come earlier. Opening the movement so it keeps time again do not.

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

Task comparison

Watchmaker

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
Diagnose, quote and explain to the client.
Estimate

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

16%32%+5.1
Open, strip, clean and oil the movement.
Estimate

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

22%8%+1.8
Spares, rate adjustment and calibration.
Estimate

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

16%28%+4.5
Cases, straps, water resistance and polish.
Estimate

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

16%22%+3.5
The counter, commissions and pieces that do not come back.
Estimate

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

16%36%+5.8
Times, real spares and a watch that keeps time.
Estimate

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

14%12%+1.7
Total100%22%

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

Skills and activities

  • repair watches
  • open movements
  • oil calibres
  • adjust rate
  • change straps
  • water-resistance test
  • diagnose watches
  • polish cases

Sources for this job· O*NET 51-9071.00· ESCO/ISCO 7311

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. 478Cheesemaker22%
  2. 479Office receptionist22%
  3. 480Stage manager22%
  4. 482Book restorer22%
  5. 483Ticket inspector22%
  6. 484Cider maker22%