Behavioral question
You are a senior PM for a data product. How would you prioritize requirements between top customer requests, technical debt of previously delivered features, and partner team requirements for critical integration?
- Uber
- Behavioral
- Hard
Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.
Start a mock interview on this question · Mock interview from a job description
What this question tests
Prioritization framework under competing, legitimate stakeholder demands with no single obvious answer.
How to approach it
- Situation: describe a real data product with concurrent pressure from top customer requests, technical debt, and a partner integration deadline.
- Task: state your goal, deciding what ships next without simply picking whichever stakeholder is loudest.
- Action: describe the framework used, for example scoring each item on customer impact, risk of inaction, and effort, rather than gut feel.
- Action: explain how you communicated the trade off, for example the partner integration was time boxed and had a hard external deadline, so it took priority, with technical debt scheduled next sprint.
- Result: state the outcome, such as the partner deadline was met, and technical debt was addressed the following cycle with a visible plan shared with the team.
- Reflect on the lesson, like building a lightweight scoring rubric to avoid re-litigating priority calls stakeholder by stakeholder.
What a strong answer includes
- Uses a concrete prioritization framework, like impact versus effort versus risk of inaction, rather than describing a gut call.
- Explains the actual trade off made and why, not just that a decision was made.
- Shows how the deprioritized stakeholders, like the technical debt owners, were kept informed with a plan, not ignored.
- Names a specific result with a timeframe, like meeting a hard partner deadline while still addressing debt the next cycle.
Common mistakes
- Describing prioritization as always favoring the customer without acknowledging technical debt has real cost if ignored.
- Giving a vague answer with no explicit framework or criteria used to decide.
Likely follow-up questions
- How do you decide when technical debt becomes urgent enough to jump the queue?
- How would you handle it if the partner team disagreed with being deprioritized?
More behavioral questions
- How do you know when to cut corners to get a product out the door?Shopify · Behavioral · Medium
- Your Engineering Manager wants to work on a new feature and you absolutely have no bandwidth. How will you handle it?PayPal · Behavioral · Medium
- Suppose a stakeholder wants you to add a new feature to your roadmap and you think that it should not be implemented. How would you convince them to drop it?Lyft · Behavioral · Medium
- Tell me about a time you had to change a KPI.Uber · Behavioral · Easy
- You need to pitch a new feature to executives and stakeholders. How would you do it?Uber · Behavioral · Medium
- What are the key components of a PRD?Uber · Behavioral · Easy
More questions from Uber
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 13: Lead the room: staff moves, forward-deployed PM, and the portfolio
- Chapter 14: Get the job: the AI PM interview loop