Survey Now Open Through September 30
The Go development team has officially launched its 2025 Go Developer Survey, inviting the global community of Go programmers to share their experiences and priorities. The survey, open until September 30, 2025, takes an estimated 10 to 20 minutes to complete and allows respondents to skip any question.
Todd Kulesza, speaking on behalf of the Go team, stated: The Go Team uses the results of this annual survey to better understand the needs and concerns of Go developers across the world. Your feedback helps us brainstorm, plan, and prioritize work on Go.
New This Year: Public Raw Dataset
For the first time, the Go team will release the raw, anonymized dataset of survey responses. Kulesza noted: This year we’ll also share the raw dataset of survey responses, so that the entire Go community can benefit from this knowledge and conduct your own analyses on the data.
Participation in this public dataset is strictly opt-in, mirroring the model used for Go Telemetry.
Background
The annual Go Developer Survey is a cornerstone of the Go project’s community engagement strategy. Since its inception, the survey has provided quantitative and qualitative insights that directly influence the language’s roadmap, tooling improvements, and ecosystem development.
Previous surveys have helped identify pain points in concurrency, error handling, and dependency management, leading to targeted improvements in subsequent releases. The 2025 edition aims to capture evolving developer needs as Go continues to expand into cloud-native, microservices, and systems programming domains.
What This Means
The results of this survey will shape Go’s development priorities for the coming year. As the language approaches its fifteenth anniversary, the team is particularly interested in feedback on areas such as generics adoption, tooling modernization, and support for AI/ML workloads.
By making the raw data publicly available (with consent), the Go team is empowering researchers, community groups, and individual developers to conduct their own analyses. This transparency could uncover regional or industry-specific trends that might otherwise be overlooked.
Call to Action
The Go team strongly encourages developers to take the survey and share it with colleagues, friends, and online communities. Kulesza emphasized: The more voices we hear, the better we can understand the diverse needs of Go developers everywhere.
Aggregated results will be published on the Go Blog in early November 2025.