LogoLogo
Book a demoLog in
  • Swarmia documentation
  • Getting started
    • Get started in 15 minutes
    • Integrations
      • GitHub
        • GitHub Enterprise Server
        • Multiple GitHub organizations
        • Forked repositories
        • Troubleshooting
          • Reinstalling the Swarmia GitHub app
          • Updating app permissions
          • Installing Swarmia outside of GitHub Marketplace
      • Jira
        • Jira Server and Jira Data Center
        • Multiple Jira organizations
      • Linear
        • Private Linear teams
        • Disconnect Linear
      • Slack
        • Private Slack channels
      • Authentication
        • Google Single Sign-On
          • Frequently asked questions
        • Okta Single Sign-On
      • HR systems
      • Data export
        • Data cloud
        • Export data as a CSV file
      • Other integrations
        • Other issue tracker integrations
        • Other source code hosting integrations
  • Configuration and data quality
    • Teams & members
      • Creating & managing teams
        • Teams API
      • Contributors
      • Roles and permissions
      • Inviting team members
    • Issue tracker configuration
      • Jira configuration
      • Jira best practices
      • Linear configuration
    • Pull request exclusions
    • Linking pull requests to issues
    • Investment categories
    • Deployments
      • Generate deployments from merged pull requests
      • Generate deployments from GitHub deployments
      • Generate deployments from GitHub checks
      • Generate deployments via the API
        • Generate deployments for monorepos via the API
    • Sprint configuration
  • Use cases
    • Improve pull request flow
      • Pull request insights
      • Reducing pull request cycle time
      • Review code faster
      • Managing pull requests in progress with the Pull Request view
      • Diagnosing low pull request throughput
      • Analyzing pull request batch size
  • Improve your team's focus
    • Optimizing issue cycle time
    • Analyzing activity patterns on Work Log
    • Grouping activity on the Work Log view
    • Focus summary
  • Balance engineering investments
    • Activity and effort-based models
    • Categorizing work
    • Common problems with balancing engineering investment
  • Deliver strategic initiatives
    • Forecasting initiatives
  • Capitalize software development costs
  • Run developer experience surveys
    • Creating a survey
    • Managing surveys
    • Viewing and sharing survey results
    • How we show your survey responses
    • Survey communication guide and templates
  • Track DORA metrics
    • Automatic change failure detection
    • How Swarmia links PRs to deployments
  • Coach software developers
  • Get visibility into your CI pipeline
  • Continuous improvement
    • Working agreements
  • Notifications
    • Team notifications
    • Personal notifications
  • Retrospectives with Swarmia
  • Metrics & definitions
    • Pull request cycle time
      • What's the difference between "Change lead time" and "Pull request cycle time" metrics in Swarmia?
    • Issue cycle time
      • Defining issue lifecycle and cycle time
    • Developer effort (FTEs)
  • DORA metrics
    • Change lead time
    • Deployment frequency
    • Mean time to recovery
    • Change failure rate
  • Throughput
  • Time to deploy
  • Batch size
  • Flow efficiency
  • Scope creep
  • Sprints
  • Frequently asked questions
    • How do you treat weekends in metrics?
    • Tracking squashed commits
    • How do merge queues affect my metrics?
    • Why is my commit not visible in Swarmia?
    • How do I account for people leaving my organization?
  • Resources
    • Security & data retention
      • Data security
      • Data access
      • Swarmia IP Addresses
      • Single Sign-On (SSO) / SAML
      • Can I get a copy of the SOC 2 Type II audit report?
      • Deleting your organization
  • Pricing & plans
    • Compare plans
    • Free plan
    • Do I need a credit card to start a free trial?
    • What are the differences between the individual modules and the standard plan?
    • How do you determine the number of developers for billing?
    • What happens to customers with the Lite plan after the December 2024 pricing and plan change?
  • Changelog
