IS WORK OVER?

Automation index

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

A prototype comes earlier. It actually playing without leaving a frame at 8 do not.

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

Task comparison

Game 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
Prototype, the loop and the input.
Estimate

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

18%48%+8.6
Physics, the bug and the one that teleports.
Estimate

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

16%40%+6.4
Build, the platform and the one that will not ship.
Estimate

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

16%22%+3.5
Frame, 30 and not leaving it at 8.
Estimate

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

16%28%+4.5
The designer, the fun and not cutting what it feels.
Estimate

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

18%14%+2.5
That it plays, and not leaving the frame at 8.
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

  • game prototypes
  • game loop
  • input
  • builds
  • frames
  • physics bugs
  • platforms
  • write game code

Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2514

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. 150Franchise consultant27%
  2. 151Backend developer27%
  3. 152Blockchain developer27%
  4. 154Front-end developer27%
  5. 155Comic artist27%
  6. 156Headteacher27%