Asking for Help the Right Way
Learn the vocabulary and structure for asking effective technical questions in English — in Slack, Stack Overflow, GitHub Issues, or with a senior colleague.
0 / 27 completed
1 / 27
What is an 'MRE' (or 'MWE') in the context of asking for help?
An MRE (Minimal Reproducible Example) or MWE (Minimal Working Example) is the smallest, self-contained code snippet that reliably demonstrates the problem. Providing one is the most effective way to get help — it shows you've already isolated the issue.
2 / 27
Which question provides the most useful context when asking for debugging help?
A good technical help request includes: what you expected, what actually happened, the error message, and what you've already tried. This context prevents the helper from repeating steps you've already taken.
3 / 27
What does 'rubber duck debugging' mean?
Rubber duck debugging is the practice of explaining your code or problem out loud, step by step — often to a rubber duck. The act of articulating the problem clearly often causes you to spot the issue yourself before even needing to ask for help.
4 / 27
Which phrase is the best way to frame a question when you are not sure if your understanding is correct?
Framing your question around your mental model ('my understanding is...') invites the helper to correct your assumptions directly. It shows intellectual honesty and makes it easy to identify exactly where your understanding breaks down.
5 / 27
What is 'XY problem' when asking for help?
The XY problem: you want to do X, you think Y is the solution, Y doesn't work, so you ask about Y — but the real problem is X. Always describe your underlying goal, not just the specific approach you got stuck on.
6 / 27
In a GitHub issue, which phrase best introduces the steps to reproduce a bug?
'Steps to reproduce:' is the standard GitHub/GitLab issue convention, typically followed by a numbered list. It signals to the maintainer exactly what they need to do to see the problem themselves.
7 / 27
You've asked for help and the person gave a suggestion that didn't work. What is the most productive response?
Closing the loop with the helper — explaining what you tried, the result, and current state — is efficient and respectful. It lets the conversation build progressively toward the solution rather than repeating ineffective suggestions.
8 / 27
Which phrase is correct when you are escalating an issue to a more senior engineer?
Good escalation summarises what you've already investigated (showing you're not escalating prematurely), states your current hypothesis, and makes a specific request. 'Could you take a look?' is appropriately polite.
9 / 27
What does 'I've been going in circles' mean in a debugging context?
'Going in circles' is an idiom meaning repeatedly cycling through the same (unsuccessful) approaches. When you say this, it signals to your helper that you need a fundamentally different approach, not another attempt at the same strategy.
10 / 27
After a colleague helps you solve a bug, which response is best practice?
Closing the loop with a thank-you and a brief explanation of the solution is good engineering culture. It acknowledges the helper's time and creates a useful reference for anyone who searches for the same error later.
11 / 27
Sarah: 'Hey, I'm getting a 500 error on the user authentication endpoint. I've checked the logs and it seems like there might be an issue with the database connection. Any ideas?'
Mark (a senior engineer) responds with: 'Okay, can you share the exact log snippet where you see the 500 error? Also, what version of the database driver are you using?'This question tests understanding of requesting targeted help.
Sarah's initial message is too broad; she needs to provide specific details to allow someone else to quickly understand and address the problem. Asking for a log snippet and database driver version demonstrates a proactive approach and shows you've already started investigating, which guides the response effectively. Option A is incorrect because it describes a different issue entirely.12 / 27
Liam: 'Hey team, I'm stuck on this new feature. The API call to the payment gateway is returning a 403 error intermittently. I've tried refreshing the page and clearing my browser cache, but it still happens. Any suggestions?'Liam's message is a good starting point, but it lacks crucial technical details. The best response acknowledges his effort while requesting more information to effectively troubleshoot. Providing just 'Insufficient' doesn't offer guidance; the goal is to elicit specifics that will help narrow down the cause of the 403 error. Including the API endpoint and request parameters is key for debugging.
13 / 27
Liam is struggling with a new feature and reports an intermittent 403 error when calling the payment gateway API. He's already tried basic troubleshooting steps like refreshing the page and clearing his browser cache. Which of the following approaches would be most effective in requesting further assistance from his team? The correct answer emphasizes gathering specific information and documenting previous troubleshooting steps. Asking for details about the error message and what
Liam has already done demonstrates a collaborative approach and avoids simply asking for a fix without understanding the context. Options A is demanding and unproductive, B is the most helpful, C shows lack of empathy, and D is irrelevant to the issue.14 / 27
Sarah: 'Hey, I'm getting a 500 error on the user authentication endpoint. I've checked the logs and it seems like there might be an issue with the database connection. Any ideas?'
Mark (a senior engineer) responds with: 'Okay, can you share the exact log snippet where you see the 500 error? Also, what version of the database driver are you using?'This question tests understanding of requesting targeted help.
Sarah's initial message is too broad; she needs to provide specific details to allow someone else to quickly understand and address the problem. Asking for a log snippet and database driver version demonstrates a proactive approach and shows you've already started investigating, which guides the response effectively. Option A is incorrect because it describes a different issue entirely.15 / 27
Liam: 'Hey team, I'm stuck on this new feature. The API call to the payment gateway is returning a 403 error intermittently. I've tried refreshing the page and clearing my browser cache, but it still happens. Any suggestions?'Liam's message is a good starting point, but it lacks crucial technical details. The best response acknowledges his effort while requesting more information to effectively troubleshoot. Providing just 'Insufficient' doesn't offer guidance; the goal is to elicit specifics that will help narrow down the cause of the 403 error. Including the API endpoint and request parameters is key for debugging.
16 / 27
Liam is struggling with a new feature and reports an intermittent 403 error when calling the payment gateway API. He's already tried basic troubleshooting steps like refreshing the page and clearing his browser cache. Which of the following approaches would be most effective in requesting further assistance from his team? The correct answer emphasizes gathering specific information and documenting previous troubleshooting steps. Asking for details about the error message and what
Liam has already done demonstrates a collaborative approach and avoids simply asking for a fix without understanding the context. Options A is demanding and unproductive, B is the most helpful, C shows lack of empathy, and D is irrelevant to the issue.17 / 27
Sarah: 'Hey, I'm getting a 500 error on the user authentication endpoint. I've checked the logs and it seems like there might be an issue with the database connection. Any ideas?'
Mark (a senior engineer) responds with: 'Okay, can you share the exact log snippet where you see the 500 error? Also, what version of the database driver are you using?'This question tests understanding of requesting targeted help.
Sarah's initial message is too broad; she needs to provide specific details to allow someone else to quickly understand and address the problem. Asking for a log snippet and database driver version demonstrates a proactive approach and shows you've already started investigating, which guides the response effectively. Option A is incorrect because it describes a different issue entirely.18 / 27
Liam: 'Hey team, I'm stuck on this new feature. The API call to the payment gateway is returning a 403 error intermittently. I've tried refreshing the page and clearing my browser cache, but it still happens. Any suggestions?'Liam's message is a good starting point, but it lacks crucial technical details. The best response acknowledges his effort while requesting more information to effectively troubleshoot. Providing just 'Insufficient' doesn't offer guidance; the goal is to elicit specifics that will help narrow down the cause of the 403 error. Including the API endpoint and request parameters is key for debugging.
19 / 27
Liam is struggling with a new feature and reports an intermittent 403 error when calling the payment gateway API. He's already tried basic troubleshooting steps like refreshing the page and clearing his browser cache. Which of the following approaches would be most effective in requesting further assistance from his team? The correct answer emphasizes gathering specific information and documenting previous troubleshooting steps. Asking for details about the error message and what
Liam has already done demonstrates a collaborative approach and avoids simply asking for a fix without understanding the context. Options A is demanding and unproductive, B is the most helpful, C shows lack of empathy, and D is irrelevant to the issue.20 / 27
Sarah: 'Hey, I'm getting a 500 error on the user authentication endpoint. I've checked the logs and it seems like there might be an issue with the database connection. Any ideas?'
Mark (a senior engineer) responds with: 'Okay, can you share the exact log snippet where you see the 500 error? Also, what version of the database driver are you using?'This question tests understanding of requesting targeted help.
Sarah's initial message is too broad; she needs to provide specific details to allow someone else to quickly understand and address the problem. Asking for a log snippet and database driver version demonstrates a proactive approach and shows you've already started investigating, which guides the response effectively. Option A is incorrect because it describes a different issue entirely.21 / 27
Liam: 'Hey team, I'm stuck on this new feature. The API call to the payment gateway is returning a 403 error intermittently. I've tried refreshing the page and clearing my browser cache, but it still happens. Any suggestions?'Liam's message is a good starting point, but it lacks crucial technical details. The best response acknowledges his effort while requesting more information to effectively troubleshoot. Providing just 'Insufficient' doesn't offer guidance; the goal is to elicit specifics that will help narrow down the cause of the 403 error. Including the API endpoint and request parameters is key for debugging.
22 / 27
Liam is struggling with a new feature and reports an intermittent 403 error when calling the payment gateway API. He's already tried basic troubleshooting steps like refreshing the page and clearing his browser cache. Which of the following approaches would be most effective in requesting further assistance from his team? The correct answer emphasizes gathering specific information and documenting previous troubleshooting steps. Asking for details about the error message and what
Liam has already done demonstrates a collaborative approach and avoids simply asking for a fix without understanding the context. Options A is demanding and unproductive, B is the most helpful, C shows lack of empathy, and D is irrelevant to the issue.23 / 27
During a code review, Alice comments: 'I'm seeing a high latency on this API endpoint. I've checked the server logs and it seems like there might be some database contention. Could you take a look at the query performance?' Which of the following responses is MOST effective for Alice to use?
Alice's response is excellent because she directly asks for actionable information – the specific query. Options A and D are dismissive and offer no guidance. Option C suggests an ineffective solution without investigation, while option B requests details needed to diagnose the problem properly. Asking about the query is key to understanding the root cause.
24 / 27
Ben sends a Slack message: 'The new microservice deployment failed with a 503 error. The documentation mentions a dependency on service X, but I can't find it running. I've checked the monitoring dashboards and they show no unusual activity.'
Ben's message already includes some valuable information (the error and the dependency). The best response is to politely question the dependency. Options A and B are unhelpful guesses. Option C directly addresses the core of Ben's concern, while option D jumps straight to escalation without further investigation – a common mistake. It's crucial to verify assumptions.
25 / 27
Chloe is working on a new feature and needs help with an API call. She sends the following PR description: 'Fixed bug related to user profile updates. Added new endpoint for retrieving profile data. I've tested it thoroughly.'
Chloe's PR description is lacking crucial information. The best response is to request details about her testing process. This ensures that the fix is truly robust and avoids potential regressions. Options A and B are polite but don't address the core issue of verification. Option D is appropriate, but less immediately urgent than understanding the test coverage.
26 / 27
David reports to his team during a standup: 'I'm struggling with implementing the new authentication flow. The API is returning a 401 error when I send invalid credentials. I've tried different combinations of usernames and passwords, but nothing seems to work.'
David is clearly stuck, and the most helpful initial response is to guide him back to the fundamental issue: reviewing the API documentation. This suggests a potential error in his approach rather than blaming the server. Options A and C are unhelpful distractions. Option D avoids responsibility and doesn't offer support.
27 / 27
Emily is debugging an issue with a complex data processing pipeline. After hours of work, she sends a message: 'I've been going in circles trying to figure out why the output isn't matching the expected results. I've checked all the transformations and the input data looks correct, but something is still wrong.'
Emily's phrase 'I've been going in circles' indicates she's exhausted all obvious debugging paths without finding a solution. Suggesting she check her logging is a practical next step – logs often reveal unexpected behavior or hidden errors. Options A and D are sympathetic but unhelpful. Option C correctly identifies the potential nature of the problem, offering a targeted suggestion.
Frequently Asked Questions
What does the "Asking for Help the Right Way" exercise practise?
Learn the vocabulary and structure for asking effective technical questions in English — in Slack, Stack Overflow, GitHub Issues, or with a senior colleague.
How many questions are in this exercise?
This exercise has 27 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 Debugging Language 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 "Asking for Help the Right Way" part of a larger series?
Yes — it's one exercise in the Debugging Language 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 Debugging Language category page for related exercises, or browse the main Exercises hub for other IT English topics.