Build
Connect & operate
Design & teams
Start hereScope a build in one callBring a spec, a wireframe, or a paragraph. You leave with an architecture, a timeline, and a number.Request a scoping call
AI software
LLM & data systems
Vibe coding
Ready to ship?Put AI where the work isAgents, RAG, and private LLMs wired into the systems your team already uses — not a chatbot bolted to a homepage.Discuss an AI project
Domain firstWe learn your workflow before we model itRegulated, operational, or high-volume — the constraints belong in the schema, not in a training doc.Talk about your domain
Plan smarterEstimate before you commitCost ranges, scope templates, and the questions we ask in discovery — free, no form.Open the cost calculator
Real conversationsTalk with a technical leadNo SDR, no discovery gauntlet. The person on the call is the one who scopes the build.Request a call
Graphic · Software Development · 2026

Software Development Statistics (2026)

The Crossover: in 2025, the share of developers using AI tools passed the share who feel good about them, and it has stayed ahead. AI now drafts code and pull requests, while developers keep the final say.

Updated Nov 12, 20267 charts · 4 key stats8 primary sourcesEmbed & share ↓
Fig. 1 · The Crossover

Developers' AI use passed their approval of AI in 2025, and stayed ahead

AI in software development statistics: share of Stack Overflow survey respondents who use AI tools vs. share favorable toward them, 2023–2026, %

025%50%75%100%2023202420252026Use AI tools82.8% in 2026Favorable62% in 2026

All respondents in each year's survey. Use and favorability are derived by adding published answer shares. The 2026 survey reworded both questions ("in your role at work"; "somewhat favorable"), so the 2025–26 step is not a like-for-like change.

Developers using at least one AI tool at work, 2026
83%
73% of AI coding assistant users use them daily
Trust AI output with important work decisions
6.6%
48.0% trust it only when they can easily verify it
GitHub pull requests started by an agent, Sept 2026
40%+
Up from 17% in March 2026
U.S. software developer jobs, 2025
1,717,800
Projected +10% by 2035 vs. 3% for all jobs
SourceBLS7
Fig. 2

Almost half of developers trust AI only when they can check it

Trust in AI-generated code and output: how much developers trust AI tools in their workflow, 2026, % of respondents

48.0%16.3%16.3%12.3%
  • Only when I can easily verify it48%48.0%
  • For many tasks, not important decisions16.3%16.3%
  • For low-risk tasks only16.3%16.3%
  • Not for most work tasks12.3%12.3%
  • For many tasks, including important decisions6.6%6.6%
  • Not sure / don't use AI0.5%0.5%
  • All respondents100%100%

Answer labels are shortened from the survey's wording (e.g. "I trust it when I can easily verify the output"). n = 14,304.

Fig. 3

AI writes the code, but rarely touches production

What developers use AI for: share currently using AI or AI agents for each task, 2026, %

Familiar code69.3%Debugging63.8%Simple questions59.4%Writing tests58.1%Unfamiliar code56%Documentation51.1%Code review40.5%Security fixes34.6%Production ops19.9%

Nine of the 19 tasks asked about. Labels are shortened from the survey's wording: "Familiar code" is "Generating code in a familiar area", "Debugging" also covers troubleshooting and refactoring, and "Production ops" is "Deploying, operating, or troubleshooting production systems." 36.0% do not use AI for production work and do not plan to. n = 12,547.

Fig. 4

Claude Code and GitHub Copilot lead AI coding tools

Most used AI coding tools: share of respondents who used each coding agent or assistant in the past year, 2026, %

Claude Code65.5%GitHub Copilot58.7%OpenAI Codex29.5%Cursor25.5%Google Antigravity16%Gemini Code Assist14.6%Open Code13.6%JetBrains AI12.8%

Base is the 12,255 respondents who answered the coding-agent question, not all survey takers. Respondents could pick several tools.

Fig. 5

Python has closed in on JavaScript, now 4 points behind

Most popular programming languages: share of respondents doing extensive work in each, 2017–2026, %

020%40%60%80%2017202020232026JavaScript62% in 2026Python58% in 2026TypeScript43.8% in 2026Java27.6% in 2026

