Go Developer Survey 2025: Key Insights and Trends

Overview of the 2025 Go Developer Survey

The Go team at Google recently published the results of its 2025 Developer Survey, conducted in September 2025. With responses from 5,379 Go developers worldwide, the survey provides a comprehensive look at how developers are using Go, their biggest challenges, and where the language and tooling need improvement. This article breaks down the most important findings.

Who Responded to the Survey?

The respondent pool was largely composed of professional developers. According to the data:

• 87% identify as professional developers.
• 82% use Go as part of their primary job.
• 72% use Go for personal or open-source projects.

Age-wise, the majority (68%) fall between 25 and 45 years old. Experience levels are high: 75% have at least six years of professional development experience. A telling statistic is that 81% of respondents reported having more general professional development experience than Go-specific experience. This suggests Go is frequently a second or later language for developers, which can create friction when idiomatic Go patterns differ from more familiar languages.

Three Major Findings

Three overarching themes emerged from the survey responses:

1. Desire for guidance on best practices and the standard library. Developers are seeking help with identifying and applying idiomatic Go patterns, making the most of the standard library, and expanding the language and built-in tooling with modern capabilities.
2. AI tool usage is widespread but satisfaction is mixed. Most Go developers now use AI-powered tools for tasks like searching for information (e.g., learning how to use a module) or automating repetitive code writing. However, satisfaction remains middling, primarily due to quality concerns.
3. Documentation for core go subcommands needs improvement. A surprisingly high proportion of respondents frequently need to review documentation for commands such as go build, go run, and go mod. This indicates that the current help system has significant room for improvement.

How Do People Feel About Go?

While the survey didn't provide a single satisfaction score, the qualitative feedback points to a community that appreciates Go's simplicity, performance, and concurrency model, but also struggles with onboarding new idiomatic patterns. The friction from transitioning from other languages is a recurring theme. Many respondents expressed a desire for more structured learning paths and clearer documentation.

What Are People Building with Go?

The survey found that Go continues to dominate in cloud infrastructure, microservices, and CLI tooling. Notably, the largest industry segment represented is Technology (46%), but a wide range of sectors from finance to healthcare are also using Go. Developers often combine Go with other languages for full-stack or system-level projects.

Biggest Challenges Facing Go Developers

Beyond the three major findings, respondents highlighted several persistent challenges:

• Learning idiomatic Go: Developers transitioning from languages like Python, Java, or JavaScript find Go's error handling, composition over inheritance, and struct-based typing unfamiliar.
• Standard library discovery: Many developers are unaware of powerful packages in the standard library and rely on third-party libraries unnecessarily.
• Tooling complexity: While the go command is powerful, its help system is not always intuitive, leading to frequent lookups.

These pain points align with the survey's call for better educational resources and modernized tooling.

Development Environments and Tools

The survey also shed light on how developers configure their Go environments. The most popular editors remain VS Code (with the Go extension) and GoLand. AI-assisted coding tools are increasingly integrated into these environments. However, the quality of AI-generated Go code is a concern—developers report spending extra time verifying and debugging AI suggestions.

Another finding is that the go command's help system could be more discoverable. The survey suggests that improving go help and adding interactive examples could reduce the time developers spend searching for documentation.

Survey Methodology

The survey was conducted online during September 2025. Invitations were sent to Go developers via official channels, including the Go blog, mailing lists, and social media. A total of 5,379 complete responses were collected. The data is self-reported, and results reflect the opinions of those who chose to respond. The Go team uses this feedback to prioritize language features, tooling improvements, and community resources for the coming year.

Back to top