Skip to content

Developer Survey 2026

The definitive report on the state of software development.

More than 30K technologists from 169 countries have shared their thoughts with us, and now it’s time to share everything we’ve learned with you. So let’s dive into this year’s Annual Developer Survey.

In the whirlwind that has been the last year of technological innovation and market uncertainty, we don’t blame you if you’re feeling burnt out. If keeping up with the latest and greatest in the tech world has been difficult for you, have no fear, because the Stack Overflow Annual Developer Survey is here!

For the sixteenth year, we’ve asked developers and technologists about everything from how they’re using AI to how happy they are at work to where they’re learning new skills. This year’s survey boils down to one question: How are you doing?

Categories
103
questions asked across 5 insightful categories
30,903
Responses
169
Countries reached
467
Technologies examined

Work

Well, it ain’t what it used to be. This year, we’re finding survey respondents are less happy in their work—the numbers are showing less happy folks and more unhappy ones. All that innovation and uncertainty can make it tough to feel comfortable in your job.

Work Job satisfaction + AI

So…how’s work going for you? 33% say they are not happy at work this year.

Dig deeper
Complacent at Work 45%, Not Happy at Work 33%, Happy at Work 22% · All Respondents · n = 18,87645%Complacent at Work33%Not Happy at Work22%Happy at Work
RespondentsPercent
Complacent at Work8,51645.1%
Not Happy at Work6,16132.6%
Happy at Work4,19922.2%

“AI has the potential to reshape the entire software and product development life cycle, but realizing that potential requires a foundational change to workflows, roles, and ownership.”

Stack Overflow CEO Prashanth Chandrasekar interview with McKinsey

Work Employer + technology details

Many are not taking this lying down: more and more technologists are finding freedom in freelance and self-employment.

The percentage of freelance or self-employed responses jumped from 3.9% to 10.5% just this year.
Dig deeper
10,000 or more employees 14%, 5,000 to 9,999 employees 5%, 1,000 to 4,999 employees 11%, 500 to 999 employees 6%, 100 to 499 employees 17%, 20 to 99 employees 17%, Less than 20 employees 17%, Just me 11%, and 1 more · All Respondents · n = 21,11514%10,000 or more employees5%5,000 to 9,999 employees11%1,000 to 4,999 employees6%500 to 999 employees17%100 to 499 employees17%20 to 99 employees17%Less than 20 employees11%Just me3%I don’t know
RespondentsPercent
10,000 or more employees2,94113.9%
5,000 to 9,999 employees1,0174.8%
1,000 to 4,999 employees2,40911.4%
500 to 999 employees1,3076.2%
100 to 499 employees3,47416.5%
20 to 99 employees3,67717.4%
Less than 20 employees3,55516.8%
Just me - I am a freelancer, sole proprietor, etc.2,21310.5%
I don’t know5222.5%
Stack Overflow CEO Prashanth Chandrasekar recently spoke to Computing’s Ctrl Alt Lead podcast about why this might be the case: “With AI, every individual becomes almost a manager of agents. That's a sea change from just an individual that's writing code.” It seems that agents are superpowering some developers' work, making it easier for them to set a solo course backed up by their own team of agents—instead of taking their decreasing satisfaction at work on the chin.

AI

How are technologists using AI?

AI AI usage

62% like using AI

To the surprise of no one, AI use has skyrocketed over the last year. Devs are using AI more than ever before in their daily work—80% of respondents from this year’s survey used AI at least an hour per day. And with increased usage has come increased favor: now more than 60% of respondents have a favorable attitude towards AI tool use in their work.
Dig deeper
Very favorable 32%, Somewhat favorable 30%, Neutral 15%, Somewhat unfavorable 15%, Very unfavorable 7%, Not sure 1% · All Respondents · n = 14,42832%Very favorable30%Somewhat favorable
RespondentsPercent
Very favorable4,56431.6%
Somewhat favorable4,38530.4%
Neutral2,20515.3%
Somewhat unfavorable2,11014.6%
Very unfavorable9946.9%
Not sure1701.2%

AI Trust in AI and other trends

How much do you trust the output from AI tools or AI agents as part of your workflow?

And technologists have figured out better ways to use their AI tools—and place more trust in them. This year, more than 87% of respondents had some level of trust in AI’s outputs, a huge increase from 31% last year. But that trust is conditional—48% trust AI only when it comes to low risk, easily verifiable tasks.
Dig deeper
When I can verify it 48%, Many tasks, not decisions 16%, Low-risk tasks only 16%, Don't trust it for most 12%, Many tasks and decisions 7%, Not sure or don't use AI 1% · All Respondents · n = 14,30448%When I can verify it16%Many tasks, not decisions16%Low-risk tasks only12%Don't trust it for most7%Many tasks and decisions1%Not sure or don't use AI
RespondentsPercent
I trust it when I can easily verify the output6,87248.0%
I trust it for many tasks, but not important work decisions2,32916.3%
I trust it for low-risk work tasks only2,32616.3%
I do not trust it for most work tasks1,75412.3%
I trust it for many tasks, including important work decisions9496.6%
Not sure / I do not use AI tools740.5%

