OfferDrill.

Interview questions

The hard ones

How to answer "how do you prioritize your work?"

This question is asking for your decision rule, not your to-do app. Here's how to name that rule in one sentence, prove it with one real story, and say what you do when everything is due at once.

Why they ask it

They want to know what happens when your week goes sideways. Every job has more work than hours. The interviewer is trying to find out whether you have a way of choosing, or whether you just work on whatever the loudest person asked for most recently.

There's a second thing underneath it. They want to know if you'll tell them when something is going to slip. A person who quietly misses a deadline is more expensive than a person who says on Monday, "I can do one of these two by Friday, which one?" Your answer is a preview of how you'll handle that moment.

If the role involves a lot of interruptions — support, ops, admin, anything client-facing — they're also checking whether you can get pulled off a task and come back to it. Say so directly if that's your world.

What not to say

"I use a to-do list and a calendar, and I keep everything in [tool]."

Tools aren't a method. Everyone has a list. You've told them nothing about how you choose what goes at the top, which is the entire question. The interviewer moves on and writes down nothing.

"I'm really good at multitasking — I just get it all done."

This reads as someone who has never had to make a hard call, or who won't admit when they're underwater. Managers have been burned by this. They hear "this person will say yes to everything and then disappear."

"I do whatever my manager says is most important."

It sounds cooperative, but it tells them you need to be managed hour by hour. Fine for a first job, costly at mid-career. The fix is to say what you decide on your own, and when you check in.

Naming a framework and stopping there — "I use the Eisenhower Matrix, urgent versus important."

Grids are fine, but a name isn't an answer. Without a real example, it sounds memorized. Say the rule in your own words and immediately show it working on a real week.

How to build a strong answer

  1. Say your rule in one sentence.
    Plain words, no jargon. Something like: "I sort by what breaks if it doesn't happen, then by who's blocked waiting on me." Or: "Deadlines that involve other people come first, because my delay becomes their delay. Solo work fills the gaps." Pick the one that's actually true about how you work. One sentence, then stop and let the rest build on it.
  2. Give your tiebreaker.
    The real test is two things that both look urgent. Say what settles it. Common honest tiebreakers: money or safety at stake, a customer waiting, a hard external date like a filing or a launch, how many people are stuck behind it, or how hard it is to recover if it's late. Naming a tiebreaker is what separates you from the person with the nice to-do list.
  3. Prove it with thirty seconds of a real week.
    One example. What landed on your desk, what you picked, what you pushed, and how it turned out. Keep the setup short — two sentences of context, then the choice. If the outcome was mixed, say that. "I got it right on the deadline and wrong on how late I flagged the other piece" is a strong sentence, not a weak one.
  4. Say what you do when it won't all fit.
    This is the part most people skip and the part interviewers care about most. Describe the conversation you have: you go to your manager or the requester with the list, say what you can finish by when, and ask them to choose what slips. Say how early you do it. "As soon as I can see it won't fit, not the day before" is the line.

Examples to adapt

These are shapes, not scripts. Say them in your own words with your own facts — anything in brackets is a detail only you know, and it has to be the true one.

Mid-career, a role with real deadlines and several stakeholders. Adapt the details to your own work — don't memorize this.

My rule is that I start with whatever has consequences outside the team. If a client or a regulator or another department is waiting, that goes first, because my delay turns into their delay. Internal work I can renegotiate; external dates usually I can't. When two things both have outside consequences, I go with the one that's harder to fix if it's late. For example, at [employer], I had [the report] due to [the client] the same week we were closing [the other project]. The report had a fixed date and someone was waiting on it to make a decision. The project close was internal and we controlled the calendar. So I finished the report, and on Monday — not Thursday — I told my manager the close would land [the actual amount] later and why. She was fine with it because she heard it early. The thing I've learned is that the prioritizing part isn't hard. Telling people what you deprioritized, early, is the part that goes wrong.

It names a rule, names a tiebreaker, proves both in one example, and ends on the escalation. The "Monday, not Thursday" detail is the kind of specific that sticks.

Early career, one internship or first job. You don't need a big story — you need a clear method and honesty about checking in.

I start by figuring out what's actually a deadline and what just feels urgent because someone asked in person. So when something comes in, I ask when it's needed and what it's for. That one question sorts most of it. Then I do the things other people are blocked on first, because my part is usually small and their part is big. During my internship at [employer], I had [the recurring task] every week plus whatever came up. I blocked the morning for the recurring work since it fed [the thing it fed], and kept the afternoon open for new requests. When something came in that I couldn't fit, I said so and asked where it should go in the order — I'd rather ask than guess wrong and have someone find out Friday. I'm still building the judgment to make more of those calls on my own, and that's a big part of what I want from this role.

It's honest about experience level without apologizing. The "when is it needed and what is it for" question is a real method, and the last line turns inexperience into direction instead of a hole.

A role with constant interruptions — support, ops, healthcare, admin, anything where the day gets hijacked.

In my work the plan never survives the morning, so I prioritize twice. At the start of the day I pick the two or three things that have to be done by end of day no matter what. Then as things come in, I have one test: is anyone or anything stopped right now? If someone's stopped — a customer down, a line halted, a person waiting — that jumps the queue. If it's uncomfortable but moving, it goes on the list. That test keeps me from treating every loud request as an emergency. At [employer] I averaged [the number] interruptions a day, and the thing that made it work was writing down where I was before I got pulled away, so I could come back without losing twenty minutes re-reading. At the end of the day, anything that didn't get done and wasn't going to get done tomorrow either, I flagged to [my supervisor] rather than letting it sit.

The "is anyone stopped right now" test is a real, usable rule. It also quietly shows they can tell a true emergency from a loud one, which is the skill that job runs on.

What comes next

Answer this one well and the interviewer usually goes here:

  • Tell me about a time you had two deadlines you couldn't both hit. What did you do?
  • What do you do when your manager and someone senior to your manager both want their thing first?
  • How do you say no to a request?
  • Tell me about a time you got the priority wrong. What happened?
  • How do you keep track of what you've pushed off?
  • What's on your list this week, and how did you order it?
  • How often do you check in with your manager about priorities?

Say it out loud before it counts.

Reading a good answer and giving one are different skills, and the gap shows up in the room. Offer asks you this question out loud, on a clock, and tells you what landed. The first one is free.

Practice this out loud

You already prioritize every single day — the work here isn't inventing a method, it's putting words to the one you've been using.