2025 Go Developer Survey: Developers Struggle with Best Practices, AI Tools Underperform, and Core Command Docs Fall Short

Breaking: 2025 Go Developer Survey Reveals Critical Pain Points

The 2025 Go Developer Survey, released today by the Go team at Google, has unveiled a trio of urgent challenges: developers are demanding clearer best practices, AI-powered tools receive middling satisfaction due to quality issues, and a surprising number need frequent help with core go subcommands. These findings, based on responses from 5,379 developers, signal a need for immediate improvements in documentation, tooling, and language evolution.

“Broadly speaking, Go developers asked for help with identifying and applying best practices, making the most of the standard library, and expanding the language and built-in tooling with more modern capabilities,” said Todd Kulesza, a member of the Go team. The survey, conducted in September 2025, points to a widening gap between developer expectations and current Go ecosystem support.

Key Findings

AI Tool Adoption vs. Satisfaction

Most Go developers now use AI-powered development tools for information seeking or repetitive coding tasks. However, satisfaction is middling, primarily due to quality concerns. “Their satisfaction with these tools is middling due, in part, to quality concerns,” Kulesza noted.

Best Practices and Standard Library

Developers are struggling to navigate idiomatic Go patterns, especially when switching between languages. “When the way to do a task in Go is substantially different from a more familiar language, it creates friction,” the survey report states. The demand for better standard library guidance and modern capabilities is urgent.

Core Command Documentation Gaps

A surprisingly high proportion of respondents frequently need to review documentation for go build, go run, and go mod. Kulesza said this suggests “meaningful room for improvement with the go command’s help system.”

Background

The Go Developer Survey is an annual, independent study conducted by the Go team at Google to understand developer needs and prioritize the language roadmap. The 2025 edition received 5,379 responses from professional developers (87%) who use Go as their primary job (82%), with 72% also using it for personal or open-source projects.

Respondents are largely experienced: 68% are aged 25-45, and 75% have at least six years of professional development experience. Notably, 81% said they had more professional experience than Go-specific experience, indicating Go is often a second or third language. The technology sector accounts for 46% of respondents, but a majority come from diverse industries.

What This Means

The survey results indicate that the Go ecosystem must address several key pain points to maintain its momentum. The call for clearer best practices and enhanced standard library resources suggests that many developers feel lost when applying Go to real-world problems. The satisfaction gap with AI tools, despite high adoption, warns that relying on generative AI without improved quality could frustrate users.

Furthermore, the need for better help systems for core commands implies that even experienced developers are hitting bottlenecks with basic workflows. The Go team will likely prioritize improvements to go command documentation, add more idiomatic examples to the standard library, and consider language features that reduce cognitive friction for polyglot developers.

“Your feedback helps both the Go team at Google and the wider Go community understand the current state of the Go ecosystem and prioritize projects for the year ahead,” Kulesza wrote. Immediate action on these issues could determine whether Go continues its upward trajectory in enterprise and open-source development.

Survey Methodology

The 2025 Go Developer Survey was conducted online in September 2025. Invitations were sent to a representative sample of Go users, yielding 5,379 responses. The margin of error is ±1.3 percentage points at a 95% confidence level. Full methodology is available on the Go blog.