How to Answer 'How Do You Prioritize Competing Deadlines?'

13 min read

Updated October 8, 2026·Originally published October 8, 2026

How to answer 'how do you prioritize competing deadlines': a four-step method, hypothetical vs. behavioral versions, examples, and a scored answer.

To answer "how do you prioritize competing deadlines?", show your process in four steps. First, sort the work by impact and by which deadlines are truly fixed — a client launch — versus someone's preferred date. Second, tell the people whose work will come later exactly when they will get it, before they have to ask, and offer a partial version sooner if that helps. Third, if two fixed deadlines still collide, go to your manager with a recommendation, not just the problem. Fourth, finish the highest-impact task before starting the next. Keep it to about 60 seconds. "I'd just work harder" or "I never miss deadlines" fails because it shows no decision at all.

The rest of this guide names that method, explains how the answer changes when the question is hypothetical ("what would you do?") versus behavioral ("tell me about a time"), gives worked examples for several roles, lists the mistakes that sink this answer, and shows a weak example answer we wrote and our rewrite run through the Interview Drills scorer.

What is the interviewer testing with a competing-deadlines question?

The interviewer is testing judgment, not stamina: how you decide what comes first, whether you tell the people affected, and whether you know when a conflict is above your pay grade. Staffing firm Mondo puts it this way: "This interview question aims to assess your time management skills, decision-making, and organizational abilities."

The question arrives in several forms:

• "How do you prioritize competing deadlines?"
• "How do you handle multiple priorities?"
• "If you had three urgent tasks due at the same time, what would you do?"
• "Tell me about a time you had to juggle multiple deadlines."
• "What do you do when two people both need something from you today?"

The first three are hypothetical or general: they ask for your process. The last two are behavioral: they ask for a story. The content is the same in both — a decision, a message to the people affected, and a finish — but the shape is different, which is covered below.

What process works for handling competing deadlines?

Use what Interview Drills calls Sort–Signal–Escalate–Finish: sort the work by impact and by how fixed each deadline really is, signal new dates to the people who will wait, escalate with a recommendation only when two fixed deadlines still collide, and finish one task at a time. Each step answers one thing the interviewer is listening for.

The step that separates strong answers is the first half of Sort: asking how much of each deadline is real. A deadline tied to a launch, a client meeting, or a legal date cannot move. A deadline that is "end of day" because someone picked a time when they made the request may move by a day at no cost — but only the person who set it can tell you, which is why Signal comes right after Sort.

Escalate is conditional. If sorting and signaling resolve the conflict, you never reach step three, and saying so ("if that doesn't resolve it…") shows the interviewer you don't push every decision upward.

How does this relate to the Eisenhower (urgent/important) matrix?

The urgent/important matrix, known as the Eisenhower Matrix, sorts tasks by urgency and importance. The Interview Guys describe it as a method that "helps you categorize tasks by urgency and importance," and Mondo lists it among techniques worth mentioning. Sort–Signal–Escalate–Finish uses the same idea in step one, with one change: instead of accepting that a task is urgent, it asks whether the urgency is real. On a competing-deadlines question, that is the difference that matters — when three things are all labeled "urgent," a matrix that takes the label at face value puts all three in the same box.

If you genuinely use the matrix, name it in step one ("I run a quick urgent-versus-important sort"). If you don't, describe your sort in plain words. A named framework you can't explain is worse than an unnamed one you can.

How is "what would you do?" different from "tell me about a time"?

The hypothetical version asks for your process, so you answer with the four steps in order, in about 60 seconds. The behavioral version asks for evidence, so you tell one real story in STAR order — Situation, Task, Action, Result — in about 90 seconds to two minutes, with the four steps showing up inside the Action.

The 60-second target for the hypothetical version is the length the Interview Drills drill for this question ("The Competing Deadlines") is set to. The behavioral range follows the STAR method guide; the answer-length guide allows up to two and a half minutes for behavioral answers.

