Behavioralmedium6 min read

How Do You Handle Competing Priorities and Deadlines?

How to show you can triage work, push back when everything is labeled urgent, and protect quality when several deadlines collide.

When everything is urgent, nothing is. The interviewer is checking whether you freeze under that pressure, quietly drop things, or actually make deliberate calls about what gets done first. They want to see a system, not heroics.

What they're really asking

How do you decide what matters when you can't do it all? Do you communicate trade-offs to the people affected, or do you go silent and hope? Can you say no, or negotiate a deadline, without it turning into a fight? They want someone who manages the work instead of being buried by it.

How to structure your answer

STAR fits well. Situation: the moment several things landed at once. Task: what you were responsible for delivering. Action: your method for ranking the work, who you talked to, and what you renegotiated. Result: what shipped, what slipped on purpose, and whether the right people were okay with it. The key is showing that prioritizing means consciously choosing what not to do, and saying so out loud.

A sample answer

In one sprint I had three things land on me at once: a launch-blocking bug on the signup page, a perf fix for a product page that took eight seconds to load, and a design polish pass for a feature demo. All three were called urgent by different people.

I ranked them by impact and reversibility. The signup bug was blocking new users from getting in, so revenue, and it had no workaround. That went first. The slow product page was hurting conversion but it was degraded, not broken, so it could wait a day. The polish pass was the demo, which was a week out and had slack.

The part that mattered was telling everyone. I messaged the designer that polish would land Thursday not Monday, and explained why. She was fine with it once she had context. I fixed signup that morning, shipped the perf fix, which cut the page from eight seconds to under two, the next day, and did the polish Thursday with room to spare. Nobody felt dropped because nobody was surprised.

What to avoid

  • Saying you "just work harder" or pull all-nighters. That's not a strategy, it's a warning sign.
  • Going quiet on stakeholders. Silently dropping a task is worse than negotiating it.
  • Treating every item as equally urgent because you can't or won't rank them.
  • No outcome. Show what shipped, what you deliberately delayed, and that the call was right.

Before you leave — how confident are you with this?

Your honest rating shapes when you'll see this again. No grades, no shame.

Comments

to join the discussion.

Loading comments…

More managerial questions