IS WORK OVER?

Automation index

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

A hall protocol comes earlier. Them not copying without humiliating the one who shakes do not.

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

Task comparison

Exam invigilator

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
Hall, the protocol and the clock.
Estimate

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

16%40%+6.4
Identity, the ID and the one who is not.
Estimate

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

18%14%+2.5
Copying, the phone and removing it without a circus.
Estimate

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

16%28%+4.5
Incident, the minute and not making it up.
Estimate

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

16%22%+3.5
The one who shakes, extra time and not humiliating.
Estimate

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

18%18%+3.2
That they do not copy, and not humiliating.
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

  • exam protocols
  • ID
  • phones
  • incident minutes
  • extra time
  • exam hall
  • remove without a circus
  • not humiliate

Sources for this job· O*NET 25-1191.00· ESCO/ISCO 2359

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. 511Dyer22%
  2. 512Prison social worker22%
  3. 513Car salesperson22%
  4. 515Virologist22%
  5. 516Medical sales rep22%
  6. 517Nursery grower22%