The two versions borrow from each other. A hypothetical answer gets stronger with one line of evidence — "That's what I did last spring when two client reports landed on the same Friday." A behavioral answer gets stronger with one line of process — "My rule is to sort by what's actually fixed first." Workable's guide advises that "To show the interviewer that your examples are not hypothetical, it's best to give real-life examples." You don't need to refuse a hypothetical question to follow that advice; answer the question you were asked, then add the one sentence of proof.

What does a good competing-deadlines answer sound like?

A good answer names the decision, the message to the people affected, and the finish, in that order. The examples below are fictional — written for this guide, with no real companies or people — to show the method in both versions and at different levels. The behavioral examples are written tight — 120 to 162 words, or about 50 to 80 seconds at a conversational 125 to 150 words per minute — so they sit below the 90-second-to-two-minute range above. When you tell your own, spend the extra time on the Action, not the setup.

Hypothetical version (any role, about 60 seconds)

"First, I'd take ten minutes to sort the three by impact and by which deadlines are actually fixed — a deadline tied to a client meeting can't move, but a 'by end of day' someone picked when they asked may be able to. (Sort) Then I'd message the people whose work comes second and third with a specific time they'll have it, and ask whether an outline or a first section earlier would unblock them. (Signal) If two are truly fixed and I can't do both well, I'd go to my manager with a recommendation: here's what I'd finish first and why. (Escalate) Then I'd finish that one before touching the next. (Finish) I did exactly this in my last role when a board deck and two client summaries landed on the same afternoon."

Behavioral version: marketing coordinator

"Last spring I had three things due on the same Thursday: launch emails for a product release, a monthly performance report for my manager, and slides for a partner webinar. (Situation and Task) I checked which dates were real. The launch date was fixed — it had been announced. The webinar was on Friday morning, so the slides could land Thursday night. The report was due Thursday because that's when we always did it, not because anyone needed it then. (Sort) I told my manager the report would come Friday at noon and asked whether a one-paragraph summary on Thursday would cover her; it did. I told the webinar host she'd have slides by 8 p.m. (Signal) Then I did the launch emails start to finish before opening anything else. (Finish) The emails went out on time, the host had slides that evening, and the full report came Friday morning. What I took from it: the first question isn't which task is urgent, it's which deadline is real. (Result)"

Behavioral version: new graduate or intern

"In my final semester I had a statistics exam, a group capstone presentation, and a paper all in the same week. (Situation) The exam and the presentation had fixed dates; the paper's due date was set by a professor who allowed one extension per term. (Sort) I asked for the extension on day one, not the night before, and told my capstone group I'd have my section of the slides done by Tuesday so they could rehearse. (Signal) I studied for the exam first because it came first and counted for more, then finished my slides, then wrote the paper over the weekend. (Finish) I passed the exam, our group presented on time, and the paper was in two days later under the extension. (Result)"

Behavioral version: team lead

"Two quarters ago, a customer escalation, a hiring deadline for an open role, and our quarterly planning doc all needed me in the same week. (Situation) The escalation was fixed — the customer's renewal was at risk. The planning doc had a hard leadership review date. The hiring deadline was internal and the recruiter confirmed it could move a week. (Sort) I told the recruiter and the two finalists the new decision date that morning. (Signal) That still left the escalation and the planning doc colliding on Wednesday, so I went to my director with a recommendation: I'd take the escalation myself and hand the first draft of the planning doc to my senior engineer, then review it Thursday. (Escalate) She agreed. (Result) The customer renewed, the planning doc went in on time, and the senior engineer has drafted it every quarter since — which freed a day of my time each cycle."

In each example the speaker decides and tells someone before the deadline hits. None of them say "I worked harder," and none of them claim the week went perfectly.

What mistakes sink a competing-deadlines answer?

The mistakes that sink this answer replace a decision with a trait — "I work harder," "I'm very organized," "I never miss deadlines" — or leave out the people affected. Each one can sound confident, which makes it easy to miss when you rehearse alone.

