IS WORK OVER?

Automation index

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

A borehole and a 3D model come earlier. Calling whether you can found there do not.

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

Task comparison

Geological 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
Boreholes, lab and the geotech profile.
Estimate

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

16%44%+7
Field, outcrop and what the map misses.
Estimate

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

18%16%+2.9
Foundations, slopes and the risk report.
Estimate

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

16%36%+5.8
Tunnel, water and the support.
Estimate

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

16%28%+4.5
The works that move, and stop or go.
Estimate

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

18%14%+2.5
Call the ground, and sign the report.
Estimate

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

16%12%+1.9
Total100%25%

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

Skills and activities

  • boreholes
  • geotech profile
  • foundations
  • slopes
  • tunnel support
  • outcrops
  • geological risk
  • ground reports

Sources for this job· O*NET 17-2151.00· ESCO/ISCO 2146

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. 281Telecom engineer25%
  2. 282Electrical engineer25%
  3. 283Electronics engineer25%
  4. 285Mechanical engineer25%
  5. 286Naval architect25%
  6. 287Chemical engineer25%