Owning a Shortcut That Became Tech Debt and the Options You Weighed

Tell me about a time you introduced technical debt. What were the consequences, and what other options did you have when you made that decision? ```hint Show the fork in the road Describe the moment of decision as a real choice among options, including the one you picked, so the interviewer can judge whether the debt was deliberate and whether you would choose it again. ``` ### Clarifying Questions - As a PM, does it count if engineers wrote the code but the shortcut came from my scope or deadline decision? - Should the debt be a shortcut taken on purpose, or can it be one the team only recognized afterward? - Can it be product debt, such as a manual workaround or an inconsistent user flow, rather than debt in the code? ### What a Strong Answer Covers - Clear ownership of the decision that created the debt, without shifting blame to engineering - The options that existed at the time and the reasoning that led to the one chosen - Concrete consequences, both the benefit gained and the cost paid later by customers and the team - How the debt was repaid or contained, and the habit or mechanism the candidate now uses to manage debt ### Follow-up Questions - Knowing how it turned out, would you make the same decision today? - How did you get the team to prioritize repaying the debt over new feature work? - How do you tell debt worth taking on from a shortcut that will hurt you later?