Skip to content
Open navigation
OpenOpen workspace

Stack Overflow Developer Survey 2026

Activities in a typical work week by education

In the Master's degree (M.A., M.S., M.Eng., MBA, etc.) group, 74% selected “Reviewing code, pull requests, or technical changes”; in the Primary/elementary school group, 32% did. Of the 18 answers tested, “Reviewing code, pull requests, or technical changes” differs most by education, a small association: χ²(7, N = 24673) = 1184.93, Holm-adjusted p < .001, V = .22. Respondents could select more than one answer, so the percentages add to more than 100%. These are unweighted respondents, not population estimates.

Published by crosstabs.com · Last updated ·
How results are checkedNamed 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 education, 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 by education: percentage of each group's respondents who selected each answer, and respondent counts
Activities in a typical work weekPrimary/elementary school (A)Secondary school (e.g. American high school, German Realschule or Gymnasium, etc.) (B)Some college/university study without earning a degree (C)Associate degree (A.A., A.S., etc.) (D)Bachelor's degree (B.A., B.S., B.Eng., etc.) (E)Master's degree (M.A., M.S., M.Eng., MBA, etc.) (F)Professional degree (JD, MD, Ph.D, Ed.D, etc.) (G)Other, please specify (H)All
Writing, editing, or generating code72.9%33185.3%AH1,53287.4%AH2,65285.7%AH67891.9%ABCDGH9,17292.4%ABCDGH6,13289.5%ABH1,37470.4%31689.9%22,187
Debugging or troubleshooting56.2%25574.0%AH1,32979.8%ABH2,42181.2%ABH64286.8%ABCDGH8,66886.4%ABCDGH5,73478.7%ABH1,20963.3%28483.3%20,542
Reviewing code, pull requests, or technical changes32.4%14743.8%A78659.4%ABH1,80163.1%ABH49972.3%ABCDGH7,21974.0%ABCDGH4,90760.2%ABH92543.2%A19466.8%16,478
Making technical design or architecture decisions37.4%17048.0%A86159.3%ABH1,79962.5%ABH49465.6%ABCH6,54470.2%ABCDEGH4,65562.2%ABH95541.2%18563.5%15,663
Answering questions from teammates, customers, users, or stakeholders21.4%9737.5%A67353.2%ABH1,61458.3%ABH46163.9%ABCDH6,38066.3%ABCDGHe4,39761.8%ABCH95038.3%A17259.8%14,744
Planning, scoping, or estimating work29.7%13541.3%A74153.3%ABH1,61855.6%ABH44062.1%ABCDGH6,20361.6%ABCDGH4,08852.5%ABH80735.2%15857.5%14,190
Writing or updating documentation31.1%14141.3%A74253.2%ABH1,61456.4%ABH44658.2%ABCH5,80761.2%ABCEH4,06358.9%ABCH90442.3%A19056.4%13,907
Deploying or releasing software26.0%11840.2%A72250.2%ABGH1,52353.2%ABGH42155.5%ABCGH5,54255.2%ABCGH3,65941.5%A63836.7%A16551.8%12,788
Writing or maintaining tests27.5%12533.0%59245.6%ABH1,38445.3%ABH35854.3%ABCDGH5,41658.0%ABCDEGH3,85047.1%ABH72435.0%15751.1%12,606
Changing production code, systems, or infrastructure24.4%11136.4%A65449.7%ABGH1,50850.4%ABGH39953.7%ABCGH5,35652.7%ABGH3,49441.4%Ab63636.3%A16349.9%12,321
Investigating an incident, outage, or production issue16.1%7331.6%A56744.9%ABGH1,36148.8%ABGH38651.2%ABCGH5,11349.6%ABCGH3,29234.8%A53533.6%A15146.5%11,478
Monitoring systems, logs, metrics, or alerts20.7%9431.6%A56843.2%ABGH1,30946.5%ABGH36848.6%ABCGH4,85446.8%ABCGH3,10534.0%A52328.5%12844.4%10,949
Maintaining dependencies, packages, or development environments20.5%9328.7%A51639.5%ABGH1,19738.6%ABH30541.6%ABGH4,15442.4%ABGH2,81033.5%Ab51527.2%12239.4%9,712
Coordinating work across teams or functions10.1%4617.2%A30827.5%AB83531.5%ABH24935.5%ABCH3,54135.7%ABCH2,37034.0%ABCH52321.8%A9832.3%7,970
Finding or fixing security, privacy, or compliance issues16.7%7623.7%A42633.2%ABG1,00835.8%ABGH28333.8%ABGH3,37432.0%ABG2,12222.3%34326.5%A11931.4%7,751
Onboarding to a new project, tool, system, or codebase12.8%5818.2%32722.4%AB68025.9%AB20524.6%ABG2,45324.0%AB1,59420.8%A31920.5%a9223.2%5,728
Analyzing data, reports, or business metrics11.7%5313.5%24320.6%AB62522.8%ABh18022.5%ABH2,24626.4%ABCEH1,75136.0%ABCDEFH55315.6%7023.2%5,721
None of the above15.2%BCDEFG699.0%CDEFG1625.6%EFG1693.4%F272.0%1961.5%992.9%F4414.9%BCDEFG673.4%833
Respondents4541,7953,0337919,9816,6341,53644924,673

A letter beside a percentage names the columns it is significantly higher than (uppercase 95%, lowercase 90%; pairwise column tests, Bonferroni-corrected). 6,230 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”

χ² = 1184.93

df = 7, Holm-adjusted p < .001

Effect size

Cramér's V = 0.219

a small association

The strongest answer, APA-style: χ²(7, N = 24673) = 1184.93, Holm-adjusted p < .001, V = .22. Each answer is tested on its own, as the respondents who selected it against those who did not, across the 8 groups (N = 24,673). The p-values are Holm-adjusted for the 18 answers tested; 18 of them differ by education at the 0.05 level.

Activities in a typical work week by education: the test of each answer, selected against not selected, by education
AnswerSelectedχ² (df = 7)Adjusted pCramér's V
Writing, editing, or generating code89.9%501.28< .0010.143
Debugging or troubleshooting83.3%668.46< .0010.165
Reviewing code, pull requests, or technical changes66.8%1184.93< .0010.219
Making technical design or architecture decisions63.5%586.15< .0010.154
Answering questions from teammates, customers, users, or stakeholders59.8%981.00< .0010.199
Planning, scoping, or estimating work57.5%600.30< .0010.156
Writing or updating documentation56.4%412.81< .0010.129
Deploying or releasing software51.8%412.13< .0010.129
Writing or maintaining tests51.1%607.91< .0010.157
Changing production code, systems, or infrastructure49.9%402.30< .0010.128
Investigating an incident, outage, or production issue46.5%563.85< .0010.151
Monitoring systems, logs, metrics, or alerts44.4%425.51< .0010.131
Maintaining dependencies, packages, or development environments39.4%248.85< .0010.100
Coordinating work across teams or functions32.3%428.34< .0010.132
Finding or fixing security, privacy, or compliance issues31.4%197.50< .0010.089
Onboarding to a new project, tool, system, or codebase23.2%77.09< .0010.056
Analyzing data, reports, or business metrics23.2%336.17< .0010.117
None of the above3.4%732.85< .0010.172

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 education. Cramér's V of 0.219 is in the small range, which is real but modest: knowing someone's group tells you only a little about their answer.

With 24,673 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 education

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 Education. 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.

  1. [1]Stack Overflow: 2026 Developer Survey public results (survey_results_public.csv)survey.stackoverflow.co
  2. [2]Stack Overflow: Open Database License (ODbL) 1.0opendatacommons.org