Handle PM Ambiguity and Drive Outcomes
YelpData Scientist · OnsiteLast updated
This question evaluates leadership, stakeholder management, and incident response competencies within a data science context, including the ability to define measurable success metrics, negotiate scope under ambiguity, and make data-driven decisions during product regressions.
Tell me about a time a PM dominated a discussion with ambiguous goals and you had to drive clarity and execution: how did you define measurable success metrics, negotiate scope and trade-offs, and align stakeholders under time pressure? Then consider this scenario: DAU drops 20% within 24 hours after a UI change; the PM wants to revert immediately. Outline a 48-hour plan including what data you would pull first (and from where), fast checks to rule out instrumentation issues, a minimal rollback vs. forward-fix decision framework with explicit thresholds, a quick experiment or holdback design to validate causality, communication to execs and support, and a postmortem plan to prevent recurrence.
Solution walkthrough is for members
Get the full walkthrough with reference code and complexity analysis, plus Kitty Coach at 300 messages a day. Hints, the code runner and community answers stay free.