If your answer keeps growing as you add caveats about each task, the guide to stopping rambling in interviews covers how to cut it back to the steps.

What a scored answer actually looks like

We wrote the answer below as an example (it is not from a user) and typed it into the Interview Drills scorer — the same prompts, model, and scoring rubric the app uses for its "The Competing Deadlines" situational drill, which asks what you would do if three urgent tasks with tight deadlines landed at the same time — on October 8, 2026, three times. Typed answers carry no voice signal, so Delivery here judges how the text reads; spoken answers add pace, filler words, and pauses.

Answer (first take, typed):

"I'm really good under pressure, so I'd just work harder and stay late to get them all done. I'm very organized and I always make my to-do lists, so I would just power through. I don't really get stressed by deadlines, I actually kind of thrive on it."

Overall score: 22–28 / 100 across three runs. First run:

• Clarity 28 · Confidence 38 · Structure 15
• Conciseness 45 · Delivery 40 · Audience awareness 18

What the scorer flagged (first run, condensed):

• No process at all: three trait claims and no step-by-step reasoning, when the question asks how you think; "work harder and stay late" should become an actual first step
• "Really good under pressure," "very organized," and "thrive on it" are stacked self-claims with no evidence; replace them with one concrete situation
• No stakeholder communication: "stay late" implies quietly absorbing the problem instead of raising it with the people affected
• The close, "I actually kind of thrive on it," is a cliché that lands with no impact; end on a specific outcome or a forward-facing statement instead

Our rewrite (written by us, built on the four steps, then scored the same way: 88 on all three runs):

"First, I'd spend ten minutes sorting them by impact and by how much of each deadline is real. Some deadlines are fixed, like a client launch, and some are just someone's preferred date. Then I'd tell the people waiting on the other two exactly when they'd get them, before they have to ask, and ask whether a partial version earlier would help. If two are genuinely fixed and I can't do both well, I'd go to my manager with a recommendation, not just the problem: here's what I'd do first and why. Then I'd do the highest-impact one start to finish instead of switching between all three."

First run: Clarity 91 · Confidence 92 · Structure 90 · Conciseness 87 · Delivery 84 · Audience awareness 82.

The rewrite is Sort–Signal–Escalate–Finish in order: the sort with the fixed-versus-preferred test, the signal "before they have to ask," escalation with a recommendation, and a single-task finish. It is 107 words — inside the 60-second target. The first take shows three of the mistakes above: the hustle answer, the trait stack, and the silent sprint. The scorer's first-run summary named Structure as the biggest fix; the rewrite changed length, wording, and structure at once, so no single edit can be credited with the jump.

What the scorer still flagged on the rewrite (first run, condensed):

• Purely hypothetical: the answer stays in the conditional ("I would," "I'd") with no line from a real situation as evidence
• The sort uses urgent-versus-important logic without naming a framework such as the Eisenhower Matrix
• It never says out loud what the question is really testing — judgment under pressure
• The closing sentence states the right idea with low energy

The first point is the hypothetical-versus-behavioral gap from earlier on this page: the scorer's top suggestion for an 88 answer was one true sentence of evidence. The second is a nudge to name a method; follow it only if the name describes what you actually do. And if you don't have a real example, don't invent one — a made-up story is exactly what a follow-up question exposes.

What follow-up questions come after a competing-deadlines answer?

Expect the interviewer to test the edges of your process: "What if your manager says all three are top priority?", "What if you can't reach the person to renegotiate?", and "Tell me about a time it didn't work." Each one checks whether the process is yours or rehearsed.

• "What if your manager says they're all top priority?" Ask for an order, not a ranking of importance: "Understood — if I can only finish one by 5, which one?" That keeps the decision with the person who owns it, without refusing the work.
• "What if you can't reach the person who set the deadline?" Treat the deadline as fixed, tell them in writing what you're doing and when they'll have it, and keep going. Waiting for a reply is not a plan.
• "Tell me about a time it didn't work." Have a short story where a deadline did slip, what you told the person, and what you changed afterward. The behavioral interview preparation guide covers building a set of stories so a second request doesn't leave you blank.

