IS WORK OVER?

Automation index

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

A wafer recipe comes earlier. The batch coming out without eating the cleanroom do not.

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

Task comparison

Semiconductor 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
Recipe, tool and the batch.
Estimate

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

16%40%+6.4
Room, the suit and the one that contaminates.
Estimate

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

18%14%+2.5
Metrology, the defect and stopping.
Estimate

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

16%28%+4.5
Shift, the yield and not hiding it.
Estimate

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

16%22%+3.5
The engineer, the change and not touching blind.
Estimate

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

18%18%+3.2
The batch comes out, and the room intact.
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

  • wafers
  • cleanroom
  • yield
  • metrology
  • process recipes
  • contamination
  • chip batches
  • suits

Sources for this job· O*NET 51-9141.00· ESCO/ISCO 3114

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. 500Irrigation technician22%
  2. 501Environmental health officer22%
  3. 502Public health officer22%
  4. 504Telephony technician22%
  5. 505Electoral officer22%
  6. 506Orthotic and prosthetic technician22%