In February 2020 nearly 65,000 developers told us how they learn and level up, which tools they’re using, and what they want.
Read the overview →Methodology →
In February 2020 nearly 65,000 developers told us how they learn and level up, which tools they’re using, and what they want.
Read the overview →Methodology →This year, we focused on seeking diverse representation while asking for information ranging from technologies and behavior to questions that will help us improve the Stack Overflow community for everybody who codes.
For almost a decade, Stack Overflow’s annual Developer Survey held the honor of being the largest survey of people who code around the world. This year, rather than aiming to be the biggest, we set out to make our survey more representative of the diversity of programmers worldwide. That said, the survey is still big. This year’s survey was taken by nearly 65,000 people.
In our efforts to reach beyond the Stack Overflow network and seek representation from a greater diversity of coders, we advertised the survey less on our own channels than in previous years and sought ways to earn responses from those who may not frequent our sites. This approach included social promotion and outreach to underrepresented coders.
While we saw a lift in underrepresented groups, the difference in representation isn’t as large as we had hoped. There was an uptick in some race and ethnicity groups, notably those of Hispanic or Latino/a/x and Black or of African descent, while other races and ethnicities remained similar or decreased. Similarly, we saw a slight increase in female-gendered respondents, while non-binary, genderqueer, or non-conforming remained the same. We acknowledge that we have a lot of work to do, and the data we obtain in our annual survey helps us make changes and set goals to improve the welcomeness and inclusiveness of our community.
Look for this icon, which highlights differences between developer demographics.
Working with the data at hand, we broke down our analysis by demographics where applicable. Look for the icon to see where demographics have an interesting impact. Also be sure to check out the topics that were new to this year’s survey, like questions regarding DevOps and working overtime.
We also need to point out that this year’s survey was taken in February, before COVID-19 was declared a pandemic by the World Health Organization and before the virus impacted every country in the world. Please keep the timing of the survey in mind when reviewing information such as job and salary data.
Finally, for those who want to dive into the results yourself, the anonymized results of the survey are available for download under the Open Database License (ODbL). We look forward to seeing what you find—if you share on social media, be sure to tag us!
Key Results
Here are a few of the top takeaways from this year’s results.
After a consistent rise over the last five years, Python fell from second last year to third this year on the list of most loved technologies, being beat out by TypeScript. Rust held the top spot for most loved technology for the fifth year in a row.
Most loved languages→Site reliability engineers and DevOps specialists remain among the highest paid individual contributor roles. 80% of respondents believe that DevOps is at least somewhat important, and 44% work at organizations with at least one dedicated DevOps employee.
Global salaries→52% of respondents think “Hello, old friend” when they search for a coding solution online and find that the first result link is purple because they’ve already visited the link.
Already visited feeling→When asked what steps to take when stuck on a coding problem, 90% of respondents indicated they visit Stack Overflow.
When you get stuck→More than 75% of developers work overtime at least occasionally -- one to two days per quarter. 25% work overtime 1-2 days per week or more.
Overtime→Australia respondents reported the highest average amount of coding experience at 16.9 years, followed by developers in United Kingdom and United States. In correlation, respondents from the United States and United Kingdom maintain the highest average age, at 33.7 and 33.1 years, respectively.
Experience by country→0.3% of respondents had never visited Stack Overflow before taking the survey.
Visiting Stack Overflow→More than 40% of respondents reported that they are members of other online developer communities beyond Stack Overflow.
Other developer communities→More than 15% of people find Stack Overflow at least somewhat more welcome than last year. We still have work to do, but it’s a start.
Engaging together→We still see evidence that people of color are underrepresented among professional developers, but we do see some improvement when we include all developers, not just those who code professionally.
Race and ethnicity→What we know about the developers who are writing the script for the future
Each month, about 50 million people visit Stack Overflow to learn, share, and build their careers. Industry estimates suggest that 20-25 million of these people are professional developers and university-level students. The vast majority of our survey respondents this year said they are professional developers or who code sometimes as part of their work or students preparing for such a career.
See ourMethodology section for details on how developers around the world accessed our survey.
About 55% of respondents identify as full-stack developers, and about 20% consider themselves mobile developers. The median number of developer type identifications per respondent this year is three, and the most common combinations include back-end, front-end, and full-stack developer. Pairs that are highly correlated include database administrator and system administrator, DevOps specialist and site reliability engineer, academic researcher and scientist, and designer and front-end developer.
Survey weighting is an approach used to analyze survey data when the survey sample doesn't match the underlying population well. For example, in our survey this year, 12% of US respondents identify as women, but data from the US Bureau of Labor Statistics estimates that women's participation in the software developer workforce is about twice that, more like 20%. We can use survey weighting to adjust for the mismatch between our survey sample and the population of developers. We know that there is a difference in developer type representation by gender, so let's compare the overall proportions in our raw results for the United States with weighted proportions, assuming that we undersampled gender minorities at the rate indicated by the BLS report. When we use weighting, we see small increases in the representation of developer roles that have the most representation from women, like Data Scientists and Academic Researchers, and decreases in others with low representation from women, like DevOps.
We know there are more ways in which our survey sample doesn't match the underlying population of developers than only gender (including frequency of use of Stack Overflow), and the United States is not the only country for which we expect such a mismatch. The reason we're using this specific example of weighting here is that it is one where we know we have systemic sampling issues and we have an estimate about the expected population proportion. We can demonstrate the effect of our survey sample on our results, both in direction and magnitude.
| Developer, back-end | 55.2% |
| Developer, full-stack | 54.9% |
| Developer, front-end | 37.1% |
| Developer, desktop or enterprise applications | 23.9% |
| Developer, mobile | 19.2% |
| DevOps specialist | 12.1% |
| Database administrator | 11.6% |
| Designer | 10.8% |
| System administrator | 10.6% |
| Developer, embedded applications or devices | 9.6% |
| Data or business analyst | 8.2% |
| Data scientist or machine learning specialist | 8.1% |
| Developer, QA or test | 8.0% |
| Engineer, data | 7.6% |
| Academic researcher | 7.2% |
| Educator | 5.9% |
| Developer, game or graphics | 5.6% |
| Engineering manager | 5.5% |
| Product manager | 5.1% |
| Scientist | 4.2% |
| Engineer, site reliability | 3.9% |
| Senior executive/VP | 2.7% |
| Marketing or sales professional | 1.3% |
| Developer, full-stack | 58.0% |
| Developer, back-end | 52.0% |
| Developer, front-end | 36.2% |
| Developer, desktop or enterprise applications | 23.9% |
| Developer, mobile | 13.9% |
| DevOps specialist | 13.9% |
| Database administrator | 12.2% |
| System administrator | 11.6% |
| Designer | 11.5% |
| Data or business analyst | 9.8% |
| Developer, embedded applications or devices | 9.3% |
| Engineer, data | 9.2% |
| Developer, QA or test | 8.8% |
| Data scientist or machine learning specialist | 8.5% |
| Engineering manager | 8.1% |
| Engineer, site reliability | 5.8% |
| Developer, game or graphics | 5.4% |
| Academic researcher | 5.4% |
| Educator | 5.1% |
| Product manager | 5.1% |
| Scientist | 4.6% |
| Senior executive/VP | 3.7% |
| Marketing or sales professional | 1.7% |
| Developer, full-stack | 57.4% |
| Developer, back-end | 51.0% |
| Developer, front-end | 36.5% |
| Developer, desktop or enterprise applications | 22.9% |
| Developer, mobile | 13.7% |
| DevOps specialist | 13.1% |
| Database administrator | 11.8% |
| Designer | 11.8% |
| System administrator | 11.1% |
| Data or business analyst | 9.9% |
| Engineer, data | 9.0% |
| Developer, embedded applications or devices | 8.8% |
| Developer, QA or test | 8.8% |
| Data scientist or machine learning specialist | 8.6% |
| Engineering manager | 7.7% |
| Academic researcher | 5.5% |
| Engineer, site reliability | 5.5% |
| Developer, game or graphics | 5.4% |
| Educator | 5.3% |
| Product manager | 5.1% |
| Scientist | 4.7% |
| Senior executive/VP | 3.7% |
| Marketing or sales professional | 1.8% |
Many developers work on code outside of work. About 78% of our respondents say that they code as a hobby. Other responsibilities outside of software can reduce developers' engagement in coding as a hobby; developers who say they have children or other caretaking responsibilities are less likely to code as a hobby. Respondents who are women are also less likely to say they code as a hobby.
| Yes | 78.2% |
| No | 21.8% |
| Yes | 77.9% |
| No | 22.1% |
| Yes | 76.5% |
| No | 23.5% |
There is a wide range of experience among developers who visit Stack Overflow, from seasoned developers who learned to code more than 30 years ago (approximately 15%), to a sizable percentage of developers (17%) who learned how to code less than five years ago. Of the professional developers on Stack Overflow, approximately 40% learned to code less than 10 years ago. See more on how theseexperience levels vary by gender.
| Less than 5 years | 17.0% |
| 5 to 9 years | 30.0% |
| 10 to 14 years | 20.1% |
| 15 to 19 years | 11.4% |
| 20 to 24 years | 8.5% |
| 25 to 29 years | 4.4% |
| 30 to 34 years | 3.5% |
| 35 to 39 years | 2.7% |
| 40 to 44 years | 1.6% |
| 45 to 49 years | 0.4% |
| 50 years or more | 0.3% |
| Less than 5 years | 10.5% |
| 5 to 9 years | 29.2% |
| 10 to 14 years | 22.7% |
| 15 to 19 years | 13.2% |
| 20 to 24 years | 9.8% |
| 25 to 29 years | 5.1% |
| 30 to 34 years | 4.0% |
| 35 to 39 years | 3.0% |
| 40 to 44 years | 1.8% |
| 45 to 49 years | 0.4% |
| 50 years or more | 0.3% |
65% of respondents have been coding professionally for less than 10 years.
| Less than 5 years | 39.6% |
| 5 to 9 years | 26.8% |
| 10 to 14 years | 14.7% |
| 15 to 19 years | 7.6% |
| 20 to 24 years | 6.0% |
| 25 to 29 years | 2.4% |
| 30 to 34 years | 1.6% |
| 35 to 39 years | 0.8% |
| 40 to 44 years | 0.4% |
| 45 to 49 years | 0.1% |
| 50 years or more | 0.1% |
Technical executives and engineering managers tend to have the most professional coding experience. Among the individual contributor roles, the most experienced developers tend to be system administrators, database administrators, and developers who create desktop and embedded applications. On the other end of the spectrum, web developers, academic researchers, and data scientists tend to have fewer years of experience. Part of this could be explained by the proliferation of coding bootcamps that teach web development and the amount of data scientists entering the field from academia.
| Senior executive/VP | 16.5 |
| Engineering manager | 13.8 |
| System administrator | 11.0 |
| Developer, embedded applications or devices | 10.9 |
| Database administrator | 10.8 |
| Developer, desktop or enterprise applications | 10.8 |
| Engineer, site reliability | 10.5 |
| DevOps specialist | 10.5 |
| Educator | 10.5 |
| Data or business analyst | 10.0 |
| Scientist | 9.9 |
| Designer | 9.8 |
| Developer, game or graphics | 9.2 |
| Engineer, data | 9.1 |
| Developer, QA or test | 8.9 |
| Developer, back-end | 8.9 |
| Developer, full-stack | 8.7 |
| Developer, mobile | 8.4 |
| Data scientist or machine learning specialist | 8.2 |
| Developer, front-end | 8.2 |
| Academic researcher | 8.1 |
Of all of the respondents, over 54% wrote their first line of code, whether it was a web page or a hello world program, by the age of 16. People who wrote their first line of code in their 20s accounted for 13% of the respondents. When looking at the average age by country, respondents from countries such as Brazil and India tend to start writing code a full two years later compared to developers in countries such as Poland and Germany, who on average start coding by the age of 15.
| Younger than 10 years | 8.9% |
| 10 to 11 years old | 10.0% |
| 12 to 13 years old | 16.0% |
| 14 to 15 years old | 19.2% |
| 16 to 17 years old | 16.3% |
| 18 to 19 years old | 14.7% |
| 20 to 21 years old | 6.3% |
| 22 to 23 years old | 3.0% |
| 24 to 25 years old | 2.1% |
| 26 to 27 years old | 1.0% |
| 28 to 29 years old | 0.7% |
| 30 years old or older | 1.7% |
| India | 16.9 |
| Brazil | 16.0 |
| France | 15.1 |
| United States | 15.0 |
| Canada | 14.9 |
| Netherlands | 14.6 |
| Australia | 14.4 |
| United Kingdom | 14.3 |
| Poland | 14.2 |
| Germany | 14.1 |
| Woman | 16.9 |
| Man | 15.2 |
| Non-binary, genderqueer, or gender non-conforming | 13.5 |
Approximately 75% of respondents worldwide completed at least the equivalent of a bachelor's degree or higher. This is consistent with what we've seen in previous years.
| Bachelor’s degree (B.A., B.S., B.Eng., etc.) | 46.2% |
| Master’s degree (M.A., M.S., M.Eng., MBA, etc.) | 22.8% |
| Some college/university study without earning a degree | 12.6% |
| Secondary school (e.g. American high school, German Realschule or Gymnasium, etc.) | 8.3% |
| Associate degree (A.A., A.S., etc.) | 3.2% |
| Other doctoral degree (Ph.D., Ed.D., etc.) | 2.9% |
| Primary/elementary school | 1.6% |
| Professional degree (JD, MD, etc.) | 1.4% |
| I never completed any formal education | 0.9% |
| Bachelor’s degree (B.A., B.S., B.Eng., etc.) | 49.3% |
| Master’s degree (M.A., M.S., M.Eng., MBA, etc.) | 25.5% |
| Some college/university study without earning a degree | 11.5% |
| Secondary school (e.g. American high school, German Realschule or Gymnasium, etc.) | 4.5% |
| Other doctoral degree (Ph.D., Ed.D., etc.) | 3.3% |
| Associate degree (A.A., A.S., etc.) | 3.2% |
| Professional degree (JD, MD, etc.) | 1.4% |
| I never completed any formal education | 0.7% |
| Primary/elementary school | 0.5% |
There are a variety of academic paths to becoming a professional software developer. Of the respondents that write code professionally and studied at the university level, over 62% have a degree in computer science, computer engineering, or software engineering and just under 10% have a degree in another engineering field. Interestingly enough, almost 10% of the respondents have a business related degree or a degree in a humanities, social science, or fine arts field of study.
| Computer science, computer engineering, or software engineering | 61.9% |
| Another engineering discipline (such as civil, electrical, mechanical, etc.) | 9.3% |
| Information systems, information technology, or system administration | 8.0% |
| A natural science (such as biology, chemistry, physics, etc.) | 4.3% |
| Mathematics or statistics | 3.6% |
| Web development or web design | 3.5% |
| A business discipline (such as accounting, finance, marketing, etc.) | 2.7% |
| A humanities discipline (such as literature, history, philosophy, etc.) | 2.0% |
| A social science (such as anthropology, psychology, political science, etc.) | 1.8% |
| Fine arts or performing arts (such as graphic design, music, studio art, etc.) | 1.4% |
| I never declared a major | 0.9% |
| A health science (such as nursing, pharmacy, radiology, etc.) | 0.5% |
| Computer science, computer engineering, or software engineering | 62.6% |
| Another engineering discipline (such as civil, electrical, mechanical, etc.) | 9.3% |
| Information systems, information technology, or system administration | 7.9% |
| A natural science (such as biology, chemistry, physics, etc.) | 4.4% |
| Mathematics or statistics | 3.6% |
| Web development or web design | 3.3% |
| A business discipline (such as accounting, finance, marketing, etc.) | 2.6% |
| A humanities discipline (such as literature, history, philosophy, etc.) | 2.0% |
| A social science (such as anthropology, psychology, political science, etc.) | 1.8% |
| Fine arts or performing arts (such as graphic design, music, studio art, etc.) | 1.4% |
| I never declared a major | 0.7% |
| A health science (such as nursing, pharmacy, radiology, etc.) | 0.4% |
Almost 85% of the respondents that are professional developers feel that formal education is at least somewhat important, which is contrary to the popular idiom that you don't need formal education to become a developer. However, almost 16% believe that it is not at all important or necessary.
| Critically important | 9.8% |
| Very important | 24.5% |
| Fairly important | 26.2% |
| Somewhat important | 23.5% |
| Not at all important/not necessary | 16.1% |
| Critically important | 9.7% |
| Very important | 24.4% |
| Fairly important | 26.4% |
| Somewhat important | 23.7% |
| Not at all important/not necessary | 15.8% |
Consistent with the data from last year, we still see evidence that people of color are underrepresented among professional developers. However, we see some improvement when we look at all respondents—not just the ones who code professionally. Despite a gradual change year over year, there is still much work to do to increase participation rates.
| White or of European descent | 68.3% |
| South Asian | 10.4% |
| Hispanic or Latino/a/x | 7.6% |
| Middle Eastern | 4.9% |
| East Asian | 4.6% |
| Black or of African descent | 4.5% |
| Southeast Asian | 4.5% |
| Multiracial | 1.7% |
| Biracial | 1.2% |
| Indigenous (such as Native American, Pacific Islander, or Indigenous Australian) | 0.8% |
| White or of European descent | 70.7% |
| South Asian | 9.6% |
| Hispanic or Latino/a/x | 7.8% |
| Middle Eastern | 4.8% |
| East Asian | 4.2% |
| Southeast Asian | 3.9% |
| Black or of African descent | 3.6% |
| Multiracial | 1.7% |
| Biracial | 1.2% |
| Indigenous (such as Native American, Pacific Islander, or Indigenous Australian) | 0.8% |
When looking at gender identity by country, we see various participation rates of professional developers who are women. Consistent with last year's survey, women developers account for almost 12% of developers in the US. In countries such as Germany, Brazil, and Poland, the participation rate is about half of that, which goes to show there is still much work to do to reach appropriate gender representation in the field. Among the respondents that code professionally, almost 92% are men.
| United States | 11.8% |
| Canada | 11.0% |
| United Kingdom | 10.9% |
| Australia | 10.1% |
| Netherlands | 8.4% |
| France | 8.0% |
| India | 7.0% |
| Germany | 6.5% |
| Brazil | 5.8% |
| Poland | 4.7% |
| Man | 91.5% |
| Woman | 8.0% |
| Non-binary, genderqueer, or gender non-conforming | 1.2% |
| Man | 91.7% |
| Woman | 7.7% |
| Non-binary, genderqueer, or gender non-conforming | 1.2% |
Approximately 1% of this year’s respondents that write code professionally are transgender.
| No | 99.0% |
| Yes | 1.0% |
| No | 99.1% |
| Yes | 0.9% |
We see varying representation from men and women in different developer roles on our survey. All categories have dramatically more developers who identify as men than women, but the ratio of men to women varies. Developer types above the line have respondents that are more likely than average to be men, and those below the dotted line have respondents who are more likely than average to be women. Developers who are data scientists or academic researchers are about 10 times more likely to be men than women, while developers who are system admins or DevOps specialists are 25-30 times more likely to be men than women. Women have the highest representation as front-end developers, designers, data scientists, data analysts, QA or test developers, scientists, and educators.
When we break down differences in years since learning to code by gender, we notice some retention problems. We see a big drop off at the 10-14 year mark when compared to men, though we've seen some improvement from last year's survey. This is consistent with other research that women leave tech jobs at higher rates than men. If we truly want to make a difference and see gender parity in the industry that is reflective of society, retention is key. It is important to not only hire people from diverse backgrounds, but to also create an environment where they feel included and can thrive.
| Less than 5 years | 15.4% |
| 5 to 9 years | 29.2% |
| 10 to 14 years | 20.5% |
| 15 to 19 years | 12.0% |
| 20 to 24 years | 9.0% |
| 25 to 29 years | 4.7% |
| 30 to 34 years | 3.8% |
| 35 to 39 years | 2.9% |
| 40 to 44 years | 1.7% |
| 45 to 49 years | 0.4% |
| 50 years or more | 0.3% |
| Less than 5 years | 25.2% |
| 5 to 9 years | 34.7% |
| 10 to 14 years | 18.1% |
| 15 to 19 years | 8.2% |
| 20 to 24 years | 6.6% |
| 25 to 29 years | 2.5% |
| 30 to 34 years | 2.0% |
| 35 to 39 years | 1.3% |
| 40 to 44 years | 1.0% |
| 45 to 49 years | 0.3% |
| 50 years or more | 0.1% |
| Less than 5 years | 15.7% |
| 5 to 9 years | 32.1% |
| 10 to 14 years | 21.6% |
| 15 to 19 years | 10.2% |
| 20 to 24 years | 9.4% |
| 25 to 29 years | 3.4% |
| 30 to 34 years | 3.6% |
| 35 to 39 years | 1.9% |
| 40 to 44 years | 1.1% |
| 45 to 49 years | 0.2% |
| 50 years or more | 0.6% |
Participants’ responses regarding their sexual orientation are consistent with previous years.
| Straight / Heterosexual | 92.1% |
| Bisexual | 5.7% |
| Gay or Lesbian | 2.7% |
| Queer | 1.5% |
| Straight / Heterosexual | 92.6% |
| Bisexual | 5.2% |
| Gay or Lesbian | 2.6% |
| Queer | 1.4% |
Among the respondents, almost 15% said they have some type of anxiety, mood, or emotional disorder. When looking at differences in physical ability, around 2% of respondents are differently-abled, such as being blind / having difficulty seeing or being deaf / having difficulty hearing. This underscores the importance of creating accessible software and creating companies that accomodate differently-abled people.
| I have an anxiety disorder | 7.2% |
| I have a mood or emotional disorder (e.g. depression, bipolar disorder) | 7.2% |
| I have a concentration and/or memory disorder (e.g. ADHD) | 5.4% |
| I have autism / an autism spectrum disorder (e.g. Asperger's) | 2.3% |
| I am blind / have difficulty seeing | 1.1% |
| I am deaf / hard of hearing | 0.7% |
| I am unable to / find it difficult to walk or stand without assistance | 0.3% |
| I am unable to / find it difficult to type | 0.2% |
Of the respondents that are professional developers, 70% are under 35 and about 5% are 50 years old or older.
| Younger than 15 years | 0.5% |
| 15 to 19 years | 5.4% |
| 20 to 24 years | 20.3% |
| 25 to 29 years | 26.5% |
| 30 to 34 years | 19.4% |
| 35 to 39 years | 12.4% |
| 40 to 44 years | 6.7% |
| 45 to 49 years | 3.9% |
| 50 to 54 years | 2.3% |
| 55 to 59 years | 1.4% |
| 60 years and older | 1.3% |
| Younger than 15 years | 0.0% |
| 15 to 19 years | 1.2% |
| 20 to 24 years | 16.6% |
| 25 to 29 years | 29.5% |
| 30 to 34 years | 21.9% |
| 35 to 39 years | 14.0% |
| 40 to 44 years | 7.5% |
| 45 to 49 years | 4.2% |
| 50 to 54 years | 2.5% |
| 55 to 59 years | 1.5% |
| 60 years and older | 1.1% |
When we break down the age of the survey respondents by country, we see that developers in North America and Western Europe tend to skew older and have more coding experience compared to other regions.
| United States | 33.7 |
| United Kingdom | 33.1 |
| Canada | 32.2 |
| Netherlands | 31.9 |
| Germany | 30.9 |
| France | 30.4 |
| Brazil | 29.4 |
| Poland | 28.9 |
| India | 26.0 |
| Australia | 16.9 |
| United Kingdom | 16.1 |
| United States | 15.8 |
| Netherlands | 15.0 |
| Canada | 14.4 |
| Germany | 14.3 |
| France | 13.0 |
| Poland | 11.5 |
| Brazil | 11.5 |
| India | 8.1 |
The tools of the trade
Unsurprisingly, for the eighth year in a row, JavaScript has maintained it's stronghold as the most commonly used programming language. Going further down the list, we also see moderate gains for TypeScript, edging out C in terms of popularity. Additionally, Ruby, once in the top 10 of this list as recently as 2017, has declined, being surpassed by newer, trendier technologies such as Go and Kotlin.
| JavaScript | 67.7% |
| HTML/CSS | 63.1% |
| SQL | 54.7% |
| Python | 44.1% |
| Java | 40.2% |
| Bash/Shell/PowerShell | 33.1% |
| C# | 31.4% |
| PHP | 26.2% |
| TypeScript | 25.4% |
| C++ | 23.9% |
| C | 21.8% |
| Go | 8.8% |
| Kotlin | 7.8% |
| Ruby | 7.1% |
| Assembly | 6.2% |
| VBA | 6.1% |
| Swift | 5.9% |
| R | 5.7% |
| Rust | 5.1% |
| Objective-C | 4.1% |
| Dart | 4.0% |
| Scala | 3.6% |
| Perl | 3.1% |
| Haskell | 2.1% |
| Julia | 0.9% |
| JavaScript | 69.7% |
| HTML/CSS | 62.4% |
| SQL | 56.9% |
| Python | 41.6% |
| Java | 38.4% |
| Bash/Shell/PowerShell | 34.8% |
| C# | 32.3% |
| TypeScript | 28.3% |
| PHP | 25.8% |
| C++ | 20.5% |
| C | 18.2% |
| Go | 9.4% |
| Kotlin | 8.0% |
| Ruby | 7.5% |
| VBA | 6.2% |
| Swift | 6.1% |
| R | 5.5% |
| Assembly | 4.9% |
| Rust | 4.8% |
| Objective-C | 4.4% |
| Scala | 3.9% |
| Dart | 3.7% |
| Perl | 3.3% |
| Haskell | 1.8% |
| Julia | 0.9% |
When focusing purely on web frameworks, we see that jQuery is still king, but is slowly losing ground to React.js and Angular year over year. We do see some consolidation, as more than 35% of respondents use jQuery, React, a version of Angular (combining Angular, which represents Angular 2+, and Angular.js) or a flavor of ASP.NET (ASP.NET or ASP.NET Core).
| jQuery | 43.3% |
| React.js | 35.9% |
| Angular | 25.1% |
| ASP.NET | 21.9% |
| Express | 21.2% |
| ASP.NET Core | 19.1% |
| Vue.js | 17.3% |
| Spring | 16.4% |
| Angular.js | 16.1% |
| Django | 14.2% |
| Flask | 14.2% |
| Laravel | 11.1% |
| Ruby on Rails | 7.0% |
| Symfony | 4.4% |
| Gatsby | 4.0% |
| Drupal | 3.2% |
| jQuery | 43.3% |
| React.js | 36.8% |
| Angular | 26.5% |
| ASP.NET | 22.9% |
| Express | 20.9% |
| ASP.NET Core | 20.3% |
| Vue.js | 17.8% |
| Spring | 17.4% |
| Angular.js | 17.0% |
| Flask | 13.6% |
| Django | 13.2% |
| Laravel | 11.1% |
| Ruby on Rails | 7.2% |
| Symfony | 4.5% |
| Gatsby | 4.1% |
| Drupal | 3.3% |
Similar to last year, we asked about many of the other miscellaneous technologies that developers are using. For the second year in a row, Node.js takes the top spot, as it is used by half of the respondents. We also see growth across the board in the popularity of data analysis and machine learning technologies such as Pandas, TensorFlow, and Torch/PyTorch.
| Node.js | 51.4% |
| .NET | 35.1% |
| .NET Core | 26.7% |
| Pandas | 15.5% |
| TensorFlow | 11.5% |
| React Native | 11.5% |
| Unity 3D | 10.9% |
| Ansible | 7.3% |
| Flutter | 7.2% |
| Teraform | 6.2% |
| Keras | 6.2% |
| Cordova | 6.0% |
| Xamarin | 5.8% |
| Apache Spark | 5.2% |
| Torch/PyTorch | 4.6% |
| Hadoop | 4.5% |
| Unreal Engine | 3.3% |
| Puppet | 2.3% |
| Chef | 1.8% |
| Node.js | 51.9% |
| .NET | 35.9% |
| .NET Core | 27.9% |
| Pandas | 14.7% |
| React Native | 11.8% |
| TensorFlow | 10.4% |
| Unity 3D | 8.7% |
| Ansible | 8.1% |
| Teraform | 7.0% |
| Flutter | 6.6% |
| Cordova | 6.4% |
| Xamarin | 6.0% |
| Keras | 5.6% |
| Apache Spark | 5.4% |
| Hadoop | 4.7% |
| Torch/PyTorch | 4.1% |
| Puppet | 2.5% |
| Unreal Engine | 2.5% |
| Chef | 2.0% |
When looking at database technologies, the results are mostly consistent with what we observed last year. MySQL has maintained the top spot, followed by PostgreSQL and Microsoft SQL Server. However, we see some slight growth in the popularity of Firebase, which edged out Elasticsearch this year.
| MySQL | 55.6% |
| PostgreSQL | 36.1% |
| Microsoft SQL Server | 33.0% |
| SQLite | 31.2% |
| MongoDB | 26.4% |
| Redis | 18.3% |
| MariaDB | 16.8% |
| Oracle | 16.5% |
| Firebase | 14.4% |
| Elasticsearch | 13.8% |
| DynamoDB | 7.1% |
| Cassandra | 3.3% |
| IBM DB2 | 2.9% |
| Couchbase | 1.9% |
| MySQL | 53.5% |
| PostgreSQL | 38.5% |
| Microsoft SQL Server | 34.8% |
| SQLite | 30.6% |
| MongoDB | 26.7% |
| Redis | 20.5% |
| MariaDB | 16.9% |
| Oracle | 16.3% |
| Elasticsearch | 15.5% |
| Firebase | 13.9% |
| DynamoDB | 7.8% |
| Cassandra | 3.6% |
| IBM DB2 | 2.9% |
| Couchbase | 2.0% |
Linux and Windows maintain the top spots for most popular platforms, with over half of the respondents reporting that they have done development work with them this year. We also see some year over year growth in the popularity of container technologies such as Docker and Kubernetes.
| Linux | 55.0% |
| Windows | 53.1% |
| Docker | 35.0% |
| AWS | 26.7% |
| Android | 26.2% |
| MacOS | 24.0% |
| Raspberry Pi | 14.9% |
| Microsoft Azure | 14.5% |
| WordPress | 14.2% |
| Google Cloud Platform | 14.1% |
| iOS | 12.2% |
| Kubernetes | 11.5% |
| Heroku | 11.1% |
| Arduino | 10.6% |
| Slack Apps and Integrations | 7.3% |
| IBM Cloud or Watson | 1.6% |
| Linux | 55.9% |
| Windows | 51.2% |
| Docker | 39.2% |
| AWS | 29.8% |
| MacOS | 25.6% |
| Android | 24.4% |
| Microsoft Azure | 15.9% |
| Google Cloud Platform | 14.5% |
| Raspberry Pi | 14.0% |
| WordPress | 13.9% |
| Kubernetes | 12.9% |
| iOS | 12.6% |
| Heroku | 10.7% |
| Arduino | 8.6% |
| Slack Apps and Integrations | 8.0% |
| IBM Cloud or Watson | 1.5% |
For five years running, Rust has taken the top spot as the most loved programming language. TypeScript is second surpassing Python compared to last year. We also see big gains in Go, moving up to 5th from 10th last year.
VBA, Objective C, and Perl hold the top spots for the most dreaded languages—languages that had a high percentage of developers who are currently using them, but have no interest in continuing to do so.
If we look at technologies that developers report that they do not use but want to learn, Python takes the top spot for the fourth year in a row. We also see some modest gains in the interest in learning Rust.
| Rust | 86.1% |
| TypeScript | 67.1% |
| Python | 66.7% |
| Kotlin | 62.9% |
| Go | 62.3% |
| Julia | 62.2% |
| Dart | 62.1% |
| C# | 59.7% |
| Swift | 59.5% |
| JavaScript | 58.3% |
| SQL | 56.6% |
| Bash/Shell/PowerShell | 53.7% |
| HTML/CSS | 53.5% |
| Scala | 53.2% |
| Haskell | 51.7% |
| R | 44.5% |
| Java | 44.1% |
| C++ | 43.4% |
| Ruby | 42.9% |
| PHP | 37.3% |
| C | 33.1% |
| Assembly | 29.4% |
| Perl | 28.6% |
| Objective-C | 23.4% |
| VBA | 19.6% |
| VBA | 80.4% |
| Objective-C | 76.6% |
| Perl | 71.4% |
| Assembly | 70.6% |
| C | 66.9% |
| PHP | 62.7% |
| Ruby | 57.1% |
| C++ | 56.6% |
| Java | 55.9% |
| R | 55.5% |
| Haskell | 48.3% |
| Scala | 46.8% |
| HTML/CSS | 46.5% |
| Bash/Shell/PowerShell | 46.3% |
| SQL | 43.4% |
| JavaScript | 41.7% |
| Swift | 40.5% |
| C# | 40.3% |
| Dart | 37.9% |
| Julia | 37.8% |
| Go | 37.7% |
| Kotlin | 37.1% |
| Python | 33.3% |
| TypeScript | 32.9% |
| Rust | 13.9% |
| Python | 30.0% |
| JavaScript | 18.5% |
| Go | 17.9% |
| TypeScript | 17.0% |
| Rust | 14.6% |
| Kotlin | 12.6% |
| Java | 8.8% |
| C++ | 8.6% |
| SQL | 8.2% |
| C# | 7.3% |
| Swift | 6.6% |
| HTML/CSS | 6.5% |
| Dart | 6.0% |
| R | 5.1% |
| Ruby | 4.5% |
| C | 4.3% |
| Scala | 4.2% |
| Haskell | 4.2% |
| Bash/Shell/PowerShell | 3.9% |
| PHP | 3.5% |
| Assembly | 2.6% |
| Julia | 2.3% |
| Objective-C | 1.8% |
| Perl | 1.1% |
| VBA | 0.7% |
ASP.NET Core is the most loved web framework, beating out React.js. Gatsby, a newcomer on the survey, is already sitting at 5th, being loved by 60% of the respondents.
Although it is amongst the most popular web frameworks, Angular.js is also considered to be the most dreaded.
| ASP.NET Core | 70.7% |
| React.js | 68.9% |
| Vue.js | 66.0% |
| Express | 61.9% |
| Gatsby | 60.7% |
| Spring | 57.7% |
| Django | 55.3% |
| Flask | 54.4% |
| Angular | 54.0% |
| Laravel | 51.4% |
| Ruby on Rails | 49.3% |
| Symfony | 45.6% |
| ASP.NET | 36.9% |
| jQuery | 36.5% |
| Drupal | 25.5% |
| Angular.js | 24.1% |
| Angular.js | 75.9% |
| Drupal | 74.5% |
| jQuery | 63.5% |
| ASP.NET | 63.1% |
| Symfony | 54.4% |
| Ruby on Rails | 50.7% |
| Laravel | 48.6% |
| Angular | 46.0% |
| Flask | 45.6% |
| Django | 44.7% |
| Spring | 42.3% |
| Gatsby | 39.3% |
| Express | 38.1% |
| Vue.js | 34.0% |
| React.js | 31.1% |
| ASP.NET Core | 29.3% |
| React.js | 22.4% |
| Vue.js | 16.4% |
| Angular | 10.6% |
| Django | 9.4% |
| Angular.js | 7.7% |
| ASP.NET Core | 6.6% |
| Flask | 5.4% |
| Express | 5.3% |
| Spring | 4.4% |
| Ruby on Rails | 4.4% |
| jQuery | 4.3% |
| Gatsby | 3.5% |
| Laravel | 3.5% |
| ASP.NET | 2.9% |
| Symfony | 1.5% |
| Drupal | 1.0% |
.NET Core and Torch/PyTorch remain the most loved of the other remaining frameworks, libraries and tools. DevOps tools Chef and Puppet are among the most dreaded technologies.
| .NET Core | 71.5% |
| Torch/PyTorch | 70.5% |
| Flutter | 68.8% |
| Pandas | 68.4% |
| Teraform | 68.0% |
| Keras | 67.1% |
| Node.js | 66.8% |
| TensorFlow | 65.2% |
| Ansible | 58.5% |
| React Native | 57.9% |
| Apache Spark | 57.5% |
| Unity 3D | 56.0% |
| Unreal Engine | 52.7% |
| .NET | 47.5% |
| Hadoop | 46.4% |
| Xamarin | 45.4% |
| Puppet | 38.5% |
| Cordova | 28.7% |
| Chef | 27.6% |
| Chef | 72.4% |
| Cordova | 71.3% |
| Puppet | 61.5% |
| Xamarin | 54.6% |
| Hadoop | 53.6% |
| .NET | 52.5% |
| Unreal Engine | 47.3% |
| Unity 3D | 44.0% |
| Apache Spark | 42.5% |
| React Native | 42.1% |
| Ansible | 41.5% |
| TensorFlow | 34.8% |
| Node.js | 33.2% |
| Keras | 32.9% |
| Teraform | 32.0% |
| Pandas | 31.6% |
| Flutter | 31.2% |
| Torch/PyTorch | 29.5% |
| .NET Core | 28.5% |
| Node.js | 18.1% |
| TensorFlow | 17.2% |
| React Native | 14.0% |
| Flutter | 10.7% |
| Unity 3D | 9.2% |
| .NET Core | 8.3% |
| Torch/PyTorch | 6.7% |
| Unreal Engine | 6.3% |
| Hadoop | 5.6% |
| Apache Spark | 5.0% |
| Pandas | 4.8% |
| Xamarin | 4.5% |
| Teraform | 4.3% |
| .NET | 3.8% |
| Keras | 3.7% |
| Ansible | 3.3% |
| Puppet | 1.7% |
| Chef | 1.6% |
| Cordova | 1.5% |
Taking a look at database technologies, Redis remains the most loved, followed by PostgreSQL and Elasticsearch. Anecdotally, Stack Overflow has been using both Redis and Elasticsearch in our tech stack for years, since the early days of the company. IBM DB2 ranked as the most dreaded database and MongoDB remains the database technology that developers want to learn the most.
| Redis | 66.5% |
| PostgreSQL | 63.9% |
| Elasticsearch | 58.7% |
| MongoDB | 56.0% |
| Firebase | 54.9% |
| MariaDB | 51.3% |
| Microsoft SQL Server | 50.9% |
| DynamoDB | 50.7% |
| SQLite | 49.4% |
| MySQL | 47.1% |
| Cassandra | 43.6% |
| Couchbase | 33.2% |
| Oracle | 33.2% |
| IBM DB2 | 23.3% |
| IBM DB2 | 76.7% |
| Oracle | 66.8% |
| Couchbase | 66.8% |
| Cassandra | 56.4% |
| MySQL | 52.9% |
| SQLite | 50.6% |
| DynamoDB | 49.3% |
| Microsoft SQL Server | 49.1% |
| MariaDB | 48.7% |
| Firebase | 45.1% |
| MongoDB | 44.0% |
| Elasticsearch | 41.3% |
| PostgreSQL | 36.1% |
| Redis | 33.5% |
| MongoDB | 19.4% |
| PostgreSQL | 15.6% |
| Elasticsearch | 12.2% |
| Redis | 12.2% |
| Firebase | 9.2% |
| MySQL | 9.0% |
| SQLite | 7.7% |
| Cassandra | 6.2% |
| DynamoDB | 5.5% |
| Oracle | 4.2% |
| MariaDB | 3.7% |
| Microsoft SQL Server | 3.7% |
| Couchbase | 2.4% |
| IBM DB2 | 1.1% |
Linux remains the most loved platform. Container technologies Docker and Kubernetes rank as the second and third most loved. They are also among the platforms that developers most want to learn, which demonstrates how beloved they are. Wordpress is still the most dreaded, but Slack Apps and integrations, newly added to the list this year, rank high at the number four spot.
| Linux | 76.9% |
| Docker | 73.6% |
| Kubernetes | 71.1% |
| AWS | 66.4% |
| Raspberry Pi | 66.1% |
| MacOS | 64.4% |
| Microsoft Azure | 62.2% |
| iOS | 61.1% |
| Google Cloud Platform | 60.9% |
| Windows | 57.5% |
| Android | 57.1% |
| Arduino | 53.2% |
| Slack Apps and Integrations | 51.0% |
| Heroku | 46.2% |
| IBM Cloud or Watson | 37.8% |
| WordPress | 33.0% |
| WordPress | 67.0% |
| IBM Cloud or Watson | 62.2% |
| Heroku | 53.8% |
| Slack Apps and Integrations | 49.0% |
| Arduino | 46.8% |
| Android | 42.9% |
| Windows | 42.5% |
| Google Cloud Platform | 39.1% |
| iOS | 38.9% |
| Microsoft Azure | 37.8% |
| MacOS | 35.6% |
| Raspberry Pi | 33.9% |
| AWS | 33.6% |
| Kubernetes | 28.9% |
| Docker | 26.4% |
| Linux | 23.1% |
| Docker | 24.5% |
| AWS | 20.2% |
| Kubernetes | 18.5% |
| Linux | 16.6% |
| Android | 16.0% |
| Google Cloud Platform | 14.0% |
| Raspberry Pi | 12.6% |
| iOS | 10.4% |
| Microsoft Azure | 9.9% |
| MacOS | 7.7% |
| Arduino | 7.4% |
| Windows | 4.7% |
| Heroku | 4.4% |
| Slack Apps and Integrations | 3.3% |
| WordPress | 2.6% |
| IBM Cloud or Watson | 2.6% |
Almost half of the respondents use Windows as their primary operating system. The rest were almost evenly split between MacOS and a flavor of Linux.
| Windows | 45.8% |
| MacOS | 27.5% |
| Linux-based | 26.6% |
| BSD | 0.1% |
Of the professional developers who responded to the survey, almost 82% use GitHub as a collaborative tool and more than half use Slack.
| GitHub | 82.8% |
| Slack | 53.0% |
| Jira | 47.7% |
| Google Suite (Docs, Meet, etc) | 41.5% |
| Gitlab | 37.0% |
| Confluence | 32.4% |
| Trello | 29.6% |
| Microsoft Teams | 25.6% |
| Microsoft Azure | 14.8% |
| Stack Overflow for Teams | 5.8% |
| Facebook Workplace | 3.0% |
| GitHub | 81.5% |
| Slack | 56.9% |
| Jira | 54.2% |
| Google Suite (Docs, Meet, etc) | 42.6% |
| Gitlab | 38.8% |
| Confluence | 37.0% |
| Trello | 30.6% |
| Microsoft Teams | 28.0% |
| Microsoft Azure | 16.2% |
| Stack Overflow for Teams | 5.2% |
| Facebook Workplace | 2.9% |
When researching new tools, over three-fourths of respondents like to try the tool for themselves via a free trial. Social proof is also important, as over 60% of developers ask other developers they know about it or visit developer communities such as Stack Overflow.
| Start a free trial | 77.1% |
| Ask developers I know/work with | 67.9% |
| Visit developer communities like Stack Overflow | 64.0% |
| Read ratings or reviews on third party sites like G2Crowd | 29.9% |
| Research companies that have advertised on sites I visit | 12.3% |
| Research companies that have emailed me | 5.5% |
With regards to technology purchases within their organization, around 57% of respondents have some or a great deal of influence.
| I have a great deal of influence | 17.8% |
| I have some influence | 39.1% |
| I have little or no influence | 43.2% |
We asked developers how frequently they learn a new language or framework. Around 75% of respondents noted that they learn a new technology at least every few months or once a year. This demonstrates how quickly innovations happen and developers are constantly learning to keep their skills fresh.
| Every few months | 37.3% |
| Once a year | 36.8% |
| Once every few years | 23.7% |
| Once a decade | 2.2% |
| Every few months | 34.9% |
| Once a year | 37.9% |
| Once every few years | 25.1% |
| Once a decade | 2.1% |
We asked respondents what they do when they get stuck on a problem. Almost 90% reported that they visit Stack Overflow. This is an encouraging sign that we're succeeding in our mission to help people get access to the knowledge they need to get things done.
| Visit Stack Overflow | 90.6% |
| Do other work and come back later | 54.4% |
| Watch help / tutorial videos | 52.8% |
| Call a coworker or friend | 49.9% |
| Go for a walk or other physical activity | 43.3% |
| Play games | 15.0% |
| Meditate | 11.7% |
| Panic | 10.9% |
| Visit another developer community | 10.3% |
For the first time, we asked developers how they feel when they search for a coding solution online and the first result link is purple because they already visited the link. About half of respondents chose 'Hello, old friend', which suggests it may be a frequent occurrence for certain tasks. Perhaps this is why over 2.1 million people visited the'How do I exit the Vim editor?' question on Stack Overflow.
| Hello, old friend | 51.6% |
| Indifferent | 18.3% |
| Amused | 15.9% |
| Annoyed | 14.3% |
Reminder: this year’s survey was taken in February, before COVID-19 was declared a pandemic by the World Health Organization and before the virus impacted every country in the world. Please keep the timing of the survey in mind when reviewing information such as job and salary data.
Over 92% of professional developers are employed at least part-time. Roughly 12% of all respondents say they are students.
| Employed full-time | 70.9% |
| Student | 12.2% |
| Independent contractor, freelancer, or self-employed | 8.9% |
| Not employed, but looking for work | 3.7% |
| Employed part-time | 3.5% |
| Not employed, and not looking for work | 0.5% |
| Retired | 0.4% |
| Employed full-time | 82.8% |
| Independent contractor, freelancer, or self-employed | 9.5% |
| Employed part-time | 3.1% |
| Student | 2.1% |
| Not employed, but looking for work | 2.1% |
| Not employed, and not looking for work | 0.2% |
| Retired | 0.1% |
India has an noticeably higher proportion of students compared to other countries that are well-represented in the survey data. In all of these locations, more than 70% of developers are employed full-time.
| Employed full-time | 78.6% |
| Student | 8.9% |
| Independent contractor, freelancer, or self-employed | 6.3% |
| Not employed, but looking for work | 2.9% |
| Employed part-time | 2.2% |
| Retired | 0.7% |
| Not employed, and not looking for work | 0.5% |
| Employed full-time | 73.1% |
| Student | 16.0% |
| Independent contractor, freelancer, or self-employed | 4.9% |
| Not employed, but looking for work | 4.2% |
| Employed part-time | 1.6% |
| Not employed, and not looking for work | 0.3% |
| Retired | 0.0% |
| Employed full-time | 77.3% |
| Independent contractor, freelancer, or self-employed | 9.7% |
| Student | 8.3% |
| Employed part-time | 1.9% |
| Not employed, but looking for work | 1.8% |
| Retired | 0.6% |
| Not employed, and not looking for work | 0.5% |
| Employed full-time | 70.3% |
| Student | 14.7% |
| Employed part-time | 6.7% |
| Independent contractor, freelancer, or self-employed | 6.5% |
| Not employed, but looking for work | 1.3% |
| Not employed, and not looking for work | 0.3% |
| Retired | 0.2% |
| Employed full-time | 72.3% |
| Student | 13.4% |
| Independent contractor, freelancer, or self-employed | 7.4% |
| Not employed, but looking for work | 3.4% |
| Employed part-time | 2.5% |
| Retired | 0.6% |
| Not employed, and not looking for work | 0.4% |
For the first time this year, we asked respondents how often they work overtime or beyond the formal time expectation of their job. Over 75% of developers work overtime at least occasionally, defined as one to two days per quarter.
| Never | 10.9% |
| Rarely: 1-2 days per year or less | 15.0% |
| Occasionally: 1-2 days per quarter but less than monthly | 21.9% |
| Sometimes: 1-2 days per month but less than weekly | 26.7% |
| Often: 1-2 days per week or more | 25.5% |
| Just me - I am a freelancer, sole proprietor, etc. | 4.9% |
| 2 to 9 employees | 9.9% |
| 10 to 19 employees | 9.3% |
| 20 to 99 employees | 21.6% |
| 100 to 499 employees | 18.7% |
| 500 to 999 employees | 6.5% |
| 1,000 to 4,999 employees | 11.0% |
| 5,000 to 9,999 employees | 4.1% |
| 10,000 or more employees | 13.9% |
Almost half of the respondents reported that their company has a good onboarding process. About one fifth had no onboarding process at all.
| Yes | 48.6% |
| No | 29.7% |
| Onboarding? What onboarding? | 21.7% |
We asked survey takers if their organizations have dedicated DevOps personnel. An equal amount of respondents reported that their company had at least one dedicated employee to handle DevOps as those who reported they had none.
| Yes | 43.8% |
| No | 43.6% |
| Not sure | 12.5% |
We also asked survey takers about the importance of DevOps to scaling software development. Almost 80% of respondents believed that DevOps is at least somewhat important, with almost half of the respondents noting that it is extremely important.
| Extremely important | 48.1% |
| Somewhat important | 31.0% |
| Neutral | 17.4% |
| Not very important | 2.0% |
| Not at all important | 1.4% |
Almost 83% of respondents reported that they are either not actively looking or interested in new job opportunities. This is consistent with our findings about developer job satisfaction—most developers are happy with their jobs.
| I’m not actively looking, but I am open to new opportunities | 57.6% |
| I am not interested in new job opportunities | 25.1% |
| I am actively looking for a job | 17.3% |
When looking across several countries with large developer populations, job satisfaction is mostly consistent. In the US, UK, Germany, and Canada, over 80% of developers are not actively looking for a job, but at least half are open to new opportunities.
| I’m not actively looking, but I am open to new opportunities | 54.7% |
| I am not interested in new job opportunities | 31.4% |
| I am actively looking for a job | 13.9% |
| I’m not actively looking, but I am open to new opportunities | 56.6% |
| I am actively looking for a job | 32.2% |
| I am not interested in new job opportunities | 11.2% |
| I’m not actively looking, but I am open to new opportunities | 52.9% |
| I am not interested in new job opportunities | 34.4% |
| I am actively looking for a job | 12.7% |
| I’m not actively looking, but I am open to new opportunities | 55.0% |
| I am not interested in new job opportunities | 34.6% |
| I am actively looking for a job | 10.4% |
| I’m not actively looking, but I am open to new opportunities | 57.2% |
| I am not interested in new job opportunities | 29.5% |
| I am actively looking for a job | 13.3% |
If we break out the data by job function, over 20% of academic researchers, data scientists, and data/business analysts are actively looking for a new job, followed closely by designers, game developers, and mobile developers at 19%. This is consistent with findings from past surveys, where we saw that academic researchers and designers were among the roles that had the lowest job satisfaction.
| Academic researcher | 21.7% |
| Data scientist or machine learning specialist | 20.5% |
| Data or business analyst | 20.2% |
| Designer | 19.6% |
| Developer, game or graphics | 19.3% |
| Developer, mobile | 19.1% |
| Educator | 18.9% |
| Scientist | 17.9% |
| Engineer, data | 17.6% |
| Database administrator | 17.2% |
| Developer, front-end | 16.9% |
| Developer, embedded applications or devices | 16.5% |
| Developer, QA or test | 16.3% |
| Developer, back-end | 16.2% |
| Developer, full-stack | 15.7% |
| Engineer, site reliability | 15.5% |
| Developer, desktop or enterprise applications | 15.5% |
| System administrator | 15.4% |
| Product manager | 15.0% |
| Engineering manager | 13.6% |
| DevOps specialist | 12.7% |
| Senior executive/VP | 11.8% |
For the first time, we asked developers what drove them to look for a new job. Better compensation was by far the most common factor for respondents with 70% of them noting that more pay was important. Wanting to work with new technologies was the second most popular factor, which is consistent with what respondents reported as one of the most important priorities when choosing between two jobs.
| Better compensation | 70.0% |
| Wanting to work with new technologies | 58.5% |
| Curious about other opportunities | 57.1% |
| Growth or leadership opportunities | 52.9% |
| Better work/life balance | 48.3% |
| Trouble with leadership at my company | 26.8% |
| Looking to relocate | 26.3% |
| Having a bad day (or week or month) at work | 20.3% |
| Trouble with my direct manager | 17.0% |
| Just because | 12.3% |
| Trouble with my teammates | 11.7% |
| Wanting to share accomplishments with a wider network | 10.3% |
We asked respondents how they learn about a company during a job hunt and received mixed responses. Most respondents turn to reviews on third party sites, such as Glassdoor and Blind. However, a large amount also learn from viewing company sponsored media, such as blogs and company culture videos. Interestingly, relatively fewer respondents seek publicly available financial information, such as data from Crunchbase, which is consistent with respondents noting that company financial performance and fundraising is not a very important factor when deciding to take a job.
| Company reviews from third party sites (e.g. Glassdoor, Blind) | 69.6% |
| Read company media, such as employee blogs or company culture videos | 65.3% |
| Personal network - friends or family | 63.4% |
| Read other media like news articles, founder profiles, etc. about the company | 49.2% |
| Directly asking current or past employees at the company | 36.2% |
| Publicly available financial information (e.g. Crunchbase) | 26.4% |
We asked the survey respondents if we control for compensation, benefits, and location, what three characteristics would most influence their decision to choose one job offer over another. Overall, the languages and technologies that the developer would be working with was most important, followed by the office environment or company culture and flexibility of schedule. Interestingly enough, the least important factors were the financial performance of the organization (11.4%), the specific team they would be working on (11.2%), and the diversity of the organization (6.6%).
However, if we control for gender, we see some differences in the rankings. For example, among the women respondents, 48% selected company culture to be one of the most important factors and 18% indicated that diversity was also of top importance. Among the non-binary respondents, 49.9% chose office environment and company culture in the top three most important factors and 33.4% strongly valued the diversity of the company.
| Languages, frameworks, and other technologies I’d be working with | 51.3% |
| Office environment or company culture | 44.5% |
| Flex time or a flexible schedule | 43.9% |
| Opportunities for professional development | 41.4% |
| Remote work options | 33.3% |
| How widely used or impactful my work output would be | 20.8% |
| Industry that I’d be working in | 15.3% |
| Family friendliness | 12.1% |
| Financial performance or funding status of the company or organization | 11.9% |
| Specific department or team I’d be working on | 11.8% |
| Diversity of the company or organization | 6.9% |
| Languages, frameworks, and other technologies I’d be working with | 52.8% |
| Office environment or company culture | 44.5% |
| Flex time or a flexible schedule | 44.0% |
| Opportunities for professional development | 41.5% |
| Remote work options | 33.6% |
| How widely used or impactful my work output would be | 21.0% |
| Industry that I’d be working in | 15.3% |
| Family friendliness | 12.2% |
| Financial performance or funding status of the company or organization | 12.1% |
| Specific department or team I’d be working on | 11.7% |
| Diversity of the company or organization | 5.5% |
| Office environment or company culture | 48.3% |
| Flex time or a flexible schedule | 45.6% |
| Languages, frameworks, and other technologies I’d be working with | 41.8% |
| Opportunities for professional development | 41.1% |
| Remote work options | 32.0% |
| How widely used or impactful my work output would be | 19.8% |
| Diversity of the company or organization | 18.6% |
| Industry that I’d be working in | 14.0% |
| Specific department or team I’d be working on | 12.5% |
| Family friendliness | 10.7% |
| Financial performance or funding status of the company or organization | 8.9% |
| Office environment or company culture | 51.7% |
| Flex time or a flexible schedule | 41.6% |
| Languages, frameworks, and other technologies I’d be working with | 39.4% |
| Diversity of the company or organization | 34.6% |
| Remote work options | 30.9% |
| Opportunities for professional development | 26.7% |
| How widely used or impactful my work output would be | 22.8% |
| Industry that I’d be working in | 19.0% |
| Specific department or team I’d be working on | 10.9% |
| Financial performance or funding status of the company or organization | 7.6% |
| Family friendliness | 7.4% |
As mentioned previously, there are differences in job priorities by gender, so we also compared the overall opinion in the raw results with a weighted opinion. Weighting does not change the results significantly; however, we see gains in office environment or company culture and diversity of the organization.
| Office environment or company culture | 47.5% |
| Languages, frameworks, and other technologies I’d be working with | 47.1% |
| Flex time or a flexible schedule | 41.1% |
| Remote work options | 37.2% |
| Opportunities for professional development | 33.5% |
| How widely used or impactful my work output would be | 23.5% |
| Industry that I’d be working in | 16.4% |
| Specific department or team I’d be working on | 16.0% |
| Family friendliness | 12.8% |
| Financial performance or funding status of the company or organization | 12.5% |
| Diversity of the company or organization | 9.1% |
| Office environment or company culture | 47.9% |
| Languages, frameworks, and other technologies I’d be working with | 45.6% |
| Flex time or a flexible schedule | 41.4% |
| Remote work options | 37.3% |
| Opportunities for professional development | 33.0% |
| How widely used or impactful my work output would be | 23.4% |
| Industry that I’d be working in | 16.2% |
| Specific department or team I’d be working on | 15.9% |
| Family friendliness | 12.5% |
| Financial performance or funding status of the company or organization | 12.0% |
| Diversity of the company or organization | 11.6% |
Across the board, engineering managers, SREs, DevOps specialists, and data engineers tend to receive the highest salaries. When focusing on the US, we see some differences at the bottom of the salary spectrum. In the US, mobile developers and educators tend to have a higher salary relative to other occupations when compared to the global developer population.
| Engineering manager | $92k |
| Engineer, site reliability | $80k |
| DevOps specialist | $68k |
| Engineer, data | $65k |
| Data scientist or machine learning specialist | $58k |
| Developer, embedded applications or devices | $57k |
| Scientist | $57k |
| Developer, desktop or enterprise applications | $56k |
| Data or business analyst | $55k |
| Developer, full-stack | $54k |
| System administrator | $54k |
| Developer, back-end | $53k |
| Developer, QA or test | $53k |
| Database administrator | $50k |
| Developer, game or graphics | $50k |
| Developer, front-end | $49k |
| Educator | $49k |
| Designer | $47k |
| Developer, mobile | $43k |
| Academic researcher | $41k |
| Engineering manager | $152k |
| Engineer, site reliability | $140k |
| Data scientist or machine learning specialist | $125k |
| DevOps specialist | $125k |
| Engineer, data | $125k |
| Developer, back-end | $120k |
| Developer, embedded applications or devices | $120k |
| Developer, mobile | $120k |
| Scientist | $120k |
| Developer, desktop or enterprise applications | $115k |
| Educator | $115k |
| Developer, full-stack | $112k |
| Developer, game or graphics | $112k |
| Database administrator | $110k |
| Developer, front-end | $110k |
| System administrator | $110k |
| Developer, QA or test | $105k |
| Academic researcher | $100k |
| Data or business analyst | $100k |
| Designer | $100k |
When we look at how salary compares with years of experience, we see the expected - developers with more experience tend to command higher salaries. However, we see some differences when we look at specific developer roles. SREs, DevOps specialists, and data engineers command a disproportionately higher salary compared to developers within a similar level of experience in different roles. This is consistent with what we saw in the salary trends as a whole. Designers, mobile developers and educators tend to command a disproportionately lower salary.
Salaries also differ in terms of years of experience when looking at the programming language a developer uses as well. For most languages, the relationship between salary and years of coding experience is linear. However, we see some outliers with users of Python and R commanding higher salaries. This could be explained by the fact that these languages are often used by data scientists who are among the most highly compensated developers.
Globally, over 75% of developers work less than 45 hours per week. Senior executives, engineering managers and product managers tend to work longer hours.
| Less than 30 hours | 7.3% |
| 30 to 34 hours | 3.6% |
| 35 to 39 hours | 13.5% |
| 40 to 44 hours | 51.7% |
| 45 to 49 hours | 11.2% |
| 50 to 54 hours | 7.0% |
| 55 to 59 hours | 1.2% |
| 60 to 64 hours | 2.6% |
| 65 to 69 hours | 0.2% |
| 70 hours or more | 1.8% |
| Senior executive/VP | 47.4 |
| Engineering manager | 43.9 |
| Product manager | 43.6 |
| Scientist | 42.3 |
| System administrator | 42.2 |
| Engineer, site reliability | 42.1 |
| Data or business analyst | 42.1 |
| Database administrator | 42.1 |
| DevOps specialist | 42.1 |
| Developer, embedded applications or devices | 41.9 |
| Data scientist or machine learning specialist | 41.8 |
| Engineer, data | 41.8 |
| Developer, QA or test | 41.7 |
| Educator | 41.7 |
| Academic researcher | 41.5 |
| Developer, desktop or enterprise applications | 41.4 |
| Designer | 41.1 |
| Developer, mobile | 41.0 |
| Developer, game or graphics | 41.0 |
| Developer, back-end | 40.8 |
| Developer, full-stack | 40.8 |
| Developer, front-end | 40.6 |
| United States | 41.8 |
| Canada | 40.6 |
| France | 40.4 |
| India | 40.3 |
| Germany | 40.3 |
| Brazil | 39.3 |
| United Kingdom | 39.2 |
Where developers come to learn, share knowledge, and build their careers
Developers visit Stack Overflow. A lot. Our survey respondents likely visit even more than the average developer, since a majority of respondents found the survey from Stack Overflow emails, notifications, and banners. Over 82% of respondents visit Stack Overflow at least a few times per week, with over 59% visiting every day. In the United States, there are only slight shifts between the results weighted by gender and unweighted results on visit frequency.
| I have never visited Stack Overflow (before today) | 0.3% |
| Less than once per month or monthly | 3.1% |
| A few times per month or weekly | 13.9% |
| A few times per week | 23.7% |
| Daily or almost daily | 30.5% |
| Multiple times per day | 28.6% |
| I have never visited Stack Overflow (before today) | 0.1% |
| Less than once per month or monthly | 4.1% |
| A few times per month or weekly | 16.8% |
| A few times per week | 27.8% |
| Daily or almost daily | 28.3% |
| Multiple times per day | 22.9% |
| I have never visited Stack Overflow (before today) | 0.1% |
| Less than once per month or monthly | 4.4% |
| A few times per month or weekly | 17.3% |
| A few times per week | 27.8% |
| Daily or almost daily | 27.9% |
| Multiple times per day | 22.4% |
About 83% of the participants in our survey say they are registered users with accounts. This provides important context for interpreting our survey results, because most Stack Overflow traffic comes from anonymous, unregistered visitors.
| Yes | 83.2% |
| No | 10.7% |
| Not sure/can't remember | 6.0% |
Almost all of responents have visited Stack Overflow and about two-thirds have visited Stack Exchange.
| Stack Overflow (public Q&A for anyone who codes) | 98.0% |
| Stack Exchange (public Q&A for a variety of topics) | 67.3% |
| Stack Overflow Jobs (for job seekers) | 36.3% |
| Stack Overflow for Teams (private Q&A for organizations) | 4.5% |
| Stack Overflow Talent (for hiring companies/recruiters) | 2.4% |
| Stack Overflow Advertising (for technology companies) | 1.4% |
| I have never visited any of these sites | 0.9% |
| Stack Overflow (public Q&A for anyone who codes) | 98.8% |
| Stack Exchange (public Q&A for a variety of topics) | 68.8% |
| Stack Overflow Jobs (for job seekers) | 39.1% |
| Stack Overflow for Teams (private Q&A for organizations) | 4.5% |
| Stack Overflow Talent (for hiring companies/recruiters) | 2.1% |
| Stack Overflow Advertising (for technology companies) | 1.1% |
| I have never visited any of these sites | 0.5% |
Some developers come to Stack Overflow only to find answers to their questions, while others participate in the community by asking, answering, voting for, or commenting on questions. Over 34% of survey respondents participate on Stack Overflow a few times per month or more often. When comparing United States weighted data to unweighted results, we see more representation from those who have never participated on Stack Overflow.
| I have never participated in Q&A on Stack Overflow | 22.3% |
| Less than once per month or monthly | 43.7% |
| A few times per month or weekly | 17.8% |
| A few times per week | 9.0% |
| Daily or almost daily | 4.7% |
| Multiple times per day | 2.6% |
| I have never participated in Q&A on Stack Overflow | 20.0% |
| Less than once per month or monthly | 49.3% |
| A few times per month or weekly | 16.8% |
| A few times per week | 7.9% |
| Daily or almost daily | 3.8% |
| Multiple times per day | 2.2% |
| I have never participated in Q&A on Stack Overflow | 21.1% |
| Less than once per month or monthly | 49.3% |
| A few times per month or weekly | 16.2% |
| A few times per week | 7.7% |
| Daily or almost daily | 3.6% |
| Multiple times per day | 2.0% |
About 43% of the respondents to our survey consider themselves part of our community, but this varies for different groups of people. For example, we find that respondents who identify as men see themselves as part of the community at much higher rates than those with other gender identities. The tech community as a whole, and we at Stack Overflow in particular, still have work to do in this area.
| Yes, definitely | 15.8% |
| Yes, somewhat | 27.0% |
| Neutral | 20.7% |
| No, not really | 26.0% |
| No, not at all | 8.5% |
| Not sure | 1.9% |
| Man | 44.5% |
| Woman | 30.0% |
| Non-binary, genderqueer, or gender non-conforming | 27.1% |
Most respondents say they feel just as welcome on Stack Overflow as they felt last year. Answers this year were slightly more polarized than those from 2019. When asked why they responded the way they did, respondents who felt less welcome mentioned the relationship between the community and the company and question quality. Respondents who felt more welcome mentioned feeling more comfortable and confident, the site being nicer or friendlier, and features of the site like emails and the newsletter.
| A lot more welcome now than last year | 6.1% |
| Somewhat more welcome now than last year | 9.5% |
| Just as welcome now as I felt last year | 70.6% |
| Somewhat less welcome now than last year | 5.9% |
| A lot less welcome now than last year | 4.0% |
| Not applicable - I did not use Stack Overflow last year | 3.9% |
For around 60% of respondents, Stack Overflow is the only online developer community they are a member of. Of the 41% who indicated they are members of other online developer communities. 15k respondents provided at least one additional community they participate in. Though this data is not present in results, it is available for analysis in the raw data.
| No | 58.3% |
| Yes | 41.7% |
| No | 58.5% |
| Yes | 41.5% |
We asked respondents in a free text question one thing they would change about Stack Overflow if they had the chance. Respondents shared ideas focusing on question quality, improving search, identifying and removing outdated answers, frustrations with duplicate question handling, and issues with the way the company treats the community.
The aspects of Stack Overflow that respondents would like to change exhibit differences across demographic groups. For example, developers who are men are more likely to want specific new features, while developers who are women are more likely to want to change norms for communication on our site.
We asked respondents whether they believe that Stack Overflow should relax restrictions on what is considered off-topic and received mixed results. Most respondents were not sure and almost 37% believe that restrictions should not be relaxed.
| Not sure | 39.8% |
| No | 36.5% |
| Yes | 23.7% |
| Not sure | 39.5% |
| No | 37.9% |
| Yes | 22.6% |
How we planned and analyzed our survey
This report is based on a survey of 65,000 software developers from 186 countries around the world. This is the number of responses we consider “qualified” for analytical purposes based on time spent on the full, completed survey; another approximately 400 responses were submitted but not included in the analysis because respondents spent less than three minutes on the survey.
The survey was fielded from February 5 to February 28.
The median time spent on the survey for qualified responses was 16.6 minutes, down from 23.3 minutes last year.
Respondents were recruited primarily through channels owned by Stack Overflow. The top sources of respondents were onsite messaging, blog posts, email lists, banner ads, and social media posts. Since respondents were recruited in this way, highly engaged users on Stack Overflow were more likely to notice the prompts to take the survey over the duration of collection promotion.
As an incentive, respondents who finished the survey could opt in to a “Census” badge if they completed the survey.
Due to United States transport/export sanctions, our survey was unfortunately unaccessible to prospective respondents in Crimea, Cuba, Iran, North Korea, and Syria, due to the traffic being blocked by our third party survey software. While some respondents used VPNs to get around the block, the limitation should be kept in mind when interpreting survey results.
In years past, our analysis of professional developers was based on site activity on Stack Overflow. This year, we utilized answers regarding employment to deduce whether or not a respondent qualifies as a professional developer and built our analyses based on this qualification.
We asked respondents about their salary. First, we asked what currency each respondent typically used. Then we asked that respondent what their salary was in that currency and whether that salary was weekly, monthly, or yearly.
We converted salaries from user currencies to USD using the exchange rate on 2020-02-19, and also converted to annual salaries assuming 12 working months and 50 working weeks.
This question, like most on the survey, was optional. There were 34,279 respondents who gave us salary data.
The top approximately 2% of salaries inside and outside of the US were trimmed and replaced with threshold values. The threshold values for inside and outside the US were different.
Many questions were only shown to respondents based on their previous answers. For example, questions about jobs and work were only shown to those who said they were working in a job.
The questions were organized into several blocks of questions, which were randomized in order. Also, the answers to most questions were randomized in order.
To identify which technologies to include on the survey this year, we looked at both the most popular and fastest growing tags on Stack Overflow (in terms of questions posted). We compared these to the technologies we included last year and looked at how many people chose each option. We synthesized all this together to curate a collection of technologies to include.
