5 exercises — practise balancing directness and professional tact in technical and workplace communication.
0 / 21 completed
1 / 21
Which sentence uses direct, precise wording appropriate for a postmortem, avoiding vague euphemism?
"The database connection pool was exhausted...causing 502 errors" is correct: postmortems require precise, direct language that names the exact technical cause and effect so the failure can be diagnosed and prevented in the future. Option A uses the vague euphemism "a bit of an issue", which conveys no actionable technical information. Option B uses the informal, imprecise euphemism "went sideways", which similarly fails to specify what actually happened. Option C softens the failure with "some challenges", a euphemism that avoids stating the concrete technical fault.
2 / 21
Which sentence uses an appropriately softened, professional euphemism (not blunt bluntness) when informing a client about a missed deadline, while still being honest?
"We underestimated the scope of the migration, which pushed the delivery date back by one week" is correct: it is professionally softened (avoiding blunt self-criticism like "messed up") while remaining specific, honest, and informative about the cause and the concrete new timeline. Option A is unnecessarily blunt and informal ("messed up"), which is inappropriate for client communication even though it is honest. Option C uses a vague euphemism, "stuff that came up", that gives the client no real information. Option D uses a flippant, imprecise euphemism ("basically dead") that fails to state a clear status. Option E is direct but gives no cause or revised timeline, making it unhelpfully blunt without being informative.
3 / 21
Which sentence replaces the vague corporate euphemism with direct, transparent wording in an internal engineering update?
"Reducing the on-call rotation from six engineers to four this quarter" is correct: it states the specific, verifiable change directly, which is what an internal engineering update needs for planning purposes. Option A uses the vague corporate euphemism "rightsizing", which obscures whether the rotation is growing or shrinking. Option C uses "optimizing", a euphemism that could mean almost any change and gives no concrete numbers. Option D uses "streamlining", another vague euphemism that avoids stating what specifically changes.
4 / 21
In a security disclosure, which sentence avoids euphemistic minimization and states the risk directly?
"A subset of user data, including email addresses and hashed passwords, was exposed for approximately six hours" is correct: security disclosures require direct, specific language naming exactly what data was exposed and for how long, so affected users can assess their risk. Option A uses the vague hedge "may have been some exposure of certain data elements", which minimizes and obscures the actual scope. Option C downplays the incident as a "minor data situation", a euphemism that understates severity and omits detail. Option D uses the noncommittal "potentially accessible under certain conditions", which avoids confirming what actually happened.
5 / 21
Choose the sentence that replaces the euphemism "let go" with more contextually appropriate direct HR/technical-team phrasing, while remaining professional.
"Are no longer with the company due to headcount reductions in this quarter's reorganization" is correct: it is direct and specific about the cause (headcount reductions, reorganization) while remaining professionally appropriate, striking the needed balance between honesty and workplace tact. Option A uses the softer euphemism "let go", which is common but less specific about the underlying cause than the correct answer. Option B uses the flippant, unprofessional euphemism "released into the wild", inappropriate for a serious HR context. Option D uses the vague, overly cheerful euphemism "moved on to new adventures", which misleadingly implies a voluntary departure.
6 / 21
During a code review of a new microservice, Alice comments on a section of code. Which response best demonstrates direct and constructive feedback, avoiding potentially misleading euphemisms?
This question targets the use of direct questioning and seeking clarification during code review. Options A and C employ overly flowery or vague language, masking potential issues. Option B directly asks for explanation, while option D avoids any critical feedback altogether – a classic euphemistic tactic to avoid confrontation. The goal is clear communication, not gentle suggestion.
7 / 21
As a Senior Engineer, you need to inform the Product Manager about an unexpected delay in delivering a key feature. Which of the following sentences provides the most professional and transparent communication?
This tests using direct language to communicate delays. Phrases like 'slight hiccup' or 'things are moving slowly' are euphemisms that downplay the issue and lack accountability. Option 2 explicitly states the delay and its impact, demonstrating transparency and responsibility—crucial for maintaining trust with stakeholders. It avoids softening the truth with vague terms.
8 / 21
You're drafting an internal engineering update summarizing a complex system failure. Which of the following statements is the most appropriate and avoids euphemistic understatement?
This focuses on using precise language in technical documentation. Options A and D are overly vague and minimize the severity of the event. Option B is slightly better but still avoids directness. Option 2 – 'A significant error occurred that impacted service availability' – clearly describes the problem and its consequences, demonstrating professionalism and accuracy. The key is to avoid sugarcoating technical problems.
9 / 21
During a code review of a new microservice, Alice comments on a section of code. Which response best demonstrates direct and constructive feedback, avoiding potentially misleading euphemisms?
This question targets the use of direct questioning and seeking clarification during code review. Options A and C employ overly flowery or vague language, masking potential issues. Option B directly asks for explanation, while option D avoids any critical feedback altogether – a classic euphemistic tactic to avoid confrontation. The goal is clear communication, not gentle suggestion.
10 / 21
As a Senior Engineer, you need to inform the Product Manager about an unexpected delay in delivering a key feature. Which of the following sentences provides the most professional and transparent communication?
This tests using direct language to communicate delays. Phrases like 'slight hiccup' or 'things are moving slowly' are euphemisms that downplay the issue and lack accountability. Option 2 explicitly states the delay and its impact, demonstrating transparency and responsibility—crucial for maintaining trust with stakeholders. It avoids softening the truth with vague terms.
11 / 21
You're drafting an internal engineering update summarizing a complex system failure. Which of the following statements is the most appropriate and avoids euphemistic understatement?
This focuses on using precise language in technical documentation. Options A and D are overly vague and minimize the severity of the event. Option B is slightly better but still avoids directness. Option 2 – 'A significant error occurred that impacted service availability' – clearly describes the problem and its consequences, demonstrating professionalism and accuracy. The key is to avoid sugarcoating technical problems.
12 / 21
During a code review of a new microservice, Alice comments on a section of code. Which response best demonstrates direct and constructive feedback, avoiding potentially misleading euphemisms?
This question targets the use of direct questioning and seeking clarification during code review. Options A and C employ overly flowery or vague language, masking potential issues. Option B directly asks for explanation, while option D avoids any critical feedback altogether – a classic euphemistic tactic to avoid confrontation. The goal is clear communication, not gentle suggestion.
13 / 21
As a Senior Engineer, you need to inform the Product Manager about an unexpected delay in delivering a key feature. Which of the following sentences provides the most professional and transparent communication?
This tests using direct language to communicate delays. Phrases like 'slight hiccup' or 'things are moving slowly' are euphemisms that downplay the issue and lack accountability. Option 2 explicitly states the delay and its impact, demonstrating transparency and responsibility—crucial for maintaining trust with stakeholders. It avoids softening the truth with vague terms.
14 / 21
You're drafting an internal engineering update summarizing a complex system failure. Which of the following statements is the most appropriate and avoids euphemistic understatement?
This focuses on using precise language in technical documentation. Options A and D are overly vague and minimize the severity of the event. Option B is slightly better but still avoids directness. Option 2 – 'A significant error occurred that impacted service availability' – clearly describes the problem and its consequences, demonstrating professionalism and accuracy. The key is to avoid sugarcoating technical problems.
15 / 21
During a Slack conversation with the team about debugging a slow API endpoint, Ben writes: 'We're seeing some… *challenges* with response times.' Which of the following is the MOST appropriate response to Ben's message?
Ben's use of 'challenges' is a euphemism masking the technical problem. Option 0 directly addresses the issue and suggests action. Options 2 and 3 minimize or deflect the seriousness of the situation, avoiding clear communication. Option 1, while slightly better, still relies on ambiguous terminology – a good response focuses on understanding the specific issue.
16 / 21
In a code review comment for a newly submitted feature, Sarah writes: 'This is… *a bit tricky* to understand.' Which of the following best demonstrates constructive feedback and avoids potentially misleading euphemisms?
Sarah's comment is a vague and unhelpful criticism. Option 0 directly identifies the area of confusion and requests clarification. Options 2 and 3 offer dismissive or irrelevant responses. Option 1 lacks detail but still seeks explanation while acknowledging Sarah's difficulty.
17 / 21
During a Slack conversation regarding a failing automated test suite, Mark writes: 'The tests are… *not cooperating*.' Which of the following responses from Liam is the MOST appropriate and professional?
Option 0 directly asks for information and initiates a solution-oriented response. 'Not cooperating' is a euphemism that obscures the actual problem. Options 2 and 3 are vague and avoid taking action. Option 4 suggests abandoning testing procedures, which is unprofessional.
18 / 21
You're writing a pull request description for a new API endpoint. Which of the following descriptions best balances clarity with professional tone?
Option 1 provides a clear and concise description of the purpose and functionality of the API endpoint using professional terminology. It avoids subjective opinions or euphemisms like 'mostly functional.' Options 2 and 3 are too vague, while option 4 is overly boastful and unprofessional.
19 / 21
As a senior developer, you're reviewing a colleague's code that introduces a complex dependency. Which of the following comments is the MOST effective and constructive?
Option 1 uses a euphemism and doesn't directly address the concerns. Option 2 focuses on potential risks and encourages a discussion about alternatives – demonstrating critical thinking. Options 3 and 4 are overly simplistic and lack specific feedback. The goal is to guide the developer to consider the broader implications of their changes.
20 / 21
During a standup meeting, Alex reports on his progress. He says: 'I've been… *working through some challenges* with the data migration.' Which of the following is the BEST follow-up from Sarah (the team lead)?
Option 0 prompts Alex to provide details about the 'challenges,' which is crucial for understanding the situation and offering support. 'Working through some challenges' is a vague euphemism that doesn't reveal the true nature of the problem. Options 2 and 3 are dismissive or overly supportive without seeking clarification.
21 / 21
David, a junior developer, writes in a Slack channel: 'The server's been having a little hiccup lately.' During a debugging session with the team, which response best demonstrates clear and professional communication regarding the issue?
This question tests directness in a common communication context – Slack. The incorrect options use euphemisms like 'hiccup' or vague statements. Option 1 is overly dismissive and lacks specifics. Option 2 provides quantifiable data about the problem, demonstrating professional technical language. Option 3 avoids addressing the issue entirely, while option 4 suggests a concrete action is being taken.
What will I practise in "Euphemism vs. Directness in Technical English — IT Grammar Exercise"?
Practise choosing between softened, professional phrasing and direct, precise wording in postmortems, security disclosures, and internal updates.
How many exercises are in this module?
This module has 21 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the grammar rule and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Grammar exercises?
Browse the full Grammar hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain grammar rules in prose; this exercise tests and reinforces those rules through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.