Behavioral question

What do you do when you get a vague feature request?

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

Practical process for turning ambiguity into a scoped, actionable requirement.

Start by asking who requested it and what underlying problem or goal they're trying to solve, not just the literal ask.
Gather context: what triggered the request, like a customer complaint or a competitor comparison.
Translate the vague ask into a specific user problem statement before considering any solution.
Check feasibility and scope with engineering early, rather than committing to a timeline blind.
Propose a scoped version back to the requester for confirmation before starting real work.

Leads with asking why, uncovering the underlying goal rather than accepting the vague request at face value.
Distinguishes gathering context from jumping straight to a solution, showing discipline under ambiguity.
Loops in engineering early for a feasibility gut check before committing to any scope or timeline.
Closes the loop by confirming the scoped interpretation with the original requester before building.

Starting to build immediately based on a literal, unclarified reading of the request.
Never circling back to confirm the interpreted scope with the original requester.

What do you do if the requester is not available to clarify?
How do you handle it if the underlying goal changes after you've started building?