Tell me about a technical debt decision you made.
- Technology:
- Behavioral
Quick answer
Explain why you accepted, reduced or paid down technical debt and how you managed the associated risk.
What the interviewer is evaluating
- Technical judgment
- Business awareness
- Risk management
How to structure your answer (STAR)
- Situation: debt and business context.
- Task: decide whether to take it.
- Action: risk analysis and mitigation.
- Result: delivery plus future plan.
Example answer
We needed to deliver a small feature quickly, but the existing module had an awkward abstraction that would have required a larger refactor.
I chose a contained implementation, documented the limitation and added tests around the boundary so future work would be safer.
We shipped on time and later replaced the abstraction when a second feature made the refactor economically worthwhile.
Discussion
Technical debt is not automatically bad. Interviewers want to see whether you understand its cost and deliberately manage it.
Describe the business constraint, the engineering risk and why the chosen approach was appropriate at that time.
Strong answers include a trigger or plan for addressing the debt instead of leaving it invisible.
Key points
- Identify the debt
- Understand its cost
- Make the trade-off explicit
- Create a follow-up trigger
Common mistakes
- Treating all technical debt as unacceptable.
- Taking debt without documenting the risk.
- Never returning to the debt.
Follow-up questions
- When would you refuse to accept the debt?
- How did you communicate the risk?