IS WORK OVER?

Automation index

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

A bible and a treatment come earlier. Knowing which scene cuts, which joke lives, and what the showrunner wants do not.

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

Task comparison

Screenwriter

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
Bibles, treatments and sequence breakdowns.
Estimate

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

20%48%+9.6
Dialogue, variants and fast rewrites.
Estimate

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

20%40%+8
Writers’ room and showrunner notes.
Estimate

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

16%18%+2.9
Fit to budget, locations and cast.
Estimate

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

16%12%+1.9
Pitch, sale and studio relationship.
Estimate

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

14%15%+2.1
Decide tone, cut and what is not written.
Estimate

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

14%12%+1.7
Total100%26%

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

Skills and activities

  • Bibles, treatments and sequence breakdowns
  • Dialogue, variants and fast rewrites
  • Writers’ room and showrunner notes
  • Fit to budget, locations and cast
  • Pitch, sale and studio relationship
  • Decide tone, cut and what is not written
  • guionista
  • screenwriter
  • script

Sources for this job· O*NET 27-3043.00· ESCO/ISCO 2641

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. 246Set designer26%
  2. 247Statistician26%
  3. 248Cultural manager26%
  4. 250Structural engineer26%
  5. 251Process engineer26%
  6. 252Midwife26%