Behavioral question
Tell me about a time you had to prioritize
Prioritization is a no. They want the list you were handed, the rule you used to cut it, who heard the no, and what happened to the thing you kept.
Check this example, then replace it
The box starts with one STAR answer. Read the scores, then delete it and paste a story from your own work. Scoring stays in the browser.
84/100
Solid
About 55 seconds spoken · 138 words. Spoken time uses 150 words per minute.
Feedback
- This has a clear STAR shape. Only keep numbers you can defend out loud.
Which sentence is which
In March 2023 the mobile team had 14 bug tickets before a store release and two days on the calendar. I was responsible for the release list. I sorted the tickets by whether the bug hit the signup path, kept 5, and wrote the other 9 into the next version’s notes. I then told support which 5 we were fixing so they could script replies for the rest. I dated that note and linked the 9 deferred tickets so the next owner did not have to reconstruct the cut. The result was the release going out on time, signup crashes down from 2.4% of sessions to 0.3%, and the other 9 bugs shipped two weeks later with no store rejection. Support used the note the same day, so we did not get a surprise ticket spike.
Why this example holds up
The rule is visible: signup path or not. You tell support, which is the stakeholder who feels a cut. Both the kept work and the delayed work have an ending.
How to answer “Tell me about a time you had to prioritize” with STAR
- Situation. Set the scene in one or two sentences: when it was and what was already wrong. For example: In March 2023 the mobile team had 14 bug tickets before a store release and two days on the calendar.
- Task. Say what you personally owned. For example: I was responsible for the release list.
- Action. Say what you did, in order, with I. For example: I sorted the tickets by whether the bug hit the signup path, kept 5, and wrote the other 9 into the next version’s notes.
- Result. End on the change, with a number you can defend. For example: The result was the release going out on time, signup crashes down from 2.4% of sessions to 0.3%, and the other 9 bugs shipped two weeks later with no store rejection.
Mistakes on this question
- Saying you “prioritized everything” by working harder. That is not a cut.
- A framework name (RICE, ICE) with no actual decision.
- Dropping work and never saying who was disappointed. Someone always is.
How to practice it
Force yourself to say the number you cut. “A few things” is how this answer stays fuzzy.
FAQ
What if my manager set the priority and I only executed?
Then it is not your prioritization story. Pick a time you made the cut, even on a small list.
Can I talk about personal time management?
Only if the tradeoff affected other people. A calendar hack is a weak version of this question.