Software Developers

Analysis reviewed 2026-08, using O*NET 30.3 and BLS projections for 2024–2034. The score, skills and ranking panels use the latest dataset.

A 35 is not a reprieve. It is the score of a job whose middle is being hollowed out while both ends grow.

Employment is projected up 15.8% to 2034, so headcount is not the story here. What changes is that typing the code stops being the scarce part of the job.

What leaves the week first

Three numbers make the 35. Automation reads 31, repetition 56, freedom to set your own tasks 80. The work is not procedural. A great many of the keystrokes inside it are. That freedom is the only thing holding the score out of the high band: nobody hands a developer a script to follow, so nobody can hand a model one either.

What goes first is every operation whose specification is finished before the work starts.

1. Boilerplate and glue codeCRUD endpoints, DTO mappers, a client for an API whose spec already exists. Only the transcription is left.
2. First-draft unit testsThe happy path and the obvious edges are close to free now. The test that encodes a business rule nobody wrote down is not.
3. Mechanical refactorsRename across a repo, framework bumps, callback-to-async rewrites, porting between two ORMs.
4. Orientation in unfamiliar codeA thirty-minute first pass through a service you have never opened compresses to about five minutes of asking and verifying.

What is still yours

Programming scores 75 on importance in this role and only 46 on transferability. It is your lowest-carrying top skill, and it is now the most assisted one. What stayed high is critical thinking at 72 and 63, judgment at 66 and 62, complex problem solving at 60 and 62. That gap is the whole argument. The paid part of the job is moving from producing code to deciding what code should exist and whether the produced code is right.

The rewriting falls unevenly. Work defined as implementing a ticket is under real pressure, because a ticket is a specification and specifications are what models consume. Work defined as finding out why the system falls over under load is not.

• Deciding what to build and what to refuseRequirements arrive contradictory. Resolving that is a negotiation with people about tradeoffs.
• System design under real constraintsA latency budget, a schema you cannot change, a team that has to maintain it at 3am.
• Debugging productionThe failure sits between components and the logs are incomplete. Choosing what to instrument first is judgment.
• Owning correctnessSomeone is accountable when generated code ships a bug. Reviewing machine output has become a first-class skill.

Where the ranking actually leads

Your board is unusually tight at the top. What the credible entries share is not the word technology. All of them pay for systems analysis, judgment under incomplete information, and holding a large system in your head. Only the object changes.

One row deserves a warning label. Airline pilot appears at a 0.205 gap with a $232,140 median, because the reasoning and monitoring skills genuinely overlap. Flight hours and type ratings do not appear in a skill vector.

• Information Security AnalystsReachable6 to 12 months

  $129,180 · +21% jobs · exposure 35

  Gap 0.079, the smallest on the board, with 28.5% projected growth and a $129,180 median. The overlap is systems thinking. The delta is monitoring discipline and threat modelling. Cheapest entry is doing security work inside your current team for two quarters before you change the title.

• Computer Hardware EngineersReachable12 to 18 months

  $161,740 · +9.1% jobs · exposure 40

  Gap 0.124 and a $161,740 median. Hardware engineering is the move most developers never consider, and the skill distance is smaller than the distance to management. It rewards the same debugging instinct one layer down.

• Computer and Information Systems ManagersA stretch12 to 24 months

  $175,140 · +15.8% jobs · exposure 39

  The largest pay step on the list at $175,140, and a 0.175 gap that understates the problem. What is missing is personnel and financial resource management. You acquire those by leading a team, not by studying.

• Airline Pilots, Copilots, and Flight EngineersNot a routenot a route

  $232,140 · +8.3% jobs · exposure 58

  Ranks on cognitive similarity and a very high median. Becoming a commercial pilot means hundreds of flight hours and a type rating, neither of which is a skill gap. Read it as a quirk of the scoring.