Methodology

The current local response extract includes 39,266 total rows recorded from June 23, 2026 through August 5, 2026, of which 30,903 are marked as valid responses.

The survey was promoted through stackoverflow.com, stackoverflow.blog and our email list to community members that are opted into learning about research opportunities or announcements.

The survey instrument should be referenced from the public Stack Exchange survey repository: StackExchange/Survey.

The public call for feedback that informed the 2026 Developer Survey should be referenced from Meta Stack Overflow: Help shape the 2026 Developer Survey.

The current valid-response rule is implemented in mark_valid_responses() in R/aggregation.R. At a high level, the function adds an integer valid_response indicator to the response data.

When bot exclusion is enabled and the input data does not already include is_bot, the function first runs flag_bots(). The current bot flag uses Qualtrics response-quality fields, including reCAPTCHA score, duplicate respondent status, straightlining questions, unanswered questions, progress, duration, and whether Country was answered.

Responses are marked valid through either the primary inclusion rule or the substantive-response recovery rule.

Primary inclusion rule:

• Consent is present and equals "I agree".
• Employment is present.
• The response is not flagged as a bot when bot exclusion is enabled.

Substantive-response recovery rule:

• The response answered all ten core fielding questions listed below.
• This recovery rule is evaluated independently of the primary non-bot condition, so a response with is_bot == TRUE can still receive valid_response == 1 when it answered all ten core fielding questions.

Core fielding questions:

• Country
• Currency
• Compensation
• TechDropDown
• Languages
• CodeTest
• Databases
• CloudPlat
• WebFramework
• DevIDE

The survey-section scripts use valid_response == 1 as the inclusion rule for exports, so the substantive-response recovery rule is preserved downstream.

Role write-ins from Role_38_TEXT are reviewed only among valid_response == 1 responses, normalized to group repeated answers, and compared against existing and analyst-approved Role categories. Reviewed matches can recode "Other, please specify" into a final Role category while retaining Role_Original and Role_NLP_Status; unresolved write-ins remain grouped as "Other" in summaries.

SOChangeAddl written responses are eligible for public use only when valid_response == 1, SOChangeAddlConsent gives permission to share publicly, and SOChangeAddl is non-empty. Responses are decoded, translated to English when needed, and manually curated with SOChangeAddlPublishText, SOChangeAddlInclude, and SOChangeAddlExcludeReason; automated text flags are used only to support review, not to make final publish decisions.

Compensation is analyzed among valid_response == 1 responses with non-missing Country, Currency, and positive numeric Compensation; values are converted to yearly USD using exchange rates, with a documented Ukraine-specific correction when likely USD values were entered under UAH. Compensation statistics and charts use rows where CompensationStatsInclude and CompensationChartInclude are TRUE, excluding rows with multiple quality flags such as very low or very high converted values, country outliers, suspicious raw-number patterns, non-employed respondents, or student/retired roles.