Behavioral question

How do you define a good PM vs. a bad PM?

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

Self awareness and judgment about what makes product management effective, grounded in specifics rather than platitudes.

State a clear point of view: a good PM makes decisions with incomplete data and owns the outcome, a bad PM avoids decisions or blames others.
Give a concrete behavior of a good PM, such as talking to users directly instead of relying only on secondhand research.
Give a concrete behavior of a bad PM, such as chasing every stakeholder request without prioritizing against a clear strategy.
Contrast how each handles conflict, a good PM surfaces disagreement early, a bad PM avoids it until it becomes a crisis.
Tie the definition back to outcomes: good PMs ship things that move a metric and are trusted by their team.
Keep the answer grounded in specific behaviors rather than abstract adjectives like 'visionary' or 'strategic'.

Uses concrete, observable behaviors, like talking to users directly, rather than abstract traits like 'visionary' or 'passionate'.
Contrasts good and bad on the same dimension, decision making under uncertainty, giving the answer clear structure.
Ties the definition to team trust and outcomes, showing the interviewer this is grounded in real working experience.
Avoids generic buzzwords and instead names specific, checkable actions an interviewer could verify with a reference.

Giving a list of abstract adjectives (visionary, strategic, empathetic) with no concrete behavior behind them.
Only describing what a bad PM does without a clear contrast to what a good PM does instead.
Sounding like a generic textbook answer with no personal conviction or example.

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