The word people fixate on in this question is "managed", so they answer by describing how busy they were: five things at once, all urgent, and somehow they got through it all. The word that actually matters is "conflicting". The question is not testing whether you can be busy. It is testing whether you can choose when two genuinely important things pull against each other and you cannot do both well.
That distinction changes the whole answer. A story about doing lots of tasks is a story about workload. A story about deciding which of two important things to protect, and why, is a story about judgement, and judgement is what gets scored.
What makes priorities "conflict"
Ordinary multitasking is not conflict. Conflict is when two things both matter, both have a claim on your time, and giving one what it needs means the other gets less. The interesting part is not the doing, it is the decision about how to allocate when there is not enough to go round.
So the interviewer is listening for a method. Not "I worked really hard and fit it all in", but "here is how I decided what came first". A clear decision rule, applied to a real clash, is the core of a strong answer. Common ones include:
- Impact and consequence: what actually breaks, and how badly, if each one slips.
- Immovable versus flexible: which deadline is genuinely fixed and which has some give, once you actually check rather than assume.
- Who is affected: whether a slip is a problem only for you, or blocks other people who cannot proceed without you.
- Reversibility: whether one can be caught up later and the other cannot.
You do not need a fancy framework. You need to show you thought about which mattered more, rather than just running faster.
A worked example
"In an internship, I had two things land in the same two days. My manager needed a data summary for a client meeting on the Wednesday, and separately I had committed to helping onboard a new starter who was beginning that same week, walking them through our systems.
Both mattered, and my instinct was to try to do both fully and end up doing neither well. So I stopped and actually thought about the consequences. If the client summary was late or rushed, my manager would be exposed in front of a client, which was a real, external, hard-to-recover problem. If the new starter's onboarding was a bit compressed, that was recoverable, I could give them a proper session later in the week, and in the meantime give them enough to be getting on with.
So I was honest with the new starter rather than half-present: I told them I had a hard client deadline, gave them a focused hour on the essentials plus some things to work through independently, and booked a proper follow-up for the Thursday. That freed me to do the client summary properly. The summary went into the meeting clean, and the new starter was actually fine, they said the independent tasks plus the Thursday session worked well.
What I learned was that the honest move under conflicting priorities is usually to be genuinely present on the higher-stakes one and openly, deliberately deprioritise the other, rather than trying to fake full attention on both."
Why it works
The candidate names the conflict clearly (client summary versus onboarding), then applies an explicit decision rule: consequence and reversibility. The client work is externally visible and hard to recover, the onboarding is internally recoverable, so the client work wins. That is a clean piece of reasoning, and stating it plainly is what demonstrates the competency.
The subtler strength is what they do with the deprioritised task. They do not just neglect it, they manage it deliberately, being honest with the new starter and rebooking properly, which shows they understand that deprioritising is a decision to communicate, not just a thing that quietly happens. And the closing insight, that honest deprioritisation beats fake full attention on everything, is a mature and genuinely useful principle.
The answers that miss the point
The workload brag. "I had six things due and I did them all" describes capacity, not judgement, and it usually is not even true, or the things were not really conflicting. It also implies you did not have to make a choice, which means there was no priority conflict to manage.
No decision rule. If you cannot say why you chose what you chose, the interviewer has not learned anything about how you think. "I just did the most urgent one first" is thin unless you show how you worked out what "most urgent" actually meant.
Neglecting instead of deprioritising. There is a difference between deliberately deciding one thing gets less and just dropping it. The former is management, the latter is being overwhelmed. Show that the deprioritised thing was handled, not abandoned.
Not communicating. Conflicting priorities almost always involve other people who are expecting something from you. A strong answer includes managing their expectations, telling someone their thing is going to be a bit later, rather than silently letting it slip and hoping they do not notice.
Building your example
Look for a real clash: two deadlines colliding, a planned task interrupted by an urgent one, commitments to two different people at the same time. The best versions have you consciously choosing, with a reason, and handling the losing side well. Jobs, projects, and busy periods at university all supply these. The STAR structure keeps it focused on the decision rather than the busyness.
Before the interview, check your answer contains an actual "because", the reason you prioritised one over the other. If it does not, you have described juggling, not managing. Say it aloud and listen for the decision. You can practise it and get told whether your reasoning comes through clearly.