Occupations

Software Developers

SOC 15-1252Knowledge / AIOctober 2026 assessment2025 employment 1.72M

Research, design, and develop computer or network software and specialized utility programs; analyze needs and build software solutions.

Occupation description · O*NET

Current assessmentOctober 2026Independent analysis for a changing world of work.

Current EOL outlook

Forecast and analytical state

See how this assessment evolved →

2030 working outlook−2% to +5%

−10%0%+10%

2035 working outlook−16% to +4%

−20%0%+20%

2035 reference points

BLS structural projection+10.2%

Metaculus probabilistic forecast−12.2%

Reference points, not inputs mechanically averaged into EOL.

Bottom line

AI capability is already advanced across coding, debugging and increasingly agentic development. Human developer demand is becoming less proportional to software output both because developers can produce more and because non-developers can increasingly create software directly, although demand growth and production bottlenecks remain powerful offsets.

Six-stage assessment

Where the evidence stands now

Same framework used across every EOL occupation

01CapabilityAdvanced / acceleratingView evidence → 02Economic ViabilityStrongView evidence → 03AdoptionHigh for AI assistance; agentic and recursive workflows rapidly broadeningView evidence → 04Task SubsumptionMaterial, heterogeneousView evidence → 05Human Labor DependencyModerateView evidence → 06Labor-Market EffectsEmerging; composition and entry-level effects more evident than aggregate displacementView evidence →

Transparent by design. Every stage judgment is traceable to the evidence supporting the current assessment.

View all Software Developers evidence →

Evidence TiltModerate evidence tilt toward displacement

What this means →

DisplacementBalancedAugmentation

Historical ContinuityUnlikely reliable as central assumption

What this means →

ReasonableIncreasingly questionableUnlikely reliable

View all evidence in Signal Tracker →Read the methodology →Jump to labor supply →

Detailed occupation assessment

Forecast ContextView detail ›

Employment / inflection

Growth slowing / plateau risk before 2030

Forecast rationale

The 2030 range still permits positive developer growth as demand expands and production bottlenecks persist. By 2035, the downside reflects smaller teams and direct non-developer software creation, while the +4% upper edge preserves the possibility that software demand and persistent human bottlenecks outpace automation.

Demand / countervailing pressure

AI-induced software demand and new applications can offset productivity, but only if they require proportional developer labor.

Key mechanism

Agentic workflow substitution; output per developer.

How EOL translates evidence into a forecast range →Worked methodology example →

Six-Stage Transition Assessment

Expanded analysis

Capability

Frontier agents now complete multi-hour software tasks on controlled benchmarks; coding is a leading AI use case. | Qualification: Platform activity != production FTE.

Advanced / accelerating
Moderate-high confidence

Evidence Synthesis

Evidence tilt

Moderate evidence tilt toward displacement

Directional summary of whether current evidence pushes EOL toward greater or lesser human labor demand relative to the occupation’s existing structural trajectory. It is categorical, not a probability, percentile, automation share, or mathematical adjustment.

Historical continuity

Unlikely reliable as central assumption

AI capability and agentic production are changing the link between software output and developer headcount faster than historical relationships imply.

Labor Supply

Pipeline: Degree-centered / porous
Supply trend: Contracting
Replenishment burden: 5.5% of employment annually
Demand-supply alignment: Near-term entrant pressure, with potential supply adjustment later

Supply implication for the forecast

If software-developer demand weakens, the first adjustment is likely to appear in campus and entry-level hiring rather than broad incumbent displacement. The computing pipeline is already contracting, which could partially cushion a later demand decline. Early-career hiring therefore remains a leading indicator of whether AI-driven productivity is translating into reduced labor demand.

How EOL analyzes labor supply →

Forecast Bridge

The analysis above is the evidence base. The bridge below summarizes how those findings translate into the 2030 and 2035 ranges without repeating the full six-stage assessment.

What BLS already captures

BLS already reflects historical software-demand growth, productivity change, occupational staffing patterns, and analyst judgment about emerging AI. EOL does not subtract today's coding automation a second time.

Why EOL still differs

The residual departure is faster agentic and recursive development plus direct non-developer software creation, reducing professional developer-hours per unit of software faster than the BLS structural path implies.

2030−2% to +5%

Neutral structural bridge: +5%. This is an EOL benchmark derived from the BLS ten-year path, not a BLS 2030 forecast.

Lower-employment edge

AI agents absorb a meaningful share of development work and developer-service substitution broadens, producing modest employment contraction despite strong software demand.

Upper-employment edge

Software demand expands strongly and human bottlenecks persist; employment reaches roughly the neutral structural path even as output per developer rises.

2035−16% to +4%

BLS structural projection: +10.2%.

Lower-employment edge

Agentic and recursive systems materially compress team size, non-developers directly create more software, and output expands without proportional professional developer hiring.

Upper-employment edge

Demand for software and new applications remains very strong, while architecture, integration, verification and accountability bottlenecks keep professional developer demand growing modestly.

Why not materially higher or lower?

A materially lower outcome would require the greater-displacement conditions to be established at broader scale than current evidence supports: Sustained software output growth with smaller teams; reliable production-grade project autonomy; larger shares of end-to-end workflows completed by agents; rising output per developer without proportional hiring. A materially higher outcome would require the employment-supportive conditions to dominate more strongly than current evidence supports: Strong developer hiring and team expansion alongside AI adoption; persistent architecture, integration, security and customer bottlenecks; AI-induced software demand consistently creating more human work than automation removes.

September revalidationv1.8 independent validation adjudicated

What Would Change Our View?

Toward greater displacement

Sustained software output growth with smaller teams.

⌄

Sustained software output growth with smaller teams; reliable production-grade project autonomy; larger shares of end-to-end workflows completed by agents; rising output per developer without proportional hiring.

Toward greater employment

Strong developer hiring and team expansion alongside AI adoption.

⌄

Strong developer hiring and team expansion alongside AI adoption; persistent architecture, integration, security and customer bottlenecks; AI-induced software demand consistently creating more human work than automation removes.

Signal Tracker

See how this assessment evolves

EOL preserves meaningful assessment updates, forecast holds, forecast changes, and BLS structural rebases over time.

Open Signal Tracker →

Sources and Assessment History

Current assessment

October 2026EOL occupation assessment

Structural reference

BLSEmployment Projections · SOC 15-1252

External calibration

MetaculusSoftware Developers · Broader proxy

Supply evidence

National Student Clearinghouse Research CenterComputing enrollment and entrant-pipeline evidence