Practise the IT-English phrasing for saying no by email: cushioning, offering alternatives, explaining briefly and staying professional.
0 / 14 completed
1 / 14
Which is the most professional way to decline taking on extra work?
Acknowledging the request and giving a brief reason declines clearly while staying courteous.
2 / 14
Why 'offer an alternative' when declining?
Offering an alternative keeps the relationship positive and shows willingness to help where you can.
3 / 14
Which phrase appropriately 'cushions' a refusal?
A cushion ('I appreciate the offer, but...') softens the refusal and keeps the tone warm.
4 / 14
How long should the 'explanation' for declining usually be?
A concise reason is honest and professional; lengthy justification can seem defensive or invite negotiation.
5 / 14
Which closing keeps the door open after declining?
A warm closing preserves the relationship for future collaboration.
6 / 14
Reviewer: 'Hey, can you take a look at this? It's pretty urgent!'
You (as a developer) are currently swamped with bug fixes and sprint commitments. You need to politely decline the request without appearing uncooperative or dismissive. Which of the following responses is most appropriate in this situation?
The key here is managing expectations and demonstrating professionalism. Option A sounds overly enthusiastic and doesn't address your capacity. Option B is blunt and could be perceived negatively. Option C attempts to shift the responsibility without acknowledging your own limitations. Option D clearly states your situation, explains why you can't take on more, and politely declines while maintaining a positive tone – showing respect for the reviewer's request.
7 / 14
Reviewer: 'Hey, can you take a look at this? It's pretty urgent!'
You (as a developer) are currently swamped with bug fixes and sprint commitments. You need to politely decline the request without appearing uncooperative or dismissive. Which of the following responses is most appropriate in this situation?
The key here is managing expectations and demonstrating professionalism. Option A sounds overly enthusiastic and doesn't address your capacity. Option B is blunt and could be perceived negatively. Option C attempts to shift the responsibility without acknowledging your own limitations. Option D clearly states your situation, explains why you can't take on more, and politely declines while maintaining a positive tone – showing respect for the reviewer's request.
8 / 14
Reviewer: 'Hey, can you take a look at this? It's pretty urgent!'
You (as a developer) are currently swamped with bug fixes and sprint commitments. You need to politely decline the request without appearing uncooperative or dismissive. Which of the following responses is most appropriate in this situation?
The key here is managing expectations and demonstrating professionalism. Option A sounds overly enthusiastic and doesn't address your capacity. Option B is blunt and could be perceived negatively. Option C attempts to shift the responsibility without acknowledging your own limitations. Option D clearly states your situation, explains why you can't take on more, and politely declines while maintaining a positive tone – showing respect for the reviewer's request.
9 / 14
Reviewer: 'Hey, can you take a look at this? It's pretty urgent!'
You (as a developer) are currently swamped with bug fixes and sprint commitments. You need to politely decline the request without appearing uncooperative or dismissive. Which of the following responses is most appropriate in this situation?
The key here is managing expectations and demonstrating professionalism. Option A sounds overly enthusiastic and doesn't address your capacity. Option B is blunt and could be perceived negatively. Option C attempts to shift the responsibility without acknowledging your own limitations. Option D clearly states your situation, explains why you can't take on more, and politely declines while maintaining a positive tone – showing respect for the reviewer's request.
10 / 14
You're working with the requests library to make an API call. The response is returned as a JSON string. You need to parse this string into a Python dictionary. Which method is *most* appropriate for doing this, considering best practices and error handling?
Using json.loads() is the standard and safest way to parse a JSON string into a Python dictionary. It handles all the necessary parsing logic and avoids potential security risks associated with using functions like eval(), which can execute arbitrary code from an untrusted source. A try-except block would be good defensive programming but isn't *most* appropriate as the initial parsing method.
11 / 14
A senior developer on your team sends you this Slack message: 'Hey @john_doe, can you take a look at this? It's pretty urgent!' You check the linked issue and see it's a critical bug in production. What's the *most* appropriate immediate response to acknowledge receipt and indicate you're investigating?
Acknowledging receipt and stating intent to investigate is crucial when someone flags an issue as 'urgent'. Option 2 politely confirms you've seen the message and are taking action. The other options either ignore the urgency or shift responsibility inappropriately.
12 / 14
You're writing a PR description for a change that refactors some code. You want to clearly communicate *why* you made the changes and how it improves the codebase. Which sentence is *most* effective in conveying this information concisely?
A good PR description should explain the *reason* behind the changes. Option 3 clearly articulates the rationale (performance & maintainability), providing context for reviewers to understand and appreciate the refactoring. The other options are too vague or lack justification.
13 / 14
A teammate asks you to review their code before they push it to the main branch. They say, 'Can you take a quick look when you have a moment?' How long should *your* explanation for declining (if necessary) be?
While politeness is key, a brief explanation that acknowledges the request and provides a realistic timeframe demonstrates professionalism. 30 seconds allows you to convey your current workload without over-explaining or appearing dismissive. A longer explanation can seem overly formal or defensive.
14 / 14
You've just declined a request from a colleague to help with a task that you are already fully committed on. You want to end the conversation in a way that maintains a positive working relationship and leaves the door open for future collaboration. Which closing statement is *most* appropriate?
Offering to revisit the request in the future demonstrates willingness to help if circumstances change and preserves a positive working relationship. It's polite, proactive, and doesn't completely shut down communication.
What does the "Declining Requests Politely" exercise cover?
Practise the IT-English phrasing for saying no by email: cushioning, offering alternatives, explaining briefly and staying professional.
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.
How many questions are in "Declining Requests Politely"?
This exercise has 14 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more Email & Writing exercises?
Browse the full Email & Writing hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.