Six question sets for employers, from core and behavioral to live reprioritization scenarios and a manager set, each question paired with why it is worth asking and what a strong answer sounds like. Built for small businesses without HR. Download as DOCX.
The most useful question I have ever asked in an interview is not clever. It is: walk me through how you decided what to work on first this morning. Candidates prepare a polished story about a big project. Almost nobody prepares an answer about today, so you get their real method instead of their rehearsed one.
Prioritization is the skill small businesses test worst and need most. Nobody hands a new hire at a ten person company a ranked queue. They get four half defined responsibilities and a founder who is busy, and they either build their own ranking or drown quietly for a quarter while everyone assumes things are fine.
At FirstHR we build for employers hiring without an HR department, where the owner runs the interview alone between everything else. This page gives you six question sets, each question paired with a stated reason it earns its place and what a strong answer sounds like, plus a 1 to 5 scorecard. Browse the rest of the hiring templates if you need the job description and offer letter next.
TL;DR
Good prioritization interview questions force a tradeoff, because that is where the skill actually lives. Ask what they worked on first this morning, a time two deadlines collided, something they deliberately chose not to do, and what they do at noon when today is already lost. Score the criterion behind the choice, not the volume of work described. Download six question sets and a 1 to 5 scorecard as DOCX.
What Prioritization Questions Actually Test
Prioritization questions test one thing: whether a candidate can name what loses. Anything that does not force a choice is a task management question wearing a different label, which is why the open prompt how do you prioritize your work produces a rehearsed answer from every candidate and separates nobody.
Three behaviors sit underneath a good answer. First, an explicit criterion: deadline risk, revenue impact, who is blocked, what breaks if it slips. Second, comfort with subtraction, meaning they can name something they dropped and are not defensive about it. Third, early communication, because a change of priority nobody hears about lands the same as a missed deadline.
That third behavior is the one owners underweight and then live with daily. A candidate who reprioritizes well but silently will still surprise you at 5pm on the wrong day. The situational prompts in set three are built to surface it, because the noon scenario has only two honest endings.
Which Question Set Should You Use?
Pick two or three sets that match the failure mode of the role, not all six. A bookkeeper and a shift lead both prioritize, but the back office risk is quiet drift on a deadline nobody is watching, while the frontline risk is a stream of interrupts that never lets the important work start.
Core Questions
Start here, any role
Six questions that work for any position, built to surface the criterion a candidate actually uses when two things compete for the same hour.
Behavioral: Competing Deadlines
Real past examples
STAR questions about collided deadlines, a missed date, and a week beyond one person. Past behavior is the strongest single predictor here.
Situational: Reprioritizing Live
For thin resumes
Scenarios to run when a candidate is early career or you want a second read on judgment. Score the reasoning, not the choice they make.
Method, Tools, Communication
Does the system exist?
How they track work, plan a week, estimate, and tell you when a plan breaks. The questions that catch framework vocabulary with no practice behind it.
Managers and Team Leads
Setting others’ priorities
For roles that rank work for other people: capacity calls, saying not yet, and keeping important but non urgent work alive.
Scorecard (1 to 5 Rubric)
Score, do not guess
Six scoring areas with space for quoted evidence, so a decision rests on what was said rather than who interviewed best.
Match the Set to How the Role Fails
For back office and administrative roles, weight the method and communication questions. For customer facing and frontline roles, weight the live scenarios. For anyone who ranks work for other people, the manager set is not optional, and it pairs naturally with your office manager or operations manager job description. Whatever you pick, ask the same set of every candidate so the answers stay comparable.
6 Question Sets to Download
Download all six as one Word document or copy individual sets. Every question comes with a stated reason it is worth asking, and every set ends with what a strong answer sounds like and what a weak one sounds like. The sixth file is the scorecard.
Download All Question Sets and the Scorecard
Five question sets plus a 1 to 5 scoring rubric, with reasons and answer guidance. All in one DOCX.
Set 1: Core Prioritization Questions
Six questions that work for any role, built to surface the criterion a candidate actually uses when two things want the same hour. Start here even if you use nothing else.
Core Prioritization Questions (Any Role)
PRIORITIZATION INTERVIEW: CORE QUESTION SET
Candidate: __
Interviewer: __
Date: __
QUESTIONS TO ASK, AND WHY EACH ONE EARNS ITS PLACE
1. Walk me through how you decided what to work on first this morning.
Why ask it: it is the hardest question to rehearse. You get their real
method, applied to real work, not a framework they read about.
2. When two things are both urgent, how do you decide which one waits?
Why ask it: prioritization only exists under scarcity. Everything else is
just a task list.
3. What is the difference between urgent and important in your work?
Why ask it: candidates who cannot separate the two will spend the whole
week on other people’s emergencies.
4. Tell me about something you deliberately chose not to do last quarter.
Why ask it: real prioritization means dropping things. A candidate who has
never dropped anything has never prioritized anything.
5. How do you know when your priorities are wrong?
Why ask it: tests self-correction. Good operators notice drift early and
reset instead of grinding on.
6. Who decides your priorities today: you, your manager, or your customers?
Why ask it: reveals whether they take ownership or wait to be assigned.
WHAT A STRONG ANSWER SOUNDS LIKE
A strong answer names a criterion, not a feeling: deadline risk, revenue
impact, who is blocked, what breaks if it slips. It gives a real example with
a real tradeoff, and states what got dropped or delayed as a result. Listen
for someone who checked their assumption with a manager or a customer rather
than guessing in silence.
A weak answer says "I just make a list and work through it," treats
everything as equally important, or claims to have never missed or dropped
anything. Both are signs the candidate has not held a genuinely overloaded
role.
NOTES
[Capture the criterion they named, the example, and what they dropped.]
Set 2: Behavioral Questions on Competing Deadlines
Real past examples of collided deadlines, a missed date, and a week beyond one person. Score these with STAR, and treat a candidate who has never missed anything with polite suspicion.
Behavioral Questions: Competing Deadlines
PRIORITIZATION INTERVIEW: BEHAVIORAL QUESTIONS
Candidate: __
Interviewer: __
Date: __
Ask for a real past example. Score with STAR: Situation, Task, Action, Result.
QUESTIONS TO ASK, AND WHY EACH ONE EARNS ITS PLACE
1. Tell me about a time two deadlines collided and you could not hit both.
Why ask it: forces the candidate to name a loser. Anyone who says they
satisfied both usually did not face a real conflict.
2. Describe a time you missed a deadline. What happened next?
Why ask it: how someone handles a miss matters more than whether they have
ever had one. Look for early warning, not late excuses.
3. Tell me about a week where the workload was genuinely beyond one person.
Why ask it: tests whether they escalate, negotiate scope, or quietly burn
out. All three predict very different behavior on your team.
4. Give me an example of a time you pushed back on a request.
Why ask it: a candidate who never says no will accept every task and
deliver none of them well.
5. Tell me about a time you got the priorities wrong. How did you find out?
Why ask it: separates people who reflect from people who rewrite history.
6. Describe a project that slipped because something else took over.
Why ask it: tests whether they track the thing they paused or simply
abandon it.
WHAT A STRONG ANSWER SOUNDS LIKE
The Situation is specific and dated. The Action is something the candidate
personally did, in the first person, not what "the team" decided. The Result
includes a number or a concrete outcome, and the candidate says what they
would do differently.
The best answers include the conversation: who they told, when they told
them, and what they proposed. Prioritization inside a small team is a
communication skill as much as a judgment skill.
Red flag: a candidate who describes a conflict but never mentions telling
anyone until after the deadline passed.
NOTES
[Situation, Action, Result, and who they informed.]
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
Set 3: Situational Questions for Reprioritizing Live
Scenarios for early career candidates or as a second read on judgment. The sixty unread messages prompt and the noon scenario are the two that earn their keep most often.
Situational Questions: Reprioritizing Live
PRIORITIZATION INTERVIEW: SITUATIONAL SCENARIOS
Candidate: __
Interviewer: __
Date: __
Use these when a candidate is early in their career and lacks past examples,
or as a second pass to test judgment on your actual situations.
QUESTIONS TO ASK, AND WHY EACH ONE EARNS ITS PLACE
1. You come back from a week off to sixty unread messages. What do you open
first, and why?
Why ask it: a clean test of triage criteria with no domain knowledge
required.
2. You are halfway through a task due at 5pm and I hand you something urgent.
What do you do in the next five minutes?
Why ask it: the first five minutes reveal whether they act or freeze.
3. Two people who both outrank you ask for the same afternoon. What now?
Why ask it: tests whether they resolve the conflict or dump it on you.
4. A customer escalates while you are closing the month. Which slips?
Why ask it: forces a tradeoff between the visible and the important.
5. You realize at noon that you cannot finish today. What is your next move?
Why ask it: early warning versus silent hope is one of the biggest
predictors of a smooth working relationship.
6. Everything on your list is marked high priority. How do you sort it?
Why ask it: this is the actual condition of most small business roles.
WHAT A STRONG ANSWER SOUNDS LIKE
A strong answer asks a clarifying question before answering, which is a good
sign rather than a stall. It then applies an explicit rule: who is blocked,
what has an external deadline, what costs money if it waits, what is
reversible. It ends with a communication step.
Scenario answers should be judged on the reasoning, not the choice. Two
candidates can pick opposite tasks and only one of them explained why.
Red flag: an answer that solves the scenario by working late. That is a
capacity answer to a prioritization question.
NOTES
[Rule they applied, clarifying questions asked, communication step.]
Set 4: Method, Tools, and Communication
How they track work, plan a week, estimate, and tell you when the plan breaks. These questions catch framework vocabulary with no practice behind it.
Method, Tools, and Communication Questions
PRIORITIZATION INTERVIEW: METHOD AND TOOLS
Candidate: __
Interviewer: __
Date: __
QUESTIONS TO ASK, AND WHY EACH ONE EARNS ITS PLACE
1. Show me how you track your work. What system do you actually use?
Why ask it: an honest answer about a simple system beats a rehearsed
framework nobody follows.
2. How do you plan a week, and how often does the plan survive contact?
Why ask it: tests planning and realism at the same time.
3. How do you estimate how long something will take?
Why ask it: bad estimation is the hidden cause of most bad prioritization.
4. How do you keep your manager informed when priorities change?
Why ask it: in a small business the owner needs to hear about a change on
the day it happens, not at the deadline.
5. What do you do with a task that keeps getting pushed to tomorrow?
Why ask it: reveals whether they kill, delegate, or let it rot.
6. How do you protect focus time when your team can interrupt you?
Why ask it: separates people who defend a block of deep work from people
who are permanently reactive.
7. How do you decide what to delegate or hand off?
Why ask it: relevant even for individual contributors, who hand work to
vendors, contractors, and teammates constantly.
WHAT A STRONG ANSWER SOUNDS LIKE
A strong answer describes one system the candidate genuinely uses and can
demonstrate, plus a habit for reviewing it. It admits a weakness in
estimation and describes a correction, such as adding buffer or breaking work
into smaller pieces.
Do not over-reward framework vocabulary. A candidate who names three
prioritization frameworks but cannot say what they worked on yesterday is
describing reading, not practice.
Red flag: "I keep it all in my head." That works until the day it does not,
and it leaves you with no visibility.
NOTES
[System named, review habit, estimation honesty.]
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
For roles that rank work for other people: capacity calls, saying not yet to a stakeholder, and keeping important but non urgent work alive when everything is on fire.
Prioritization Questions for Managers and Leads
PRIORITIZATION INTERVIEW: MANAGERS AND TEAM LEADS
Candidate: __
Interviewer: __
Date: __
Use this set when the role sets priorities for other people, not just for
itself.
QUESTIONS TO ASK, AND WHY EACH ONE EARNS ITS PLACE
1. How do you decide what your team works on when requests exceed capacity?
Why ask it: the core of the job. A lead who accepts everything creates a
team that finishes nothing.
2. Tell me about a time you told a stakeholder no, or not yet.
Why ask it: tests whether they protect the team or pass pressure straight
through.
3. How do you communicate a change in priority so the team does not whiplash?
Why ask it: constant reprioritization without explanation is a top driver
of turnover on small teams.
4. How do you make sure important but non urgent work actually happens?
Why ask it: process improvement, documentation, and training die first
under pressure, and their absence compounds.
5. How do you handle a team member who is busy but working on the wrong
things?
Why ask it: a coaching question disguised as a prioritization question.
6. How would you prioritize your first ninety days here?
Why ask it: the single best test of judgment about your business,
answerable only by a candidate who researched you.
WHAT A STRONG ANSWER SOUNDS LIKE
A strong candidate describes a visible, shared way of ranking work, so the
team can see why something moved. They give a specific example of declining
or deferring a request, including how they explained the decision to the
person who asked.
On the ninety day question, look for someone who plans to learn before they
reorganize, and who names one or two outcomes rather than ten.
Red flag: a candidate whose only answer to overload is asking the team to
work harder.
NOTES
[Ranking method, an example of a real no, ninety day plan.]
Set 6: Prioritization Interview Scorecard
Six scoring areas from 1 to 5 with space for quoted evidence, so the decision rests on what was said rather than who interviewed best. This is the asset most question lists leave out.
Prioritization Interview Scorecard (1 to 5 Rubric)
PRIORITIZATION INTERVIEW SCORECARD
Candidate: __
Interviewer: __
Date: __
Score each area from 1 (poor) to 5 (excellent). Write the evidence, not the
impression. If you cannot quote something the candidate said, the score is
not yet earned.
SCORING AREAS
Names an explicit criterion for ranking work Score: [ 1 2 3 4 5 ]
Evidence: __
Handles a real tradeoff, and says what lost Score: [ 1 2 3 4 5 ]
Communicates early when a deadline is at risk Score: [ 1 2 3 4 5 ]
Evidence: __
Uses a system they can actually demonstrate Score: [ 1 2 3 4 5 ]
Evidence: __
Protects important but non urgent work Score: [ 1 2 3 4 5 ]
Evidence: __
SUMMARY
Total score: ______ / 30
Overall recommendation: [ ] Strong yes [ ] Yes [ ] No [ ] Strong no
Strongest evidence: __
Biggest concern: __
Interviewer signature: __
Guidance: score within an hour of the interview, before the next candidate.
If more than one person interviews, each scores independently and only then
compares, so the most senior opinion in the room does not set the anchor.
Four Questions, Broken Down
Every question below earns its place for a specific reason, and the reason changes what you listen for. These four carry the most weight across the widest range of roles, so if you only have ten minutes for prioritization, use these.
Walk me through how you decided what to work on first this morning.
Why ask it: Almost impossible to rehearse. Prepared candidates arrive with a polished story about a big project; nobody prepares an answer about today.
Strong answer: Names the actual first task, the reason it came first, and what it beat. Something like: the invoice run came first because a vendor payment was due, so the report moved to the afternoon.
Weak answer: Describes a general philosophy with no example from that morning, or says the day had no competing demands, which is rarely true.
Tell me about something you deliberately chose not to do last quarter.
Why ask it: Prioritization is subtraction. A candidate who has never cut anything has been ranking a list, not making choices under real constraint.
Strong answer: Names a specific thing that was dropped or deferred, the reason it lost, who was told, and what happened as a result. Comfort with the tradeoff is the signal.
Weak answer: Cannot produce an example, or reframes the question into a story about how they found a way to do everything after all.
You realize at noon that you cannot finish today. What is your next move?
Why ask it: Early warning versus silent hope is the behavior you will live with every week. It predicts your working relationship better than almost any other answer.
Strong answer: Tells the affected person immediately, proposes a revised date or a reduced scope, and offers an option rather than only a problem.
Weak answer: Plans to work late and say nothing, or waits until end of day to raise it. Working late is a capacity answer to a prioritization question.
How do you make sure important but non urgent work actually happens?
Why ask it: Documentation, process fixes, and training are the first things dropped under pressure, and their absence compounds quietly for months.
Strong answer: Describes a protected slot, a recurring review, or a rule that reserves capacity, plus a real example of non urgent work that shipped.
Weak answer: Says it happens when things quiet down. Things do not quiet down at a small business, and both of you know it.
The pattern is the same in all four: the first answer is often rehearsed, and the signal arrives in the second or third follow up. Ask what lost, who you told, what the result was, and what you would do differently.
Green Flags and Red Flags
The clearest green flag is a candidate who names what they gave up without being asked twice. The clearest red flag is one who solves every scenario by working late, because that answers a capacity question you did not ask and dodges the prioritization question you did.
Green flags
Names an explicit criterion, not a feeling
Says what lost, and seems fine about it
Warns people before a date slips
Asks a clarifying question before answering
Signals of real practice
Can describe yesterday, not just a framework
Admits an estimation weakness and a fix
Has a system they could show you
Reserves time for non urgent work
Softer warnings
Every task is described as high priority
Priorities are always set by someone else
Has never dropped or deferred anything
Keeps it all in their head
Hard red flags
Solves every scenario by working late
Hid a slipping deadline until it passed
Blames the team for a missed date
Only response to overload is more hours
Treat the softer warnings as prompts to probe rather than as disqualifiers. Someone whose priorities have always been assigned may simply have never worked anywhere that allowed otherwise, and a good follow up separates that from a genuine lack of judgment. The hard red flags are different, and they overlap heavily with the general interview warning signs worth taking seriously.
How to Score the Answers
Score six areas from 1 to 5 within an hour of the interview, before the next candidate blurs the details. If you cannot quote a sentence the candidate actually said, the score is not yet earned, which usually means the question set was too shallow rather than that the candidate was weak.
Scoring area
Score 1 to 2
Score 4 to 5
Names an explicit criterion
Ranks by feeling or by whoever asked last
Names a checkable rule: blocked, deadline, cost, reversible
Handles a real tradeoff
Claims to have satisfied every demand
Says what lost and why, without defensiveness
Reprioritizes when things change
Freezes, or finishes the old task on autopilot
Reassesses fast and states the new order out loud
Communicates early
Raises the slip after the deadline passed
Warns the same day, with a revised date or reduced scope
Has a real system
Keeps it all in their head
Describes one system they use and could show you
Protects non urgent work
Says it happens when things quiet down
Reserves a slot or a rule, with a real example
Have every interviewer score alone before the group talks. Prioritization answers are easy to talk yourself into, because a confident candidate describing a crisis sounds decisive whether or not the reasoning held. The same discipline sits behind our interview evaluation form if you want one sheet across every competency.
Fair, Legal, and Structured Interviewing
Ask the same job related questions, in the same order, of every candidate. That single habit is what makes a prioritization interview both fair and useful, and it is the same practice behind a structured interview, which produces more comparable evidence and less room for bias than a free conversation.
Keep the scenarios about work, not the person
Prioritization questions drift into personal territory more easily than most, because the honest answer to why a candidate left at four is often about a child, a caregiving duty, or a medical appointment. Federal anti discrimination law, enforced by the EEOC, prohibits basing hiring decisions on protected characteristics, and EEOC guidance says information requested during the pre employment process should be limited to what is essential for determining whether a person is qualified. So ask how they handle a fixed external deadline, not how they handle school pickup. Ask whether they can meet the schedule the job requires, not why they might not. This is general information, not legal advice.
Ask the same questions in the same order
The Uniform Guidelines on Employee Selection Procedures require that selection procedures be administered and scored in a standardized way for anyone using them to screen candidates. Structured interviewing meets that standard and also produces better hires: the same core questions, asked in the same order, scored on the same rubric, make candidates comparable instead of memorable. For prioritization questions this matters twice over, because the follow up is where the signal lives. Decide your follow ups in advance so every candidate gets the same depth, not just the ones you liked in the first five minutes.
Score independently, then compare
When more than one person interviews, each should complete the scorecard alone before anyone speaks. Prioritization answers are unusually easy to talk yourself into, because a confident candidate describing a crisis sounds decisive whether or not the reasoning held up. Independent scoring keeps the most senior voice in the room from setting the anchor for everyone else. Compare the quoted evidence first and the overall impressions second. If nobody can quote a sentence the candidate actually said, that is a sign the question set was too shallow rather than a sign the candidate was strong.
Weight the sets to the real job
A bookkeeper closing the month and a shift lead running a floor both prioritize, but the failure modes are different. For back office roles, weight the method and communication questions, since the risk is quiet drift on a deadline nobody is watching. For customer facing and frontline roles, weight the situational scenarios, since the job is a constant stream of interrupts. For any role that ranks work for other people, the manager set is not optional. Pick the two or three sets that match the job, ask every candidate the same ones, and skip the rest.
Busy Interviews Better Than Effective
Research published in Harvard Business Review by Heike Bruch and Sumantra Ghoshal, Beware the Busy Manager, found that only about 10 percent of managers spend their time in a committed, purposeful way. The rest lack energy, focus, or both, and the most common trap is high energy with low focus. That is exactly the profile that interviews well, which is why you score the criterion behind a choice rather than the volume of activity described.
Two sources are worth keeping open while you write your question list. The EEOC guidance on prohibited employment practices states that information requested during the pre employment process should be limited to what is essential for determining whether a person is qualified. The Uniform Guidelines on Employee Selection Procedures require that selection procedures be administered and scored in a standardized way.
For question banks organized by competency, SHRM publishes sample interview questions across twelve competency areas, including stress management and composure, split into behavioral, situational, and general formats. It is a useful cross check once you have drafted your own set. This is general information, not legal advice.
Testing Prioritization Without an HR Department
Without HR, the constraint you are testing the candidate for is the same one you are interviewing under. You have no recruiter to coordinate scorecards and no panel to balance a strong first impression, so the structure has to be in the questions themselves. Here is how to close that gap.
At a small company, nobody hands the new hire a ranked list
This is why prioritization matters more here than at a large employer, and why generic interview kits under test it. A big company gives a new hire a manager, a queue, and a defined lane. A small business gives them four half defined responsibilities and a founder who is busy. The hire either builds their own ranking or drowns quietly for three months while you assume things are fine. So the question is not whether a candidate can follow priorities, it is whether they can set them with incomplete information and then tell you what they chose. Weight the core set and the communication questions accordingly.
Busy is not the same as effective, and interviews reward busy
A candidate who describes a frantic week with sixty tasks sounds impressive in an interview and can still be the wrong hire. Research published in Harvard Business Review by Heike Bruch and Sumantra Ghoshal found that roughly ten percent of managers spend their time in a committed, purposeful way, while the rest lack energy, focus, or both, and that the most common trap is high energy paired with low focus. That is exactly the profile that interviews well. The fix is to ask what the candidate did not do, and to score the criterion behind the choice rather than the volume of work described.
You are the interviewer, the hiring manager, and the person with no time
Most owners run these interviews alone, between everything else, which is the same constraint you are testing the candidate for. Pick two or three question sets rather than all six, write your follow ups down before the first call, and score within the hour while the answers are still exact. Once you choose someone, the work shifts from evaluating to hiring well, and FirstHR handles that side for a small business: send the offer for e signature, run the new hire paperwork as a guided onboarding workflow, assign the first week of tasks, and keep the signed documents on the employee profile. FirstHR is an onboarding and HR platform, not a project management tool, so pair it with whatever your team plans work in. Applicant tracking is coming soon to FirstHR.
One practical note on running it: prepare your follow ups before the call, not during it. The follow up is the part that gets dropped when you are improvising, and it is the part that carries the signal. If you want a fuller walkthrough of the session itself, our guide on how to conduct an interview covers the mechanics. Applicant tracking is coming soon to FirstHR.
From Interview to Hire
Once the scorecards are in, the work shifts from evaluating to hiring well: a clear offer letter, the new hire paperwork, and a first ninety days that is actually ranked. The last part matters more than usual here, because you just hired for judgment about what comes first and then have to give that judgment something to work from.
Pick two or three sets
Match the sets to the job rather than asking all six, and use the same ones for every candidate so the comparison holds.
Write the follow ups first
Decide in advance what you will probe: what lost, who was told, what the result was. The follow up is where the signal is.
Score, then offer
Complete the rubric within the hour, compare quoted evidence, then put the role, pay, and start date in writing with e signature.
Set priorities on day one
Give the new hire a ranked first ninety days in writing, so the judgment you hired for has something to work from.
FirstHR connects that side for a small business: the offer and policy acknowledgments go out for e signature, the new hire paperwork runs as a guided onboarding workflow, first week tasks get assigned and tracked, and every signed document lands on the employee profile. To be clear about scope, FirstHR is an onboarding and HR platform, not a project management or task tracking tool, so pair it with whatever your team plans work in. Applicant tracking is coming soon to FirstHR.
Key Takeaways
Prioritization questions only work when they force a tradeoff, so ask what lost rather than how the candidate prioritizes.
Walk me through what you worked on first this morning is the hardest prioritization question to rehearse.
Score the criterion behind a choice, not the volume of work described, because busy interviews better than effective.
Treat early communication as a scoring area of its own; silent reprioritization lands like a missed deadline.
Use behavioral questions first and situational scenarios as a second pass, scoring the reasoning rather than the choice.
Ask the same job related questions of every candidate and score independently on a written rubric before anyone discusses.
Frequently Asked Questions
What are good prioritization interview questions to ask candidates?
The strongest prioritization questions ask about a real, recent, constrained choice rather than a philosophy. Four that consistently work: walk me through how you decided what to work on first this morning; tell me about a time two deadlines collided and you could not hit both; tell me about something you deliberately chose not to do last quarter; and you realize at noon that you cannot finish today, what is your next move. Each one forces a tradeoff, which is where prioritization actually lives. Pair every question with a follow up that asks what lost, who was told, and what the result was. Skip open questions like how do you prioritize your work, because every candidate has an answer prepared for that one and it tells you almost nothing.
What does a strong prioritization answer sound like?
A strong answer names an explicit criterion, gives a specific example, and states what got dropped. The criterion is something checkable: who is blocked, what has an external deadline, what costs money if it waits, what is reversible. The example is dated and detailed, and the candidate describes what they personally did rather than what the team decided. The best answers include the communication step, meaning who they told and when they told them, because on a small team a change of priority that nobody hears about is the same as a missed deadline. A weak answer stays general, treats every task as equally important, claims to have never dropped anything, or resolves every scenario by working late. Working late is a capacity answer to a prioritization question.
Should I use behavioral or situational prioritization questions?
Use behavioral questions first and situational questions as a second pass. Behavioral questions ask what the candidate actually did in a past situation, and past behavior is the more reliable predictor, so lead with prompts like tell me about a time two deadlines collided. Situational questions pose a hypothetical, which is useful when a candidate is early in their career and has thin experience to draw on, or when you want to test judgment against your own real conditions. When you use a scenario, score the reasoning rather than the choice, because two candidates can pick opposite tasks and only one of them can explain why. A practical split for most small business roles is three or four behavioral questions and two scenarios.
How do I score prioritization answers fairly?
Use a written rubric with a small number of scoring areas and space for quoted evidence. Six areas cover it: names an explicit criterion, handles a real tradeoff and says what lost, reprioritizes calmly when things change, communicates early when a deadline is at risk, uses a system they can demonstrate, and protects important but non urgent work. Score each from 1 to 5 within an hour of the interview, before the next candidate blurs it. If you cannot quote a sentence the candidate said, the score is not yet earned and the question set was probably too shallow. When more than one person interviews, everyone scores alone before the group talks, so the most senior opinion does not set the anchor. A downloadable scorecard is included on this page.
Are prioritization interview questions legal to ask?
Yes, as long as they stay about the work. Questions about how a candidate ranks tasks, handles competing deadlines, or communicates a slipping date are job related and permitted. The caution is specific to this topic: prioritization questions drift into personal territory more easily than most, because the honest reason a candidate had to leave early is often caregiving, a medical appointment, or family. Do not ask about those. Ask whether the candidate can meet the schedule the role requires, not why they might not. Federal law enforced by the EEOC prohibits basing hiring decisions on protected characteristics such as age, disability, religion, national origin, sex, and pregnancy or family plans. Ask the same job related questions of every candidate and the risk mostly takes care of itself. This is general information, not legal advice.
How is prioritization different from time management?
Time management is about executing a plan; prioritization is about choosing which plan deserves the time. A candidate can be excellent at time management and still spend a whole week on work that did not matter, which is the more expensive failure. In an interview, time management shows up as systems, calendars, and estimation, while prioritization shows up as tradeoffs: what they chose, what they dropped, and the criterion behind both. Test both, but weight prioritization for any role where the work arrives faster than it can be completed, which describes most jobs at a small business. The method set on this page covers the time management side, and the core and behavioral sets cover the judgment side.
Which roles should I ask prioritization questions for?
Ask them for any role where more work arrives than one person can finish, which at a small business is nearly every role. They matter most for office managers, operations and administrative roles, customer support, bookkeeping and finance, project coordinators, and any team lead who ranks work for other people. Weight the sets to the failure mode of the job. For back office roles the risk is quiet drift on a deadline nobody is watching, so weight method and communication. For frontline and customer facing roles the job is a stream of interrupts, so weight the situational scenarios. For anyone setting priorities for others, the manager set is not optional. Skip the sets that do not fit rather than asking all six.
How many prioritization questions should one interview include?
Four to six is usually right for a single interview, with real follow ups on each, rather than a long checklist answered shallowly. Depth beats breadth here, because the first answer is often rehearsed and the signal appears in the second and third follow up: what lost, who did you tell, what was the result, what would you do differently. Budget roughly fifteen to twenty minutes of a sixty minute interview for prioritization if the role depends on it heavily, less if it is one competency among several. Pick your questions in advance, write the follow ups down, and ask the same ones of every candidate so the answers are comparable. The sets on this page are sized so you can take two or three questions from each.
