IS WORK OVER?

Automation index

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

A report and a sheet come earlier. Digging and not breaking the context do not.

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

Task comparison

Archaeologist

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
Sheets, drawing and the intervention report.
Estimate

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

16%40%+6.4
Excavate, sieve and record units.
Estimate

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

20%12%+2.4
Authorities, developer and site deadlines.
Estimate

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

16%22%+3.5
Lab, dating and publication.
Estimate

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

16%28%+4.5
Store, conservation and outreach.
Estimate

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

16%16%+2.6
Not losing a context by going too fast.
Estimate

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

16%14%+2.2
Total100%22%

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

Skills and activities

  • Excavate, sieve and record units
  • Authorities, developer and site deadlines
  • Lab, dating and publication
  • Store, conservation and outreach
  • Not losing a context by going too fast
  • arqueologo
  • archaeologist

Sources for this job· O*NET 19-3091.00· ESCO/ISCO 2632

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. 364Insulation installer22%
  2. 365Adult literacy tutor22%
  3. 366Pesticide applicator22%
  4. 368Building surveyor22%
  5. 369Foley artist22%
  6. 370Language assistant22%