How do you manage technical debt on a team that is always under delivery pressure?

Summary

Make debt visible in a register with its cost and 'interest', prioritise debt in code you change often or that causes incidents, protect a steady budget (often 15–20% per sprint) instead of rare clean-up sprints, and report results in product terms.

Longer Answer

Clean-up sprints get cancelled when launches arrive; a steady budget survives. Bundle paydown into features that touch debt hotspots. Leave stable, rarely touched code alone. Distinguish deliberate, prudent debt — a conscious trade-off with a payback plan — from reckless debt. Show product numbers they can weigh: "test suite 25 to 9 minutes saves six engineer-hours a day", "refund changes now take two days instead of five".

Key Points

• Debt register with impact and interest
• Steady 15–20% budget; bundle with features
• Report outcomes in product terms

Deep dive: Managing Technical Debt Deliberately

What interviewers look for

Business framing of debt, prioritisation by impact, and a sustainable mechanism.

Red flags

• 'We need a rewrite'
• Debt work only when there is spare time