AI Knowledge sources and trust

And how exactly are AI users verifying the outcomes of an AI-generated answers?

Well, 93% of our respondents think that it all comes down to citing your sources. AI technology may have improved by leaps and bounds over last year, but it’s responses aren’t trustworthy enough yet to take at face value.
Dig deeper
Very important 52%, Important 27%, Somewhat important 14% · All Respondents · n = 13,945
RespondentsPercent
Very important7,26952.1%
Important3,70126.5%
Somewhat important1,95614.0%

Technology

What's your favorite tech? It wouldn’t be a Stack Overflow Developer Survey if we didn’t include our technology leaderboard!

Technology Most popular technologies

Top programming languages used for AI shows Python leading at 39% usage

While the top-used technologies of the year—JavaScript, SQL, HTML/CSS, Python, and Bash/Shell—may not surprise you, how they are being used just might. For instance, when it comes to coding agents, AI seems to love Python above nearly all else, coming in at 39% usage.
Dig deeper
JavaScript 38%, SQL 30%, HTML/CSS 33%, Python 39%, Bash/Shell (all shells) 29%, TypeScript 30%, Java 15%, C# 16%, and 2 more · Used for AI · n = 14,099Python39%JavaScript38%HTML/CSS33%SQL30%TypeScript30%Bash/Shell (all shells)29%C#16%Java15%PowerShell15%C++11%
RespondentsPercent
JavaScript5,41938.4%
SQL4,20729.8%
HTML/CSS4,69233.3%
Python5,49539.0%
Bash/Shell (all shells)4,03828.6%
TypeScript4,29330.4%
Java2,05214.6%
C#2,27716.2%
PowerShell2,05714.6%
C++1,59511.3%

Technology Most popular technologies

Top programming languages used by those with 16+ years of professional work experience

For both the seasoned developer and the green AI-assisted developer alike, JavaScript comes out near the top, trailing SQL (the first-place winner) by just one point.
Dig deeper
JavaScript 62%, SQL 63%, HTML/CSS 56%, Python 53%, Bash/Shell (all shells) 52% · 16+ yrs work exp · n = 5,29663%SQL62%JavaScript56%HTML/CSS53%Python52%Bash/Shell (all shells)
RespondentsPercent
JavaScript3,28262.0%
SQL3,33763.0%
HTML/CSS2,98756.4%
Python2,81853.2%
Bash/Shell (all shells)2,74051.7%

Technology Build vs. AI

When it comes to building vs. buying—the age-old trolley problem of software development—only 19% of our respondents are building their own tools to replace vendors.

However, of those that are building instead of buying, over half are using AI tools to help them do it, showing AI’s utility for developers looking to bring their SaaS in-house.
Dig deeper
Small scripts/automations 77%, Team-level internal tools 63%, Customer-facing products 54%, Cross-team/platform tools 46%, Replacing paid vendors 19% · All Respondents · n = 13,33877%Small scripts/automations
RespondentsPercent
Small scripts/automations10,30477.3%
Team-level internal tools8,39863.0%
Customer-facing products7,25454.4%
Cross-team/platform tools6,13046.0%
Replacing paid vendors2,48218.6%

Community

What’s the developer community up to? Whether you’ve become best buds with an AI-powered chatbot or have taken up the anti-AI pitchforks alongside the other luddites, we can all recognize how much AI has changed. We saw that very clearly reflected in this year’s survey—especially in how developers are engaging with knowledge and community.

Community Finding and trusting answers

How do you search for answers?

While the lion’s share of respondents still seek guidance from traditional search tools when they face a new challenge, nearly 70% of technologists also use AI agents to help them solve problems—beating out maintained repositories and trusted humans as direct sources of learning.
Dig deeper
RespondentsPercent
Use online search tools to find general guidance and/or discourse13,77482.7%
Ask an AI agent11,64369.9%
Go directly to a maintained repository or more than one and search within its contents (this could be a repository like Wikipedia or IMDB or GitHub projects)7,28843.7%
Send a message to a human I trust directly4,80328.8%
Post a message in a group text or private discussion among humans I know2,46214.8%

Community Knowledge sources and trust

When you need to answer a work-related question, which sources do you use most often?

