Menu
Computer Programmer
Three components - Automation Resistance, Structural Moat, and Demand - add up to 28.
Direct AI exposure is severe for routine coding, tests, and documentation, while the small remaining protection comes from legacy systems, debugging, domain context, and knowing why an old codebase behaves the way it does in production.
Observed AI exposure is about 74.5%, and modeled median job-loss pressure is about 55.2%. Those signals fit the work: routine code, tests, scripts, translations, documentation, and bug fixes can be drafted by AI. Legacy-system knowledge and domain debugging keep the value above the floor, but not by much.
AI is useful for explaining code, drafting functions, writing tests, converting syntax, and summarizing errors. The gain is real, but much of it flows to employers who need fewer routine code hours. Because demand is weak, leverage does not translate into strong worker protection.
The barrier is codebase and domain depth, not a license or physical setting, so protection is modest outside hard-to-replace legacy environments where mistakes are expensive and institutional memory still matters to the employer over time.
Programming is desk and screen work. The federal occupational profile and task descriptions point to indoor computer-centered work, so there is no physical setting that slows substitution. Any protection has to come from judgment, domain context, or codebase depth instead.
There is no broad occupational license for computer programming. Degrees, certificates, vendor familiarity, and portfolios can help a hiring case, but they are employer signals rather than legal gates. That keeps the formal protection low even when a specific employer needs a trusted maintainer.
Physical robotics is not the substitute path for this occupation. The pressure comes from software that writes, explains, tests, and modifies code. Keeping the robotics lane separate prevents software automation from being counted as if it were a physical deployment problem.
The federal profile and occupational-preparation data place the occupation in a higher-preparation zone, usually tied to a bachelor-level path or substantial portfolio proof. That preparation matters, but it does not protect the routine code-to-spec layer from AI the way a required license would.
The labor-market signal is weak because the dedicated occupation is smaller, declining, and mostly supported by replacement openings rather than expansion, even though legacy systems and business-specific code still create some paid maintenance seats for new entrants.
The dedicated federal row is small for Tech: about 121,200 jobs and about 5,500 annual openings. Employment is declining, and the openings are mainly replacement flow. That gives some labor-market scale but a weak base for a new entrant choosing a multi-year path.
The source match is clean, but the demand source itself is not favorable. Public data and the occupational profile point to replacement hiring, task automation, and a shift of higher-skill work toward software developers. Legacy code maintenance keeps the source quality above churn-only.
Resilience is limited because the active shock is inside the task core: routine programming can be accelerated or consolidated. The work holds better when it involves old systems, business-specific rules, and debugging where mistakes are expensive, but those are narrower seats.
The case weakens if employers use AI tools and senior developers to handle routine code, tests, documentation, and bug fixes with fewer dedicated programmers. The exposed jobs would be ticket execution with little design, domain, or production ownership inside software teams.
The case strengthens if organizations keep needing specialists who understand older languages, mainframes, custom business rules, and risky integrations. The threshold is not old code alone; it is paid demand for people who can change old systems safely over several years.
A mixed outcome needs review if the title keeps shrinking but workers successfully shift into software development, systems analysis, security, or data engineering. The original job would still be weak, but the skill path would be less fragile during retraining.