Developer Satisfaction Survey Vocabulary
Practice developer satisfaction survey vocabulary: Likert scale design, eNPS calculation, survey fatigue, open vs. closed questions, and action planning from results.
0 / 25 completed
1 / 25
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 / 25
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 / 25
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 / 25
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 / 25
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.
6 / 25
Sarah: 'This PR is a mess! The code isn't documented, the variable names are cryptic, and it seems like you just slapped some logic together. I'm going to leave several comments pointing out these issues.'
Which of the following best describes Sarah's sentiment in this Slack message? This scenario demonstrates constructive criticism, which is a vital part of code reviews. Sarah is clearly identifying specific problems (lack of documentation, unclear variable names) and offering to address them through comments. The other options misrepresent her intention; she's not being passive-aggressive or simply requesting clarification – she's actively pointing out areas needing improvement. It's important to understand the nuance when evaluating feedback in a development setting.
7 / 25
Mark: 'I'm feeling really frustrated with the current codebase. It's constantly changing without clear rationale, and I spend half my time just trying to understand what others have done before me. The lack of consistent architectural decisions is making it incredibly difficult to maintain any sense of forward momentum.' Which of the following best describes Mark's sentiment in this Slack message?
Mark's message conveys a deep sense of frustration stemming from inconsistent changes and a lack of architectural guidance. The key here is that he's not simply disagreeing with a specific decision; rather, he's highlighting a fundamental problem—the codebase's instability and the absence of clear direction. This reflects a common developer sentiment when faced with poorly managed technical debt or a chaotic development environment – it's about feeling lost and unproductive due to systemic issues, not just isolated problems.
8 / 25
// Code Review Scenario
During a code review of a new feature pull request, Liam comments: "This function is doing too much. It should be broken down into smaller, more manageable units. Also, the error handling could be improved – it's currently quite verbose and doesn't clearly explain why an error occurred."
Which of the following best describes Liam's sentiment in this code review comment?
Liam's comment demonstrates constructive criticism – he's offering suggestions for improvement regarding code design and error handling. The key here is that he's not simply pointing out a problem; he's proposing solutions. Option A accurately captures this intent, while the other options misrepresent his tone or focus.
9 / 25
// PR Description
During a pull request review for a new API endpoint, Anya writes: 'This endpoint returns all user data, including sensitive information like credit card details. While technically functional, it violates our security policy and exposes users to significant risk. I've flagged this for immediate attention.' Which of the following best describes Anya's sentiment in this PR description?
Anya's message demonstrates a concerned sentiment because she is explicitly pointing out a violation of a policy (security) and detailing the potential negative consequences – exposing user data. The incorrect options represent different levels of emotional intensity that aren't present in her careful and factual description; simply stating requirements or expressing disappointment doesn't capture the urgency and seriousness of her feedback. This response focuses on professional, actionable language.
10 / 25
David: 'Just got an email from QA – the latest deploy broke production. Apparently, a minor change in the authentication module caused a cascading failure. Seriously, this is getting ridiculous.'
Which of the following best describes David's sentiment in this Slack message?David's message clearly indicates frustration due to the negative consequences of a recent deployment. The phrase 'getting ridiculous' emphasizes his exasperation with repeated issues. Importantly, it's not neutral reporting; the tone suggests he's personally affected by the problem. Selecting 'concerned' is a reasonable interpretation of his underlying worry, but 'frustrated' better captures the core emotion expressed in the message.11 / 25
Sarah: 'This PR is a mess! The code isn't documented, the variable names are cryptic, and it seems like you just slapped some logic together. I'm going to leave several comments pointing out these issues.'
Which of the following best describes Sarah's sentiment in this Slack message? This scenario demonstrates constructive criticism, which is a vital part of code reviews. Sarah is clearly identifying specific problems (lack of documentation, unclear variable names) and offering to address them through comments. The other options misrepresent her intention; she's not being passive-aggressive or simply requesting clarification – she's actively pointing out areas needing improvement. It's important to understand the nuance when evaluating feedback in a development setting.
12 / 25
Mark: 'I'm feeling really frustrated with the current codebase. It's constantly changing without clear rationale, and I spend half my time just trying to understand what others have done before me. The lack of consistent architectural decisions is making it incredibly difficult to maintain any sense of forward momentum.' Which of the following best describes Mark's sentiment in this Slack message?
Mark's message conveys a deep sense of frustration stemming from inconsistent changes and a lack of architectural guidance. The key here is that he's not simply disagreeing with a specific decision; rather, he's highlighting a fundamental problem—the codebase's instability and the absence of clear direction. This reflects a common developer sentiment when faced with poorly managed technical debt or a chaotic development environment – it's about feeling lost and unproductive due to systemic issues, not just isolated problems.
13 / 25
// Code Review Scenario
During a code review of a new feature pull request, Liam comments: "This function is doing too much. It should be broken down into smaller, more manageable units. Also, the error handling could be improved – it's currently quite verbose and doesn't clearly explain why an error occurred."
Which of the following best describes Liam's sentiment in this code review comment?
Liam's comment demonstrates constructive criticism – he's offering suggestions for improvement regarding code design and error handling. The key here is that he's not simply pointing out a problem; he's proposing solutions. Option A accurately captures this intent, while the other options misrepresent his tone or focus.
14 / 25
// PR Description
During a pull request review for a new API endpoint, Anya writes: 'This endpoint returns all user data, including sensitive information like credit card details. While technically functional, it violates our security policy and exposes users to significant risk. I've flagged this for immediate attention.' Which of the following best describes Anya's sentiment in this PR description?
Anya's message demonstrates a concerned sentiment because she is explicitly pointing out a violation of a policy (security) and detailing the potential negative consequences – exposing user data. The incorrect options represent different levels of emotional intensity that aren't present in her careful and factual description; simply stating requirements or expressing disappointment doesn't capture the urgency and seriousness of her feedback. This response focuses on professional, actionable language.
15 / 25
David: 'Just got an email from QA – the latest deploy broke production. Apparently, a minor change in the authentication module caused a cascading failure. Seriously, this is getting ridiculous.'
Which of the following best describes David's sentiment in this Slack message?David's message clearly indicates frustration due to the negative consequences of a recent deployment. The phrase 'getting ridiculous' emphasizes his exasperation with repeated issues. Importantly, it's not neutral reporting; the tone suggests he's personally affected by the problem. Selecting 'concerned' is a reasonable interpretation of his underlying worry, but 'frustrated' better captures the core emotion expressed in the message.16 / 25
Sarah: 'This PR is a mess! The code isn't documented, the variable names are cryptic, and it seems like you just slapped some logic together. I'm going to leave several comments pointing out these issues.'
Which of the following best describes Sarah's sentiment in this Slack message? This scenario demonstrates constructive criticism, which is a vital part of code reviews. Sarah is clearly identifying specific problems (lack of documentation, unclear variable names) and offering to address them through comments. The other options misrepresent her intention; she's not being passive-aggressive or simply requesting clarification – she's actively pointing out areas needing improvement. It's important to understand the nuance when evaluating feedback in a development setting.
17 / 25
Mark: 'I'm feeling really frustrated with the current codebase. It's constantly changing without clear rationale, and I spend half my time just trying to understand what others have done before me. The lack of consistent architectural decisions is making it incredibly difficult to maintain any sense of forward momentum.' Which of the following best describes Mark's sentiment in this Slack message?
Mark's message conveys a deep sense of frustration stemming from inconsistent changes and a lack of architectural guidance. The key here is that he's not simply disagreeing with a specific decision; rather, he's highlighting a fundamental problem—the codebase's instability and the absence of clear direction. This reflects a common developer sentiment when faced with poorly managed technical debt or a chaotic development environment – it's about feeling lost and unproductive due to systemic issues, not just isolated problems.
18 / 25
// Code Review Scenario
During a code review of a new feature pull request, Liam comments: "This function is doing too much. It should be broken down into smaller, more manageable units. Also, the error handling could be improved – it's currently quite verbose and doesn't clearly explain why an error occurred."
Which of the following best describes Liam's sentiment in this code review comment?
Liam's comment demonstrates constructive criticism – he's offering suggestions for improvement regarding code design and error handling. The key here is that he's not simply pointing out a problem; he's proposing solutions. Option A accurately captures this intent, while the other options misrepresent his tone or focus.
19 / 25
// PR Description
During a pull request review for a new API endpoint, Anya writes: 'This endpoint returns all user data, including sensitive information like credit card details. While technically functional, it violates our security policy and exposes users to significant risk. I've flagged this for immediate attention.' Which of the following best describes Anya's sentiment in this PR description?
Anya's message demonstrates a concerned sentiment because she is explicitly pointing out a violation of a policy (security) and detailing the potential negative consequences – exposing user data. The incorrect options represent different levels of emotional intensity that aren't present in her careful and factual description; simply stating requirements or expressing disappointment doesn't capture the urgency and seriousness of her feedback. This response focuses on professional, actionable language.
20 / 25
David: 'Just got an email from QA – the latest deploy broke production. Apparently, a minor change in the authentication module caused a cascading failure. Seriously, this is getting ridiculous.'
Which of the following best describes David's sentiment in this Slack message?David's message clearly indicates frustration due to the negative consequences of a recent deployment. The phrase 'getting ridiculous' emphasizes his exasperation with repeated issues. Importantly, it's not neutral reporting; the tone suggests he's personally affected by the problem. Selecting 'concerned' is a reasonable interpretation of his underlying worry, but 'frustrated' better captures the core emotion expressed in the message.21 / 25
Sarah: 'This PR is a mess! The code isn't documented, the variable names are cryptic, and it seems like you just slapped some logic together. I'm going to leave several comments pointing out these issues.'
Which of the following best describes Sarah's sentiment in this Slack message? This scenario demonstrates constructive criticism, which is a vital part of code reviews. Sarah is clearly identifying specific problems (lack of documentation, unclear variable names) and offering to address them through comments. The other options misrepresent her intention; she's not being passive-aggressive or simply requesting clarification – she's actively pointing out areas needing improvement. It's important to understand the nuance when evaluating feedback in a development setting.
22 / 25
Mark: 'I'm feeling really frustrated with the current codebase. It's constantly changing without clear rationale, and I spend half my time just trying to understand what others have done before me. The lack of consistent architectural decisions is making it incredibly difficult to maintain any sense of forward momentum.' Which of the following best describes Mark's sentiment in this Slack message?
Mark's message conveys a deep sense of frustration stemming from inconsistent changes and a lack of architectural guidance. The key here is that he's not simply disagreeing with a specific decision; rather, he's highlighting a fundamental problem—the codebase's instability and the absence of clear direction. This reflects a common developer sentiment when faced with poorly managed technical debt or a chaotic development environment – it's about feeling lost and unproductive due to systemic issues, not just isolated problems.
23 / 25
// Code Review Scenario
During a code review of a new feature pull request, Liam comments: "This function is doing too much. It should be broken down into smaller, more manageable units. Also, the error handling could be improved – it's currently quite verbose and doesn't clearly explain why an error occurred."
Which of the following best describes Liam's sentiment in this code review comment?
Liam's comment demonstrates constructive criticism – he's offering suggestions for improvement regarding code design and error handling. The key here is that he's not simply pointing out a problem; he's proposing solutions. Option A accurately captures this intent, while the other options misrepresent his tone or focus.
24 / 25
// PR Description
During a pull request review for a new API endpoint, Anya writes: 'This endpoint returns all user data, including sensitive information like credit card details. While technically functional, it violates our security policy and exposes users to significant risk. I've flagged this for immediate attention.' Which of the following best describes Anya's sentiment in this PR description?
Anya's message demonstrates a concerned sentiment because she is explicitly pointing out a violation of a policy (security) and detailing the potential negative consequences – exposing user data. The incorrect options represent different levels of emotional intensity that aren't present in her careful and factual description; simply stating requirements or expressing disappointment doesn't capture the urgency and seriousness of her feedback. This response focuses on professional, actionable language.
25 / 25
David: 'Just got an email from QA – the latest deploy broke production. Apparently, a minor change in the authentication module caused a cascading failure. Seriously, this is getting ridiculous.'
Which of the following best describes David's sentiment in this Slack message?David's message clearly indicates frustration due to the negative consequences of a recent deployment. The phrase 'getting ridiculous' emphasizes his exasperation with repeated issues. Importantly, it's not neutral reporting; the tone suggests he's personally affected by the problem. Selecting 'concerned' is a reasonable interpretation of his underlying worry, but 'frustrated' better captures the core emotion expressed in the message.Frequently Asked Questions
What does the "Developer Satisfaction Survey Vocabulary" exercise practise?
Practice developer satisfaction survey vocabulary: Likert scale design, eNPS calculation, survey fatigue, open vs. closed questions, and action planning from results.
How many questions are in this exercise?
This exercise has 25 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 "Developer Satisfaction Survey 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.