IS WORK OVER?

Automation index

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

An earmould and a gain curve come earlier. Getting the patient to hear and live with it do not.

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

Task comparison

Hearing aid 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
Audiometry, thresholds and the fitting.
Estimate

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

16%40%+6.4
Take the mould, trial and the one who hates the whistle.
Estimate

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

18%18%+3.2
Program, verify and retune the aid.
Estimate

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

16%32%+5.1
Repair, batteries and aftercare.
Estimate

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

16%28%+4.5
Explain, family and the stigma of the device.
Estimate

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

18%14%+2.5
That they actually hear, and not taking the aid back.
Estimate

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

16%12%+1.9
Total100%24%

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

Skills and activities

  • fit hearing aids
  • take earmoulds
  • audiometry
  • program aids
  • verify gain
  • repair aids
  • hearing thresholds
  • aftercare

Sources for this job· O*NET 29-2092.00· ESCO/ISCO 3214

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. 324University professor24%
  2. 325Judicial secretary24%
  3. 326Property valuer24%
  4. 328Job insertion technician24%
  5. 329Radiation therapist24%
  6. 330Surveyor24%