Tell me about a time you had competing priorities: how to answer

Most answers to this question sound alike. Three pieces of work landed in the same week. You made a list, blocked out your calendar, stayed late on Wednesday and Thursday, and everything shipped on time.

It sounds like a good week, but as an answer it leaves out what the interviewer is listening for. Nothing was dropped, nobody had to be told, and no choice was made. You worked harder, which every candidate says.

Prioritization answers are scored on what you chose not to do, and who you told. This guide shows how to find that in your own week and tell it in about two minutes.

What interviewers listen for

When there's more work than time, something gets delayed, handed off or dropped. Interviewers want to hear which task that was, why it lost, and how the people who wanted it found out.

The reason matters more than the method. A product leader who interviews says they aren't looking for a framework. They want to hear why one option gave the best return, in plain terms.

When everything is labeled top priority, the reason has to come from you. The most upvoted reply on r/recruitinghell to a candidate stumped by “ten equally high-priority tasks” is to set your own criteria, make sure everyone knows them, and apply them. An answer that names the criteria shows the interviewer how you'd handle their backlog too.

Then comes the conversation. Telling your manager you're overloaded and agreeing together what moves comes across as open and collaborative, not weak, as one r/interviews reply points out. A story with a real cost makes that conversation easy to show, so start by finding one.

Choosing the story

Good prioritization stories have a visible cost. Look for a week when you couldn't do everything and somebody noticed what didn't happen.

These kinds of story work well:

• More work than you could do. Two or three requests, and one of your own tasks that moved.
• A deadline at risk. Caught before it was missed, with a plan that changed. If the deadline was actually missed, it's a failure story and is better told as one.
• A trade-off. Speed against quality, one customer against many, a feature against cleanup work. Say what you gave up.
• Two people with clashing requests. One person gave you two assignments, another gave you a third, and there wasn't time for all three.

That last one is popular for good reason. A reply with nearly 500 upvotes describes exactly that version as a safe answer, because the clash is about workload, not personality. That reply was answering a conflict question; the conflict guide explains what the story needs there.

What makes it strong is what you did with the two people. Did you put both requests side by side, recommend an order and ask whoever could decide? Or did you quietly pick one and hope? If a senior person had to hear no, the stakeholder management guide covers that conversation.

Early in your career, the same shape shows up in coursework, a part-time job or an internship: two deadlines, one moved, and you told the person who set it. Small stakes are fine if the choice was real. Once you have the story, the order you tell it in does most of the work.

How to tell it

Keep the setup short so most of your time goes on the choice. This is the STAR order with the decision at the center:

1. The load. What was on your plate, and the deadline that made it impossible to do everything.
2. How you ranked it. One or two reasons: impact, who was blocked, what had a fixed date, what was easy to undo.
3. What you dropped, moved or handed off. A task of your own, named plainly.
4. Who you told, and when. The message, and how the person took it. “Not this time, and here's when” keeps people on side better than a flat no.
5. What happened. Including to the work you set aside.

The reasons depend on the job. A mental health worker on r/jobs ranks tasks by how likely they are to cause harm to people, which is a different list from a sprint board. Use the reasons your field actually uses.

Expect follow-ups on exactly these points: when you first told people, what happened to the work you gave up, and “What did you tell the people who wanted what you gave up?”

You can practice this out loud in Kora: you pick your role, answer behavioral questions, get follow-ups when your answer leaves out an important detail, and get feedback after each answer.

The week from the start of this page had a real answer all along. It wasn't the late nights; it was whatever you'd have moved to Monday if you hadn't stayed late, and the message to the person waiting for it. The examples below show that difference in six roles.

Example answers

Answering “How do you prioritize your work?”

The question is asked more often as “How do you prioritize your work?”, which asks about your habits, not a particular week. It invites a description of your system: a to-do list, a matrix, a color-coded calendar. The system matters less than a time you used it.

Give your rule in a sentence, then move to a real example: “I rank by what's blocking someone else and what has a fixed date. Last spring that meant…” A widely upvoted post on r/interviews says interviewer training teaches never to ask a speculative question, and suggests asking instead about a time you handled competing priorities from several stakeholders.

Keep the system part short. Experienced candidates sometimes resent being asked to walk through how they manage a to-do list, and the irritation shows. One rule and one story is enough.

Some candidates hear the question as a warning that the team is understaffed. Usually it isn't. An engineering manager in the same thread points out that everyone in a business has requests they consider urgent, and someone has to weigh them.

What makes the answer go wrong

Most weak answers describe effort instead of a choice. These are the common versions:

• Working harder. Late nights show you worked hard, not that you chose. In a thread about this question, one reply sums up what interviewers want to know: did you plan, or did you throw up your hands?
• Flagging late. A candidate on r/analytics says a deadline story is less about why it slipped than what you did once you knew: did you flag it early, or hope? Say when you raised it.
• No outcome. An interviewer on r/interviews says many candidates forget the outcome entirely, and “the project ended” doesn't count as one.

Other ways it gets asked

The same story usually fits several wordings, with a change in what you lead with.

“How do you deal with changing priorities?” This belongs here when the tasks were clear but their order kept shifting. If it was unclear what the work should be, or the goal moved under you, that's an ambiguity question, and the answer centers on what you assumed.

“Tell me about a time you worked under a tight deadline.” Lead with the date and what you cut to meet it. The hours you put in aren't the point.

“Tell me about a hard trade-off. What did you give up?” Common for engineers, product managers and analysts. Spend more time on why the option you gave up lost, and what happened to it.

“How would you handle ten equally urgent tasks?” A scenario. Say how you'd find out which are truly urgent and who you'd ask, then back it up with a time you did that.

Product prioritization cases. Some product manager interviews ask you to rank features for a made-up product. That's a product-sense exercise rather than a behavioral question, and this guide doesn't cover it.

The software engineer guide covers the trade-off question as engineers get it, and what a behavioral interview is explains how this question fits with the others.