Creating a survey
Improve developer experience by collecting insights directly from your engineers at scale. Identify patterns and turn them into actions.
Last updated
Was this helpful?
Improve developer experience by collecting insights directly from your engineers at scale. Identify patterns and turn them into actions.
Last updated
Was this helpful?
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.
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.
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.
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.
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.)
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:
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.
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.
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.
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.
