Tell Me About a Time You Managed Multiple Priorities
Every graduate role involves juggling more than one thing at once — this question is how employers test whether you can do it without dropping something important. Here's how to answer it well.
Why Employers Ask This Question
"Tell me about a time you had to manage multiple priorities" — along with its close relatives "describe how you handled competing deadlines" and "how do you decide what to work on first" — is a staple of graduate interviews at every major employer, from investment banks to the Big Four to tech firms. It sits alongside teamwork and problem-solving as one of the most consistently tested competency-based interview questions, because almost every entry-level role involves more workstreams than hours in the day.
Unlike a question that tests a single skill, this one is really testing judgement under load: can you tell the difference between what's urgent and what's important, can you make a defensible trade-off when you can't do everything, and can you keep the people affected by your choices informed rather than quietly dropping something and hoping nobody notices. Interviewers are far less interested in how busy you were than in how you decided what to do about it.
| What Interviewers Are Really Assessing | Signal | Why It Matters to Them |
|---|---|---|
| How you distinguish urgent from important | Judgement, ability to see beyond the loudest task | New hires who firefight the loudest request first often neglect quietly critical work |
| The criteria behind your ranking | Structured thinking, not just gut instinct | Shows you can defend a prioritisation decision if it's later questioned |
| Whether you communicated trade-offs | Stakeholder awareness, transparency | Employers need people who flag a slipping deadline early, not the day it's due |
| How you adapted when priorities shifted | Flexibility, composure under changing demands | Graduate roles rarely have a static workload — priorities move constantly |
| Whether anything was actually delivered late or dropped | Honesty, follow-through | A credible answer includes the real trade-off made, not a story where everything got done perfectly |
Many candidates answer this question by describing how much they had on, which only proves they were overloaded — not that they handled it skilfully. The strongest answers spend more time explaining the criteria used to rank tasks than describing the volume of work itself. Interviewers already assume graduate life is busy; what they want to know is how you think when everything can't be done at once.
This question also frequently comes with a probing follow-up — "what did you have to deprioritise, and how did that go down?" — because interviewers want to hear about a genuine trade-off, not a story where you somehow managed to do everything perfectly and nobody was affected. Preparing an honest account of what got put lower down your list, and why, will make your answer far more credible.
How to Choose the Right Example
The biggest mistake candidates make when preparing this answer is picking the busiest period of their life rather than the period that best shows deliberate decision-making. Test any candidate example against these five filters before committing to it.
| Filter | Ask Yourself |
|---|---|
| Genuine competing demands | Were there at least two or three things that all mattered and couldn't all be done to the same standard in the time available? |
| A real trade-off | Did something actually have to move down the list, get delegated, or get done to a lower standard? |
| Your own criteria | Can you explain what made you rank one task above another, rather than just describing the order you happened to tackle them in? |
| Communication with others | Did you tell anyone affected about the trade-off, rather than silently making the call alone? |
| A concrete outcome | Did the situation actually resolve — everything landed somewhere, even if not everything landed perfectly? |
Good sources if you have limited work experience
This question does not require a corporate job. Strong examples regularly come from balancing a part-time job with coursework deadlines, running a society or sports team alongside exams, juggling a dissertation with multiple modules due in the same week, coordinating a group project where teammates depended on your input for several tasks at once, or managing a placement year where more than one manager assigned you work with overlapping deadlines. What matters is the decision-making, not the setting.
Two tasks colliding once is a scheduling clash; three or more overlapping demands over a sustained period is a genuine prioritisation challenge. The strongest stories describe an ongoing situation — a week or two, not a single afternoon — where you had to keep re-ranking tasks as things changed, not just resolve one clash and move on.
The PACE Framework
Structure your answer using PACE — an adaptation of the standard STAR interview technique built specifically around prioritisation, since the ranking logic and the communication around it are exactly what this question is designed to surface.
| Step | What to Cover | Roughly How Long |
|---|---|---|
| P — Pinpoint | The competing demands you faced, what made them genuinely hard to rank, and the deadline or constraint behind each one | 20–25% of your answer |
| A — Assess | The criteria you used to rank them — urgency, impact, dependency on others, reversibility — and what you decided to tackle first and last | 25–30% |
| C — Communicate | Who you told about the trade-off, especially anything you deprioritised, and how you kept them updated as things changed | 20–25% |
| E — Evaluate | The concrete outcome — what got delivered, what was delayed or handed off, and what you'd refine next time | 20–25% |
Why "Assess" is the step that separates strong answers from average ones
Most candidates can describe what they eventually did, but far fewer can clearly explain the criteria that got them there. A single sentence — "I ranked the client deliverable above the internal report because it had an external deadline and other people were blocked on it" — gives the interviewer direct evidence of judgement, not just a sequence of events. Naming your criteria explicitly is the single highest-leverage addition you can make to this answer.
That's roughly 220–320 words. Practise out loud with a timer rather than reading silently — spoken delivery runs slower than most candidates expect, and this question in particular tempts candidates to list every task they were juggling instead of focusing on the two or three that mattered most to the story.
6 Example Answers by Background
Below are six condensed scenarios covering different starting points, so you can adapt the underlying structure to your own experience rather than forcing a script that doesn't fit.
| Background | Competing Priorities Example | Key Skill Demonstrated |
|---|---|---|
| Part-time job + coursework | Two assignment deadlines falling in the same week as extra shifts during a staff shortage | Realistic self-assessment, negotiating workload with a manager |
| Society or committee role | Running a flagship event while exam revision was also due, with sponsors and exam boards both expecting attention | Delegation, ruthless ranking under fixed deadlines |
| Group project | Being the only member with the technical skills needed by two different sub-teams that both needed input the same week | Sequencing dependencies, transparent communication with both teams |
| Placement year / internship | Two managers each assigning "urgent" work with overlapping deadlines and no visibility of each other's requests | Escalation, diplomatic pushback, stakeholder management |
| Dissertation + modules | A dissertation supervisor meeting deadline colliding with two unrelated module submissions in the same fortnight | Long-range planning, breaking large tasks into a schedule in advance |
| Sports team captaincy | Balancing fixture scheduling, a teammate's personal issue needing attention, and your own training and exams in the same month | Compartmentalising, protecting time for the highest-impact tasks |
Full worked example
"In my final year, I was president of a 40-member student society at the same time as two assignment deadlines and my dissertation proposal all fell within the same ten-day window. The problem wasn't just volume — it was that the society's biggest annual event, which sponsors had already paid for, needed final logistics confirmed that same week, and delaying it wasn't an option. I assessed each demand against how fixed its deadline was and how many other people depended on it: the event had an external, immovable deadline and other people's plans hinged on it, so it went first. My dissertation proposal had a formal deadline but only affected me, so I blocked two focused evenings for it rather than treating it as urgent all week. The lowest-stakes assignment, which allowed short extensions, I flagged to my tutor in advance rather than waiting until it was overdue. I delegated the event's supplier calls to two committee members I'd trained, checking in twice rather than handling every call myself. The event ran successfully, my proposal was submitted on time, and I used my one available extension on the lowest-priority assignment rather than being forced into one on something more important. It taught me that naming the actual trade-off out loud — 'this has to move, and here's why' — gets a far better response from people than quietly trying to do everything and letting quality slip everywhere at once."
It states three concrete competing demands, names explicit criteria for ranking them (deadline flexibility, how many other people were affected), shows a real trade-off (the extension used deliberately, not accidentally), includes delegation and proactive communication, and closes with a transferable lesson — all in under 220 words.
Employer-Specific Angles
The PACE structure stays constant, but which part of it to emphasise shifts depending on the employer. Research each employer's published competency framework and lean your emphasis toward what they say they value most.
| Employer | What They Tend to Value in This Answer |
|---|---|
| Goldman Sachs | Sharp, defensible ranking criteria under genuine time pressure, and composure when describing a demanding period |
| PwC / Deloitte / EY / KPMG | Proactive communication with stakeholders about trade-offs — these firms typically staff graduates across multiple client engagements simultaneously, so this is a day-one skill, not a hypothetical one |
| Amazon | Ownership of the final call and a bias for making a decision rather than waiting to be told what to prioritise, echoing Amazon's published Leadership Principles |
| Microsoft | Adaptability when priorities shifted mid-way through, and reflection on how your approach to prioritisation has evolved with experience |
A story where every single task somehow got delivered perfectly and on time despite genuine overload reads as either untrue or as evidence you don't understand what a real trade-off looks like. A credible, specific compromise — even a small one — makes the rest of the answer far more believable than a suspiciously flawless outcome.
Common Variations of This Question
This question appears under several different phrasings across employers and interview formats, and each variation shifts the emphasis slightly. Recognising the version you're being asked helps you decide which part of your PACE answer to lead with.
| Variation | What It's Really Asking | Emphasis to Lead With |
|---|---|---|
| "How do you prioritise your workload?" | Your general system or process, not necessarily one specific story | The Assess step — describe your usual criteria, then anchor it with a brief example |
| "Describe a time you had competing deadlines" | A specific, high-pressure instance | Pinpoint and Assess — make the competing deadlines and your reasoning vivid |
| "What do you do when everything feels urgent?" | Your ability to distinguish true urgency from perceived urgency | Assess — explain how you separate genuinely time-critical work from work that only feels that way |
| "Tell me about a time you had to say no to a request" | Your comfort with pushing back and communicating a trade-off | Communicate — focus on how you had the conversation, not just the decision itself |
For a wider bank of prioritisation and time-management questions with fully worked STAR answers, see our dedicated time management interview questions guide, which covers 20 variations in more depth than a single blog post can.
6 Mistakes That Undermine Your Answer
- Mistake 1: Describing how busy you were instead of how you decided. Volume of work is not the point — the ranking logic behind your decisions is what interviewers are actually assessing.
- Mistake 2: Claiming nothing was ever deprioritised. A story with zero trade-offs at all is rarely believable and tells the interviewer nothing about your judgement under genuine constraint.
- Mistake 3: Leaving out the criteria behind your ranking. Stating what you did first without saying why leaves the interviewer unable to distinguish a considered decision from a lucky guess.
- Mistake 4: Not mentioning communication with anyone affected. Silently making a trade-off without telling the people it impacts is a red flag, not a strength, in a team-based graduate role.
- Mistake 5: Choosing an example with only two things happening at once. A single scheduling clash is easy to resolve and doesn't demonstrate sustained prioritisation skill the way three or more overlapping demands does.
- Mistake 6: Rambling through every task instead of focusing on the two or three that matter. Listing everything you had on that week dilutes the story — pick the handful of competing demands that best illustrate your decision-making and cut the rest.
Frequently Asked Questions
Practise the Tests That Come Before the Interview
A strong prioritisation answer gets you through the interview — but most graduate schemes screen with a numerical, verbal, or inductive reasoning test first. Practise the SHL-style tests employers actually use, then read the full time management question bank to prepare for every variation of this question.