Editorially revised on 9 October 2026.
A situational interview asks what you would do under stated conditions. A useful response explains your decision, the information you would seek and the boundary of your authority. It should not claim that an imagined action already produced a real result.
This guide contains five original fictional scenarios with annotated response branches. It is a response-construction exercise, not a prediction of an employer's questions or scoring system. Use the organisation's actual procedures when they are provided, and ask about important missing conditions before assuming them.
Identify whether the question asks would or did
“What would you do if two urgent tasks conflicted?” is hypothetical. “Tell me about a time you handled conflicting tasks” asks for actual experience. The first can use conditional language; the second requires an event you really participated in.
If the question is unclear, briefly clarify which form the interviewer wants. Do not retrofit a fictional story into a past-tense achievement. You can explain that you have not handled the exact situation and then, if invited, describe how you would approach it.
Harvard's interviewing guidance supports preparation using relevant qualifications, contributions and examples. It does not establish one response formula for all employers. The sequence below is an original editorial practice method.
Use a compact decision note
| Element | What to explain |
|---|---|
| Objective | What needs to be achieved in the stated situation? |
| Missing fact | Which uncertainty changes your next action? |
| First action | What can you do within your authority? |
| Decision branch | What changes if the missing fact has a different answer? |
| Confirmation | How would you check completion or communicate the next step? |
This note should make your answer easier to follow, not longer than necessary. Choose the uncertainty that actually matters. Listing every possible risk without deciding anything can obscure your reasoning just as much as a confident answer built on assumptions.
Fictional scenario 1: an urgent report lacks an input
The interviewer says a report is due this afternoon, but one team's figures have not arrived. You are responsible for compiling the report, not approving estimates or changing its deadline.
A fictional response: “I would confirm which input is missing and when it is expected, then tell the report owner what that means for completeness. I would prepare the verified sections while seeking the missing figures through the agreed route. If the owner authorises a partial report, I would label the missing section clearly; otherwise I would ask for a decision on timing rather than insert an estimate without permission.”
The first action preserves useful progress. The branch depends on approval for a partial output, and the answer does not invent authority to estimate figures. A follow-up could ask what you would do if the source team cannot respond. Explain that you would communicate that new fact and seek a decision through the appropriate reporting line.
Avoid saying “I would deliver a complete report anyway.” That statement does not explain how missing evidence becomes available. Completion and apparent completeness are different outcomes.
Fictional scenario 2: two requests have the same deadline
Two managers send tasks due at the same time. You cannot finish both within the available hours, and neither request states the consequence of delay.
A fictional response: “I would clarify the required outputs, the time each task needs and the consequence of missing either deadline. I would make the conflict visible to the people responsible for priorities and propose an order based on those facts. While awaiting the decision, I would work on a useful reversible step that does not prevent the agreed priority from being completed.”
The response does not assume the more senior requester must always win or that working unpaid extra hours is automatically available. It asks for a prioritisation decision from the appropriate owner. If one task concerns an immediate safety issue, the branch may change according to the organisation's safety and escalation procedures.
A follow-up might say that the managers disagree. You can explain how you would present the conflict and seek resolution through the established line of authority, while keeping both informed about what can actually be completed. Do not promise two full outputs when the scenario says that is impossible.
Fictional scenario 3: someone requests a file containing private information
A colleague asks you to send a customer spreadsheet to an unfamiliar external address. The scenario does not establish that the recipient is authorised or that the file is suitable for external sharing.
A fictional response: “I would pause the transfer and verify the recipient, purpose and approved sharing route under the organisation's policy. I would ask the responsible owner whether the requested data is necessary and whether a permitted, limited version is appropriate. If authorisation cannot be established, I would not send the file and would explain what verification is still needed.”
This answer identifies a boundary without inventing a legal rule or assuming every external transfer is prohibited. It also does not make you the sole approver merely because you hold the file. The decision depends on actual permissions and the applicable policy.
If the interviewer says the recipient is authorised, the next branch is checking the approved method and minimum required information. If an accidental transfer has already occurred, follow the relevant reporting process promptly instead of claiming that deleting your local copy resolves the incident.
Fictional scenario 4: a customer asks for something unclear
A customer says, “Please fix the invoice,” but does not specify the error. You can investigate records but cannot change charges without approval.
A fictional response: “I would ask which line or amount appears wrong and compare that concern with the order and invoice records. I would explain what I can verify and avoid promising a credit before approval. If I find a discrepancy, I would document it and route the proposed correction to the person authorised to approve it. If the records match, I would explain the basis and check whether the customer's concern relates to a different issue.”
The first question avoids repairing the wrong thing. The decision branches distinguish an identified discrepancy from a misunderstanding or another unresolved concern. The answer remains respectful without agreeing to every request automatically.
A follow-up could ask what happens when the customer is upset. You can acknowledge the concern, keep the explanation clear and use the organisation's escalation route where needed. Do not invent a discount or promise a particular financial outcome solely to sound accommodating.
Fictional scenario 5: you find an error during a handover
You discover that a handover note contains an incorrect task status. Another team may rely on it soon, and you are unsure whether they have already acted.
A fictional response: “I would check the correct status from the relevant record, notify the receiving team and responsible owner promptly, and ask whether any action has already been taken. I would correct the note through the agreed process while preserving a clear record of the change. If downstream work was affected, I would help establish the facts and follow the appropriate recovery steps within my remit.”
The response addresses the immediate dependency before discussing long-term improvement. It does not claim that silently editing the note makes the problem disappear. Nor does it assume you can reverse another team's work without consulting them.
A final branch might concern preventing recurrence. You could propose a confirmation step or a clearer handover field after understanding the cause. Describe that as a proposal to review, not proof that one checklist will eliminate all future errors.
Practise by changing one condition
For each scenario, change a single fact and explain whether your response changes. In the missing-input case, suppose partial delivery is explicitly permitted. In the priority case, suppose one task has a verified safety consequence. In the file case, suppose the recipient is authenticated but the sharing method is not approved.
This exercise exposes whether you are reasoning from facts or reciting a script. Record the decision you changed and why. If nothing changes despite a material change in conditions, revisit your assumptions.
Ask a practice partner to identify unsupported authority in your answer. Statements such as “I would approve,” “I would override” or “I would guarantee” need a basis in the role and scenario. A clear explanation of when you would seek approval can demonstrate judgement without claiming powers you do not have.
Keep hypothetical outcomes conditional
Finish with how you would check the action, not an invented success metric. “I would confirm that the revised note reached the receiving team” is a verification step. “This reduced errors by 40%” is a claim about an actual result and cannot be attached to an imagined scenario.
If you have a real comparable example, label the transition explicitly: “In a previous role, I handled a similar issue…” Then describe your actual part and result. For broader evidence-based contribution answers, use why should we hire you. For the employment-transition question, use reason for leaving a job.
Frequently asked questions
Should every response use STAR?
A hypothetical question needs a clear proposed decision and its conditions. STAR may help organise an actual past example, but it does not turn an imagined result into evidence. Follow the question asked.
Is asking for clarification a weak response?
A focused question can identify a fact that changes the decision. Explain why it matters, then give a conditional approach if the interviewer wants you to proceed with assumptions.
What if I have no experience of the situation?
Be honest about that. If the question is hypothetical, explain a sensible approach within the stated role. If it asks for a real example, offer a genuinely related experience or ask whether a different example would be useful.