Code generation changes how software is produced, but a working snippet is only one part of delivering a reliable system. Requirements, interfaces, testing and operational responsibility are central to interpreting this occupation's exposure.
Product development, embedded systems and enterprise applications have different constraints. The sample describes development broadly and cannot distinguish a narrowly specified change from a project with uncertain requirements.
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 11 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 6 ai-assisted 2 human-led
Reading uncertainty: changing one task by one
category step would put this index at approximately 31–44/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
Analyze user needs and software requirements to determine feasibility of design within time and cost constraints.
O*NET task 21662 · Importance 4.08/5
Task source: 08/2025 · Rating: 08/2025
Human-led
Requirements analysis determines which problem is worth solving under real constraints. Code suggestions cannot decide priorities or reconcile inconsistent user expectations.
Develop or direct software system testing or validation procedures, programming, or documentation.
O*NET task 21669 · Importance 3.90/5
Task source: 08/2025 · Rating: 08/2025
AI-assisted
Tests and documentation can be drafted. A developer must establish meaningful expected behavior, check coverage and judge whether a passing test demonstrates the requirement.
Confer with systems analysts, engineers, programmers and others to design systems and to obtain information on project limitations and capabilities, performance requirements and interfaces.
O*NET task 21664 · Importance 3.75/5
Task source: 08/2025 · Rating: 08/2025
Human-led
System design discussions align teams on interfaces and constraints. Generated options can inform the discussion without establishing agreements between responsible owners.
Modify existing software to correct errors, adapt it to new hardware, or upgrade interfaces and improve performance.
O*NET task 21670 · Importance 3.74/5
Task source: 08/2025 · Rating: 08/2025
AI-assisted
A candidate patch can reduce implementation effort. Reproducing the failure, checking compatibility and assessing unintended behavior remain necessary before release.
Status reports can be drafted from supplied records. The author must verify what was actually completed and explain unresolved risks rather than repeat optimistic summaries.
Analyze information to determine, recommend, and plan installation of a new system or modification of an existing system.
O*NET task 21661 · Importance 3.61/5
Task source: 08/2025 · Rating: 08/2025
AI-assisted
Existing code and specifications can be analyzed with assistance. Installation decisions still require environment knowledge, migration planning and an accountable rollback decision.
Store, retrieve, and manipulate data for analysis of system capabilities and requirements.
O*NET task 21676 · Importance 3.59/5
Task source: 08/2025 · Rating: 08/2025
AI-assisted
Queries and analysis code can be generated. Data permissions, representative workloads and the meaning of a measured result require verification.
Design, develop and modify software systems, using scientific analysis and mathematical models to predict and measure outcomes and consequences of design.
O*NET task 21667 · Importance 3.56/5
Task source: 08/2025 · Rating: 08/2025
AI-assisted
Implementation and modeling can be assisted. Architecture, operational constraints and evidence that the system meets its purpose remain responsibilities across the development lifecycle.
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-1252.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.
An assistant implements an API endpoint from a specification. It also proposes tests. The developer checks whether the endpoint behaves correctly under invalid input, authorization boundaries, retries and failure of a dependency.
What must be checked
Review the specification independently of generated code, run meaningful tests and inspect integration behavior. Passing tests written from the same mistaken assumption does not validate the requirement.
Practical skills to strengthen
Show a deployed project with documented design trade-offs and failure handling.
Practice reviewing unfamiliar code and explaining security-sensitive decisions.
Learn to turn an ambiguous request into testable acceptance criteria.
Changes worth watching
Watch changes in expectations for the amount of code one developer maintains.
Track review and incident work alongside coding speed.
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 $135,980
in 2025, with 95,300 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 + 10.2%
over ten years. Employment growth can coexist with automation of particular tasks. It does not make every worker or location equally likely to benefit.
Typical entry education
Bachelor's degree
Related work experience
None
Typical on-the-job training
None
Systems analysis emphasizes requirements and organizational processes; security analysis adds threat and incident work. Neither move follows automatically from using a coding assistant.
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.
Document a business workflow and turn it into requirements with stakeholder acceptance criteria.
BLS typical entry: Bachelor's degree; related experience: None.
10 shared skills among each role's top
12
Programming, Critical Thinking, Judgment and Decision Making, Reading Comprehension, Active Learning, Systems Analysis, Active Listening, Complex Problem Solving, Systems Evaluation, Writing.
These broad O*NET skills are selected by importance, with
ties broken by skill ID. Overlap does not measure
proficiency or hiring readiness.
Investigate a controlled security scenario and explain the evidence, impact and remediation.
BLS typical entry: Bachelor's degree; related experience: Less than 5 years.
8 shared skills among each role's top
12
Critical Thinking, Judgment and Decision Making, Reading Comprehension, Active Learning, Systems Analysis, Active Listening, Complex Problem Solving, Writing.
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.
