January 21, 2026 – The 2025 Go Developer Survey, released today by the Go team at Google, reveals a sharp rise in the use of AI-powered development tools among Go programmers, yet satisfaction with these tools remains tepid due to quality concerns. Additionally, the survey highlights a widespread struggle with Go's command-line help system, pointing to significant opportunities for improvement in the language's tooling and best practices support.
Conducted in September 2025, the survey garnered responses from 5,379 Go developers worldwide. According to the findings, most Go developers now rely on AI tools for tasks such as learning new modules or writing repetitive code, but they report middling satisfaction, primarily because of inaccuracies in generated output.
“While developers are eager to integrate AI into their workflows, satisfaction is dampened by quality issues,” said Todd Kulesza, member of the Go team and author of the survey report. “This year’s data clearly show that the community wants better guidance on best practices and more modern capabilities from the language and its built-in tooling.”
Key Findings at a Glance
- AI adoption surges: Majority of respondents use AI for information seeking (e.g., learning how to use a module) or toil reduction (e.g., writing repetitive code).
- Quality gap persists: Satisfaction with AI tools is moderate; quality of generated content is the top pain point.
- Documentation disatisfaction: A surprisingly high number of developers frequently need to revisit documentation for core Go commands like
go build,go run, andgo mod. - Developer profile: 87% of respondents are professional developers; 82% use Go at their primary job. The majority have more professional experience than Go-specific experience, indicating Go is often a second or later language.
Background
The Go Developer Survey is an annual effort by the Go team to understand the evolving needs of the community. It helps prioritize features, documentation, and ecosystem improvements. This year’s survey, distributed during September 2025, focused on development challenges, tool usage, and satisfaction with the language’s ecosystem.
Most respondents (68%) are aged 25–45 and have at least six years of professional development experience (75%). 81% reported having more professional development experience than Go-specific experience, reinforcing that Go is frequently a second language—a pattern that creates friction when idiomatic Go patterns differ from those in more familiar languages.
What This Means
The results underscore a growing divide between developer expectations and current Go tooling. With AI adoption accelerating, the Go team must address quality issues to keep satisfaction from declining further. The high demand for better built-in help and modern language features suggests that incremental improvements to the go command and standard library may no longer suffice.
“These findings indicate that the Go community is ready for more advanced tooling and clearer guidance around best practices,” said Kulesza. “We see this as a call to action to improve both the learning experience and the day-to-day development workflow.”
Industry-wise, the technology sector dominates (46%), but the survey captures developers from a wide range of fields. The friction from switching languages remains a key challenge—a finding that could influence future Go language design and documentation strategies.