Skip to content
man bot

ISCO 2512 · O*NET 15-1252.00 · codes unverified

Software developer

The most assisted job on the site, and one of the more exposed. Both of those are true at once, which is the entire reason the two numbers are shown separately.

Mentioned in chapter two, because it is the role readers most expect to be safe. Read the essay →

44
Resilience Shifting

A large share of the work is moving. The remaining core is narrower and more senior than it used to be.

0 rebuilding 100 anchored

Scale, labels and thresholds are provisional. This is open question Q-02.

12 of 20 in the launch set

How the score is made

Four declared inputs, never collapsed into one number. Assistance is kept apart from outright automation, because a tool that makes you faster and a tool that replaces you are not the same event. Physical work counts as shelter only to the extent robotics cannot reach it.

The full method is written out, including what it cannot tell you.

Note on this occupation Placeholder values. Augmentation this high alongside automation this moderate is exactly the pattern the score exists to show.

Assisted
88

Higher is generally good news. It means more of the work gets faster without the work going away.

Done outright
58

This is the number most people mean when they say exposure. It is kept separate from assistance on purpose.

Physical
4

Protective only for as long as robotics cannot reach it. Read this one next to the robotics number, never alone.

Robotics reach
40

Low reach turns physical work into shelter. High reach turns it into the main exposure.

placeholder Working Paper 140, Generative AI and Jobs 2025 index O*NET 31.0 Anthropic Economic Index Pin one release data 0.1-placeholder

What changes

Tasks moving to machines, in whole or in part.

  • Writing routine implementation code from a clear specification.
  • Test scaffolding, boilerplate and migrations.
  • Reading unfamiliar code to work out what it does.

What stays human

Tasks that need a person, and why.

  • Choosing what to build, and what to refuse to build.
  • Owning a system at three in the morning when it is failing.
  • Judging which shortcut is survivable.

What's new

Work that did not exist in this job ten years ago.

  • Reviewing far more generated code than any team used to write.
  • Designing systems that assume a model is in the loop.
  • Security and provenance work created by that assumption.

These three lists are editorial commentary, written against task-level data but not generated from it (OCC-05). Treat them as the author's reading, not as output.

Compare with another job

Pick one. You get a card with both scores, both sets of components, and a link worth sending to someone.

Sources used on this page