IS WORK OVER?

Automation index

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

A deposit model comes earlier. Going down and not leaving an unsafe face does not.

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

Task comparison

Mining 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 deposit, blast and rates.
Estimate

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

16%40%+6.4
Drawings, permits and mining plans.
Estimate

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

16%28%+4.5
Face, safety and ventilation.
Estimate

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

18%14%+2.5
Plant, contractors and output.
Estimate

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

16%22%+3.5
Restoration, waste and regulation.
Estimate

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

18%16%+2.9
Not leaving a miner below.
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

  • Model deposit, blast and rates
  • Drawings, permits and mining plans
  • Face, safety and ventilation
  • Plant, contractors and output
  • Restoration, waste and regulation
  • Not leaving a miner below
  • ingeniero de minas
  • mining engineer

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. 410Instrumentation engineer22%
  2. 411Facilities engineer22%
  3. 412Mechatronics engineer22%
  4. 414Bridge engineer22%
  5. 415Commissioning engineer22%
  6. 416Gas network engineer22%