Stack Overflow Developer Survey 2026
Activities in a typical work week by work setting
In the Hybrid (some in-person, leans heavy to flexibility) group, 79% selected “Reviewing code, pull requests, or technical changes”; in the In-person group, 55% did. Of the 18 answers tested, “Reviewing code, pull requests, or technical changes” differs most by work setting, a small association: χ²(4, N = 21170) = 708.49, Holm-adjusted p < .001, V = .18. 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 work setting, 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 | Hybrid (some in-person, leans heavy to flexibility) (A) | Hybrid (some remote, leans heavy to in-person) (B) | In-person (C) | Remote (D) | Your choice (very flexible, you can come in when you want or just as needed) (E) | All |
|---|---|---|---|---|---|---|
| Writing, editing, or generating code | 92.6%C3,106 | 92.8%C3,885 | 86.6%3,027 | 94.5%ABCE7,084 | 91.1%C2,407 | 92.2%19,509 |
| Debugging or troubleshooting | 88.6%CE2,972 | 87.1%C3,644 | 80.0%2,796 | 89.1%BCE6,676 | 86.2%C2,277 | 86.8%18,365 |
| Reviewing code, pull requests, or technical changes | 79.1%BCE2,652 | 73.0%C3,057 | 54.8%1,914 | 77.3%BCE5,793 | 72.5%C1,914 | 72.4%15,330 |
| Making technical design or architecture decisions | 69.5%C2,330 | 67.6%C2,831 | 53.4%1,865 | 72.8%ABC5,455 | 72.3%BC1,910 | 68.0%14,391 |
| Answering questions from teammates, customers, users, or stakeholders | 72.2%CDE2,420 | 69.9%Cd2,925 | 50.5%1,766 | 67.5%C5,063 | 68.7%C1,815 | 66.1%13,989 |
| Planning, scoping, or estimating work | 65.8%BC2,207 | 62.2%C2,602 | 45.4%1,586 | 67.3%BC5,045 | 65.4%Cb1,726 | 62.2%13,166 |
| Writing or updating documentation | 64.7%BCE2,171 | 61.1%C2,556 | 47.8%1,670 | 63.1%C4,728 | 61.0%C1,612 | 60.2%12,737 |
| Deploying or releasing software | 58.4%BC1,958 | 55.1%C2,307 | 43.3%1,512 | 61.1%BCa4,583 | 58.4%Cb1,543 | 56.2%11,903 |
| Writing or maintaining tests | 59.4%BC1,992 | 55.2%C2,309 | 37.8%1,320 | 60.3%BCE4,521 | 56.4%C1,489 | 54.9%11,631 |
| Changing production code, systems, or infrastructure | 55.9%C1,873 | 53.3%C2,230 | 42.0%1,468 | 59.5%ABC4,458 | 57.7%BC1,524 | 54.6%11,553 |
| Investigating an incident, outage, or production issue | 55.1%BC1,848 | 51.1%C2,138 | 37.6%1,312 | 55.8%BC4,185 | 53.6%C1,415 | 51.5%10,898 |
| Monitoring systems, logs, metrics, or alerts | 51.2%BC1,716 | 47.2%C1,976 | 37.1%1,298 | 53.0%BC3,970 | 51.0%BC1,348 | 48.7%10,308 |
| Maintaining dependencies, packages, or development environments | 44.9%BC1,505 | 41.0%C1,718 | 29.7%1,037 | 47.6%BCa3,566 | 46.6%BC1,231 | 42.8%9,057 |
| Coordinating work across teams or functions | 38.4%C1,288 | 37.7%C1,578 | 27.2%950 | 36.6%C2,740 | 38.1%C1,007 | 35.7%7,563 |
| Finding or fixing security, privacy, or compliance issues | 36.4%BC1,220 | 31.7%C1,328 | 23.5%820 | 38.5%BC2,884 | 37.8%BC999 | 34.3%7,251 |
| Analyzing data, reports, or business metrics | 25.6%C860 | 25.8%C1,080 | 21.5%750 | 25.0%C1,876 | 27.6%C728 | 25.0%5,294 |
| Onboarding to a new project, tool, system, or codebase | 25.6%C860 | 25.3%C1,057 | 21.0%735 | 25.4%C1,906 | 27.1%C717 | 24.9%5,275 |
| None of the above | 0.7%24 | 0.8%34 | 4.2%ABDE146 | 0.7%51 | 1.7%ABD45 | 1.4%300 |
| Respondents | 3,353 | 4,186 | 3,494 | 7,496 | 2,641 | 21,170 |
A letter beside a percentage names the columns it is significantly higher than (uppercase 95%, lowercase 90%; pairwise column tests, Bonferroni-corrected). 9,733 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 “Reviewing code, pull requests, or technical changes”
χ² = 708.49
df = 4, Holm-adjusted p < .001
Effect size
Cramér's V = 0.183
a small association
The strongest answer, APA-style: χ²(4, N = 21170) = 708.49, Holm-adjusted p < .001, V = .18. Each answer is tested on its own, as the respondents who selected it against those who did not, across the 5 groups (N = 21,170). The p-values are Holm-adjusted for the 18 answers tested; 18 of them differ by work setting at the 0.05 level.
| Answer | Selected | χ² (df = 4) | Adjusted p | Cramér's V |
|---|---|---|---|---|
| Writing, editing, or generating code | 92.2% | 211.78 | < .001 | 0.100 |
| Debugging or troubleshooting | 86.8% | 183.76 | < .001 | 0.093 |
| Reviewing code, pull requests, or technical changes | 72.4% | 708.49 | < .001 | 0.183 |
| Making technical design or architecture decisions | 68.0% | 447.97 | < .001 | 0.145 |
| Answering questions from teammates, customers, users, or stakeholders | 66.1% | 474.11 | < .001 | 0.150 |
| Planning, scoping, or estimating work | 62.2% | 532.67 | < .001 | 0.159 |
| Writing or updating documentation | 60.2% | 281.12 | < .001 | 0.115 |
| Deploying or releasing software | 56.2% | 325.37 | < .001 | 0.124 |
| Writing or maintaining tests | 54.9% | 532.39 | < .001 | 0.159 |
| Changing production code, systems, or infrastructure | 54.6% | 310.38 | < .001 | 0.121 |
| Investigating an incident, outage, or production issue | 51.5% | 350.88 | < .001 | 0.129 |
| Monitoring systems, logs, metrics, or alerts | 48.7% | 258.86 | < .001 | 0.111 |
| Maintaining dependencies, packages, or development environments | 42.8% | 342.36 | < .001 | 0.127 |
| Coordinating work across teams or functions | 35.7% | 137.39 | < .001 | 0.081 |
| Finding or fixing security, privacy, or compliance issues | 34.3% | 273.37 | < .001 | 0.114 |
| Analyzing data, reports, or business metrics | 25.0% | 34.73 | < .001 | 0.041 |
| Onboarding to a new project, tool, system, or codebase | 24.9% | 37.41 | < .001 | 0.042 |
| None of the above | 1.4% | 244.17 | < .001 | 0.107 |
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 “Reviewing code, pull requests, or technical changes” 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 work setting. Cramér's V of 0.183 is in the small range, which is real but modest: knowing someone's group tells you only a little about their answer.
With 21,170 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 “Reviewing code, pull requests, or technical changes” 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 work setting
- Technology settings the role touched in the last 12 months by work setting
- Role in choosing software tools by work setting
- Tasks delegated to AI agents by work setting
- Cloud platforms: Worked with in past year by work setting
- Where they look to answer a work question by work setting
- AI tools or agents currently used at work by work setting
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 WorkSetting. 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.