Stack Overflow 2022 Developer Survey
Individual responses on the 2022 Developer Survey fielded by Stack Overflow
@kaggle.ebrahimelgazar_stack_overflow_2022_developer_survey
Individual responses on the 2022 Developer Survey fielded by Stack Overflow
@kaggle.ebrahimelgazar_stack_overflow_2022_developer_survey
This is the voice of the developer. Analysts, IT leaders, reporters, and other developers turn to this report to stay up to date with the evolving developer experience, technologies that are rising or falling in favor, and to understand where tech might be going next.
In May 2022 over 90,000 developers responded to our annual survey about how they learn and level up, which tools they're using, and which ones they want.
This year, we went deep into AI/ML to capture how developers are thinking about it and using it in their workflows. Stack Overflow is investing heavily in enhancing the developer experience across our products, using AI and other technology, to get people to solutions faster. Stack Overflow Labs is where we're sharing all we're doing - check it out for a deep dive on AI/ML insights as well as see what we're experimenting with so far.
Happy reading!
This 2022 Developer Survey results are organized on Kaggle in two tables:
Massive, heartfelt thanks to all Stack Overflow contributors and lurking developers of the world who took part in the survey this year. We value your generous participation more than you know. <3
At Stack Overflow, we put developers first and want all developers to feel welcome and included on our site. Can we use our annual survey to understand what kinds of users are less likely to identify as part of our community, participate, or feel kinship with fellow developers? Check out our blog post for more details.
CREATE TABLE survey_results_public (
"responseid" BIGINT,
"mainbranch" VARCHAR,
"employment" VARCHAR,
"remotework" VARCHAR,
"codingactivities" VARCHAR,
"edlevel" VARCHAR,
"learncode" VARCHAR,
"learncodeonline" VARCHAR,
"learncodecoursescert" VARCHAR,
"yearscode" VARCHAR,
"yearscodepro" VARCHAR,
"devtype" VARCHAR,
"orgsize" VARCHAR,
"purchaseinfluence" VARCHAR,
"buynewtool" VARCHAR,
"country" VARCHAR,
"currency" VARCHAR,
"comptotal" DOUBLE,
"compfreq" VARCHAR,
"languagehaveworkedwith" VARCHAR,
"languagewanttoworkwith" VARCHAR,
"databasehaveworkedwith" VARCHAR,
"databasewanttoworkwith" VARCHAR,
"platformhaveworkedwith" VARCHAR,
"platformwanttoworkwith" VARCHAR,
"webframehaveworkedwith" VARCHAR,
"webframewanttoworkwith" VARCHAR,
"misctechhaveworkedwith" VARCHAR,
"misctechwanttoworkwith" VARCHAR,
"toolstechhaveworkedwith" VARCHAR,
"toolstechwanttoworkwith" VARCHAR,
"newcollabtoolshaveworkedwith" VARCHAR,
"newcollabtoolswanttoworkwith" VARCHAR,
"opsysprofessional_use" VARCHAR,
"opsyspersonal_use" VARCHAR,
"versioncontrolsystem" VARCHAR,
"vcinteraction" VARCHAR,
"vchostingpersonal_use" VARCHAR,
"vchostingprofessional_use" VARCHAR,
"officestackasynchaveworkedwith" VARCHAR,
"officestackasyncwanttoworkwith" VARCHAR,
"officestacksynchaveworkedwith" VARCHAR,
"officestacksyncwanttoworkwith" VARCHAR,
"blockchain" VARCHAR,
"newsosites" VARCHAR,
"sovisitfreq" VARCHAR,
"soaccount" VARCHAR,
"sopartfreq" VARCHAR,
"socomm" VARCHAR,
"age" VARCHAR,
"gender" VARCHAR,
"trans" VARCHAR,
"sexuality" VARCHAR,
"ethnicity" VARCHAR,
"accessibility" VARCHAR,
"mentalhealth" VARCHAR,
"tbranch" VARCHAR,
"icorpm" VARCHAR,
"workexp" DOUBLE,
"knowledge_1" VARCHAR,
"knowledge_2" VARCHAR,
"knowledge_3" VARCHAR,
"knowledge_4" VARCHAR,
"knowledge_5" VARCHAR,
"knowledge_6" VARCHAR,
"knowledge_7" VARCHAR,
"frequency_1" VARCHAR,
"frequency_2" VARCHAR,
"frequency_3" VARCHAR,
"timesearching" VARCHAR,
"timeanswering" VARCHAR,
"onboarding" VARCHAR,
"professionaltech" VARCHAR,
"truefalse_1" VARCHAR,
"truefalse_2" VARCHAR,
"truefalse_3" VARCHAR,
"surveylength" VARCHAR,
"surveyease" VARCHAR,
"convertedcompyearly" DOUBLE
);CREATE TABLE survey_results_schema (
"qid" VARCHAR,
"qname" VARCHAR,
"question" VARCHAR,
"force_resp" VARCHAR,
"type" VARCHAR,
"selector" VARCHAR
);Anyone who has the link will be able to view this.