## How to answer (high-signal behavioral rubric) Use **STAR** with an added “**Why**” and “**Metrics**” layer: - **S (Situation):** One sentence of context (team, goal, constraints). - **T (Task):** Your responsibility and what “success” meant. - **A (Action):** 3–6 concrete actions you personally took. - **R (Result):** Quantified impact + what you learned. - **Why/Tradeoffs:** Explain the decision logic (what you optimized for). Aim to show: (1) calm under change, (2) clear prioritization, (3) proactive communication, (4) risk management, (5) delivery focus. --- ## 1) Priority change — strong answer structure **What interviewers are probing** - Do you re-plan quickly and align with stakeholders? - Do you protect the most valuable work and cut scope appropriately? - Do you avoid thrash by clarifying the new “north star”? **Suggested flow (STAR)** 1. **S:** Project was mid-flight; new company or product priority emerged. 2. **T:** You needed to adjust plan while minimizing wasted work. 3. **A:** - **Clarify the new goal:** “What decision will this enable?” “What metric matters now?” - **Re-prioritize using a framework:** impact vs effort, or RICE/ICE; separate must-have vs nice-to-have. - **Create an updated plan:** new milestones, revised scope, explicit de-scopes. - **Communicate early:** share tradeoffs, what will slip, and what will still ship. - **Preserve reusable work:** refactor analysis/code so prior work isn’t fully lost. 4. **R:** Report outcome with metrics (time saved, revenue impact, latency reduction, experiment shipped) and a process improvement (e.g., weekly alignment, decision log). **Pitfalls to avoid** - Complaining about leadership or “random changes.” - Saying you “just did what I was told” without describing prioritization. - No measurable outcome. --- ## 2) Initial requirements change — strong answer structure **What interviewers are probing** - Can you handle ambiguity and evolving requirements without getting stuck? - Do you validate assumptions early? **Suggested actions to highlight** - **Detect change early:** regular check-ins, early prototypes, “requirements readback.” - **Document assumptions:** what data is needed, what definition of success is used. - **Version the plan:** “Plan A / Plan B” with clear triggers. - **Negotiate scope:** adjust deliverables (MVP first), add follow-up phase. - **Align on acceptance criteria:** what counts as “done,” and what quality bar. **Example of measurable results (you can adapt)** - “Shipped an MVP dashboard in 1 week, then added segmentation the following sprint; reduced stakeholder back-and-forth by 30%.” --- ## 3) Meet a deadline with incomplete information — strong answer structure **What interviewers are probing** - Judgment under uncertainty: do you make reversible decisions? - Communication: do you escalate and set expectations? - Risk management: do you protect quality while moving fast? **A high-quality approach** 1. **Clarify what’s unknown:** list missing inputs (requirements, data fields, labels, access). 2. **Define minimum viable deliverable (MVD):** what can be delivered that is still useful. 3. **Timebox discovery:** e.g., “2 hours to validate data availability; 1 day to prototype.” 4. **Make assumptions explicit:** write them down and get quick sign-off. 5. **Create parallel tracks:** while waiting for info, build reusable scaffolding (ETL, metrics definitions, baseline model, dashboard skeleton). 6. **Escalate with options, not problems:** - Option A: deliver MVP by deadline with caveats. - Option B: delay by X days for higher confidence. - Option C: reduce scope (drop segment Y). 7. **Add guardrails/QA:** sanity checks, reconciliation against known totals, backtests where possible. 8. **Post-mortem:** improve intake process, add a checklist, automate data validation. **Common pitfalls** - Hiding uncertainty until the last minute. - Overpromising instead of offering scoped options. - Delivering something “on time” but unusable due to missing validation. --- ## What to prepare before interviews (quick checklist) - 1 story where **priorities changed** (re-plan + stakeholder alignment). - 1 story where **requirements changed** (assumptions + iteration). - 1 story where you **delivered under ambiguity** (MVP + risk management). For each: have **numbers** (time, $$, adoption, accuracy, latency, hours saved) and a clear “what I learned.”