IS WORK OVER?

Automation index

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

A pack and a budget come earlier. Saying the margin is not that does not.

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

Task comparison

Financial controller

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
Reporting, budgets and variances.
Estimate

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

20%48%+9.6
Close, provision and check against the books.
Estimate

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

16%32%+5.1
Management, plants and P&L owners.
Estimate

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

16%22%+3.5
Systems, masters and data quality.
Estimate

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

16%18%+2.9
Audit, controls and documentation.
Estimate

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

16%16%+2.6
Not dressing an EBIT.
Estimate

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

16%14%+2.2
Total100%26%

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

Skills and activities

  • Reporting, budgets and variances
  • Management, plants and P&L owners
  • Systems, masters and data quality
  • Audit, controls and documentation
  • Not dressing an EBIT
  • controller
  • control de gestion
  • financial controller

Sources for this job· O*NET 13-2011.00· ESCO/ISCO 2411

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. 239Librarian26%
  2. 240Fundraiser26%
  3. 241Ship agent26%
  4. 243Drafter26%
  5. 244Web developer26%
  6. 245Game designer26%