6766
Programming

Go Developer Survey 2025: Your Voice Matters

Posted by u/Jiniads · 2026-05-03 17:07:39

The Go team is excited to launch the 2025 Go Developer Survey! Each year, this survey helps us understand how you're using Go, what's working well, and where we can improve. The feedback directly shapes future development priorities. Below, we answer the most common questions about the survey, how to participate, and what happens with your responses.

What is the 2025 Go Developer Survey?

The annual Go Developer Survey is the primary way the Go team gathers insights from the global community. It covers topics like satisfaction with Go, commonly used frameworks, challenges you face, and new feature requests. The survey runs from September 16 to September 30, 2025. It takes about 10–20 minutes to complete, and every question is optional—you can skip any that don’t apply. The aggregated findings will be shared on this blog in early November alongside raw survey data for the community to explore.

Go Developer Survey 2025: Your Voice Matters
Source: blog.golang.org

Who can take the survey?

Any developer who uses Go—whether at work, on side projects, or just learning—is encouraged to participate. The more diverse the voices, the better the Go team can understand the needs of developers across industries, experience levels, and regions. You can share the survey link with colleagues, friends, and online communities. We especially welcome responses from newcomers and underrepresented groups. This is your chance to make sure that Go evolves in a way that serves everyone, not just the loudest voices.

How will my responses be used?

Your answers directly influence the Go team’s priorities. Past surveys have led to improvements in generics, error handling, tooling, and documentation. Aggregated results are published so the whole community can benefit. For deeper analysis, we also release a raw dataset of anonymized responses—but only if you opt in. This opt-in model follows the same philosophy as Go Telemetry: you control what data is shared. Without your permission, your individual responses will not be included in the public dataset. We take privacy seriously.

What about privacy? How does the opt-in work?

Privacy is a top priority. At the end of the survey, you will be asked for explicit permission to include your responses in the public dataset. This is entirely voluntary. If you decline, your answers are only used for internal aggregation and are not shared. The dataset itself strips personal identifiers like email addresses and IP addresses. We also apply rounding and suppression techniques to protect against re-identification. You can review the full privacy policy during the survey. This approach ensures transparency and gives you full control over your contribution.

How can I help spread the word?

We rely on the community to make this survey representative. Please share the survey link on social media, in developer forums, at meetups, or via email to your team. The more participants, the richer the data. You can also mention it in Go-related Slack channels, Reddit threads (r/golang), or within your organization. Every response helps us paint an accurate picture of how Go is being used worldwide. Together, we can ensure that Go continues to be a practical, enjoyable language for all developers.

Where can I find the raw survey data?

In early November 2025, the Go team will publish the aggregated results on this blog. Additionally, for the first time, we will release the raw survey dataset—anonymized and with opt-in consent only. This allows researchers, educators, and community members to conduct their own analyses. The dataset will be available on the Go Blog and via a direct download link. You can use it to explore trends, compare with past years, or create visualizations. We think this open approach will spur even more innovation in the Go ecosystem.

When will the results be published?

Look for the survey results in early November 2025, right here on the Go Blog. The post will include high-level findings, interesting trends, and links to the raw dataset. If you want to stay up to date, follow the Go Blog or the official Go Twitter account. Past surveys have revealed exciting insights—like the rapid adoption of generics and the growing use of Go in cloud infrastructure. We can’t wait to see what we learn from you this year!