How do you prioritize when you have multiple competing requests or projects?
Prioritization for data roles comes down to three inputs: business impact, stakeholder urgency, and the actual effort required. Strong candidates describe a repeatable system — not just 'I talk to my manager' — and give a concrete example of a tradeoff they made and why.
How to think about it
What the interviewer is actually testing
Data teams receive more requests than they can fulfill, and a practitioner without a prioritization system creates chaos — saying yes to everyone, finishing nothing well, or invisibly dropping the highest-value work. Interviewers want to see that you operate with deliberate judgment, communicate proactively about tradeoffs, and influence which work gets done rather than just executing whatever lands in your queue.
How to structure a strong answer
Describe your framework first. A concrete system signals maturity. Good frameworks consider:
- Business impact: does this move a metric that matters to the company right now?
- Reversibility: is this decision time-sensitive or can it wait a week without real cost?
- Effort-to-impact ratio: a two-hour query that unblocks a VP beats a two-week model that informs a low-stakes dashboard
- Dependencies: does another team’s work stall if you don’t ship this?
Give a real example. Abstract frameworks without evidence sound rehearsed. Describe a week or quarter when you had more requests than time and walk through the call you made. Who did you push back to? What did you deprioritize and why?
Show that you communicate the tradeoff. Prioritizing silently is only half the job. The other half is making the choice visible: “I told the analytics manager that I could deliver the cohort analysis this week or the attribution model — not both — and asked which had higher deadline pressure.”
Close with the outcome. Did the prioritized work land well? Did deprioritizing something cause a problem you could have avoided? Honest reflection is more credible than a perfect story.