Go 2025 Developer Survey Now Open – Deadline September 30

By

Go 2025 Developer Survey Launches Today

URGENT: The Go team has officially opened the 2025 Go Developer Survey, with responses accepted until September 30. The survey, which takes 10–20 minutes to complete, aims to capture the evolving needs of the global Go community.

“Your feedback helps us brainstorm, plan, and prioritize work on Go,” said Todd Kulesza, speaking on behalf of the Go team. All questions are optional, but every response helps shape the language’s future.

Background

This annual survey has been a cornerstone of Go’s development roadmap for years. The Go team uses the aggregated data to identify pain points, desired features, and usage patterns across industries and skill levels.

This year, the team will also release the raw anonymized dataset after aggregating results. This follows the same opt-in model used for Go Telemetry — only respondents who explicitly grant permission will have their answers included in the public dataset.

What This Means

The survey results, expected to be published on the Go blog in early November, directly influence the language’s direction. Past surveys have led to decisions on tooling, error handling, and package management.

With broader community data, external researchers and organizations can also conduct their own analyses. As Kulesza noted, “We love it when you share the survey with your colleagues, friends, and online communities. The more voices we hear, the better we can understand the diverse needs of Go developers everywhere.”

How to Participate

1. Take the survey — available now at the official Go survey link.
2. Opt in for your responses to be included in the public dataset (optional but encouraged).
3. Share widely — forward to coworkers, meetups, and online forums before the September 30 deadline.

The raw dataset will be released alongside the summary blog post. This transparency marks a significant step for community-driven development.

For more details on past survey outcomes, see Background or check previous posts on the Go Blog.

Related Articles

• Stack Allocation in Go: Boosting Performance with Constant-Sized Slices
• Automating Intellectual Toil: How I Built eval-agents with GitHub Copilot
• Python Developers: New Quiz Puts Flattening List Skills to the Test
• Navigating AI Governance in Enterprise Vibe Coding: A Practical Guide
• AI Agents Rewrite the Playbook: Will Human-Written Source Code Become Obsolete?
• How the Python Packaging Council Came to Be: A Step-by-Step Guide
• Everything You Need to Know About the Python Security Response Team
• Python 3.15 Alpha 6: A Developer Preview Packed with New Features and Performance Gains