IS WORK OVER?

Automation index

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

A dye recipe comes earlier. Getting the colour the same over ten thousand metres do not.

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

Task comparison

Textile engineer

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
Recipes, weaves and piece QC.
Estimate

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

18%48%+8.6
Shop, looms and the warp break.
Estimate

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

16%22%+3.5
Supplier, cotton and the sustainability card.
Estimate

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

16%36%+5.8
Finishes, shrinkage and fastness tests.
Estimate

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

16%28%+4.5
The brand, the deadline and the colour that misses.
Estimate

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

18%14%+2.5
Ten thousand metres the same, and not hiding the bad yardage.
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

  • dye recipes
  • weaves
  • looms
  • colour fastness
  • shrinkage
  • piece card
  • warp
  • textile finishes

Sources for this job· O*NET 17-2199.00· ESCO/ISCO 2141

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. 188Security engineer27%
  2. 189Traffic engineer27%
  3. 190Hydraulic engineer27%
  4. 192Immunologist27%
  5. 193Schools inspector27%
  6. 194Data protection inspector27%