IS WORK OVER?

Automation index

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

A track study comes earlier. The train not derailing without signing a half-done set of points do not.

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

Task comparison

Railway 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
Track, geometry and the study.
Estimate

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

16%40%+6.4
Points, the blade and the one that will not close.
Estimate

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

18%14%+2.5
OLE, the height and the gauge.
Estimate

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

16%28%+4.5
Works, the possession and not leaving the wire wrong.
Estimate

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

16%22%+3.5
The operator, the rush and not jumping to a yes.
Estimate

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

18%18%+3.2
That it does not derail, and not signing half-done points.
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

  • track geometry
  • points
  • OLE
  • gauge
  • possessions
  • blades
  • railway studies
  • not jump to a yes

Sources for this job· O*NET 17-2051.00· ESCO/ISCO 2142

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. 420Tunnel engineer22%
  2. 421Power engineer22%
  3. 422Geomatics engineer22%
  4. 424Forestry engineer22%
  5. 425Geotechnical engineer22%
  6. 426Welding inspector22%