IS WORK OVER?

Automation index

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

An image comes earlier. Flashing without bricking the batch without skipping rollback do not.

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

Task comparison

Firmware engineer

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
Image, the signature and the slot.
Estimate

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

16%40%+6.4
Flash, the batch and the one that bricks.
Estimate

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

18%14%+2.5
Rollback, the test and not skipping it.
Estimate

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

16%28%+4.5
Boot, the brick and the one that will not start.
Estimate

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

16%22%+3.5
The factory, the cadence and not jumping to a yes.
Estimate

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

18%18%+3.2
Flash without bricking, and not skipping rollback.
Estimate

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

16%12%+1.9
Total100%22%

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

Skills and activities

  • firmware images
  • digital signature
  • slots
  • flash
  • rollback
  • boot
  • factory batches
  • not brick

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. 396Agronomist22%
  2. 397Control engineer22%
  3. 398Corrosion engineer22%
  4. 400Instrumentation engineer22%
  5. 401Facilities engineer22%
  6. 402Mechatronics engineer22%