Surveys

Surveys collect qualitative feedback directly from your developers, complementing the quantitative data Antenna gathers from your Git, project tracker, and AI tool integrations. A survey asks a short set of scored questions, each tagged with one or more dimensions, and reports the results as scores you can compare across dimensions and track from one survey to the next.

Creating surveys

Create a survey

Go to Surveys in the enterprise navigation and click Create new survey. The survey starts in draft mode and does not yet collect responses.

Open the survey

Click Start collecting responses to move the survey to Open. The survey can now accept responses.

Each survey has a unique link. Use Copy link to survey to share it with your developers. Responses appear on the results page as they arrive.

Stop collecting responses

Click Close survey once you have the responses you need. Closing a survey is permanent: respondents can no longer submit answers, and the survey cannot be reopened. The results will remain available.

Collecting responses

Developers open the survey link, enter their name and email, and answer each question on the provided scale. No Antenna account or sign-in is required, and completing a survey takes only a few minutes. Each email address can submit once per survey.

Exploring results

Every survey has a results page with four summary cards:

Card	What it shows
Overall Satisfaction	Average of every scored answer, on the survey’s scale
Responses	Completed submissions
Questions	Questions included in the survey
Needs Attention	Questions with more negative than positive responses

Select any card to open a drilldown with the data that supports it.

Sentiment scores

The Sentiment table rolls every question up by dimension. Each row shows a response-weighted satisfaction score normalized to 0–100, how many questions carry that dimension, and the distribution of answers from Very unsatisfied to Very satisfied.

Question breakdown

Each question shows its average score, response count, and answer distribution. Answers below the middle of the scale count as negative, answers above it count as positive, and answers at the midpoint count as neutral. A question is flagged as needing attention when negative responses outnumber positive ones.

Engineering Pulse

The Engineering Pulse survey is a short, recurring check on how developers experience day-to-day software development at your company. It is deliberately broad, highlighting which parts of the developer experience are healthy and which warrant a closer look. Because it takes only a few minutes to complete, you can repeat it often enough to see whether things are trending in the right direction.

The Engineering Pulse survey uses a single agree/disagree scale, from Strongly Disagree to Strongly Agree, across a small set of statements. Every question is required, and each one is tagged with exactly one dimension, so a dimension’s score reflects a single clear statement rather than a blend of topics.

The Engineering Pulse survey covers the dimensions below. Together, they capture how effectively developers feel they can make progress, how sustainable that pace is, and how much of their experience is shaped by the systems and people around them.

Dimension	Why it matters
Satisfaction	Overall sentiment toward the development environment, and the single best summary of developer experience.
Productivity	Whether developers feel able to consistently move work forward.
Well-being	Whether the current pace is sustainable, or a sign of burnout risk.
Engagement	How connected developers feel to the value of their work — a driver of both quality and retention.
Focus	How much uninterrupted time developers get, which is often the limiting factor on deep work.
Collaboration	Access to timely help, knowledge, feedback, and decisions from colleagues.
Quality	Confidence in the reliability and maintainability of what the team ships.
Flow	Confidence in the path from finished code to production.
Learning	Whether the team reflects on and improves its own ways of working.
Outlook	Whether developers expect their experience to improve — a leading indicator of the other dimensions.

Permissions

Managers, Directors, and Admins can view surveys and their results.
Only Admins can create, open, and close surveys.

See Roles and Permissions for the full permissions matrix.