IS WORK OVER?

Automation index

How much of a Back-office clerk’s job can AI already do?

A match comes earlier. The trade settling without hanging do not.

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

Task comparison

Back-office clerk

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
Matching, settlement and the fail.
Estimate

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

18%48%+8.6
Custody, corporates and the one that does not square.
Estimate

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

16%40%+6.4
Reconcile, the nostro and the gap.
Estimate

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

16%22%+3.5
Regulatory, the report and the deadline.
Estimate

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

16%28%+4.5
The desk, the rush and not leaving the fail.
Estimate

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

18%14%+2.5
That it settles, and not hanging.
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

  • matching
  • settlement
  • custody
  • reconcile nostro
  • fails
  • corporate actions
  • regulatory reports
  • hung trades

Sources for this job· O*NET 43-4011.00· ESCO/ISCO 4312

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. 216Seismologist27%
  2. 217Storyboard artist27%
  3. 218Municipal officer27%
  4. 220Cadastre officer27%
  5. 221HVAC technician27%
  6. 222Competition officer27%