Behavioral question

How do you say no to feature ideas or requests?

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

Prioritization philosophy and the ability to decline requests professionally while maintaining stakeholder trust.

State your framework: evaluate requests against strategy, user value evidence, and cost, rather than reacting emotionally to each ask.
Explain how you communicate a no: acknowledge the request's intent, explain the tradeoff clearly, and offer an alternative if one exists.
Give a concrete example: a feature request that did not align with the current quarter's priority and how you explained that.
Describe following up with a record, such as adding it to a backlog with a clear reason for deferral, so it is not lost.
Address relationship management: how you keep the requester feeling heard even when the answer is no.
Close with the outcome, such as a maintained relationship and the requester later agreeing the priority call was right.

Gives a concrete framework, strategy fit plus evidence plus cost, rather than a vague 'I use my judgment' answer.
Uses a specific real example instead of a purely hypothetical or generic description of saying no.
Shows how the requester was kept engaged, such as documenting the idea for later, avoiding a dismissive no.
Demonstrates the relationship survived or improved, showing this is a repeatable, trust building skill.

Giving a vague answer with no concrete framework or specific example.
Describing a purely dismissive no with no acknowledgment of the requester's underlying need.
No mention of how the declined idea is tracked or revisited later.

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