Skip to content
Open navigation
OpenOpen workspace

Stack Overflow Developer Survey 2026

Organization's measures on AI cost and usage by employment status

In the Employed group, 41% selected “Set limits on AI tool or model usage or spending”; in the Retired group, 3% did. Of the 1 answers tested, “Set limits on AI tool or model usage or spending” differs most by employment status, a small association: χ²(5, N = 11468) = 238.82, Holm-adjusted p < .001, V = .14. 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: Which, if any, of the following has your organization done related to AI tool or model usage? 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%.

Organization's measures on AI cost and usage by employment status: percentage of each group's respondents who selected each answer, and respondent counts
Organization's measures on AI cost and usageEmployed (A)I prefer not to say (B)Independent contractor, freelancer, or self-employed (C)Not employed (D)Retired (E)Student (F)All
Set limits on AI tool or model usage or spending41.3%CE3,8960.0%023.7%E45323.3%e102.6%121.2%738.1%4,367
Reviewed internal usage or spending data for AI tools or models30.7%CE2,9010.0%017.0%32516.3%77.9%312.1%428.3%3,240
Approved different AI tools or models for different types of work29.4%CE2,77633.3%117.2%32923.3%105.3%212.1%427.2%3,122
Set limits on who can use certain AI tools or models27.6%CE2,60433.3%114.9%28414.0%65.3%212.1%425.3%2,901
Increased spending on AI tools or models because results justified it21.0%1,9780.0%019.8%37814.0%67.9%33.0%120.6%2,366
Not sure18.1%1,70433.3%116.1%30727.9%1221.1%833.3%c1117.8%2,043
None of the above14.4%1,35566.7%232.6%A62425.6%1165.8%ACD2539.4%A1317.7%2,030
Compared buying an AI tool with building something internally11.7%C1,10033.3%19.7%1867.0%30.0%00.0%011.2%1,290
Stopped using or reduced spending on other software tools while increasing investment in AI tools or models8.8%8310.0%08.0%15314.0%62.6%13.0%18.7%992
Negotiated shorter commitments or the ability to switch AI tools or models over time3.0%2870.0%03.8%739.3%a40.0%00.0%03.2%364
Respondents9,43931,91243383311,468

A letter beside a percentage names the columns it is significantly higher than (uppercase 95%, lowercase 90%; pairwise column tests, Bonferroni-corrected). 19,435 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 “Set limits on AI tool or model usage or spending”

χ² = 238.82

df = 5, Holm-adjusted p < .001

Effect size

Cramér's V = 0.144

a small association

The strongest answer, APA-style: χ²(5, N = 11468) = 238.82, Holm-adjusted p < .001, V = .14. Each answer is tested on its own, as the respondents who selected it against those who did not, across the 6 groups (N = 11,468). The p-values are Holm-adjusted for the 1 answers tested; 1 of them differs by employment status at the 0.05 level. 9 answers are not tested: too few respondents selected them for the test to be reliable (an expected count below 1, or more than 20% of the expected counts below 5).

Organization's measures on AI cost and usage by employment status: the test of each answer, selected against not selected, by employment status
AnswerSelectedχ² (df = 5)Adjusted pCramér's V
Set limits on AI tool or model usage or spending38.1%238.82< .0010.144
Reviewed internal usage or spending data for AI tools or models28.3%Not tested: expected counts too small
Approved different AI tools or models for different types of work27.2%Not tested: expected counts too small
Set limits on who can use certain AI tools or models25.3%Not tested: expected counts too small
Increased spending on AI tools or models because results justified it20.6%Not tested: expected counts too small
Not sure17.8%Not tested: expected counts too small
None of the above17.7%Not tested: expected counts too small
Compared buying an AI tool with building something internally11.2%Not tested: expected counts too small
Stopped using or reduced spending on other software tools while increasing investment in AI tools or models8.7%Not tested: expected counts too small
Negotiated shorter commitments or the ability to switch AI tools or models over time3.2%Not tested: expected counts too small

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 1 answers gives 1 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 “Set limits on AI tool or model usage or spending” 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.144 is in the small range, which is real but modest: knowing someone's group tells you only a little about their answer.

With 11,468 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 “Set limits on AI tool or model usage or spending” 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

Source

Stack Overflow. 2026 Developer Survey, https://survey.stackoverflow.co/2026, licensed under the ODbL 1.0. Tabulated by crosstabs.com. Variables AIToken (Organization's measures on AI cost and usage) 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.

  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