When is this the wrong structure?

Sort–Signal–Escalate–Finish is for questions about colliding work. Don't force it onto "Tell me about a time you missed a deadline," which is a failure question: there, the interviewer wants your mistake, your repair, and what you changed, and a tidy prioritization process can read as dodging the miss.

It also does not need to be announced. You don't have to say "My framework has four steps" unless it helps you stay on track; the order of your sentences does the work. And if the role is one where deadlines are set entirely by others and nothing can be renegotiated, say so, and put the weight on Sort and Finish — while still telling people early when something is at risk.

How do you practice this answer before the interview?

Practice it out loud: write the four step names on a card, say the hypothetical version in about 60 seconds, then tell one real story in STAR order in under two minutes, and check each take for adjectives where a step should be. Saying it aloud matters because trait words like "organized" and "good under pressure" slip in when you're speaking and are easier to catch in a recording than in a draft.

Record one take and check three things: whether your first sentence is a step rather than a trait, whether you name who you would tell, and whether your last sentence is a finished task or an outcome rather than "I thrive on it." Fix one problem per take.

Interview Drills is an AI-powered interview training platform designed for people who have a real interview coming up. It diagnoses interview weaknesses with a free 3-minute quiz, prescribes a 14-day training track of practice drills, scores spoken answers on six dimensions in under 60 seconds, and, on the Interview Accelerator and Interview Pro plans, feeds the candidate's resume into scoring and feedback.

If you are not sure which part of your interviewing needs work, the free 3-minute quiz (25 questions, no account needed) identifies your interview persona and blind spot.

Frequently asked questions

How do you answer 'how do you prioritize when you have competing deadlines?'

Walk through your process in order. Sort the work by impact and by which deadlines are truly fixed versus someone's preferred date; tell the people whose work will come later exactly when they will get it, before they ask; if two fixed deadlines still collide, go to your manager with a recommendation, not just the problem; then finish the highest-impact task before starting the next. Spoken, that takes about 60 seconds.

Is 'how do you handle multiple priorities' the same question as 'how do you prioritize competing deadlines'?

Yes. Both test the same judgment: how you decide what comes first, who you tell, and when you escalate. 'Multiple priorities' can cover ongoing workload rather than one collision, so add a sentence on how you keep priorities current, such as a weekly check with your manager. The same four steps answer both.

Should I mention the Eisenhower Matrix in my answer?

Only if you actually use it and can say how. The urgent/important matrix is one way to sort tasks, and naming a method can show your thinking is systematic. But a named framework with no explanation adds nothing. Describe the sort you run, in your own words, and name the matrix as a label for it if it fits.

Is it okay to say I would work late to get everything done?

Not as your answer. Extra hours can be part of a plan, but leading with them tells the interviewer you would absorb the problem silently instead of deciding what matters and telling the people affected. Put the decision and the communication first; mention extra effort, if at all, as the last step.

What if I have never had competing deadlines at work?

Use school, an internship, volunteer work, or a part-time job. Two exams and a group project due in the same week is a real collision. The interviewer is judging how you decided what came first and who you told, not how senior the work was. If the question is hypothetical, answer with your process and add one sentence from that experience.

What should I say if I would have to miss a deadline?

Say you would raise it early, with a plan. Tell the person waiting on it as soon as you know, give them a new date you can actually hit, and offer a partial version sooner if that helps them. A missed deadline that someone hears about two days ahead is a scheduling change; one they discover on the day is a trust problem.

How long should an answer to 'how do you prioritize competing deadlines' be?

For the hypothetical version ('what would you do?'), about 60 seconds, roughly 125 to 150 words at a conversational pace. For the behavioral version ('tell me about a time'), about 90 seconds to two minutes, the length of a typical STAR story, because it adds the situation and the result.