Page scaffolding and routine code changes are assistable. Delivering a useful website still requires checking behavior, accessibility, performance and integrations in the actual publishing or business context.
Template-based sites, complex applications and commerce integrations differ substantially. The occupation sample is broader than the act of producing HTML or generating a visual mockup.
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 23 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.
1 routine automation 6 ai-assisted 1 human-led
Reading uncertainty: changing one task by one
category step would put this index at approximately 44–56/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 supporting code for Web applications or Web sites.
O*NET task 14707 · Importance 4.58/5
Task source: 07/2017 · Rating: 07/2017
AI-assisted
Supporting code can be generated from clear requirements. Integration, accessibility, security and edge cases require verification in the actual site.
Design, build, or maintain Web sites, using authoring or scripting languages, content creation tools, management tools, and digital media.
O*NET task 14694 · Importance 4.42/5
Task source: 07/2017 · Rating: 07/2017
AI-assisted
Website drafts and changes can be assisted. Maintaining a working service includes content accuracy, user journeys and deployment behavior beyond code generation.
Back up files from Web sites to local directories for instant recovery in case of problems.
O*NET task 14698 · Importance 4.35/5
Task source: 07/2017 · Rating: 07/2017
Routine automation
Scheduled backups are established software automation. Retention, access and tested restoration determine whether those files are useful when recovery is needed.
Evaluate code to ensure that it is valid, is properly structured, meets industry standards, and is compatible with browsers, devices, or operating systems.
O*NET task 14700 · Importance 4.09/5
Task source: 07/2017 · Rating: 07/2017
AI-assisted
Automated checks can identify some invalid code and compatibility issues. They do not establish complete usability or correctness across all relevant user situations.
Perform Web site tests according to planned schedules, or after any Web site or product revision.
O*NET task 14710 · Importance 4.04/5
Task source: 07/2017 · Rating: 07/2017
AI-assisted
Routine test execution is automated readily. Choosing meaningful coverage and interpreting failures remain part of the full testing duty.
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-1254.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 builds a registration form. The developer checks validation, keyboard use, error recovery and the server-side behavior when data is missing or a request is repeated.
What must be checked
Test the complete flow on small screens and assistive technologies, inspect network requests and verify failure states. A convincing screenshot does not prove the interaction works.
Practical skills to strengthen
Show a site with measured accessibility and performance checks.
Practice debugging browser and server interactions.
Explain a trade-off between a dependency and a simpler implementation.
Changes worth watching
Watch whether simple page production becomes bundled into publishing tools.
Track demand for maintenance, integration and ownership of measurable user outcomes.
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 $92,650
in 2025, with 5,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 + 3.8%
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
Interface design adds research and interaction judgment. Broader software development adds system responsibilities beyond a browser interface.
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.
Build a small service behind an interface and verify its data and failure behavior.
BLS typical entry: Bachelor's degree; related experience: None.
10 shared skills among each role's top
12
Programming, Critical Thinking, Reading Comprehension, Complex Problem Solving, Operations Analysis, Active Listening, Active Learning, Judgment and Decision Making, Writing, Systems Analysis.
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.