On this page
  • Questions
  • Custom questions
  • Teams and schedule
  • Preview
  • Launching the survey
  • Reminders
  • Frequently asked questions
  • Why should I run developer surveys?
  • How are developer surveys different from employee engagement surveys?
  • How are people notified about the survey?

Was this helpful?

  1. Run developer experience surveys

Creating a survey

Improve developer experience by collecting insights directly from your engineers at scale. Identify patterns and turn them into actions.

PreviousRun developer experience surveysNextManaging surveys

Last updated 1 month ago

Was this helpful?

Only Swarmia users with the can create and manage surveys. Contact hello@swarmia.com if you'd like to allow everyone in your organization to create surveys.

To start creating an engineering survey, navigate to the Surveys page from the sidebar and click Create survey.

Your progress is automatically saved as a draft so you can exit the view and resume later.

Give the survey a name, which will also be visible to the respondents.

Questions

Select the questions to include in the survey. Choose from Swarmia's questions, carefully crafted in collaboration with experts in psychometrics. They are all framed as statements, and the respondents answer them on a five-point scale from strongly disagree to strongly agree. You'll see the estimated time to complete based on your selections.

In addition to the questions you select, the survey will also include an option for the respondents to add open comments at the end.

Custom questions

You can also add your own questions by selecting Add question in one of the topics.

These use the same format as the built-in questions. They should be statements, and the respondents rate how much they agree with each on a five-point scale. Agreeing with the statement is considered good and yields the highest score of 5.

Teams and schedule

On the next tab, select the teams for which the survey will be available.

You can't remove people from the survey after launching it. The team structure and memberships will be saved as a static "snapshot" when the survey goes live. New people in the teams will be automatically added to live surveys, but no other changes will be made.

Example: You launch a survey for Team Yellow. After that, you add Jane to the team and remove John from it. Both Jane and John will be included in the survey.

Choose an end date for the survey. When it's reached, the survey will close for responses, and the results will become available to admins.

The start date can't be changed. The survey will go live immediately when you launch it.

Preview

Click Preview to see how the respondents will see the survey.

A popup opens, showing the preview with your latest selections. (You can respond as if you belong to any team, but your submission won't be recorded.)

Launching the survey

Click Launch survey when you're ready to go live. The survey is open for responses immediately.

To distribute the survey, click Copy link to get a link you can send to your teams. We also provide you an example message with all the survey information prefilled.

Users in the audience will also see a notification banner on their Swarmia home page:

Reminders

Swarmia automatically sends a Slack notification to all survey participants one hour after the survey opens. After that, Swarmia will notify people who haven’t responded 7, 3, and 1 day(s) before the survey closes.

We'll notify you if we can't find some of the people from Slack. In that case, we recommend manually reminding them.

Frequently asked questions

Why should I run developer surveys?

You need data to make the most informed decisions for improving your engineering effectiveness. To get the full picture, you can't rely only on system metrics from sources like version control systems or issue trackers. Surveys help you form a comprehensive understanding of how your developers perceive their work. They also allow engineers to voice their frustrations, suggest improvements, and feel heard.

How are developer surveys different from employee engagement surveys?

Employee engagement surveys are a generic way to measure job satisfaction and identify areas for improvement, usually at the company level. Swarmia's developer surveys are purpose-built for engineers with questions about topics like code reviews, automated tests, and technical debt.

Instead of just informing the human resources department and executives, they're a resource for the engineering organization and teams to address hands-on problems autonomously. The engineers can describe challenges in technical terms and get understood.

We recommend running developer surveys alongside any engagement surveys in your company. If you're concerned about the overlap between the two, you can disable some or all the questions under Direction, Collaboration, and Culture.

How are people notified about the survey?

Respondents can access the survey via a link you send them when launching it. We will also send personal Slack notifications one hour after the launch so you can prepare any announcements. People who haven’t responded 7, 3, and 1 day(s) before the survey closes will be reminded via Slack.

on our blog.

You can by team to manually remind the ones lagging behind.

Read our tips for creating high-quality questions
follow the survey participation rates
Admin role