Amazon Behavioral Deep-Dive

# How to Approach These Prompts + Sample STAR Answers Use STAR to be concise and concrete: - Situation: One sentence of context (who, what, scale). - Task: Your specific responsibility and success criteria. - Action: What you did (decisions, tradeoffs, stakeholder mgmt). Use numbers, experiments, docs. - Result: Quantified outcomes and what you learned. Amazon nuances to weave in: - Customer Obsession and Working Backwards (start with customer, not feature). - Dive Deep with data; invent and simplify; bias for action (two-way doors). - Ownership, insist on highest standards, deliver results, earn trust. - Disagree and commit; write clear docs; set measurable bar-raisers. Template you can reuse: - S: [Where/when], [customer/business problem], [scale]. - T: I owned [scope] with a goal of [metric X by Y%/date]. - A: [Discovery] → [Decision/strategy] → [Execution] → [Change management]. - R: [Metric deltas], [customer impact], [follow-on decisions or learning]. --- ## 1) Introduce yourself and why this role is a fit - LPs: Customer Obsession, Ownership, Deliver Results - S: I’ve spent 6+ years as a PM across marketplace and B2B SaaS, building 0→1 and scaling 1→n products. - T: My focus has been turning ambiguous customer problems into measurable business outcomes. - A: Led cross-functional squads (eng/design/data/ops), worked backwards from PRDs and narratives, instrumented north-star metrics, and used experiments to de-risk bets. - R: Shipped features that lifted conversion 8–15%, reduced churn 3–6 pts, and cut costs 10–20%. This role is a fit because it values customer obsession, bar-raising execution at scale, writing and analytics rigor, and operating in ambiguity—areas where I’ve delivered repeatedly. ## 2) Used customer data to generate insight - LPs: Dive Deep, Customer Obsession - S: At a mid-size marketplace, growth was plateauing despite steady traffic. - T: I owned activation and retention; goal: +10% 30-day retention. - A: - Analyzed cohorts and funnels; found users who completed 3 actions within 48 hours retained 2.1×. - Instrumented missing events; ran interviews to validate friction points. - Built an onboarding “Quick Start” wizard to nudge those 3 actions; A/B tested with guardrails. - R: 30-day retention +18%, first-week engagement +22%, 90-day revenue +9%. We reset the activation KPI around those 3 actions. ## 3) Created a new performance metric - LPs: Are Right, A Lot; Insist on the Highest Standards - S: Teams optimized for short-term conversion, but LTV was uneven. - T: Define a metric that predicted long-term value for roadmap prioritization. - A: - Paired with data science to design Time to First Value (TTFV): median days to a user’s first meaningful outcome. - Formula: TTFV = median(time(First Value Event) − time(Signup)). - Socialized via a 1-pager; set targets per segment; added to weekly business review. - R: TTFV dropped 32% in 2 quarters; 90-day retention +11%; roadmap shifted toward features with higher LTV impact. ## 4) Not enough data—how I proceeded - LPs: Bias for Action, Dive Deep, Frugality - S: We considered a new payment option in a region with little history. - T: Decide whether to invest without robust data. - A: - Triangulated proxies (search interest, competitor support, partner quotes) and ran 15 customer calls. - Launched a two-way-door pilot to 10% traffic with tight guardrails (error, fraud, CSAT thresholds). - Instrumented event-level tracking; pre-defined stop/expand criteria. - R: Pilot showed +7% conversion at acceptable risk; we expanded to 50% in 3 weeks and full in 6, adding ~4% total conversion lift. ## 5) Idea pitched, initially turned down - LPs: Earn Trust, Have Backbone; Disagree and Commit - S: I proposed a loyalty bundle (free returns + expedited shipping); finance worried about margins. - T: Validate the idea without major cost. - A: - Built a quasi-experiment: targeted offer to a matched cohort; sized margin impact; modeled payback. - Shared a 2-page narrative with scenarios and a kill-switch plan. - R: Test cohort LTV +14%, NPS +12 pts, net margin +2 pts. My manager greenlit a scaled pilot; we rolled out in two phases. ## 6) Earned trust of a resistant team - LPs: Earn Trust, Dive Deep - S: Platform team pushed back on an eventing overhaul they saw as risky. - T: Align on a safe, feasible path. - A: - Held a design review to surface risks; co-authored an RFC with eng. - De-scoped to a phased migration with backward compatibility and canary rollouts. - Took operational ownership (dashboards, on-call runbooks). - R: Shipped with zero Sev-1s; data completeness 98%→99.9%; later became a reference for other teams. ## 7) Conflicting team goals - LPs: Think Big, Deliver Results - S: Growth wanted homepage promos; Search Relevance flagged quality risk. - T: Resolve prioritization conflict. - A: - Defined a joint metric: net query success = CTR × post-click engagement × order rate. - Limited promos to low-ambiguity intents; tuned ranking to discount promos for exploratory queries. - Aligned in a doc with experiment design and stop-loss thresholds. - R: Orders +5% with no relevance regression; both teams hit quarterly goals. ## 8) Gathered feedback and drove change - LPs: Earn Trust, Insist on the Highest Standards - S: Stakeholders felt we were a “feature factory.” - T: Improve perceived partnership and outcomes. - A: - Ran a lightweight 360 survey and stakeholder interviews; top themes: unclear problem statements, opaque priority changes. - Introduced a one-pager template (customer problem, success metric, alt options, launch criteria) and monthly roadmap reviews. - R: Stakeholder satisfaction +24 pts; defect rate −30%; on-time delivery +18 pts in two quarters. ## 9) About to miss a deadline / mid-project setback - LPs: Ownership, Deliver Results - S: A key vendor API change threatened a critical launch (T−3 weeks). - T: Protect the business-critical outcome. - A: - Triage: split scope into must/should; re-planned with daily war-room standups. - Negotiated a grace period with the vendor; built a fallback path with minimal functionality. - Escalated early; aligned leadership on adjusted success criteria. - R: Hit the public launch date with must-haves; shipped remainder 2 weeks later; customer defect rate <0.3% vs 1% target. ## 10) Invent, simplify, deliver fast, scale later - LPs: Invent and Simplify, Bias for Action - S: Returns processing was slow and costly. - T: Reduce cost/time to refund without degrading fraud controls. - A: - V1: simple rules engine for instant refunds on low-risk items; self-serve flows; no ML initially. - After proving value, V2: trained a risk model and integrated with carriers. - R: V1 in 6 weeks cut refund time 5→1 days and contact rate −28%; V2 reduced returns cost −18% and increased repeat rate +6%. ## 11) Calculated risk—one success, one failure - LPs: Bias for Action, Learn and Be Curious - Success: - S/T: Reduced checkout friction; tested a one-tap “Buy Now.” - A: Guardrailed experiment with AOV caps and fraud checks. - R: Conversion +4.1%, mobile NPS +6 pts; rolled out. - Failure: - S/T: Gated advanced search behind an account wall to improve data quality. - A: Launched to 50% traffic; monitored bounce and retention. - R: Bounce +9 pts, retention −3 pts; rolled back in 48 hours. Lesson: do not gate core discovery; use progressive profiling instead. ## 12) Difficult customer situation - LPs: Customer Obsession, Earn Trust - S: A top seller had a misrouting bug causing order delays. - T: Resolve fast and restore trust. - A: - Spun up a cross-functional war room; hotfix in 24 hours; manual reroutes for impacted orders. - Proactively communicated root cause and prevention; offered fee credits. - R: On-time rate restored to 98.7% within 72 hours; churn averted; seller later joined a beta program. ## 13) Disagreed with manager - LPs: Have Backbone; Disagree and Commit - S: Manager wanted to ship a feature before instrumentation to hit a date. - T: Advocate for data quality without slipping the schedule. - A: - Presented a 1-pager on risks and a plan to add minimal critical telemetry within the same sprint. - We agreed on a 2-day slip to include must-have events. - R: Post-launch analysis avoided a misattribution; the feature needed iteration. We shipped a patch in a week; I committed to the final plan after the decision. ## 14) Most innovative thing built - LPs: Think Big, Invent and Simplify - S: Delivery ETA accuracy drove CSAT; ours underperformed. - T: Improve ETA accuracy significantly. - A: - Combined carrier feeds, historical route variability, and weather into a lightweight predictive model. - Wrapped it in a simple service with clear fallback logic; wrote a PRD and ops playbook. - R: ETA error down 28%, WISMO contacts −19%, CSAT +7 pts. The approach scaled to other regions with minor tuning. ## 15) Remotely influenced stakeholders - LPs: Earn Trust, Ownership - S: Payments team in another region owned APIs we needed; time zones and priorities misaligned. - T: Secure their commitment without hard authority. - A: - Wrote a clear narrative (customer impact, ROI, lift for them); included a RACI and success metrics. - Scheduled async reviews, recorded Loom walkthroughs, and adapted to their sprint cadence. - Offered to contribute our engineer for the integration. - R: Secured a 2-sprint commitment; integration unblocked in 4 weeks; feature shipped on plan. ## 16) Strengths and weakness - LPs: Ownership, Customer Obsession, Dive Deep - Strengths: Working backwards from the customer; crisp problem framing and writing; data-driven prioritization; calm, iterative execution that delivers measurable outcomes. - Weakness: I can over-index on speed early in ambiguous spaces. I now front-load alignment with a short narrative and pre-commit success metrics, which reduced late rework by ~30% on my last two projects. Still improving by scheduling explicit “alignment checks” before build. ## 17) Coaching or training a team member - LPs: Hire and Develop the Best - S: An APM’s specs were solution-led and missed success criteria. - T: Raise their bar on problem definition and metrics. - A: - Introduced a one-page template (customer, problem, options, metrics, risks) and weekly doc reviews. - Shadowed their customer calls; gave tactical feedback and examples. - R: Their next spec led to a feature with +6% activation; they shipped on time and started mentoring a new hire. ## 18) Disappointed a team member and addressed it - LPs: Earn Trust, Ownership - S: I reassigned a feature without explaining the reasoning; the engineer felt sidelined. - T: Repair trust and set a better process. - A: - 1:1 to listen; apologized for the poor communication; shared constraints (compliance expertise needed). - Created a transparent assignment rubric and added them as tech lead on the next related project. - R: Relationship recovered; team eNPS improved; the engineer led the next launch successfully. --- ## Validation Checklist Before the Interview - Each story is 60–90 seconds spoken with clear STAR. - Outcomes quantified (baseline, delta, timeline) and tied to a business/customer impact. - Leadership Principles explicitly demonstrated. - Includes tradeoffs, risks, and what you’d do differently. - Ready to dive deep with data and operational details if asked. Tip: Keep a 1-pager per story with metrics, dates, team size, and your unique contribution so you can dive deep under follow-up questions.