Well-specified coding, conversion and routine maintenance can be assisted. Programmers still need to understand existing behavior and verify changes against the environment where the program actually runs.
BLS distinguishes programmers from software developers. A decline in one occupation's projection does not establish that all coding work disappears or that AI is the sole cause of the projection.
Compare the duties below with a normal week in your own role. Time
spent, responsibility, employer tools and access to reliable data can
change the picture substantially. Use the personal task audit to
identify those differences.
Task-by-task exposure
We selected 8 of 13 O*NET core
tasks by importance. Importance is an O*NET rating on a 1–5 scale; it
is not the percentage of time spent. The category and explanation are
our interpretation, not an O*NET assessment of AI.
0 routine automation 7 ai-assisted 1 human-led
Reading uncertainty: changing one task by one
category step would put this index at approximately 38–50/100. This is a
sensitivity example, not a statistical confidence interval. Small
score differences are not a sound reason to change careers.
Selected core tasks and our interpretation
Task and source detail
Assessment and reason
Write, analyze, review, and rewrite programs, using workflow chart and diagram, and applying knowledge of computer capabilities, subject matter, and symbolic logic.
O*NET task 1273 · Importance 4.42/5
Task source: 08/2018 · Rating: 08/2018
AI-assisted
A generated implementation can follow a clear specification. The programmer must still check behavior, edge cases and the assumptions hidden in the specification.
Correct errors by making appropriate changes and rechecking the program to ensure that the desired results are produced.
O*NET task 1267 · Importance 4.38/5
Task source: 08/2018 · Rating: 08/2018
AI-assisted
Patch suggestions can help localize an error. Reproducing the problem and checking for regressions remain necessary to establish that the repair works.
Perform or direct revision, repair, or expansion of existing programs to increase operating efficiency or adapt to new requirements.
O*NET task 1272 · Importance 4.37/5
Task source: 08/2018 · Rating: 08/2018
AI-assisted
Refactoring and expansion can be assisted. Existing integrations and undocumented expectations make human review important even when generated changes appear locally correct.
Write, update, and maintain computer programs or software packages to handle specific jobs such as tracking inventory, storing or retrieving data, or controlling other equipment.
O*NET task 1270 · Importance 4.15/5
Task source: 08/2018 · Rating: 08/2018
AI-assisted
Routine program structures can be generated. The full duty includes maintenance and suitability for the specific business process or controlled equipment.
Consult with managerial, engineering, and technical personnel to clarify program intent, identify problems, and suggest changes.
O*NET task 1271 · Importance 4.04/5
Task source: 08/2018 · Rating: 08/2018
Human-led
Clarifying intent requires agreement between people with different priorities. Software can summarize a discussion but cannot decide the authorized change.
Conduct trial runs of programs and software applications to be sure they will produce the desired information and that the instructions are correct.
O*NET task 1268 · Importance 3.96/5
Task source: 08/2018 · Rating: 08/2018
AI-assisted
Test execution is repeatable, while useful test design and interpretation need judgment. Passing generated tests is weak evidence if those tests repeat the same mistaken assumptions.
Prepare detailed workflow charts and diagrams that describe input, output, and logical operation, and convert them into a series of instructions coded in a computer language.
O*NET task 1276 · Importance 3.58/5
Task source: 08/2018 · Rating: 08/2018
AI-assisted
Workflow diagrams and code drafts can be assisted. The programmer must verify inputs, branch conditions and exceptions against the process being implemented.
Compile and write documentation of program development and subsequent revisions, inserting comments in the coded instructions so others can understand the program.
O*NET task 1269 · Importance 3.56/5
Task source: 08/2018 · Rating: 08/2018
AI-assisted
Comment and documentation drafts can reflect supplied code. They require checks for outdated behavior, omitted limitations and unsupported explanations of intent.
Routine automation includes conventional configured software; it does
not imply autonomous AI or adoption by every employer. Human-led
allows supporting tools. Vendor links document a capability, not a
validated rating of this complete task. Older task dates are shown
even though the database release is August 2026.
Task wording and importance: O*NET occupation 15-1251.00,
O*NET 31.0 Database
, U.S. Department of Labor, Employment and Training Administration, CC BY 4.0.
Selected and adapted by Career Risk Score; USDOL/ETA has not approved,
endorsed or tested these changes.
What assistance looks like in practice
Hypothetical workflow to illustrate the boundary; not a reported case
study.
A legacy application needs a data-format change. An assistant suggests an implementation and updated tests. The programmer traces where the format is produced and consumed before accepting a change that passes a narrow test.
What must be checked
Check compatibility with existing records, downstream callers and error handling. Preserve a reproducible test case for the original issue and verify the release process.
Practical skills to strengthen
Build skill in debugging and maintaining an unfamiliar codebase.
Document the operational context behind a small change.
Add requirements and system-design practice to implementation skills.
Changes worth watching
Watch whether openings combine coding with testing, design or support responsibilities.
Track the share of work involving legacy integration and exception handling.
There is no supported date when this occupation becomes “safe” or
disappears. Revisit these observations as your tasks and tools change.
Tools behind these capability examples
These are relevant documented capabilities, not endorsements,
adoption statistics or hands-on product reviews. Features depend on
the product, plan and employer configuration. References checked
September 2026.
BLS reports median annual pay of $100,390
in 2025, with 4,400 projected
openings per year on average during 2025–35. Openings include
replacement needs as well as growth; they are not a count of currently
advertised vacancies.
The projected employment change is -7.3%
over ten years. A declining employment total can coexist with replacement openings. It does not by itself explain the cause of decline.
Typical entry education
Bachelor's degree
Related work experience
None
Typical on-the-job training
None
Software development can broaden the scope of responsibility, but a new title alone does not provide design or product experience. Support work adds direct user investigation and troubleshooting.
BLS categories describe typical entry, not a complete qualification
checklist. “None” does not mean no learning is needed. National
medians are not starting salaries; location, sector, experience, hours
and benefits matter. Wage data exclude self-employed earnings. Consult
local job descriptions and relevant credential authorities before
paying for training.
These links identify transferable work and a concrete gap to explore.
They are not guaranteed pathways, “AI-proof” jobs or recommendations
based on a small score difference.
Take a small feature from requirements through design, tests and release.
BLS typical entry: Bachelor's degree; related experience: None.
9 shared skills among each role's top
12
Programming, Active Listening, Critical Thinking, Complex Problem Solving, Reading Comprehension, Systems Analysis, Writing, Judgment and Decision Making, Active Learning.
These broad O*NET skills are selected by importance, with
ties broken by skill ID. Overlap does not measure
proficiency or hiring readiness.
Use your own plausible pay figures to explore a move. Both pay fields start
at this occupation's national median so the calculator does not imply a
salary increase. A destination median describes existing workers, not your
likely starting offer.
A fixed-pay illustration in nominal dollars. Unpaid months occur at the
start of preparation; costs are charged at the start. Transition must fit
within the comparison period. Excludes taxes, benefits, raises, inflation,
investment returns and the chance of getting a job. A negative result is
possible. No inputs are saved or sent by this calculator.
Calculation and a worked example
Stay = current pay × years. Move = preparation pay × (preparation years −
unpaid months ÷ 12) + new pay × (years − preparation years) − one-time
cost.
For $60,000 current pay, $70,000 new pay, $50,000 preparation pay, two
years preparing, three unpaid months, $8,000 costs and a ten-year
comparison: stay = $600,000; move = $639,500. The $39,500 difference is a
scenario result, not a forecast. Break-even checks cumulative totals each
month under these same assumptions.
Check the evidence and limits
The index weights these sampled tasks equally. It does not measure
time, adoption, cost savings, unemployment or individual ability. The
examples and transition exercises are editorial inferences. Product
documentation supports the narrower capability described, not the
claim that a whole job can be replaced.
