Answer each story with a tight **STAR** structure (Situation, Task, Action, Result) and a short reflection at the end: what you learned and what you would repeat or change. Across all three, the interviewer is testing maturity — specificity, ownership, evidence, and follow-through — not heroics. ## 1) Constructive feedback **What interviewers look for:** empathy + clarity, evidence-based feedback (behavior, not character), and follow-through that produced a visible improvement. **Strong outline (STAR):** - **S:** A concrete collaboration problem (e.g., analysis reviews kept surfacing unclear assumptions, or a dashboard repeatedly shipped without metric definitions). - **T:** Improve quality/speed without damaging trust. - **A:** - Set intent and ask permission first ("I want to help us ship faster"); choose a private setting. - Be specific and behavior-focused ("the doc lacked metric definitions and edge cases"), not personal. - Make it two-way: listen, ask questions, understand constraints, and adapt. - Offer a concrete fix: a checklist/template, pair-review, or worked examples. - Close the loop: agree on next steps and re-review. - **R:** Measurable improvement (e.g., review iterations 3→1, fewer reported bugs, faster decisions, better stakeholder trust). **Good signal:** you improved the working relationship while still addressing the issue. **Bad signal:** vague "communication issues," sounding accusatory, focusing on being right, or no evidence the other person actually improved. ## 2) Pivoting to a change **What interviewers look for:** ability to re-scope under uncertainty, stay data-driven, and keep momentum and stakeholders aligned. **Strong outline (STAR):** - **S:** A mid-project shift where the original plan was reasonable but new information changed the decision (e.g., leadership reprioritizes from CTR to incremental conversions, an experiment result invalidates the hypothesis, a data source deprecates, or a market event hits). - **T:** Re-plan with minimal wasted work and protect the most important deliverables. - **A:** - Name the trigger signal clearly (experiment results, leadership reprioritization, technical blocker, business event). - Reconfirm the objective and success metrics. - Do a gap analysis: what work transfers vs. must be redone. - Propose options with explicit trade-offs (timeline, quality, risk). - Build an updated plan with milestones, owners, and decision checkpoints. - Communicate early — a one-pager aligning PM/Eng/stakeholders — and manage morale and ambiguity. - **R:** Delivered the revised outcome; stakeholders aligned; rework avoided (quantify: launch time saved, wasted effort reduced, metric outcome). **Good signal:** decisive but data-driven. **Bad signal:** the story sounds chaotic, or you changed direction without a clear rationale. ## 3) Conflict resolution **What interviewers look for:** professionalism, curiosity, and a focus on shared goals — disagreeing without becoming defensive, and knowing when to escalate. **Strong outline (STAR):** - **S:** A real disagreement with stakes, ideally cross-functional (e.g., Eng wants a quick heuristic; you want a statistically sound experiment), framed as a difference in goals/incentives/interpretation, not a personality clash. - **T:** Reach a decision without damaging the relationship. - **A:** - Start with a 1:1 to understand constraints (deadlines, reliability, user impact). - Restate the shared goal and clarify the decision criteria. - Bring evidence: a small prototype, backtest, user research, or risk assessment. - Offer a reversible compromise — phased rollout, guardrails/monitoring, or an A/B test — rather than trying to win the debate verbally. - Escalate only if needed, and neutrally, in an options-based way. - **R:** Decision made; conflict reduced; measurable outcome (on-time ship, fewer incidents, better metric) plus a positive relationship impact. **Good signal:** you can disagree productively and know when escalation is appropriate. **Bad signal:** "I escalated to my manager" as the main action, blaming the other party, avoiding the conflict, a story where you weren't the primary actor, or a "conflict" that was really a minor misunderstanding. --- ### Practical template for each answer - **Situation:** 2–3 sentences - **Task:** what you owned - **Action:** 3–5 concrete steps you took - **Result:** business outcome plus an interpersonal lesson ### How to make answers stand out - Include 1–2 concrete metrics (lift, error rate, review-cycle time, timeline saved). - Name the stakeholders (PM, Eng, Sales) and how you tailored your communication to each. - End reflectively: e.g., you now set expectations earlier, document decision criteria, or build feedback loops before tension develops. ### Common mistakes - Too much background and not enough action. - Vague claims without measurable outcomes. - Stories where you were not the primary actor. - Conflict stories that are actually minor misunderstandings. - Feedback stories with no evidence the other person improved.

All three prompts are behavioral STAR stories scored on the same rubric: pick a real, high-stakes example; own a clear role; take specific, evidence-based actions; and finish with a measurable result plus a reflection. Tailor depth to seniority — more emphasis on trade-offs, stakeholder alignment, and lessons learned for senior candidates.