Your question is Managing Technical Debt at Scale. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
You are advising a company whose product is growing, but the engineering team is spending more time on bugs, slow releases, and brittle systems. Leadership wants a clear way to think about technical debt without freezing product progress.
How do you think about technical debt in the context of a growing product?
The team needs to keep shipping while avoiding a future slowdown. The answer should show how to decide which debt to fix now, which debt to accept, and how to make that choice repeatable.