To answer “tell me about a time you managed competing priorities”, describe one specific week or project where two or more important requests collided, explain the method you used to rank them, name what you deliberately delayed or declined, and finish with the measurable outcome for each priority. The interviewer wants to hear a decision, not a list of how busy you were. A strong answer takes about two minutes and ends with every stakeholder knowing what was happening and why.
What is the interviewer really testing with this question?
Almost every job has more requests than hours. This question checks whether you make that trade-off on purpose or let whoever shouts loudest set your agenda. Interviewers commonly listen for four things:
- Judgment. You ranked the work by impact and deadline, not by which task was most pleasant or which person was most senior.
- A repeatable method. You can name how you decided, so the interviewer believes you would do it again on their team.
- Communication. The people whose work you delayed heard it from you, early, with a new date.
- Follow-through. The work you pushed back still got done, or you explain why dropping it was the right call.
It is a close cousin of the tight deadline question, but the skill is different. A deadline story is about speed on one piece of work. A competing priorities story is about choosing between several pieces of work when you cannot do all of them at once.
How do you answer “tell me about a time you managed competing priorities”?
Use the STAR method, but put most of your time into the Action, because that is where the prioritization happens. A simple frame:
- Situation (2 sentences): the competing requests, who asked for each and the deadlines.
- Task (1 sentence): what you owned and why you could not do everything at once.
- Action (60% of the answer): how you ranked the work, who you talked to, what you delayed, delegated or declined, and how you protected focus time.
- Result (2–3 sentences): the outcome for each priority, with numbers, plus what you would repeat.
Naming a framework makes your judgment easy to follow. You do not need jargon, but one of these usually fits:
| Framework | How it ranks work | When to name it in your answer |
|---|---|---|
| Urgent vs important (often called the Eisenhower matrix) | Do now if urgent and important; schedule if important only; delegate if urgent only; drop the rest | Operations, support, admin or any role with constant interruptions |
| Impact vs effort | Quick wins first, big bets scheduled, low-impact heavy work questioned | Product, engineering and analytics backlogs |
| Must, should, could, won’t (MoSCoW) | Sorts scope inside one deliverable | Project and program management, launches with a fixed date |
| Cost of delay | Ranks by what each week of waiting costs in revenue, risk or customer pain | When one request has a hard external date, such as a contract or regulation |
| Escalate to the shared manager | Lets the person who owns both goals decide, with your recommendation attached | When two leaders both outrank you and the trade-off is theirs to make |
Three example answers we wrote
These are example answers we wrote for different roles. Swap in your own details and real numbers; an invented story falls apart under follow-up questions.
Example answer we wrote: software engineer, bug fix vs feature launch
Situation: I was one of four backend engineers on a payments team. In the same week, a customer escalation came in about duplicate refunds, and product wanted me to finish the API for a partner launch that was nine days out.
Task: I owned both pieces, and each was roughly four days of work, so I could not finish both on the original dates.
Action: I sized the refund bug first: it was affecting about 40 refunds a day and creating manual work for support. I ranked it with a simple cost-of-delay comparison and shared it with my manager and the product manager in a five-line message: the refund fix goes first because every day costs real money and support time; the partner API slips two days unless we cut one endpoint. I proposed moving the reporting endpoint to a follow-up release, since the partner said they would not use it in the first month. The PM agreed. I blocked my calendar for two mornings, shipped the refund fix behind a feature flag, then moved to the API.
Result: Duplicate refunds dropped to zero within three days. The partner launch went out on the original date with three of four endpoints, and the reporting endpoint shipped eleven days later. I now send a one-message trade-off summary whenever two commitments collide.
Example answer we wrote: marketing manager, three stakeholders, one week
Situation: As the only content marketer at a 60-person SaaS company, I had three requests due the same Friday: a webinar landing page for sales, a product launch blog post for the CEO, and a customer case study for customer success.
Task: I had time for two of the three at the quality each deserved.
Action: I put all three on an impact-versus-effort grid. The landing page was low effort and fed registrations that had a hard date. The launch post was high effort but tied to a press announcement that could not move. The case study was high effort with a flexible date. I met with the customer success lead for ten minutes, explained the trade-off and offered a firm new date two weeks out, plus a short quote graphic she could use with the customer in the meantime. I wrote the landing page in one afternoon, spent the rest of the week on the launch post, and sent daily status notes to all three requesters.
Result: The webinar reached 310 registrations against a target of 250, the launch post went live on time, and the case study shipped on the new date. The customer success lead later asked me to use the same grid for her team’s quarterly requests.
Example answer we wrote: operations analyst, saying no to a senior leader
Situation: I supported the finance and operations leads at a logistics company. During month-end close, the VP of sales asked me for a new territory report by Wednesday.
Task: Month-end reconciliation was due Thursday and fed the board pack, so I needed to protect it without brushing off a senior leader.
Action: I replied the same hour instead of letting the request sit. I said I could not build the full report until Friday because of close, explained that the board pack depended on it, and offered two options: a quick cut of existing data by Wednesday noon, or the full report on Friday. He chose the quick cut. I spent 90 minutes on it, then returned to close. I also asked my manager to add a month-end freeze note to our team request form so this would not repeat.
Result: Close finished a day early, the VP used the quick cut in his Wednesday meeting, and the full report landed Friday. Ad hoc requests during close dropped noticeably over the next quarter because people could see the freeze dates.
How to say no gracefully in your story
Many candidates avoid stories where they turned someone down, but a well-handled no is often the strongest part of this answer. It shows you protect the most important work. The pattern is the same in every example above:
- Respond fast. A quick “not yet, and here is why” beats silence followed by a missed date.
- Give the reason in business terms. “The board pack depends on it” works better than “I’m swamped.”
- Offer options. A smaller version now, the full version later, or someone else who can help.
- Commit to a date, then keep it. The follow-through is what earns trust for the next no.
If the trade-off belonged to someone above you, say so. Escalating with a recommendation is good judgment, not weakness. For stories where the hard part was managing expectations rather than ranking work, see how to answer the stakeholder expectations question.
Weak vs strong answers
| Element | Weak answer | Strong answer |
|---|---|---|
| Opening | “I’m always juggling a lot of things.” | One specific week, with each request and deadline named |
| Method | “I just worked late and got it all done.” | A named way of ranking: impact, cost of delay, urgent vs important |
| Trade-off | Nothing was delayed or cut | One thing was delayed, trimmed or declined, on purpose |
| Communication | Stakeholders found out when the date passed | Each requester heard the plan early, with a new date |
| Result | “Everyone was happy.” | An outcome for each priority, with numbers |
“I worked weekends” is the most common weak answer. Effort is fine to mention, but on its own it tells the interviewer you have no system and will burn out when the load doubles.
Follow-up questions to expect, and mistakes to avoid
Interviewers often probe the decision itself. Prepare short answers to these:
- How did you decide what was most important?
- Who disagreed with your ranking, and how did you handle it?
- What would you have done if your manager had ranked it differently?
- What happened to the work you delayed?
- Looking back, would you prioritize the same way?
Common mistakes that weaken the answer:
- Picking a story with no real conflict. Two tasks with different deadlines are a schedule, not competing priorities.
- Hiding the trade-off. If nothing was delayed, the interviewer cannot see your judgment.
- Blaming the requesters. “Sales always dumps work on us” reads as friction, not prioritization.
- Listing tools instead of decisions. Your to-do app is not the answer; the choice you made is.
- Rambling through every task. Name two or three priorities at most. Our guide on how to stop rambling in interviews helps you trim.
Have a second story ready too. A related prompt, tell me about a time you missed a deadline, often follows in the same round, and it is where you show what happens when prioritization does not go to plan. For the full list of these prompts, see our index of “tell me about a time” interview questions.
Practice it
A prioritization story only sounds decisive when you have said it out loud a few times. Draft the four parts in the free STAR story builder, then rehearse it in a free mock interview that scores your spoken answers. CoPilot Interview builds the questions from your résumé and the job description, scores each answer out of 10 and tells you what to fix, such as a missing trade-off or a result without numbers. It is free for 15 minutes a day, with no account needed.
Rehearse your prioritization story tonight
Answer behavioral questions out loud, get a score out of 10 with specific fixes, and repeat until the trade-off comes through in one sentence.
Try a free AI mock interviewFAQ
What is a good example of managing competing priorities?
A good example names two or three specific requests that collided, the method you used to rank them, what you delayed or declined, and a measurable outcome for each. A bug fix versus a feature launch, or month-end close versus an urgent request from a senior leader, both work well.
Which prioritization framework should I mention in an interview?
Use the one you actually used. Urgent versus important, impact versus effort, must-should-could-won’t and cost of delay are all widely understood. Naming the method matters less than explaining the trade-off it led to.
Is it okay to say I said no to my manager or a senior leader?
Yes, if you said it respectfully, gave a business reason, offered options and kept the new date. Interviewers usually see a well-handled no as good judgment. If the decision was above your level, explain that you escalated with a recommendation.
How is this different from the tight deadline question?
A tight deadline story is about delivering one piece of work fast. A competing priorities story is about choosing between several pieces of work when you cannot do them all, so the interviewer expects to hear what you delayed or cut.
How long should my answer be?
Aim for about two minutes. Spend most of it on the Action, where you explain how you ranked the work and communicated the trade-off, and keep the Situation to two sentences.
What if I have never had to choose between priorities?
Most people have, even outside work. A semester with overlapping exams and a part-time job, or a volunteer role with two events in one week, can work for entry-level candidates if you explain the method and the outcome.