How a PM Decides When to Pay Down Tech Debt Versus Ship New Features
Company: Uber
Role: Product Manager
Category: Product / Decision Making
Difficulty: medium
Interview Round: Other
How do you decide between spending engineering time on paying down tech debt and spending it on shipping new products or features? Walk through how you weigh the two.
```hint Price the debt
Ask what the debt is costing right now and who pays for it: customers, engineers, or the roadmap you are about to build.
```
### Clarifying Questions
- Is this about a product area you own end to end, or a shared platform that other teams build on?
- Does the interviewer want your general approach, a specific decision from your past work, or both?
- Is the debt in question causing visible customer problems today, or mainly slowing engineering down?
### What a Strong Answer Covers
- A way to put tech debt and feature work on comparable terms instead of treating debt as a gut call.
- How the balance shifts with context: product maturity, scale, and reliability or regulatory exposure.
- A repeatable mechanism agreed with engineering, rather than a fresh negotiation every planning cycle.
- How the choice is explained to stakeholders who see only features.
- A real example where the candidate accepted a cost to make the call, and what happened.
### Follow-up Questions
- Your engineering lead wants to pause features for a quarter to rewrite a core service, while sales has promised a large customer a feature this quarter. What do you do?
- After a debt paydown ships, how do you tell whether it was worth it?
- When would you deliberately take on new tech debt?
Overview: A product manager is asked how they weigh engineering time spent paying down tech debt against time spent shipping new products and features. It tests making both kinds of work comparable, setting a repeatable mechanism with engineering, adjusting to context, and supporting the approach with a real example.