Your question is Build a Feature From Ambiguous Requirements. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
You've been asked to build a new product feature, but the initial request is vague and different stakeholders are using broad language like "make it easier," "support enterprise needs," or "improve the workflow." There is clear interest in shipping something soon, but the problem definition, success criteria, and must-have scope are not yet well defined.
Tell me about a time you had to build a feature with very vague requirements. How did you turn ambiguity into an execution plan, manage scope and stakeholder expectations, and make trade-offs to get something shipped?