Strategy question

How would you define tech debt?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Tests conceptual clarity on a commonly misused term, and whether the candidate can distinguish it from simple bugs.

Define it precisely: the implied cost of a faster, less robust solution now, to be paid back later.
Distinguish it from a bug: debt is a known, intentional trade-off, a bug is an unintended defect.
Give an example: skipping automated test coverage to hit a launch date, knowing it slows future changes.
Explain why it matters to a PM: it affects future velocity and risk, changing what you can promise on the roadmap.
Note debt isn't purely a red flag; it's often rational under time or certainty constraints.

Gives a precise definition that distinguishes debt from bugs or poor code quality generally.
Uses a concrete, realistic example instead of an abstract one.
Connects the definition to PM-relevant consequences, future velocity and roadmap risk.

Chapters of the AI PM course that teach what this question tests.