Resolve Product Disagreement and Balance Technical Debt

Answer the following questions about collaboration and engineering judgment. Use real experience where possible, and make your own role and reasoning clear. ### Part 1 — Resolve a serious disagreement with a product manager Describe a time you and a product manager strongly disagreed about product direction or technical implementation. How did you communicate and reach agreement? #### What This Part Should Cover - The shared objective and the different concerns behind the disagreement. - Evidence, alternatives, and the decision process. - The outcome and effect on the working relationship. ### Part 2 — Balance a deadline with technical debt A project has an urgent deadline, but technical debt is substantially slowing development. How would you balance business delivery with code quality? #### What This Part Should Cover - Which debt must be addressed to deliver safely and which work can be deferred. - Scope, sequencing, verification, and explicit ownership of remaining debt. ### What a Strong Answer Covers - Respect for product needs and technical constraints without assuming either side is automatically right. - Specific actions and tradeoffs supported by evidence. - A practical delivery decision with visible consequences and follow-through. ### Follow-up Questions - What would you do if the product manager remained unconvinced after seeing your evidence? - How would you prevent deferred debt from becoming an unowned promise after launch?