IS WORK OVER?

Automation index

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

An assortment comes earlier. The category winning without fighting own-label do not.

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

Task comparison

Category manager

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
Assortment, prices and the shelf.
Estimate

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

18%48%+8.6
Supplier, the negotiation and the one that will not list.
Estimate

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

16%40%+6.4
Promo, the calendar and the one that clashes.
Estimate

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

16%22%+3.5
Data, margin and not killing the category.
Estimate

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

16%28%+4.5
Own-label, the clash and not hiding it.
Estimate

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

18%14%+2.5
That the category wins.
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

  • assortment
  • supplier negotiation
  • category margin
  • promos
  • own-label
  • the shelf
  • calendar
  • listings

Sources for this job· O*NET 11-2022.00· ESCO/ISCO 1221

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. 140Banker27%
  2. 141Bid manager27%
  3. 142Carpenter27%
  4. 144Research scientist27%
  5. 145Climatologist27%
  6. 146Colourist27%