Stack Overflow Developer Survey 2026
Activities in a typical work week by employment status
In the Employed group, 71% selected “Answering questions from teammates, customers, users, or stakeholders”; in the Student group, 18% did. Of the 18 answers tested, “Answering questions from teammates, customers, users, or stakeholders” differs most by employment status, a medium association: χ²(5, N = 24714) = 3427.96, Holm-adjusted p < .001, V = .37. Respondents could select more than one answer, so the percentages add to more than 100%. These are unweighted respondents, not population estimates.
How results are checked
Named statistical review pending. Selected automated reference cases are published on the validation page.The table
The table
Question asked: In a typical week, which of the following activities are part of your work? Select all that apply.
Respondents could select more than one answer. Shown by employment status, as the percentage of each group's respondents who selected each answer, with the number of respondents beneath. A respondent is counted in every row they selected, so a column adds to more than 100%.
| Activities in a typical work week | Employed (A) | I prefer not to say (B) | Independent contractor, freelancer, or self-employed (C) | Not employed (D) | Retired (E) | Student (F) | All |
|---|---|---|---|---|---|---|---|
| Writing, editing, or generating code | 92.9%BCDEF15,514 | 59.9%194 | 91.0%BDEF3,387 | 76.4%BE979 | 60.4%308 | 84.7%BDE1,839 | 89.9%22,221 |
| Debugging or troubleshooting | 88.2%BCDEF14,732 | 52.8%171 | 82.9%BDEF3,087 | 67.4%BE864 | 51.6%263 | 67.1%BE1,456 | 83.2%20,573 |
| Reviewing code, pull requests, or technical changes | 76.0%BCDEF12,692 | 33.0%E107 | 62.9%BDEF2,343 | 47.2%BEF604 | 19.2%98 | 29.9%E650 | 66.7%16,494 |
| Making technical design or architecture decisions | 69.0%BDEF11,525 | 33.6%109 | 68.8%BDEF2,561 | 45.2%BEF579 | 34.1%174 | 33.7%731 | 63.4%15,679 |
| Answering questions from teammates, customers, users, or stakeholders | 70.7%BCDEF11,817 | 24.7%F80 | 52.8%BDEF1,964 | 31.7%EF406 | 21.0%107 | 17.5%380 | 59.7%14,754 |
| Planning, scoping, or estimating work | 64.2%BCDEF10,728 | 28.4%E92 | 58.7%BDEF2,187 | 39.4%BEF505 | 18.4%94 | 27.5%E596 | 57.5%14,202 |
| Writing or updating documentation | 62.4%BCDEF10,424 | 34.3%111 | 54.0%BDEF2,011 | 41.3%EF529 | 30.8%157 | 31.6%686 | 56.3%13,918 |
| Deploying or releasing software | 56.8%BDEF9,494 | 27.2%F88 | 59.3%BDEFa2,208 | 36.4%BEF466 | 24.5%125 | 19.3%419 | 51.8%12,800 |
| Writing or maintaining tests | 57.2%BCDEF9,551 | 22.2%72 | 49.2%BDEF1,833 | 41.8%BEF535 | 22.2%113 | 23.7%514 | 51.1%12,618 |
| Changing production code, systems, or infrastructure | 56.1%BDEF9,368 | 24.1%f78 | 53.6%BDEF1,997 | 31.7%EF406 | 20.2%103 | 17.6%382 | 49.9%12,334 |
| Investigating an incident, outage, or production issue | 54.1%BCDEF9,038 | 21.9%F71 | 46.7%BDEF1,739 | 28.9%EF370 | 15.1%F77 | 8.8%191 | 46.5%11,486 |
| Monitoring systems, logs, metrics, or alerts | 50.3%BCDEF8,403 | 22.5%Fe73 | 47.1%BDEF1,755 | 29.8%EF382 | 15.1%77 | 12.2%265 | 44.3%10,955 |
| Maintaining dependencies, packages, or development environments | 43.9%BDEF7,328 | 22.5%EF73 | 42.4%BDEF1,577 | 26.1%EF334 | 13.3%68 | 15.7%340 | 39.3%9,720 |
| Coordinating work across teams or functions | 38.1%BCDEF6,372 | 18.5%EF60 | 29.2%BDEF1,087 | 18.9%EF242 | 7.3%37 | 8.1%176 | 32.3%7,974 |
| Finding or fixing security, privacy, or compliance issues | 34.7%BDEF5,797 | 21.6%EF70 | 36.0%BDEF1,340 | 20.9%EF268 | 12.0%61 | 10.0%218 | 31.4%7,754 |
| Onboarding to a new project, tool, system, or codebase | 24.9%BDEF4,164 | 14.8%48 | 26.5%BDEF986 | 16.5%EF212 | 9.4%48 | 12.6%274 | 23.2%5,732 |
| Analyzing data, reports, or business metrics | 24.6%DEF4,106 | 19.4%F63 | 28.8%ABDEF1,071 | 14.4%F185 | 13.1%67 | 10.6%230 | 23.2%5,722 |
| None of the above | 1.0%162 | 21.9%ACDF71 | 2.0%A73 | 13.7%ACF176 | 25.7%ACDF131 | 10.2%AC221 | 3.4%834 |
| Respondents | 16,705 | 324 | 3,723 | 1,281 | 510 | 2,171 | 24,714 |
A letter beside a percentage names the columns it is significantly higher than (uppercase 95%, lowercase 90%; pairwise column tests, Bonferroni-corrected). 6,189 of 30,903 respondents have no answer to one of the two questions (not asked or not answered) and are left out.
Analysis
Results
Chi-square test of “Answering questions from teammates, customers, users, or stakeholders”
χ² = 3427.96
df = 5, Holm-adjusted p < .001
Effect size
Cramér's V = 0.372
a medium association
The strongest answer, APA-style: χ²(5, N = 24714) = 3427.96, Holm-adjusted p < .001, V = .37. Each answer is tested on its own, as the respondents who selected it against those who did not, across the 6 groups (N = 24,714). The p-values are Holm-adjusted for the 18 answers tested; 18 of them differ by employment status at the 0.05 level.
| Answer | Selected | χ² (df = 5) | Adjusted p | Cramér's V |
|---|---|---|---|---|
| Writing, editing, or generating code | 89.9% | 1299.86 | < .001 | 0.229 |
| Debugging or troubleshooting | 83.2% | 1512.19 | < .001 | 0.247 |
| Reviewing code, pull requests, or technical changes | 66.7% | 2897.17 | < .001 | 0.342 |
| Making technical design or architecture decisions | 63.4% | 1594.27 | < .001 | 0.254 |
| Answering questions from teammates, customers, users, or stakeholders | 59.7% | 3427.96 | < .001 | 0.372 |
| Planning, scoping, or estimating work | 57.5% | 1714.93 | < .001 | 0.263 |
| Writing or updating documentation | 56.3% | 1115.24 | < .001 | 0.212 |
| Deploying or releasing software | 51.8% | 1524.90 | < .001 | 0.248 |
| Writing or maintaining tests | 51.1% | 1229.02 | < .001 | 0.223 |
| Changing production code, systems, or infrastructure | 49.9% | 1618.47 | < .001 | 0.256 |
| Investigating an incident, outage, or production issue | 46.5% | 2069.57 | < .001 | 0.289 |
| Monitoring systems, logs, metrics, or alerts | 44.3% | 1509.43 | < .001 | 0.247 |
| Maintaining dependencies, packages, or development environments | 39.3% | 945.24 | < .001 | 0.196 |
| Coordinating work across teams or functions | 32.3% | 1138.81 | < .001 | 0.215 |
| Finding or fixing security, privacy, or compliance issues | 31.4% | 750.32 | < .001 | 0.174 |
| Onboarding to a new project, tool, system, or codebase | 23.2% | 285.91 | < .001 | 0.108 |
| Analyzing data, reports, or business metrics | 23.2% | 363.40 | < .001 | 0.121 |
| None of the above | 3.4% | 2169.58 | < .001 | 0.296 |
How to read it
No single chi-square test covers this table. A respondent appears in every row they selected, so the rows are not separate groups of people, and a test of the whole table would count the same person several times. Each answer is tested on its own instead: did the share who selected it differ between the groups? Testing 18 answers gives 18 chances of a false alarm, so the p-values are Holm-adjusted to keep the chance of any false alarm in this table at 0.05.
For “Answering questions from teammates, customers, users, or stakeholders” the test rejects independence at the 0.05 level (Holm-adjusted p < .001): differences this large between the groups are unlikely if selecting it did not depend on employment status. Cramér's V of 0.372 is in the medium range, which is of moderate strength: a clearly visible pattern in the table.
With 24,714 respondents, even small differences reach statistical significance. Read the percentages and the effect size before the p-value.
Limits
- The survey has no weights. These tables are unweighted counts of the people who answered, so they describe the respondents, not developers in general.
- The test treats respondents as a simple random sample. They are people who chose to answer a survey Stack Overflow promoted, not a random sample of developers, so a result holds for these respondents and may not hold beyond them.
- The adjustment covers the answers of this question by this group only, not the other tables in the library. The headline answer is the strongest of those tested, so its effect size is larger than a typical answer's.
- A difference between groups is not evidence that group membership causes the answer.
Next steps
Work with this table
Open the test of “Answering questions from teammates, customers, users, or stakeholders” in the calculator
The link fills in the respondents who selected this answer and those who did not, by group. The whole table does not open there: its rows overlap, and the calculator's test needs rows that are separate people.
Open this question in the full file
The workspace opens all 30,903 respondents in your browser with this question selected. The survey has no weights, so the table there is unweighted too. Change the group, add a filter or export from there.
Open in the workspace →Run this on your own data — free, no signup
Upload a CSV, Excel, SPSS, Stata, SAS, R, Parquet or JSON file. Everything runs in your browser; your file never leaves your device.
Open the workspace →The same question by other groups
Other questions that differ by employment status
- Other work, school or life responsibilities by employment status
- Role in choosing software tools by employment status
- How they learned to code in the past year by employment status
- How they learned to code for AI in the past year by employment status
- Involvement in building internal tools by employment status
- Sources that most influence which skills to learn by employment status
Source
Stack Overflow. 2026 Developer Survey, https://survey.stackoverflow.co/2026, licensed under the ODbL 1.0. Tabulated by crosstabs.com. Variables RoleFunctions (Activities in a typical work week) and Employment. Stack Overflow licenses the survey data under the Open Database License (ODbL) 1.0 and its contents under the Database Contents License (DbCL) 1.0: credit Stack Overflow, keep the licence notice, and share any database made from the data under the ODbL. These tables and their downloads are offered on those terms.