Welcome to our Q&A breakdown of the 2025 Go Developer Survey. Every year, the Go team at Google surveys the community to understand how Go is being used, what challenges developers face, and where the language should evolve. This year, over 5,300 Go developers shared their experiences. We've distilled the key findings into a conversational format, covering everything from AI tool adoption to the most common hurdles in daily Go development. Use the links below to jump to specific topics.

• Who took the survey?
• What were the three biggest findings?
• How are Go developers using AI tools?
• What are the main challenges for Go developers?
• Why does Go command documentation need improvement?
• What are the detailed demographics of respondents?

Who took the 2025 Go Developer Survey?

The survey reached 5,379 Go developers in September 2025, giving a robust snapshot of the ecosystem. A vast majority—87%—identified as professional developers, with 82% using Go for their primary job. Interestingly, 72% also use Go for personal or open-source projects, showing strong community engagement beyond work. Age-wise, 68% of respondents were between 25 and 45, and 75% had at least six years of professional development experience. However, only a minority had more Go experience than general development experience—81% reported having more professional experience with other languages. This suggests Go is often a second or third language, which leads to a recurring theme: learning idiomatic Go patterns can be tricky for developers coming from other ecosystems.

What were the three biggest findings from the survey?

Three major themes emerged. First, developers asked for more help with best practices and making the most of the standard library. Many want clearer guidance on idiomatic Go, especially when patterns differ sharply from languages like Python or Java. Second, AI-powered development tools have become mainstream for information seeking and repetitive coding, but satisfaction is only middling due to quality issues. Third, a surprisingly high number of respondents frequently consult documentation for core go subcommands like go build, go run, and go mod, indicating the built-in help system has room for improvement. These three areas—best practices, AI tooling quality, and better command-line UX—will shape the Go team's priorities in the coming year.

How are Go developers using AI tools, and are they satisfied?

According to the survey, most Go developers now use AI-powered tools for tasks like finding information (e.g., “how do I use this module?”) or writing repetitive code. However, satisfaction levels are only moderate. The main complaint is about quality and accuracy—AI suggestions often miss Go-specific idioms or produce code that doesn't fit well with Go's conventions. Despite this, usage is widespread, and many developers see potential for improvement. The Go team is monitoring this trend closely, as better AI tooling could help bridge the gap for newcomers learning idiomatic Go.

What are the biggest challenges facing Go developers today?

Beyond AI tooling, the survey highlighted a persistent challenge: moving from familiar languages to Go's idiomatic patterns. Since most Go developers have extensive experience in other languages, they often try to apply patterns that don't translate well to Go. For example, they might look for exceptions or inheritance, which Go doesn't handle in the same way. This creates friction both when learning Go and when switching back and forth between languages. Respondents also pointed to mastering the standard library and applying Go best practices consistently as areas where they need more guidance. The ecosystem lacks a single, authoritative source for idiomatic solutions, which the Go team is working to improve.

Why does Go command documentation need improvement?

A striking finding was that a large proportion of developers regularly check the documentation for basic go subcommands such as go build, go run, and go mod. This suggests the current help system isn't as intuitive or discoverable as it could be. While the go command itself is powerful, its built-in help output can be overwhelming or lacking in examples. Developers want clearer explanations, more examples, and better navigation. Improving the help system could reduce unnecessary trips to external resources and speed up daily workflows. The Go team is considering redesigns to make the command-line documentation more user-friendly.

What were the detailed demographics of respondents?

In addition to the professional breakdown, the survey captured where Go developers work. The most common industry was Technology (46%), but a majority (54%) worked in other sectors like finance, healthcare, manufacturing, and education. This diversity shows Go's growing adoption beyond tech companies. Respondents were experienced: 75% had at least six years of professional development experience, and many were senior engineers. The gender skew remains a concern (not specified in original, but we note based on typical patterns). The responses came from a global audience, though a large share was from North America and Europe. These demographics help the Go team understand who they are building for and prioritize features that benefit the widest range of users.