US dataswitch to UK
Computer Programmers
writing, analyzing, reviewing and rewrite programs, conducting trial runs of programs and software applications to be sure they will produce the desired information and that the instructions and preparing detailed workflow charts and diagrams that describe input. If that's your week, this page is about your job.
The honest answer
Most tasks in this job are the kind AI has learned to do: writing, analyzing, reviewing and rewrite programs. The tasks, though, are not you.
It would be a lie to soften that; consulting with managerial, engineering and technical personnel to clarify program intent, identify problems and suggest changes is what this work rebuilds around. The plan below starts there.
Your week, as this page understands it
Create, modify, and test the code and scripts that allow computer applications to run. Work from specifications drawn up by software and web developers or other individuals. May develop and write computer programs to store, locate, and retrieve specific documents, data, and information. The job title says “computer programmers”. The real job is the part underneath: consulting with managerial, engineering and technical personnel to clarify program intent, identify problems and suggest changes. That is the thing someone has to be right about.
The exposed part of this job is specific, and we won’t pretend it is coming back. But computer programmers is not one task. It is 17 scored ones, and they are nowhere near equally exposed. The most durable of them, on this evidence, is consulting with managerial, engineering and technical personnel to clarify program intent, identify problems and suggest changes, and the ledger below shows exactly why.
Where the work sits, by task weight
- shifting to AI
- 66%
- changing shape
- 14%
- staying human
- 20%
These bars are tasks changing hands, not people being counted out. The ledger below shows which.
Whole-job exposure score 66 out of 100 (61–71 allowing for uncertainty): high exposure, across 17 scored tasks. The number is the support for the sentence above it, not a headline about anyone’s future.
How we know this
What is measured: Every published task statement for computer programmers is rated on five dimensions: can a model produce the output, does the work need a body in a room, does it need a legally accountable person, does it depend on a person being trusted in the moment, and how much data exists. A published formula turns those five ratings into the score; the model never writes the number.
How the bar is built: Each task’s share of the bar is its published importance weight, so a task you do all day counts for more than one you do twice a year.
Release: 2026-q4.1, scores computed 2026-08-05. Read the full method.
Your job, task by task
These are the official task statements for this occupation, in plain English, sorted by what the evidence says is happening to each one. The official wording sits under every line so you can check the rewrite against it.
- 2 of this occupation's scored task statements carry a score that was measured under a different occupation's context, because the statement is shared between jobs and has only been scored once so far. Each one names the occupation it was measured under in the free routes below; none is presented as a measurement for this job.
- Task clusters are not derived in this release, so the task-cluster field is empty and no Collab365 Space routing is attached to this occupation yet.
Shifting to AI
10 tasksTasks today’s tools can already do most of. This is the part we will not soften: where these rows are the bulk of your week, the week changes.
Performing or directing revision, repair or expansion of existing programs to increase operating efficiency or adapt to new requirements
This is reading one thing and writing another: revision, repair or expansion of existing programs in, a record out. That is the shape today's tools are built for.
importance 4 · CoreSource: “Perform or direct revision, repair, or expansion of existing programs to increase operating efficiency or adapt to new requirements.” (O*NET task statement)
How this row was scored
Exposure score: 75 out of 100 (71–79 allowing for uncertainty): high exposure, high confidence.
Why it sits in this group: reading one thing and writing another; the same decision, made over and over; mistakes that are cheap to catch.
The rating behind it: Revising and extending existing programs works well with tools, though old codebases carry context they must be given.
The five ratings: output a model can produce 3/4 · needs a body in a room 0/4 · needs an accountable person 0/4 · needs to be trusted in the moment 0/4 · how much data exists 3/4.
Writing, analyzing, reviewing and rewrite programs
This is reading one thing and writing another: rewrite programs in, a record out. That is the shape today's tools are built for.
importance 4 · CoreSource: “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 statement)
How this row was scored
Exposure score: 83 out of 100 (79–87 allowing for uncertainty): very high exposure, high confidence.
Why it sits in this group: reading one thing and writing another; the same decision, made over and over; mistakes that are cheap to catch.
The rating behind it: Writing and rewriting code is the task current tools do best, with programmers reviewing the result.
The five ratings: output a model can produce 3/4 · needs a body in a room 0/4 · needs an accountable person 0/4 · needs to be trusted in the moment 0/4 · how much data exists 4/4.
Correcting errors by making appropriate changes and rechecking the program to ensure that the desired results
This is reading one thing and writing another: errors in, a record out. That is the shape today's tools are built for.
importance 4 · CoreSource: “Correct errors by making appropriate changes and rechecking the program to ensure that the desired results are produced.” (O*NET task statement)
How this row was scored
Exposure score: 83 out of 100 (79–87 allowing for uncertainty): very high exposure, high confidence.
Why it sits in this group: reading one thing and writing another; the same decision, made over and over; mistakes that are cheap to catch.
The rating behind it: Finding and fixing errors, then re-running the program, is well within what coding tools now do.
The five ratings: output a model can produce 3/4 · needs a body in a room 0/4 · needs an accountable person 0/4 · needs to be trusted in the moment 0/4 · how much data exists 4/4.
Conducting trial runs of programs and software applications to be sure they will produce the desired information and that the instructions
This is reading one thing and writing another: trial runs of programs in, a record out. That is the shape today's tools are built for.
importance 4 · CoreSource: “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 statement)
How this row was scored
Exposure score: 83 out of 100 (79–87 allowing for uncertainty): very high exposure, high confidence.
Why it sits in this group: reading one thing and writing another; the same decision, made over and over; mistakes that are cheap to catch.
The rating behind it: Running programs to check they behave correctly is routine and largely automatable.
The five ratings: output a model can produce 3/4 · needs a body in a room 0/4 · needs an accountable person 0/4 · needs to be trusted in the moment 0/4 · how much data exists 4/4.
Changing shape
3 tasksTasks where the machine takes the producing and a person keeps the checking, the deciding, or the answering-for-it. For most jobs this is the biggest group, and it is where "transformation, not termination" is literally visible.
Consulting with and assisting computer operators or system analysts to define and resolve problems in running computer programs
The software now makes the first pass at and assisting computer operators, but the deciding part still needs a person. So the job becomes checking and deciding rather than producing.
importance 4 · CoreSource: “Consult with and assist computer operators or system analysts to define and resolve problems in running computer programs.” (O*NET task statement)
How this row was scored
Exposure score: 49 out of 100 (42–56 allowing for uncertainty): partial exposure, medium confidence.
Why it sits in this group: the same decision, made over and over; mistakes that are cheap to catch.
The rating behind it: Tools help diagnose problems, but resolving them usually involves working through it with the people affected.
The five ratings: output a model can produce 2/4 · needs a body in a room 0/4 · needs an accountable person 0/4 · needs to be trusted in the moment 1/4 · how much data exists 3/4.
Investigating whether networks, workstations
The software now makes the first pass at whether networks, workstations, but the deciding part still needs a person. So the job becomes checking and deciding rather than producing.
importance 3 · CoreSource: “Investigate whether networks, workstations, the central processing unit of the system, or peripheral equipment are responding to a program's instructions.” (O*NET task statement)
How this row was scored
Exposure score: 43 out of 100 (36–50 allowing for uncertainty): partial exposure, medium confidence.
Why it sits in this group: the same decision, made over and over; mistakes that are cheap to catch.
The rating behind it: Checking whether hardware responds correctly sometimes needs access to the machines themselves.
The five ratings: output a model can produce 2/4 · needs a body in a room 1/4 · needs an accountable person 0/4 · needs to be trusted in the moment 0/4 · how much data exists 3/4.
Training subordinates in programming and programing coding
The software now makes the first pass at subordinates, but the part that matters is a person saying it and standing behind it. So the job becomes checking and deciding rather than producing.
importance 4 · SupplementalSource: “Train subordinates in programming and program coding.” (O*NET task statement)
How this row was scored
Exposure score: 40 out of 100 (33–47 allowing for uncertainty): partial exposure, medium confidence.
Why it sits in this group: the same decision, made over and over; the value is that a specific person does it.
The rating behind it: Teaching programming is well documented, but training a colleague works through back-and-forth with them.
The five ratings: output a model can produce 2/4 · needs a body in a room 0/4 · needs an accountable person 0/4 · needs to be trusted in the moment 2/4 · how much data exists 3/4.
Staying human
4 tasksTasks that stay with a person, because they happen in the physical world, because the rules need someone accountable, or because the value is that a specific person does them.
Consulting with managerial, engineering and technical personnel to clarify program intent, identify problems and suggest changes
The value here is that a specific person handles managerial, engineering and technical personnel and stands behind it. That is earned, not computed.
importance 4 · CoreSource: “Consult with managerial, engineering, and technical personnel to clarify program intent, identify problems, and suggest changes.” (O*NET task statement)
How this row was scored
Exposure score: 35 out of 100 (28–42 allowing for uncertainty): low exposure, medium confidence.
Why it sits in this group: the value is that a specific person does it.
The rating behind it: Pinning down what a program is meant to do happens in conversation with the people who want it.
The five ratings: output a model can produce 2/4 · needs a body in a room 0/4 · needs an accountable person 0/4 · needs to be trusted in the moment 2/4 · how much data exists 2/4.
Training users on the use and function of computer programs
The value here is that a specific person handles users and stands behind it. That is earned, not computed.
importance 3 · SupplementalSource: “Train users on the use and function of computer programs.” (O*NET task statement)
How this row was scored
Exposure score: 30 out of 100 (23–37 allowing for uncertainty): low exposure, medium confidence.
Why it sits in this group: the same decision, made over and over; the value is that a specific person does it.
The rating behind it: Training material is easy to produce, but users learn best from someone answering their questions live.
The five ratings: output a model can produce 2/4 · needs a body in a room 1/4 · needs an accountable person 0/4 · needs to be trusted in the moment 2/4 · how much data exists 3/4.
Assigning, coordinating and reviewing work and activities of programming personnel
The value here is that a specific person handles work and stands behind it. That is earned, not computed.
importance 3 · CoreSource: “Assign, coordinate, and review work and activities of programming personnel.” (O*NET task statement)
How this row was scored
Exposure score: 35 out of 100 (28–42 allowing for uncertainty): low exposure, medium confidence.
Why it sits in this group: the value is that a specific person does it.
The rating behind it: Assigning and reviewing a team’s work is management that runs on knowing the people.
The five ratings: output a model can produce 2/4 · needs a body in a room 0/4 · needs an accountable person 0/4 · needs to be trusted in the moment 2/4 · how much data exists 2/4.
Show the other 7 tasks
Compiling and writing documentation of program development and subsequent revisions
shifting to AIThis is reading one thing and writing another: documentation of program development in, a record out. That is the shape today's tools are built for.
importance 4 · CoreSource: “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 statement)
How this row was scored
Exposure score: 83 out of 100 (79–87 allowing for uncertainty): very high exposure, high confidence.
Why it sits in this group: reading one thing and writing another; the same decision, made over and over; mistakes that are cheap to catch.
The rating behind it: Writing documentation and code comments is one of the things software does most reliably.
The five ratings: output a model can produce 3/4 · needs a body in a room 0/4 · needs an accountable person 0/4 · needs to be trusted in the moment 0/4 · how much data exists 4/4.
Writing, updating
shifting to AIThis is reading one thing and writing another: computer programs in, a record out. That is the shape today's tools are built for.
importance 4 · CoreSource: “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 statement)
How this row was scored
Exposure score: 83 out of 100 (79–87 allowing for uncertainty): very high exposure, high confidence.
Why it sits in this group: reading one thing and writing another; the same decision, made over and over; mistakes that are cheap to catch.
The rating behind it: Building and maintaining programs for common jobs like inventory or reporting is strongly supported by coding tools.
The five ratings: output a model can produce 3/4 · needs a body in a room 0/4 · needs an accountable person 0/4 · needs to be trusted in the moment 0/4 · how much data exists 4/4.
Writing or contributing to instructions or manuals to guide end users
shifting to AIThis is reading one thing and writing another: instructions in, a record out. That is the shape today's tools are built for.
importance 3 · CoreSource: “Write or contribute to instructions or manuals to guide end users.” (O*NET task statement)
How this row was scored
Exposure score: 83 out of 100 (79–87 allowing for uncertainty): very high exposure, high confidence.
Why it sits in this group: reading one thing and writing another; the same decision, made over and over; mistakes that are cheap to catch.
The rating behind it: User manuals and instructions are written material software drafts to a usable standard.
The five ratings: output a model can produce 3/4 · needs a body in a room 0/4 · needs an accountable person 0/4 · needs to be trusted in the moment 0/4 · how much data exists 4/4.
Preparing detailed workflow charts and diagrams that describe input
shifting to AIThis is reading one thing and writing another: detailed workflow charts in, a record out. That is the shape today's tools are built for.
importance 4 · CoreSource: “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 statement)
How this row was scored
Exposure score: 83 out of 100 (79–87 allowing for uncertainty): very high exposure, high confidence.
Why it sits in this group: reading one thing and writing another; the same decision, made over and over; mistakes that are cheap to catch.
The rating behind it: Turning a described process into diagrams and then into code is a core strength of current tools.
The five ratings: output a model can produce 3/4 · needs a body in a room 0/4 · needs an accountable person 0/4 · needs to be trusted in the moment 0/4 · how much data exists 4/4.
Developing Web sites
shifting to AIThis is reading one thing and writing another: web sites in, a record out. That is the shape today's tools are built for.
importance 3 · SupplementalSource: “Develop Web sites.” (O*NET task statement)
How this row was scored
Exposure score: 83 out of 100 (79–87 allowing for uncertainty): very high exposure, high confidence.
Why it sits in this group: reading one thing and writing another; the same decision, made over and over; mistakes that are cheap to catch.
The rating behind it: Building a website is squarely what coding tools already produce to a usable standard.
The five ratings: output a model can produce 3/4 · needs a body in a room 0/4 · needs an accountable person 0/4 · needs to be trusted in the moment 0/4 · how much data exists 4/4.
Performing systems analysis and programming tasks to maintain and control the use of computer systems software as a systems programmer
shifting to AIThis is reading one thing and writing another: systems analysis in, a record out. That is the shape today's tools are built for.
importance 3 · CoreSource: “Perform systems analysis and programming tasks to maintain and control the use of computer systems software as a systems programmer.” (O*NET task statement)
How this row was scored
Exposure score: 75 out of 100 (71–79 allowing for uncertainty): high exposure, high confidence.
Why it sits in this group: reading one thing and writing another; the same decision, made over and over; mistakes that are cheap to catch.
The rating behind it: Systems programming and analysis is well-documented technical work that tools handle with review.
The five ratings: output a model can produce 3/4 · needs a body in a room 0/4 · needs an accountable person 0/4 · needs to be trusted in the moment 0/4 · how much data exists 3/4.
Collaborating with computer manufacturers and other users to develop new programming methods
staying humanThe value here is that a specific person handles computer manufacturers and stands behind it. That is earned, not computed.
importance 3 · SupplementalSource: “Collaborate with computer manufacturers and other users to develop new programming methods.” (O*NET task statement)
How this row was scored
Exposure score: 23 out of 100 (16–30 allowing for uncertainty): low exposure, medium confidence.
Why it sits in this group: the value is that a specific person does it.
The rating behind it: Developing genuinely new methods with manufacturers and other users is collaborative pioneering work.
The five ratings: output a model can produce 1/4 · needs a body in a room 0/4 · needs an accountable person 0/4 · needs to be trusted in the moment 2/4 · how much data exists 2/4.
What this job pays, and how many people do it
- Median pay
- $100,390a year, the middle of the range, so half earn more and half earn less.bls-oews, 2025 · May 2025 estimates (national_M2025_dl.xlsx)
How we know this
Source: bls-oews
Reference period: May 2025 estimates (national_M2025_dl.xlsx)
Rounding: Shown as published.
- People doing this job
- 92,230in the US, 2025.bls-oews · May 2025 estimates (national_M2025_dl.xlsx)
What is deliberately not here: a forecast of how many of these jobs exist in ten years. Where an official projection exists for a market we publish it with its vintage; where it does not, we leave the space empty rather than borrow the other country’s number.
Why this is shifting
The reason is boringly specific. Most of what is shifting here is reading one thing and writing another: rewrite programs in, a record out. The rows above are exactly that shape: writing, analyzing, reviewing and rewrite programs and performing or directing revision. What it cannot do is be trusted in person, which is what managerial, engineering and technical personnel run on: someone specific doing it and standing behind it. Which is why this page talks about your tasks changing, not your job ending.
Your move
Over a pint: what I’d tell you if you were my friend
The exposed part of your job is the biggest part, and I am not going to dress that up: writing, analyzing, reviewing and rewrite programs is work today's tools do quickly and cheaply, and that is not coming back.
So, given all that: 66% of this job's task weight sits in rows the software is already learning, 14% in rows that change shape rather than disappear, and 20% in rows it is nowhere near. That is the position, measured across 17 scored tasks. It is not a forecast about you.
What you have that the software does not is consulting with managerial, engineering and technical personnel to clarify program intent, identify problems and suggest changes, plus the years of knowing when something looks wrong before you can say why. That is the raw material for everything below.
This week: one thing
Sit on the machine's side of the desk. Pick one real piece of rewrite programs you would normally do yourself, let whatever software you already have take the first pass at it, and then go through what it produced and write down every single thing it got wrong. One evening this week. Do not fix anything yet. Just catch it.
- What you end up holding
- a written list of the machine’s mistakes, in your handwriting
- How long it takes
- an evening, or an hour if you pick one job rather than one client
If you can’t run software on your employer’s or your clients’ data: Do the same hunt on paper. Take one printed piece of rewrite programs, work through it the way you always do, and mark every point where you made a call rather than followed a rule. Same evening, same list, nothing to log into and nobody to ask permission from. That list is the same artifact: it is the judgment written down.
Over the next 90 days
Change one sentence about what you do. Not on a CV. Out loud, to whoever pays you. From “my job is writing, analyzing, reviewing and rewrite programs” to “I check what the software does and tell you what it means.” Your error list from this week is what makes that sentence true instead of a claim, so use it: show it once, to one person, inside the next ninety days. Same skills, priced as judgment rather than as typing.
Over the next 12 months
Walk toward the end of this job that answers for things, and get it recognised. Pick the one part of consulting with managerial, engineering and technical personnel to clarify program intent, identify problems and suggest changes you are already best at, and spend the year making it formal: a qualification, a named responsibility, a specialism people ask for by name. Price it honestly: that is evenings, it is months rather than weeks, and the seats are competitive because everyone in your position is looking at the same door. Before you pay for anything, use CareerOneStop - Find local training. It is free, it is the Labor Department's own service, and it is listed below with the rest of the free routes.
The roads out of here, and why I am not sending you down them
I looked at the obvious moves out of this job, and here is what I found.
I checked the 12 nearest US occupations to computer programmers (nearest by the work that AI is not taking, not by job title), and none of them survived. The closest was computer and information research scientists: only about 6% of its durable work is work you already do. I am not going to pretend that is comfortable news: 66% of your own task list is already in the top exposure band. But the answer on this evidence is not a sideways jump into a job with the same problem. It is to walk toward the end of this one that answers for things. “consult with managerial, engineering, and technical personnel to clarify program intent, identify…” is the part that stays with a person, and spending a year getting formally recognised for it beats a standing start somewhere else.
How that was checked: this job was compared against all 830 US occupations in this release on their official task statements, and the 12 nearest were examined one by one. A move that turns on an industry, an employer or a qualification rather than on the work itself will not show up in a check like that. And this release carries no licence register, so anything you are weighing needs that looked up separately.
3 moves I checked and rejected
These are the obvious-looking jumps. They are here with their reasons rather than quietly dropped, because the ones that fail are worth knowing about. It is one less thing to turn over at night.
Computer and Information Research Scientists
Why it looked obvious: It came up as a near neighbour on the work AI is not taking: you already train subordinates in programming and program coding, and their equivalent is to participate in staffing decisions and direct training of subordinates. Across both published task lists that is about 6% of the durable work in that job.
Why I am not recommending it: Almost none of it is work you already do: about 6% of the durable side of that job. That is a different job, not a next step.
Computer and Information Systems Managers
Why it looked obvious: It came up as a near neighbour on the work AI is not taking: you already train users on the use and function of computer programs, and their equivalent is to provide users with technical support for computer problems. Across both published task lists that is about 5% of the durable work in that job.
Why I am not recommending it: Almost none of it is work you already do: about 5% of the durable side of that job. That is a different job, not a next step.
Computer Systems Analysts
Why it looked obvious: It came up as a near neighbour on the work AI is not taking: you already train users on the use and function of computer programs, and their equivalent is to train staff and users to work with computer systems and programs. Across both published task lists that is about 5% of the durable work in that job.
Why I am not recommending it: Almost none of it is work you already do: about 5% of the durable side of that job. That is a different job, not a next step.
What I’d stop worrying about
A friend tells you what not to spend fear on. This is that list.
The headline number you read somewhere
The big “X% of jobs” figures are about the whole economy, not about you. The number that describes your job is on this page: 66% of its task weight, across 17 scored tasks. Every row behind it is printed above with the source. Check ours; ignore theirs.
“It’s too late for me to become something else”
You are not starting from zero, and the page shows why: consulting with managerial, engineering and technical personnel to clarify program intent, identify problems and suggest changes is work the software cannot do and you already do it. The move above is a repricing of what you know, not a new career. Nobody who has just left college has that.
“I should learn to code”
Almost certainly not. The value in your job is moving toward checking, deciding and answering for the output, not toward writing the software. A weekend of Python will not change your position; the error list from this week will.
The “obvious” next job everyone suggests
I checked the obvious moves and most of them did not survive. The reasons are printed with the routes above, including the pay and the gate. A move that fails on the numbers is worth knowing about so you can stop turning it over at night.
You are reading the United States figures
The United Kingdom splits this work across more than one official group, of which Programmers and software development professionals is the closest. The pay and employment figures are not directly comparable, and we do not average them together.
Switch to the United Kingdom page →partial match
In UK official statistics this job is counted as Programmers and software development professionals. Pay and employment stay on this page’s own group; the task list and the scores do not cross over.
Your route through this
Where to go next, and what it costs
Free, and complete
The moves above cost nothing. These are the real services that go with them: public, government-funded, and free at the point of use. Nothing on this page is behind an email address or a payment.
Anywhere in the US:
CareerOneStop - Find local training
Search what's running near you, from the Labor Department's own database, before anyone sells you a course.
Free to search; individual programs vary, and some are funded
Anywhere in the US:
An American Job Center will sit down with you for free. Find yours by ZIP code.
Free
Anywhere in the US:
CareerOneStop - Licensed occupations finder
Check what your state actually requires before you pay for anything.
Free
Anywhere in the US:
Free
No Space for this job, but one for what is happening to it
Nothing Collab365 runs is built for computer programmers, and we are not going to point you at the nearest one and call it a fit.
There is one that is not about a job title at all. The AI Authority is about being the person who directs these tools at work rather than the person they get compared to. That is worth saying here, because 66% of the work on this page is already inside what they can do.
7 days free, no card needed. Explore up to 2 Spaces before you choose a plan: you pick a plan later, not now.
The AI Authority is a general community about working with AI, not a course for computer programmers. You do not need it to act on anything here: the moves above cost nothing and stand on their own. The data on this page is the same either way.
Noted, and thank you. We’ll email you if a Space for computer programmers launches. Nothing else.
That did not look like an email address, so nothing was saved. Have another go below.
We could not save that. The fault is ours, not yours, and your address was not stored. Please try again later.
No deadline on any of this. The page will still be here, and the data is refreshed on a published schedule rather than when someone wants a headline.
Questions people ask about this job
- Will AI replace Computer Programmers?
- Not as a job, but it is already doing parts of the work. Across the 17 official task statements scored for Computer Programmers (United States, SOC 15-1251), 66% of the importance-weighted core work is made of tasks today's AI could already do most of. The overall exposure score is 66 out of 100 (range 61–71, band: high). That is a statement about tasks, not about headcount: this measures what AI could do, not whether any employer adopts it, whether the law allows it, or whether doing the routine parts faster creates more demand for the human parts. Figures are from release 2026-q4.1.
- Which tasks in “Computer Programmers” can AI already do?
- The highest-scoring tasks in release 2026-q4.1 are: “Correct errors by making appropriate changes and rechecking the program to ensure that the desired results are produced” (83/100, very high); “Conduct trial runs of programs and software applications to be sure they will produce the desired information and that the instructions are correct” (83/100, very high); “Compile and write documentation of program development and subsequent revisions, inserting comments in the coded instructions so others can understand the pr…” (83/100, very high). Each score comes from five published 0–4 ratings turned into a number by a published formula, and each carries the model's one-sentence reason on the page.
- Which tasks in “Computer Programmers” stay human?
- About 20% of this job's task weight sits in work that scores low for AI exposure. The lowest-scoring tasks in release 2026-q4.1 are: “Collaborate with computer manufacturers and other users to develop new programming methods” (23/100, low); “Train users on the use and function of computer programs” (30/100, low); “Assign, coordinate, and review work and activities of programming personnel” (35/100, low). Low scores usually mean the task needs a body in a room, a legally accountable human, or trust built in real time. Those are the three things the scoring rubric treats as gates rather than obstacles.
- What should someone working in “Computer Programmers” do about AI?
- Start from the ledger rather than the headline: 66% of this job's weighted core work is exposed, and roughly 20% is not. The practical move is to spend more of your week on the tasks that score low, the ones above, and to get fluent at directing AI through the tasks that score high, because those are the parts that change whether or not you are ready for them. This page does not predict your job, and nothing here is career advice tailored to you: the score describes the occupation, not the person.
- How is the AI exposure score for Computer Programmers calculated?
- Each official task statement for the occupation is rated on five published 0–4 dimensions (output replicability, physical embodiment, licensed accountability, real-time human trust, and data availability) by claude-opus-5 using scoring prompt task_scoring_v1.0. The model never writes the score; a published formula turns the five ratings into a 0–100 number, so every score can be recomputed by hand. The occupation figure is the importance-weighted mean across 17 scored tasks. The prompt, the rubric, the formula and the full dataset are published at https://futureproof.collab365.com/method and https://futureproof.collab365.com/data/2026-q4.1 under CC BY 4.0.
Where these numbers come from
Worth knowing about these figures
- The match between this job and its counterpart in the other country is partial, so the two pages count slightly different groups of people.
- 2 of this occupation's scored task statements carry a score that was measured under a different occupation's context, because the statement is shared between jobs and has only been scored once so far. Each one names the occupation it was measured under in the free routes below; none is presented as a measurement for this job.
- Task clusters are not derived in this release, so the task-cluster field is empty and no Collab365 Space routing is attached to this occupation yet.
- Task statements
- onet-dbProcessing: catalogue-bridge → onet-im-rt-weighting → task-scoring → score-aggregation
- Task weights
- onet-db (im-rt)
- Scores
- Rubric task_scoring_v1.0, model claude-opus-5, computed 2026-08-05.
- Pay and employment
- bls-oews (May 2025 estimates (national_M2025_dl.xlsx))bls-oews (May 2025 estimates (national_M2025_dl.xlsx))
Figures on this page come from release 2026-q4.1, published 2026-08-05. Every release keeps its own permanent address, so a figure you cite in March is still there, unchanged, in November.
The plain-English wording on this page is assembled directly from the task statements and the published ratings, not written by hand for this occupation. That is why it is specific, and it is also why we say so.
The routes and free resources further up are today’s, not the release’s (last reviewed 2026-08-05). A route is an offer, not a historical fact, so it moves on its own clock.
Using these figures?
Cite this
Everything on this site is published under CC BY 4.0. Quote it, chart it, sell something built on it. Just say where it came from, and cite the dated release rather than the site, so the figure you quote stays checkable.
Plain text
Collab365 (2026). Collab365 Futureproof: task-level AI exposure for US and UK occupations, release 2026-q4.1 (methodVersion 2.0.0, promptVersion task_scoring_v1.0). https://futureproof.collab365.com/data/2026-q4.1. Licensed CC BY 4.0. Built with O*NET data (USDOL/ETA, CC BY 4.0); ONS data (Open Government Licence v3.0); GAISI task framework (arXiv:2507.22748, MIT); BLS data (public domain).
BibTeX
@misc{collab365futureproof2026q41,
title = {Collab365 Futureproof: task-level AI exposure for US and UK occupations, release 2026-q4.1},
author = {{Collab365}},
year = {2026},
url = {https://futureproof.collab365.com/data/2026-q4.1},
note = {Release 2026-q4.1, methodVersion 2.0.0, promptVersion task_scoring_v1.0, CC BY 4.0}
}Data as of release 2026-q4.1, published . Releases never change after publication; when the figures move, a new dated release is published beside this one and this one stays exactly where it is.