Ask about the part that is unclear before choosing an answer. Name the ambiguity: a word you do not know, a missing constraint, a choice between two meanings, or a part you did not hear. Once the interviewer responds, answer that version of the question rather than continuing to negotiate the wording.
LSE Careers recommends asking for clarification when you do not understand a question.[42] The phrase guide below is our original practical application of that advice. It does not guarantee how an interviewer will react or override the rules of a timed assessment.
First identify what you missed
A question can be unclear even when every word is familiar. “How would you improve onboarding?” might refer to customer onboarding, employee onboarding or a specific process discussed earlier. An answer about the wrong process can be detailed and still irrelevant.
Before speaking, locate the gap. Did the audio cut out? Is a term unfamiliar? Do you need to know which period, stakeholder or constraint matters? Ask for the missing information, not for the interviewer to write your answer.
If the question is clear and you simply need thinking time, ask for that instead. “May I take a moment to choose an example?” is different from “What do you mean?” The recovery card for a blank moment focuses on restarting when the meaning is already clear.
The clarification phrase guide
These are adaptable phrases, not lines to recite in every interview. Replace the bracketed words with what you actually need to clarify.
| Type of gap | A possible clarification | What to do with the reply |
|---|---|---|
| You did not hear the ending | “Could you repeat the last part, after [phrase]?” | Use the repeated constraint in your answer |
| A term is unfamiliar | “How are you using [term] in this context?” | Answer within the definition given; state any remaining knowledge gap |
| There are two plausible meanings | “Do you mean [A], or [B]?” | Choose the confirmed meaning |
| The scope is broad | “Would you like one detailed example or an overview of my approach?” | Match the requested level of detail |
| A scenario lacks a constraint | “Should I assume the deadline is fixed?” | Explain how that constraint changes the decision |
| A question has several parts | “I heard [A] and [B]. Is there another part you'd like me to cover?” | Answer in the confirmed order |
| You may have misunderstood a follow-up | “Are you asking what I personally did, rather than what the team delivered?” | Describe your contribution without retelling everything |
The most useful clarification is the smallest one that lets you proceed. Do not turn the table into a checklist you run before every answer.
Fictional dialogue: resolve scope without asking for hints
Consider this made-up interview exchange:
Interviewer: “How would you improve onboarding?”
Candidate: “Do you mean the customer's first setup after signing, or the internal handoff from sales?”
Interviewer: “The internal handoff.”
Candidate: “I'd start by finding which information is missing when ownership moves to the next team. In a previous team project, my part was checking that each handoff named an owner. I can explain that example, then how I'd adapt the approach here.”
The clarification identifies two plausible interpretations. It does not ask, “What answer are you looking for?” The candidate then separates a proposed approach from a past example. Only use a past example you actually have; the one above is fictional.
A less useful follow-up would keep asking for more detail after enough information is available: “Which team? Which software? Which customer segment? What would you prioritize?” Some of those questions could matter in a detailed case, but they should serve the task, not postpone every decision.
In a technical scenario, explain why a constraint matters
If the question asks you to choose an architecture, a missing requirement can change the answer. Ask about the requirement that drives your first decision: latency, recovery needs, budget, data sensitivity or an existing dependency. Choose what is relevant rather than reading a generic list.
For example: “Should I optimize for an immediate response or is a delayed result acceptable? That changes whether I'd consider a queued workflow.” This is an illustrative reasoning example, not a claim about a particular production system.
If the interviewer says to make an assumption, state it and proceed. “I'll assume delayed results are acceptable and explain what I would revisit if that changes.” You have made the boundary visible. Do not pretend the assumption was confirmed.
Clarification also cannot replace missing knowledge. If you do not know what a technology does after its meaning is explained, say so. Asking repeated vocabulary questions to imply familiarity is not a substitute for an honest knowledge boundary.
When you cannot ask a follow-up
A recorded or written assessment may not provide an interviewer who can clarify in real time. Read the instructions and use only the permitted resources. If assumptions are allowed, state the interpretation you are using before answering. If the instructions require a specific interpretation, follow that instead.
Do not treat the lack of a live clarifier as permission to consult an unauthorized assistant or another person. This guide does not establish the rules of any assessment. The permission decision guide separates permitted preparation from live assistance and capture.
If a technical failure prevents you from hearing or reading the prompt, use the stated support or reporting process where one exists. Record the practical issue without inventing a completed answer or assuming an automatic retake will be granted.
Repair a misunderstanding you notice late
Sometimes the follow-up reveals that you answered a different question. Make the correction explicit and concise: “I answered about the customer setup. You were asking about the internal handoff; let me address that.” Then give the relevant answer.
You do not need to defend every sentence of the first response. Keep any useful fact, but remove the unrelated story. If the interviewer has already moved on, ask whether there is room for a brief correction rather than talking over the new question.
During practice, have a partner mark where your interpretation first diverged. Did you miss a word, assume a scope, or answer the question you had prepared? That observation tells you what to change. It does not require a score or a prediction about the hiring outcome.
Questions readers ask
Will asking for clarification make me look unprepared?
This article cannot predict a particular interviewer's reaction. LSE's published guidance recommends asking when you do not understand.[42] Our recommendation is to make the request specific and then use the answer. Avoid asking for information that was just supplied.
Should I repeat the whole question back?
Only if that helps resolve the uncertainty. If you missed one condition, ask about that condition. Repeating a long prompt without naming the gap may leave both people unsure what needs clarifying.
What if I still do not understand after the reply?
State the remaining issue plainly. You might offer your interpretation and ask whether it is usable. If the issue is missing knowledge rather than ambiguous wording, acknowledge that boundary and explain any relevant part you can address.
Can a transcript tell me what the interviewer meant?
A transcript can provide text to inspect, but this guide has not established that it resolves intent or captures every word accurately. InterviewRep describes user-requested answer suggestions and warns that suggestions can be inaccurate.[16] A generated interpretation is not confirmation from the person asking the question. Use the live-assistance guide for the actual workflow and keep any use within the rules.
Practice one ambiguity at a time
Ask a partner to give you a broad question with two plausible meanings. Identify the distinction, ask one targeted clarification, and answer the confirmed version. On the next attempt, have them tell you to choose an assumption. Practice proceeding with that assumption visible instead of waiting for a perfect prompt.
Sources
10 minutes for new accounts. No credit card required. Use only where assistance and capture are permitted. Check current plans and terms.