The 4.0-point gap is JavaScript's 62.0% minus Python's 58.0% in 2026 (30.2 points in 2017). SQL (58.4%) and HTML/CSS (58.2%) also edge Python in 2026 and are left out for clarity. Each year is a different self-selected sample.

Fig. 6

U.S. software developer jobs are projected to grow 3× faster than average

Software developer job outlook: projected change in U.S. employment, 2025–35, %

Software developers10%Computer occupations6%QA analysts & testers6%All occupations3%

BLS rounds these projections to whole percents. Software developers: 1,717,800 jobs in 2025, 1,892,600 projected for 2035 (+174,700). "3× faster" compares the rounded 10% with 3%.

SourceBLS7
Fig. 7

Software developers earn 2.7× the U.S. median wage

Software developer salary: median annual wage in the U.S., May 2025, US$

Software developers$135,980Computer occupations$109,470QA analysts & testers$104,300All occupations$50,980

2.7× is $135,980 ÷ $50,980 (derived). The lowest 10% of software developers earned less than $82,460 and the highest 10% more than $214,670.

SourceBLS7
Free to republish

Add This Graphic to Your Website

Paste one snippet and every chart, stat and citation above appears on your page. It stays interactive and responsive, and it updates automatically when we revise the data.

  • All sources travel with every card
  • Resizes to fit any column width
  • Light or dark theme, full set or a single card
  • Free with attribution, which is built in
Share this graphic
<div class="graphic-embed" data-graphic="software-development-statistics">
  <a href="https://dev.co/graphics/software-development-statistics">Software Development Statistics (2026)</a> by DEV.co
</div>
<script async src="https://dev.co/embed.js"></script>
Auto-resizes to fit its content. Works on WordPress, Webflow, Squarespace, Ghost and plain HTML.
Preview

What this graphic shows

This graphic gathers the software development statistics that best describe 2026 from three primary sources: Stack Overflow's annual Developer Survey, GitHub's Octoverse report and the U.S. Bureau of Labor Statistics. Its central chart, The Crossover, tracks two answers from four years of Stack Overflow surveys. In 2023, 44.2% of respondents used AI tools and 76.3% felt favorable toward them. By 2025, use had climbed to 78.5% while favorability fell to 59.7%. In 2026, 82.8% use at least one AI tool at work and 62.0% are favorable.

The other cards follow that gap into daily work: how far developers trust AI output, which tasks they hand to it, which coding agents they use, which languages they write, and what the U.S. job market for software developers looks like.

How many developers use AI tools?

83% of the developers who answered Stack Overflow's 2026 survey use at least one AI tool at work, and 73% of those who use AI coding assistants or agents use them every day. Coding assistants and agents are the most common kind (65.9% of respondents), ahead of general-purpose chat tools (62.5%). Among daily users, 30.9% spend four or more hours a day working with AI.

GitHub's platform data shows the same shift from the other side. By September 2026, more than 40% of pull requests on GitHub started with an agent's first draft, up from 17% in March. That was 110 million agent-started pull requests in September alone.

Do developers trust AI-generated code?

Only 6.6% of developers trust AI output for many tasks including important work decisions. The most common answer, at 48.0%, is that they trust it when they can easily verify the output. Another 16.3% trust it for low-risk tasks only, and 12.3% do not trust it for most work tasks. Developers act on that: 76.5% run AI-generated code locally before using it, and only 9.6% use answers as-is.

Trust shows up in where AI is used. 69.3% use it to generate code in a familiar area and 63.8% for debugging or refactoring, but only 19.9% use it for deploying, operating or troubleshooting production systems.

Claude Code is the most used AI coding tool in Stack Overflow's 2026 survey, used in the past year by 65.5% of respondents who answered the question, followed by GitHub Copilot at 58.7%. OpenAI Codex (29.5%) and Cursor (25.5%) follow at less than half those levels. Most developers mix tools: 40.5% use three to five distinct AI products in a typical week.

