IS WORK OVER?

Automation index

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

A model comes earlier. It taking the lorry without signing off a crack do not.

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

Task comparison

Bridge 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
Model, loads and the span.
Estimate

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

16%40%+6.4
Works, the prestress and the one who did not tension.
Estimate

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

18%14%+2.5
Inspection, the crack and not looking away.
Estimate

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

16%28%+4.5
Traffic, the closure and not leaving the village hanging.
Estimate

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

16%22%+3.5
The contractor, 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 takes the lorry, and not signing the crack.
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

  • spans
  • prestress
  • cracks
  • bridge inspection
  • loads
  • traffic closures
  • structural models
  • tensioning

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. 411Facilities engineer22%
  2. 412Mechatronics engineer22%
  3. 413Mining engineer22%
  4. 415Commissioning engineer22%
  5. 416Gas network engineer22%
  6. 417District heating engineer22%