Treat debt as a business cost rather than a moral issue. Quantify it: how much slower does it make delivery, how many incidents does it cause, what happens if it fails. Then fund it in the same conversation as features, either as a standing allocation (often fifteen to twenty percent) or attached to roadmap work touching that area. Pay down the debt that is actually charging interest, not the code you dislike.
Why interviewers ask this
Interviewers want a manager who can argue for engineering health in business terms, rather than surrendering to feature pressure or hoarding refactor time. They listen for prioritization within the debt itself, since not all of it is worth paying, and for how you make the cost visible to product and executive stakeholders. Concrete numbers in your answer are what make it credible.
How to structure your answer
- Reframe debt as measurable cost and risk, not tidiness.
- Prioritize the debt charging the highest interest.
- State how you fund it: standing allocation or attached to feature work.
- Explain how you make the tradeoff visible to stakeholders.
Example answer
I refuse to run it as a separate moral argument, because engineering always loses that one. I make it a cost conversation. We keep a debt register with an estimate of what each item costs us: this service adds two days to every feature that touches it, that one caused four of the last ten incidents, this dependency goes out of support in nine months and blocks a compliance renewal. Then I prioritize by interest rate rather than by how ugly the code is, because plenty of horrible code is stable and untouched and can stay that way forever. On funding, my default is a standing twenty percent plus cleanup attached to roadmap work, so if we are already in that area we fix it while we are there. The argument that lands with product is always the delivery one. On my last team I could show that two thirds of our incident time came from one legacy path, and once it was framed as we lose a week a month to this, the six week fix was an easy sell rather than a fight.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- How do you handle a stakeholder who wants that twenty percent back this quarter?
- How do you stop a refactor from turning into a rewrite?
- Which debt would you deliberately never pay down?
Related engineering manager questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions