5 exercises — the language of developer experience surveys, from scale design to NPS to closing the feedback loop.
Key DX survey terms
1-to-10 scale — produces variance for trend tracking and NPS calculation
Biggest pain point — open-ended question that surfaces qualitative signal
Developer NPS — % promoters minus % detractors; negative = more detractors
Survey fatigue — declining response quality from over-surveying
Cohort segmentation — slicing results by team type, seniority, role
0 / 14 completed
1 / 14
A DX researcher explains to the team: "We use a Likert scale — specifically a 1-to-10 scale — rather than a yes/no question because it gives us variance and lets us track movement over time." What is the primary advantage of a 1-to-10 scale in developer surveys?
Continuous variance is the key advantage of a 1-to-10 scale. A binary yes/no only tells you which camp a developer is in, while a 1-10 rating reveals intensity and allows you to: compute a mean score, track quarter-over-quarter movement (e.g. "satisfaction moved from 6.4 to 7.1"), segment into promoters (9-10), passives (7-8), and detractors (1-6) for NPS calculation, and correlate scores with team or tool variables. Common phrasing: "On a scale of 1 to 10, how would you rate your confidence in the development environment setup?" or "On a scale of 1 to 10, how likely are you to recommend this team as a great place to work?"
2 / 14
During a survey design workshop, a developer advocate says: "The best DX surveys focus on a single biggest pain point question — it surfaces qualitative signal that no closed question can capture." Which phrasing best represents this open-ended technique?
"What is your biggest pain point in the development workflow right now?" is a classic open-ended DX survey question. It is powerful because: (1) it does not presuppose a category — developers may mention build times, review wait, unclear requirements, or poor documentation; (2) responses cluster naturally into themes you can prioritise; (3) verbatim answers provide quotable evidence for leadership. Best practice: pair one open-ended pain-point question with your quantitative Likert items so you have both signal types. In reporting language: "The top-cited pain point was slow CI pipelines — mentioned by 41% of respondents."
3 / 14
A platform team lead reads a report: "Our developer NPS is currently −12, which is significantly below industry benchmarks. Detractors cite build times and inconsistent environments." What does a negative developer NPS indicate?
Developer NPS (Net Promoter Score for developer tools or teams) = % Promoters − % Detractors. A score of −12 means detractors outnumber promoters by 12 percentage points — a clear signal of systemic dissatisfaction. NPS ranges from −100 (everyone is a detractor) to +100 (everyone is a promoter). For internal developer tooling, scores above +20 are considered good; above +50 is excellent. Typical report phrasing: "Our developer NPS dropped from +5 to −12 following the platform migration — we need to address the top detractor themes before the next release." Detractor themes are surfaced via the open-ended follow-up: "What would most improve your experience?"
4 / 14
An engineering manager says: "We are seeing classic signs of survey fatigue — response rates dropped from 78% to 31% over three quarters, and the remaining responses show less thoughtful answers." Which practice best combats survey fatigue in developer experience programmes?
Short surveys + consistent cadence + visible action is the gold-standard approach to preventing survey fatigue. The three components work together: (1) brevity — 5 to 7 questions take under 3 minutes; developers skip long surveys; (2) consistency — a quarterly pulse keeps data comparable and developers know what to expect; (3) closing the feedback loop — the most critical factor: when developers see changes made in response to their answers, they trust future surveys. The phrase to use: "We ran a 5-question pulse survey in Q2 and response rate was 82% — because we published a 'You said, we did' report after Q1."
5 / 14
A DX programme manager presents results: "We segment survey respondents by team type — platform, product, embedded — because aggregated scores can mask very different experiences across groups." What is the term for this analysis technique?
Cohort segmentation (also called cut analysis or demographic slicing) means analysing survey data by meaningful subgroups such as team type, seniority level, geographic location, or time at the company. It matters because: an overall satisfaction score of 7.2 could hide a product team at 8.5 and a platform team at 5.4 — two very different situations requiring different interventions. Common segments in developer surveys: team type (platform vs. product vs. embedded), tenure (new joiners vs. 2+ years), role (IC vs. tech lead), and office vs. remote. Reporting language: "When we segment by team type, junior developers rate onboarding 4.1 while seniors rate it 7.8 — a gap that demands targeted action."
6 / 14
During a code review discussion, Sarah says to Mark: "I'm noticing a lot of 'workarounds' in this module. It feels like we're constantly patching around the core API limitations instead of genuinely addressing them with proper design changes."
What does Sarah likely mean when she uses the term 'workaround' in this context?
Sarah's use of 'workaround' indicates a temporary solution implemented to overcome a limitation in the existing system. This term often implies that the underlying problem isn't being properly addressed and might lead to further instability or require repeated fixes over time – a common frustration for developers dealing with constrained APIs. The goal is usually a permanent, design-driven solution rather than continual patching.
7 / 14
During a code review discussion, Sarah says to Mark: "I'm noticing a lot of 'workarounds' in this module. It feels like we're constantly patching around the core API limitations instead of genuinely addressing them with proper design changes."
What does Sarah likely mean when she uses the term 'workaround' in this context?
Sarah's use of 'workaround' indicates a temporary solution implemented to overcome a limitation in the existing system. This term often implies that the underlying problem isn't being properly addressed and might lead to further instability or require repeated fixes over time – a common frustration for developers dealing with constrained APIs. The goal is usually a permanent, design-driven solution rather than continual patching.
8 / 14
During a code review discussion, Sarah says to Mark: "I'm noticing a lot of 'workarounds' in this module. It feels like we're constantly patching around the core API limitations instead of genuinely addressing them with proper design changes."
What does Sarah likely mean when she uses the term 'workaround' in this context?
Sarah's use of 'workaround' indicates a temporary solution implemented to overcome a limitation in the existing system. This term often implies that the underlying problem isn't being properly addressed and might lead to further instability or require repeated fixes over time – a common frustration for developers dealing with constrained APIs. The goal is usually a permanent, design-driven solution rather than continual patching.
9 / 14
During a code review discussion, Sarah says to Mark: "I'm noticing a lot of 'workarounds' in this module. It feels like we're constantly patching around the core API limitations instead of genuinely addressing them with proper design changes."
What does Sarah likely mean when she uses the term 'workaround' in this context?
Sarah's use of 'workaround' indicates a temporary solution implemented to overcome a limitation in the existing system. This term often implies that the underlying problem isn't being properly addressed and might lead to further instability or require repeated fixes over time – a common frustration for developers dealing with constrained APIs. The goal is usually a permanent, design-driven solution rather than continual patching.
10 / 14
Mark (Product Team Lead) sends a Slack message: "Hey team, just ran the initial DX survey data. The 'ease of onboarding' score is consistently low – around a 3 out of 10. We need to dig into why new developers are struggling."
The primary goal here isn't simply to collect more data, but to *act* on the identified problem. A low score on 'ease of onboarding' suggests a tangible issue – likely bugs or confusing steps – that should be addressed directly by prioritizing bug fixes. Ignoring it would mean missing an opportunity for immediate improvement.
11 / 14
Emily (Code Reviewer) comments on a PR: "This workaround feels like a band-aid. Instead of addressing the core API limitation – slow data retrieval – we're building around it. We need to focus on genuine solutions."
Emily's comment isn't about a specific technical solution; it's a critique of the *strategy*. 'Band-aid' and 'building around' are idioms that signal she sees this as a short-term fix masking a deeper problem – the core API limitation. This points to the need for strategic solutions, not just quick fixes.
12 / 14
David (Engineering Manager) in a standup update says: "We're seeing high levels of frustration around the lack of clear documentation for our new authentication service. Developers are spending significant time reverse-engineering it, and that's impacting their velocity."
David's statement directly identifies a key pain point: the lack of documentation. The fact that developers are 'reverse-engineering' it highlights its absence and the negative impact on their velocity. Prioritizing detailed documentation is the logical response to this observed frustration.
13 / 14
Lisa (DX Analyst) writes in a PR description: "To ensure we're capturing the most relevant feedback, I've added a question to the survey asking developers to rate their 'cognitive load' when using this feature. This will help us understand how complex our APIs are perceived to be."
'Cognitive Load,' in this context, refers to the mental effort required to use a system. It's a common DX metric used to assess API complexity and usability. Lisa is correctly applying this concept to gather data on how developers perceive the feature's difficulty – directly addressing the goal of understanding API complexity.
14 / 14
John (Platform Team Lead) says: "We're segmenting our survey responses by team type – Frontend, Backend, and DevOps – to identify if specific teams are experiencing disproportionately high levels of pain. Aggregated scores don't tell the whole story."
John recognizes that different team types (Frontend, Backend, DevOps) will have distinct needs and pain points when interacting with the platform. Segmenting allows for a more granular understanding of the DX experience, revealing if certain teams are disproportionately affected – which is crucial for targeted improvements.
What does the "DX Survey Design Vocabulary" exercise practise?
Practice the vocabulary of developer experience surveys: 1-to-10 scales, pain point questions, developer NPS, survey fatigue, and cohort segmentation.
How many questions are in this exercise?
This exercise has 14 questions, each multiple-choice with a full explanation shown after you answer.
What English level is this exercise for?
This exercise is tagged Intermediate. If the vocabulary feels difficult, browse the Developer Experience Metrics category page for an easier module to start with.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free with no account, sign-up, or paywall.
Do I get feedback if I answer incorrectly?
Yes — whichever option you choose, right or wrong, you'll immediately see an explanation clarifying the correct term and why the other options don't fit.
Can I retry this exercise?
Yes — once you finish all the questions, a "Try again" button on the results screen resets the exercise so you can practise as many times as you like.
Do I need an account to track my progress?
No account is required. Your progress bar and score for this session are tracked in the browser as you go, but nothing is saved once you leave the page.
Is "DX Survey Design Vocabulary" part of a larger series?
Yes — it's one exercise in the Developer Experience Metrics category on CoderSlingo. See the category page for the full list of related exercises on similar terminology.
Can I link directly to this exercise?
Yes — this exercise has its own permanent URL, so you can bookmark it or share the link directly with a colleague or study partner.
Where can I find more exercises like this one?
See the Developer Experience Metrics category page for related exercises, or browse the main Exercises hub for other IT English topics.