JavaScript is still the most used programming language, at 62.0% of Stack Overflow's 2026 respondents, its 12th straight year at the top. But Python has closed most of the gap, rising from 31.7% in 2017 to 58.0% in 2026, 4.0 points behind. TypeScript climbed from 9.4% to 43.8% over the same decade, while Java fell from 39.3% to 27.6%.

GitHub counts differently, by monthly contributors to repositories, and there TypeScript has been the most used language since 2025, with Python second and JavaScript third.

How many software developers are there in the U.S.?

There were 1,717,800 software developer jobs in the United States in 2025, according to the BLS, plus 187,600 software quality assurance analyst and tester jobs, for 1,905,400 in all. GitHub, which counts accounts rather than jobs, says it serves more than 225 million developers worldwide, including 38.3 million in the United States.

Is software development a growing career?

Yes: the BLS projects software developer employment to grow 10% from 2025 to 2035, against 3% for all occupations. That is 174,700 more software developer jobs, and about 106,100 openings a year for developers, QA analysts and testers combined, many of them to replace workers who change occupations or leave the labor force. The median software developer earned $135,980 in May 2025, about 2.7 times the $50,980 median for all U.S. workers.

Methodology & caveats

Stack Overflow figures come from each year's published results for all respondents. The surveys are online and self-selected, mostly reaching Stack Overflow's own users, so they describe that community rather than every developer. The 2026 survey had 30,903 valid responses from 169 countries, fielded June 23 to August 5, 2026. Many questions were optional, so each chart's base (n) differs. The coding-agent shares use only the 12,255 people who answered that question.

The Crossover's values are derived by adding published answer shares (for example, daily + weekly + monthly users in 2025). The 2026 "use AI" value is 100% minus the 17.2% who said they don't use AI tools. Stack Overflow changed the questions in 2026: use is now asked about "your role at work" instead of "your development process," and the favorability scale now reads "somewhat favorable" and "neutral." Treat the 2025–2026 step as indicative, not exact. Stack Overflow's own rounded headlines (77%, 72%, 60%, 62% favorable) differ slightly from the sums for 2023 and 2024.

GitHub's agent figures are platform measurements for pull requests with a detected agent signal, and its 225 million developers are accounts, not people in jobs. BLS employment and projections are for the United States only, use the 2025 base year, and are rounded to the nearest 100 jobs or whole percent. The "3×" and "2.7×" comparisons are our own arithmetic on those published figures. Gartner's 2026–27 software spending forecast was not used because its release could not be checked at the source.

Sources

  1. [1]
    Stack Overflow. 2023 Developer Survey: AI (AI tools in the development process; AI tool sentiment)https://survey.stackoverflow.co/2023/#ai
  2. [2]
    Stack Overflow. 2024 Developer Survey: AI (sentiment and usage)https://survey.stackoverflow.co/2024/ai
  3. [3]
    Stack Overflow. 2025 Developer Survey: AI (AI tools in the development process; AI tool sentiment)https://survey.stackoverflow.co/2025/ai
  4. [4]
    Stack Overflow. 2026 Developer Survey: AI data (fielded June 23 – August 5, 2026)https://survey.stackoverflow.co/2026/ai/data
  5. [5]
    Stack Overflow. 2026 Developer Survey: Methodology (30,903 valid responses from 169 countries)https://survey.stackoverflow.co/2026/methodology
  6. [6]
    GitHub. Octoverse: Commits, pushes, reach new highs in 2026 as developers build with agents (Oct 28, 2026)https://github.blog/news-insights/octoverse/octoverse-commits-pushes-reach-new-highs-in-2026-as-developers-build-with-agents/
  7. [7]
    U.S. Bureau of Labor Statistics. Occupational Outlook Handbook: Software Developers, Quality Assurance Analysts, and Testers (2025 data, 2025–35 projections)https://www.bls.gov/ooh/computer-and-information-technology/software-developers.htm
  8. [8]
    Stack Overflow. 2026 Developer Survey: Technology data (programming languages, 2017–2026 time series)https://survey.stackoverflow.co/2026/technology/data
Cite this graphicDEV.co. “Software Development Statistics (2026).” DEV.co Graphics, updated 2026-11-12. https://dev.co/graphics/software-development-statistics