Practise the language of customer discovery interviews: open questions, avoiding leading questions, probing for the why, and past behaviour.
0 / 10 completed
1 / 10
Which is an open question that invites a rich answer?
Open 'walk me through' questions elicit stories and detail, whereas yes/no questions cut the conversation short.
2 / 10
Which question is leading and should be avoided?
Leading questions plant the answer you want, producing flattering but useless data; neutral questions reveal real needs.
3 / 10
Asking 'why is that a problem for you?' is a way to ___.
Probing 'why' uncovers the root motivation behind a behaviour, which is where real product opportunities live.
4 / 10
To get reliable signal, ask about ___ rather than hypotheticals.
What people actually did is far more predictive than what they say they would do, which is often aspirational.
5 / 10
Which response keeps you listening rather than pitching?
In discovery you're learning, not selling; encouraging the customer to keep talking yields the insights you came for.
6 / 10
Sarah, a senior developer, comments on a PR draft: 'This function seems inefficient. Can you explain the reasoning behind using this particular algorithm?' Which of the following best reflects Sarah's intention?
Sarah's question isn't simply pointing out a potential problem; she's actively soliciting an explanation. The key here is that she wants to understand the developer's thought process. Options A and B describe this open-ended approach effectively, while options C and D represent approaches that would shut down discussion or make assumptions.
7 / 10
Mark sends a Slack message to the team: 'Just deployed the new feature. Let me know if you spot any issues.' Which of the following best describes Mark's communication style?
Mark's message is designed to encourage collaboration. He's not dictating what *should* be done or demanding immediate fixes; instead, he's opening the door for others to report issues. Options A and D are overly forceful, B describes a more nuanced approach, and C implies avoidance of responsibility.
8 / 10
David is describing a recent API response to his team: 'The server returned a 400 Bad Request error with the message 'Invalid input data'.' What does David primarily want to convey?
A 400 Bad Request indicates that the client (David's application) provided invalid data. It's a signal for investigation, not necessarily a critical bug or successful processing. Options A and D are incorrect because a 400 always signifies an error. Option C is too strong – it's an error to investigate, not something needing immediate maintenance.
9 / 10
Emily needs to update her standup report: 'We finished implementing the user authentication flow.' Which of the following is the MOST effective way for Emily to phrase this statement?
Standup updates should be brief and focused on outcomes. Emily's goal is to quickly inform her team about what was accomplished without getting bogged down in technical details. While options C and D are valuable information, they aren't appropriate for a concise standup update; option A is irrelevant.
10 / 10
John wants to gather feedback on a proposed database schema. He asks a junior developer: 'Do you think this design will scale well with future growth?' Which question is John most likely trying to avoid?
John's question is inherently biased. It presumes that scalability is the *most* important factor, potentially overlooking other design considerations. This can lead to the junior developer tailoring their feedback to align with John's pre-conceived notion. Option A describes a truly open question.
What will I practice in "Customer Interview Language"?
This is a Product Management Language exercise set. It walks through 10 scenario-based multiple-choice questions built around real usage of product management language terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 10 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the product management language vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more Product Management Language exercises?
See the Product Management Language exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — product management language vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.