When it comes to work-related questions, however, developers are still turning to the humans in their loops—also known as coworkers and teammates—first in order to get the answers they need (72%), with code repositories (63%) and internal documentation (60%) following as close runner-ups.
Dig deeper
Coworkers or teammates 72%, Code and comments 63%, Internal docs and wikis 60%, Internal chat tools 45%, Official docs 31% · All Respondents · n = 14,46272%Coworkers or teammates63%Code and comments60%Internal docs and wikis45%Internal chat tools31%Official docs
RespondentsPercent
Coworkers or teammates10,40571.9%
Code repositories or code comments9,06562.7%
Internal documentation (i.e. Design, product, or planning docs), wiki, or knowledge base8,68760.1%
Internal chat tools, such as Slack or Teams6,57245.4%
Official docs4,41530.5%

Community Finding and trusting answers

Nearly two-thirds of developers rely less on Stack Overflow for straightforward questions due to AI, with 29% asking fewer questions overall.

64% visiting less for simple questions
Dig deeper
Visit less for simple questions 64%, Ask fewer questions 29%, Contribute less 27%, No change 22%, Used to verify 16%, Other 6%, Ask advanced questions 6%, Visit more via AI 6%, and 1 more · All Respondents · n = 16,98564%Visit less for simple questions
RespondentsPercent
Visit less for simple questions10,89264.1%
Ask fewer questions4,91028.9%
Contribute less4,49626.5%
No change3,70421.8%
Visit more for verification (for example, source attribution)2,70715.9%
Other1,0846.4%
Ask more advanced questions9675.7%
Visit SO more because AI-generated answers lead you there9655.7%
Contribute more2031.2%

Knowledge

What does everyone need to know? In software development, context seems to be the reigning king this year, whether or not AI agents are involved. But the right context is not always reaching developers at the right time.

Knowledge Context Challenges

What gets in the way of you getting the context you need for work?

Over 63% of developers find incomplete information to be a barrier to getting the right context at work, while 79% regularly discover the important context they need only after the fact. A lot of time goes into that context search, 75% spent five plus hours searching for answers.
Dig deeper
Incomplete information 63%, Context in people’s heads 61%, Information is outdated 56%, Across too many tools 53%, Don't know where to look 31% · All Respondents · n = 12,37463%Incomplete information61%Context in people’s heads56%Information is outdated53%Across too many tools31%Don't know where to look
RespondentsPercent
Information is incomplete7,82563.2%
Important context lives in people’s heads7,54160.9%
Information is outdated6,98956.5%
Information is spread across too many tools6,60353.4%
I do not know where to look3,81630.8%

Knowledge Context Challenges

How often do you discover important work context only after you have already started or completed a task?

This has left teams with a bit of a problem of their own creation. Developers have relied on the expert knowledge from resources like technical documentation, Stack Overflow, or online search to drive their work, but, as reported in a pulse survey earlier this year, we know low-effort documentation is leading to more and more dissatisfaction in AI-driven work.
Dig deeper
Very often 12%, Often 23%, Sometimes 43%, Rarely 17% · All Respondents · n = 12,68743%Sometimes
RespondentsPercent
Very often1,53912.1%
Often2,96423.4%
Sometimes5,46543.1%
Rarely2,13616.8%

“AI is forcing software organizations to document the judgment they previously relied on people to supply.”

Knowledge AI adoption and cost

31% of respondents say that the accuracy of AI answers is important to the adoption or expansion of AI tool use.

Dig deeper
Useful, accurate results 31%, Security & privacy 29%, Price matches the value 27%, Legal & compliance 22%, Not sure 22% · All Respondents · n = 11,46231%Useful, accurate results29%Security & privacy27%Price matches the value22%Legal & compliance22%Not sure
RespondentsPercent
The tool produces useful and accurate results3,52030.7%
The tool meets security, privacy requirements3,29028.7%
The price is acceptable for the value it provides3,09027.0%
The tool meets legal or compliance requirements2,55722.3%
Not sure2,52222.0%

Knowledge Context Challenges

Project goals or requirements (85%) and code, repositories, or technical documentation (73%) are the top important sources for context at work

And the most important context for AI agents and assistants to have? Why, your internal projects, of course! Project requirements (85%) and the code and docs themselves (73%) are the two most important contexts that developers need their AI agents to have.
Dig deeper
Project goals 85%, Code and documentation 73%, Prior decisions 44%, Related tickets 37%, Business goals 33%, Pull requests and history 26%, and 8 more · All Respondents · n = 12,678
RespondentsPercent
Project goals or requirements10,80685.2%
Code, repositories, or technical documentation9,29773.3%
Prior decisions and rationale5,58044.0%
Related tickets, tasks, or issues4,67936.9%
Business goals or product strategy4,18933.0%
Pull requests, commit history, or release notes3,33226.3%
Customer or user feedback3,29626.0%
Team norms, preferences, or ways of working3,18325.1%
Compliance, security, or policy requirements2,49819.7%
Current status or ownership2,49019.6%
Past discussions in chat, email, or meetings2,00015.8%
Data, dashboards, or reports9327.4%
I do not usually need additional context2662.1%
Other790.6%