IS WORK OVER?

Automation index

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

A cash forecast comes earlier. Having liquidity on Friday without lying to the bank do not.

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

Task comparison

Treasurer

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
Cash, forecast and the maturities.
Estimate

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

18%48%+8.6
Banks, facilities and the one that does not land.
Estimate

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

16%40%+6.4
Payments, the supplier and the one that waits.
Estimate

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

16%22%+3.5
Board, the report and not dressing cash.
Estimate

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

16%28%+4.5
The crunch, confirming and not hiding the hole.
Estimate

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

18%14%+2.5
Liquidity on Friday, and not lying to the bank.
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

  • cash forecast
  • maturities
  • facilities
  • supplier payments
  • confirming
  • liquidity
  • banks
  • board report

Sources for this job· O*NET 11-3031.00· ESCO/ISCO 1211

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. 231Dairy technician27%
  2. 232Switchboard operator27%
  3. 233Telemarketer27%
  4. 235Trader27%
  5. 236Transcriber27%
  6. 237University tutor27%