Practice developer satisfaction survey vocabulary: Likert scale design, eNPS calculation, survey fatigue, open vs. closed questions, and action planning from results.
0 / 5 completed
1 / 5
A survey question reads: 'On a scale of 1–5, how would you rate your onboarding experience?' This is an example of a ___ scale question.
A Likert scale uses a numeric or agree/disagree range (typically 5 or 7 points) to measure attitudes. It produces quantifiable data that can be tracked over time and compared across teams.
2 / 5
What is eNPS in a developer survey context?
eNPS (Employee Net Promoter Score) asks 'How likely are you to recommend this company as a place to work?' on a 0–10 scale. Promoters (9–10) minus Detractors (0–6) gives the eNPS. It's widely used in developer experience programmes.
3 / 5
What is 'survey fatigue' in the context of developer experience measurement?
Survey fatigue occurs when developers are surveyed too often or feel their feedback never leads to action. It results in low response rates and less honest answers, undermining the measurement programme.
4 / 5
Why should developer surveys include a mix of open-ended and closed questions?
Closed questions (scales, multiple choice) give trackable metrics over time. Open-ended questions let developers explain problems in their own words, providing qualitative context that numbers alone cannot capture.
5 / 5
After running a developer satisfaction survey, the next critical step is:
Survey results must lead to visible action. Publishing an action plan — with specific changes, owners, and timelines — is essential to maintain developer trust and future survey participation rates.