Computer and Mathematical · Bachelor's degree
SALARY RANGE
$71,588
10th
$95,017
25th
$130,160
Median
$169,208
75th
$201,748
90th
Median hourly: $62.58/hr
Source: Bureau of Labor Statistics, 2024 OEWS (most recent release)
EMPLOYMENT OUTLOOK
Growth outlook: Much faster than average
Projected change: +10.5% (+10K jobs)
Projection period: 2024-2034
Typical education: Bachelor's degree
Source: Bureau of Labor Statistics, 2024-2034 Employment Projections
ORUNE'S AI ANALYSIS
Based on O*NET task data and published AI research
0
AI handles independently
6
AI assists (and growing)
2
Distinctly human
AI currently handles 0 of 8 tasks independently, assists with 6 more, and 2 remain distinctly human. The balance is shifting as AI capabilities grow.
RELATED ROLES
See how AI is changing this role in detail.
Check Software DevelopersWhat is changing in this field
The mechanical parts of building software are getting cheaper. Architecture, code review, debugging AI output, and translating ambiguous problems into specs are getting more valuable. The question facing most working developers right now is whether to compete with AI on velocity or to move toward judgment work that AI cannot do well yet.
Adoption signals
IDE-integrated AI coding assistants are now the default
A majority of large enterprise development organizations have rolled out or piloted GitHub Copilot, Claude Code, Cursor, or similar tools. The conversation has moved from "should we adopt" to "how do we measure value beyond keystrokes saved."
Source: GitHub Octoverse and major enterprise developer surveys
Code review and test generation are next, not just code-writing
AI-assisted code review, test scaffolding, and PR summarization are seeing rapid adoption inside teams that already use AI for code generation. Boilerplate work compresses fastest; design review and architectural judgment compress slowest.
Source: Industry tooling roadmaps and developer-experience research
Effects on hiring are unevenly distributed by seniority
Recent reporting suggests the entry-level engineering market has been hit hardest first, while senior IC and staff-level roles have seen continued or even accelerated demand. The middle of the experience curve is where the largest shape changes are happening.
Source: BLS Employment Projections and major hiring reports
Specialization matters more than language
Domain depth (security, ML systems, distributed systems, embedded) is being valued more relative to generic full-stack work, since AI tools narrow the gap on the latter faster.
Source: Hiring data from major engineering organizations
How this lands at different career stages
Early career (0-5 years)
The execution-heavy work that traditionally builds early-career muscle is the same work AI handles best. That makes the conventional path slower than it used to be. The compensating move is building judgment fast: learn to read code well, learn to debug AI output critically, get reps reviewing PRs even when you are not the primary reviewer. The goal is to compress the years it takes to reach "I can architect a service" from a decade to four or five.
Mid career (5-15 years)
This is the inflection point. Two paths are visible. One is becoming the senior IC who ships ten times more by orchestrating AI tools well. The other is moving toward design, architecture, or product roles where the value is judgment about what to build. Both work. The path that does not work is staying in execution-only roles where the moat is speed, since speed is exactly what is being commoditized.
Senior career (15+ years)
Your pattern recognition across systems and your taste for what a good codebase looks like are the durable edge. AI can write code that compiles. It still struggles to write code that ages well. Lean into the architecture, the postmortems, the mentorship. New engineers are missing reps that AI absorbed; you can fill that gap and that work is increasingly recognized as senior-level value.
Demand trajectory
Software has historically expanded with productivity gains, not contracted. Cheaper code has tended to mean more software gets funded, not fewer engineers. The total developer headcount is likely to keep growing, but the shape is shifting: fewer pure-execution junior roles, more senior IC and architect roles, and a wider gap between teams that integrate AI well and those that do not.
Editorial depth module.
Salary and employment data from the Bureau of Labor Statistics (2024 OEWS, 2024-2034 Employment Projections).
Task analysis based on O*NET occupational data and published AI research.
Learn more about our data sources