Software Developer
Also: Programmer · Software engineer · Coder
Designs, writes, tests and maintains software.
1926
A · The occupation 100 years ago
Did not exist. Programming emerged in the late 1940s, initially done largely by women who had been human computers.
Historical imagery: not yet included. Images are added only after licensing (public domain or explicit permission) is confirmed.
1926–2026
B · The evolution
1948
Programming is born
Early stored-program computers required programming, much of it done by women.
1957
High-level languages
FORTRAN (1957) and COBOL (1959) made programming more productive.
1981
The PC software industry
Personal computers created a mass market for software.
1995
The web era
Web development became a mass occupation.
2023
AI pair programmers
In an experiment, developers with Copilot completed a task 55.8% faster.
Technologies that reshaped this occupation
What disappeared
- No major tasks fully disappeared.
What technology took on
- • Writing code (from c.2022)
- • Debugging and testing (from c.2022)
- • System design and architecture (from c.2024)
- • Documentation (from c.2023)
What remained fundamentally human
- • Requirements and stakeholder work
- • Security and reliability responsibility
2026
C · The occupation today
One of the largest professional occupations. AI coding assistants are ubiquitous; controlled experiments show large speed-ups on defined tasks, and AI agents increasingly write and test code. Entry-level hiring has become more uncertain.
Required skills
- Programming
- System design
- Problem solving
- Communication
Typical tools & software
- IDEs
- AI coding assistants
- Cloud platforms
Demonstrated today
Technology already used for these tasks (documented in 2015–2026)
- • Writing code
- • Debugging and testing
- • System design and architecture
- • Documentation
Speculative capability
Not yet demonstrated at scale — these appear only in scenarios
- • Supervising AI coding agents (central c.2026)
- • AI system governance (central c.2030)
Barriers to automation (editorial assessment, 0–1)
These factors delay or cap automation in the model. Strong underlying demand partly offsets very high exposure.
- Regulation & licensing0.20
- Physical environment0.05
- Human accountability0.50
- Social acceptance0.20
- Economic viability0.80
- Underlying demand trend+0.40
2030→2126
D · The future
Scenarios, not predictions. Confidence falls with the horizon.
2050 · CENTRAL SCENARIO
Most code generated by AI; developers specify, architect, review, secure and take responsibility for systems. Demand for software keeps growing.
2126 · CENTRAL SCENARIO
Software creation may be largely autonomous; human roles in defining goals, governance and novel systems.
2126 · CONSERVATIVE
Developers remain central with very powerful tools.
2126 · ACCELERATED
Programming as a mass occupation largely gone; a small community oversees autonomous development.
| Year | Scenario | Transformation | Employment outlook | Skills outlook | Confidence |
|---|---|---|---|---|---|
| 2030 | Conservative | 23 | Growing | ||
| Central | 22 | Growing | Core human skills remain in requirements and stakeholder work, security and reliability responsibility; new capabilities needed for supervising ai coding agents, ai system governance; plus fluency directing and auditing AI tools. | Moderate | |
| Accelerated | 30 | Stable, transforming | |||
| 2050 | Conservative | 22 | Growing | ||
| Central | 37 | Stable, transforming | Core human skills remain in requirements and stakeholder work, security and reliability responsibility; new capabilities needed for supervising ai coding agents, ai system governance; plus fluency directing and auditing autonomous systems. | Low | |
| Accelerated | 54 | Stable, transforming | |||
| 2075 | Conservative | 37 | Stable, transforming | ||
| Central | 57 | Stable, transforming | Core human skills remain in requirements and stakeholder work, security and reliability responsibility; new capabilities needed for supervising ai coding agents, ai system governance; plus fluency directing and auditing autonomous systems. | Speculative | |
| Accelerated | 66 | Contracting | |||
| 2126 | Conservative | 52 | Stable, transforming | ||
| Central | 64 | Contracting | Core human skills remain in security and reliability responsibility; new capabilities needed for supervising ai coding agents, ai system governance; plus fluency directing and auditing autonomous systems. | Speculative | |
| Accelerated | 70 | Contracting |
Salary implications: not modelled. No credible occupation-level wage forecasts exist for these horizons, so we do not publish one.
Tasks
E · Occupational transformation
- Routine cognitive
- Non-routine analytic
- Creative production
- Interpersonal & care
- Judgement & accountability
- Human-led · 2
- Assisted · 3
- Automated · 1
- New task · 2
- Retired · 0
| Task | Machine involvement | |
|---|---|---|
| Writing code | Creative | Assisted |
| Debugging and testing | Analysis & problem solving | Assisted |
| System design and architecture | Analysis & problem solving | Assisted |
| Requirements and stakeholder work | Human interaction | Human-led |
| Security and reliability responsibility | Judgement | Human-led |
| Documentation | Routine information | Automated |
| Supervising AI coding agentsnew | Analysis & problem solving | Assisted |
| AI system governancenew | Judgement | Human-led |
How this is derived: tasks are classified with the routine/non-routine framework (Autor, Levy & Murnane 2003); each task type follows a capability curve per scenario, delayed by this occupation's adoption barriers (regulation, physical environment, social acceptance, economics) and capped by accountability. The index is a share of task content, not the probability that the job disappears. Full methodology →
Evidence
5 sources cited
On the timeline
Profile last updated 2026-11-17.