Behavioral question

Tell me about a time you took an ambiguous enterprise customer request and turned it into a clear product decision that balanced speed, custom work, and long-term repeatability. How did you align the customer, engineering, and leadership, and what tradeoff did you make?

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

Start a mock interview on this question · Mock interview from a job description

What this question tests

A behavioral question testing the ability to convert an ambiguous, high-stakes enterprise request into a scoped, repeatable product decision.

How to approach it

  1. Situation: a real ambiguous enterprise request where speed, custom work, and long-term repeatability were all in tension.
  2. Task: state what was actually ambiguous, for example the customer describing a business outcome without a specific technical ask.
  3. Action: describe how the ambiguity was resolved, through structured discovery questions that translated the outcome into a concrete, scoped technical requirement.
  4. Action: describe the tradeoff decision made, for example a configurable feature instead of a hardcoded custom build, to preserve repeatability without missing the customer's timeline.
  5. Action: describe how the customer, engineering, and leadership were each brought to agreement, and what concern each group raised.
  6. Result: state the outcome for the customer and whether the solution was reused elsewhere afterward.

What a strong answer includes

Common mistakes

Likely follow-up questions

More behavioral questions

More questions from Harvey

Learn the skill behind it

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

Preparing for a specific role?

Book summaries for this kind of question

Browse all 4,000+ questions in the bank