How to Answer “How Do You Prioritise Your Work?” in an Interview

“How do you prioritise your work?” sounds like an invitation to talk about to-do lists. It isn’t. The interviewer wants to know what you do when two people need something from you by the same deadline and you can’t do both well. A good answer names the test you use to rank tasks, shows you checking that ranking with the people affected, and ends with a real example where it worked.

This article answers the questions candidates most often have about this question, in the order they tend to come up while preparing.

What is the interviewer really asking?

Three things, usually:

• Judgement. Can you tell what matters most to the team or the business, rather than what is loudest or easiest?
• Communication. When you decide something will wait, do you tell the people who are waiting for it?
• Adaptability. When priorities change halfway through the week, do you re-plan, or keep going with the old plan?

The UK Civil Service’s published behaviour framework shows how the expected answer grows with seniority. Prioritising appears in two of its behaviours: “Managing a Quality Service” and “Delivering at Pace”, which is defined as taking “responsibility for delivering timely and quality results with focus and drive”. The indicators change by grade:

Most private employers won’t publish anything this detailed, but the pattern is a useful guide. A junior candidate should talk about their own tasks. A manager should talk about the team’s priorities and the trade-offs they negotiated.

Is this a behavioural question or a “how would you” question?

It can be either. The wording tells you which:

• “How do you prioritise your work?” is about your general method. Describe it briefly, then prove it with one example.
• “Tell me about a time you had several urgent deadlines at once” is behavioural. Lead with the example and mention your method as part of what you did.
• “What would you do if your manager and a client both needed something by 3pm?” is hypothetical. Walk through your reasoning step by step, then add “and when that happened to me…” if you have a real case.

Whichever version you get, the example is what makes your answer believable. A method with no example sounds rehearsed.

What structure works best?

A four-part answer fits comfortably into about two minutes:

1. Your ranking test, in one sentence. For example: “I rank work by what is blocked without it and when it is actually needed, not by who asked first.”
2. How you keep track. Name the real tool: a shared task board, a ticketing queue, a calendar with blocked time, a daily list. Keep this short. The tool matters less than the habit.
3. How you handle clashes. This is the part most candidates skip, and it’s what interviewers most want to hear. Explain who you check with and how you tell people about a delay.
4. One example with a result. A specific week, the competing demands, the call you made, and what happened.

What does a strong answer sound like?

The answers below are illustrative. They show the shape of a good answer. Build your own from real events, because the follow-up questions will test the detail.

Illustrative answer: administrative or support role

“I start each day by sorting requests into what’s blocking someone else, what has a fixed deadline, and what can be batched. Blocking work goes first, because a missing purchase order or meeting room holds up several people at once. In my last role I supported three managers. One Monday, two of them asked for board-pack documents due on the same afternoon. I asked each of them which sections were needed first. Then I did the sections they both depended on, and agreed a one-hour extension with the manager whose meeting started later. Both packs went out on time for their meetings, and after that we set up a shared calendar of board dates so the clash didn’t happen again.”

Illustrative answer: technical or project role

“Our team works from a ticket queue, so the starting point is the agreed priority level. But I also look at impact. A bug affecting payments outranks a cosmetic fix, even if the cosmetic one was logged earlier. When a senior stakeholder asked me to drop sprint work for a new feature demo, I didn’t just switch. I showed my lead which two sprint items would slip, and he decided the demo was worth it. We moved those items to the next sprint and told the product owner the same day. The demo went ahead and nothing slipped without people knowing.”

Illustrative answer: people manager

“I separate what the team must deliver this quarter from what is merely requested. Every Monday we review the board against those commitments. When a regulatory deadline was brought forward by two weeks, I paused one internal project, moved two people onto the filing, and explained the trade-off to the internal project’s sponsor in writing. We filed on time. The paused project restarted with a revised date that the sponsor had agreed to in advance.”

Illustrative answer: student or fresh graduate

“During my final semester I had a dissertation draft, two coursework deadlines and a part-time retail job. I mapped every deadline for the term into one calendar in week one and worked backwards from each to set a weekly target. When my shift pattern changed in week eight, I spoke to my supervisor early and moved my draft review by a week, rather than rushing it. I submitted everything on time.”

If you are early in your career, examples from study, volunteering or part-time work are fine, as long as there were real competing demands.

Should I mention the Eisenhower matrix or another named method?

Only if you actually use it, and only in one sentence. The urgent-versus-important grid is widely linked to Dwight D. Eisenhower. Quote Investigator traced the idea to a 1954 address in Evanston, Illinois. In it, Eisenhower credited the thought to an unnamed “former college president” and said: “I have two kinds of problems, the urgent and the important. The urgent are not important, and the important are never urgent.”

The idea is helpful because it separates two things candidates often blur together: how soon something is due, and how much it matters. But an interviewer gains little from hearing a framework named. They gain a lot from hearing how you applied it to a real clash. Something like “I distinguish urgency from impact” followed by an example works better than a summary of the four quadrants.

What follow-up questions should I expect?

• “What did you deprioritise, and how did that person react?”
• “How did you know which task mattered more to the business?”
• “What would you do if your manager disagreed with your ranking?”
• “Tell me about a time your prioritisation went wrong.”
• “How do you deal with interruptions during focused work?”

Prepare a short, honest answer to the “went wrong” version. A sentence about a deadline you missed because you underestimated a task, plus what you now do differently, is more convincing than claiming it never happens.

What should I avoid saying?

• “I just work harder” or “I stay late.” Long hours are a cost, not a method, and they suggest the problem would come back.
• “I do everything in the order it arrives.” This tells the interviewer you don’t rank work at all.
• Only talking about tools. Listing apps without saying how you decide what goes at the top makes the answer empty.
• Deciding alone and telling nobody. If your example involves quietly letting someone’s work slip, it raises a red flag about communication.
• Criticising a former manager for giving you too much work. Describe the demands neutrally.

How do I prepare in 20 minutes?

1. Reread the job advert and underline anything about deadlines, multiple stakeholders, volume or fast-changing priorities. Those words tell you which kind of clash to talk about.
2. Write your ranking test in one sentence.
3. Pick one example where demands genuinely clashed. Note the people involved, what you decided, who you told, and the result.
4. Pick a second, smaller example in case they ask for another.
5. Say both out loud once and time them.

Your CV can back this up. A bullet that shows volume and deadlines, such as the number of requests handled or projects run in parallel, gives the interviewer a reason to believe your answer. If you are updating your CV for the role, the resume examples by job show how to phrase workload and deadline achievements, and the ATS resume score checker can flag whether your CV reflects the keywords in the advert.

Frequently asked questions

How long should my answer be?

None of the sources here sets a length. Around one and a half to two minutes, including the example, is a practical target that leaves room for follow-ups.

Is it the same as “How do you handle multiple deadlines?”

Very close. The deadlines version leans more on planning ahead, while the prioritisation version leans more on how you rank and re-rank tasks. The same example can usually answer both, with a different emphasis.

What if my job didn’t really involve competing priorities?

Most jobs involve some. Look at study, volunteering, family responsibilities around work, or a busy period such as a seasonal peak. Choose a real clash, even a small one, rather than inventing a dramatic one.

Is this the same as being asked about stress?

No. Stress questions are about how you cope with pressure. This one is about how you decide what to do first. If you are asked both, use different examples.

Sources

• Success Profiles: Civil Service behaviours (UK Cabinet Office, GOV.UK)
• Quote Origin: What Is Important Is Seldom Urgent and What Is Urgent Is Seldom Important (Quote Investigator)