Explore safer careers (5)
Lower estimated automation risk
Why it fits
Builds on application delivery experience for architecture, integration, scalability, security, and technical advisory work.
Why it fits
Moves into secure system design, vulnerability mitigation, controls implementation, and technical guidance.
Why it fits
Extends data modeling and SQL experience into architecture standards, governance, integration, and performance design.
Why it fits
Applies SQL, ETL, and data integration skills to data quality, warehouse design, and user support.
Why it fits
Builds on coding and systems knowledge for security controls, risk assessment, incident response, and policy work.
Occupation snapshot
What does this snowflake show?
What's this?
We rate jobs using four factors. These are:
- Chance of being automated
- Job growth
- Wages
- Volume of available positions
These are some key things to think about when job hunting.
Risk & user votes
Calculated automation risk
Low Risk (21-40%): This occupation has a lower risk of full replacement by AI, software, or robotic systems. Some tasks may be automated or assisted, but the role usually still relies on human judgement, communication, responsibility, physical adaptability, or practical decision-making.
More information on what this score is, and how it is calculated is available here.
Human strengths important in this job
These are human abilities and work contexts that are important in this occupation. They may help explain why parts of the role are harder to replace end-to-end, but they are not the only inputs into the automation score.
Thinking creatively
Very importantWhy this matters
Decision-making and problem solving
Very importantWhy this matters
Social perceptiveness
Quite importantWhy this matters
Coordinating others’ work
Quite importantWhy this matters
Developing objectives and strategies
Quite importantWhy this matters
Show 2 more strengths
Active learning
Quite importantWhy this matters
Operations analysis
Quite importantWhy this matters
What users think
Based on 11,054 votes
Our visitors have voted that it's probable this occupation will be automated. However, employees may be able to find reassurance in the automated risk level we have generated, which shows 36% chance of automation.
What do you think the risk of automation is?
What is the likelihood that Computer Programmers will be replaced by robots or artificial intelligence within the next 20 years?
Sentiment
Based on user votes over time
View sentiment trend
How opinions have changed over time
How opinions have changed over time
Pay & outlook
Wages
In 2024, the median annual wage for Computer Programmers was $98,670 ($47 per hour).
The median annual wage for Computer Programmers was 99.3% higher than the national median annual wage, which stood at $49,500.
View wage trend
Wages over time
Growth
The number of 'Computer Programmers' job openings is expected to decline 6.0% by 2034
View employment trend
Total employment, and estimated job openings
Updated projections are due 09-2025.
Volume
As of 2024 there were 109,870 people employed as 'Computer Programmers' within the United States.
This represents around 0.07% of the employed workforce across the country
Put another way, around 1 in 1 thousand people are employed as 'Computer Programmers'.
People also viewed
Job description
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.
O*NET-SOC code: 15-1251.00
What people are saying (295)
Please take into account the trajectory of progress rather than the current state of things.
But though AI (= LLMs) has gotten better in the sense of creating more complex outputs, it otherwise suffers from exactly the same problems as early versions: no compositionality, no continual learning, no consistency, and no self-correction.
If you ask it to fix a certain bug fix in a complex codebase, you have a high chance that it also starts to change something completely unrelated. It doesn't really grasp how precisely elements make up the complex whole; instead, it applies pattern-matching, by which it gets misled. You can waste days with AI on what would be a five-minute manual fix.
Also, junior devs' job isn't to churn out mediocre code for generic, long-solved tasks or create the 1000th to-do list app. Instead, they get onboarded and are supposed to familiarize themselves with your codebase to improve it. But you know that "PT" in ChatGPT stands for "pre-trained?" So AI doesn't learn anything new. AI is like suffering from anterograde amnesia.
Anyway, neither apps nor code are like a commodity where "more is better". In the end, the point is to create something new. Otherwise there is not much point: just use an already existing and tested library. And it's exactly the "new" part where AI sucks because it struggles to transcend its training data.
So no, AI is incapable of replacing junior devs.
It would have a lot of immediate positive effects if AI worked like you describe: it would insanely empower open-source projects (often lacking maintainers) to fix all their long lists of bugs or introduce new features. But this is not what we observe at all. Because AI is overhyped and underdelivers.
-> MNCs keep laying off juniors while recording profits. Why? Because they have trained their AIs to do the jobs of 100s of people. Where they needed 100 people, they only need 1 now.
-> OpenAI just hired ex-bankers to develop financial AIs that will eventually replace junior finance professionals in their company. Others are following suit.
-> Salesforce has openly admitted to cutting jobs because of AI. So have many other top companies.
Don't get me wrong, I think AI is way off from completely replacing digital labour. I almost agree with you on most of your points.
But it's getting there, and it's getting there quickly. It's only a matter of time until researchers develop a new system that supersedes transformer models. And judging by the Billions being burned every day on AI research, it's almost inevitable.
I think you'll find the "AI 2027" paper very interesting. Please do have a read. And thanks for your reply :)
For instance, I asked ChatGPT to write me a simple code that creates a "conversation" with OpenAI's APIs. It could not even do that accurately.
Current likelihood of replacing a computer programmer is laughable at best. Maybe over 20 years there might be "some" progress.
Reply to comment