When an interviewer questions your presentation, clarify what they are asking, answer directly and explain the evidence or assumption behind your response. You do not need to defend every slide unchanged. A thoughtful correction or a clearly stated limit can make your reasoning easier to assess.
Prepare for questions about scope, alternatives, data and implementation. These seven habits are useful for portfolio presentations, case exercises and project discussions. Follow the assessment rules and use only information you are permitted to share.
1. Listen for the actual question
Let the interviewer finish before deciding that they disagree with you. A question about an assumption may simply request clarification. If several points are raised, briefly identify them and answer in a sensible order.
Hypothetical wording: “You are asking about the data period and why I excluded one category. I will start with the period.” Avoid responding to the question you prepared instead of the one asked. If the wording is unclear, ask a focused clarification rather than guessing.
2. Give the short answer first
Start with the conclusion, then provide the supporting detail. If asked whether the recommendation works without a particular resource, state whether it does before describing the alternatives. This helps the listener follow your reasoning.
Do not repeat the whole presentation. A useful answer might be: “Not in the proposed form; that resource is a dependency. A smaller version would be possible, but it would change the scope.” Keep the distinction between the original proposal and the alternative clear.
3. Identify the evidence you actually have
Point to the relevant supplied fact, calculation or observation. If a claim was an assumption, name it as an assumption. Do not invent a source during the discussion to make the slide appear stronger.
For a practice project, explain what the data can and cannot support. “These fictional records demonstrate the calculation” is different from “This proves how customers behave.” If the interviewer asks for evidence you do not have, describe what you would need to check rather than improvising a statistic.
4. Explain an alternative fairly
If asked why you rejected another option, describe its genuine advantages as well as the constraint that affected your choice. Avoid making the alternative sound absurd merely to protect your recommendation.
Hypothetical wording: “The other option would be simpler to launch, but it would not cover the required group in this brief.” If the interviewer changes the constraint, reconsider the choice. A recommendation can reasonably change when the facts change; explain which condition is doing the work.
5. Correct a mistake clearly
If a question reveals an error, acknowledge the specific issue and explain its effect. Distinguish a minor label mistake from a calculation error that changes the recommendation. Do not quietly adjust the answer while pretending nothing changed.
A useful response is: “You are right that I used the wrong period in that comparison. I would need to recalculate before relying on the conclusion.” Avoid promising that the corrected result will be the same when you have not checked it.
6. Set a boundary when information is missing
You can answer partially while identifying the unresolved part. Explain what you know, what remains uncertain and how you would investigate it. This is more useful than either guessing confidently or stopping at “I do not know”.
For a technical question outside your experience, be specific about the limit. Do not claim implementation expertise because you recognise a term. If the role requires that skill, an honest discussion helps the interviewer understand your current level and learning needs.
7. Close the answer and check whether it addressed the point
Finish with a sentence that connects your explanation back to the question. Pause so the interviewer can follow up. If appropriate, ask whether they want more detail on the calculation or implementation step.
Avoid turning every response into a long monologue or repeatedly asking for reassurance. Your aim is a clear exchange. Keep notes of questions you could not resolve if the employer permits, and follow any agreed instructions about sending additional material afterwards.
Practise with three challenges
After a fictional project presentation, ask a friend to question one assumption, propose an alternative and point out a possible limitation. Practise answering without immediately defending the slides. Review whether you stated the answer first and separated evidence from assumptions.
Before the interview
Prepare the source or reasoning behind your main claims, know which figures are hypothetical and check that your sample files contain no confidential information. Review the brief again so you can explain how the presentation answers it.
Is changing my recommendation a sign of weakness?
A reasoned change in response to new information can be appropriate. Explain what changed and why.
Should I guess if I think I am expected to know?
Do not present a guess as fact. State your current understanding and the check needed.
Use the portfolio walkthrough guide to prepare the presentation itself, or the case interview approach for an unfamiliar problem.
