Project Context
You are the program manager embedded in ShopSwift, a high-volume e-commerce marketplace (~18M monthly active users, ~220K orders/day peak). The company’s checkout is a legacy flow built over 5 years with inconsistent behavior across Web and iOS. Leadership has approved a new feature called One-Click Pay (stored card + shipping address + instant confirmation) to reduce checkout friction and defend against competitors who already offer one-tap checkout.
The business stakes are high: Checkout drives ~$1.4B GMV/quarter. Growth forecasts assume a +1.0% absolute conversion lift within 60 days of launch. However, the current checkout has fragile integrations with tax, fraud, and payment processors. A regression that drops conversion by even 0.3% for a week would be escalated to the CEO. Additionally, because One-Click Pay stores payment credentials, you must meet PCI requirements and internal security standards.
The cross-functional team is small and stretched:
| Function | Headcount | Notes |
|---|
| Backend Eng (Payments + Orders) | 5 | 2 are also on on-call rotation for incidents |
| Web Eng | 2 | Shared with a site performance initiative |
| iOS Eng | 2 | One is new to the codebase (3 weeks) |
| QA | 1 | Owns automation framework but coverage is incomplete |
| Design | 1 | Also supporting a rebrand project |
| Data Science/Analytics | 1 | Can build dashboards + experiment readouts |
| Security/Compliance | 1 | Part-time; also handling annual PCI audit prep |
You have 8 weeks to ship an MVP to 10% of US traffic with a clear path to ramp. The VP of Growth wants it live before a major marketing campaign already booked for Week 9.
Stakeholder Landscape
- VP of Growth: Wants the fastest possible launch and is pushing to cut “edge cases.” Measures success by conversion lift and speed-to-market.
- Director of Payments Engineering: Accountable for payment success rate and chargebacks; will block launch if rollback/monitoring is weak.
- Security & Compliance Lead: Conservative; requires strong acceptance criteria around tokenization, data retention, and audit logging.
- Customer Support (CS) Manager: Worried about increased contacts if order confirmation, refunds, or address changes behave differently.
- Design Lead: Wants a consistent UX across Web and iOS; concerned that rushing will create long-term inconsistency.
These stakeholders disagree on what “done” means. Your job is to drive alignment by translating ambiguous requirements into high-quality user stories and acceptance criteria that engineering and QA can execute against.
Constraints
- Timeline: 8 weeks to MVP (10% US traffic), with a decision gate in Week 6.
- No additional headcount approved; at most $60K for contractors/tools.
- Reliability: Checkout uptime must remain ≥ 99.95%; payment authorization success must remain ≥ 98.8%.
- Experimentation: Must run behind a feature flag and be measurable via A/B test; analytics engineer has capacity for one major dashboard.
- Compliance: Must not store raw PAN; must use existing token vault; must log consent and allow deletion per policy.
- Dependencies:
- Fraud service team can only deliver a new risk signal in Week 5.
- Tax service has a planned migration in Weeks 3–4, increasing incident risk.
Deliverables (What you must produce in the interview)
- A set of user stories for One-Click Pay MVP (at least 6–10) spanning happy path + critical edge cases.
- Acceptance criteria for 3 of the most complex stories, written so QA can test and engineering can implement unambiguously.
- A prioritization and trade-off proposal: what is in MVP vs deferred, and why.
- A launch plan including feature flags, rollout stages, monitoring, and rollback criteria.
- A plan for stakeholder alignment: how you will get sign-off on stories/AC and prevent last-minute scope churn.
Complications (Realistic curveballs)
- Mid-sprint scope change: In Week 2, the VP of Growth insists One-Click Pay must support promo codes at launch because a partner campaign depends on it. Engineering says promo code logic is the #1 source of checkout bugs.
- Resource disruption: In Week 4, the QA lead is pulled into a P0 incident for 5 days, reducing test capacity right when integration testing should ramp.
- Platform inconsistency: iOS wants to ship a native “slide to confirm” interaction; Web wants a standard button. Design can’t support two bespoke flows long-term.
In your response, focus on how you create crisp stories and acceptance criteria that drive execution, reduce rework, and enable a safe launch under tight constraints. Be explicit about how you handle ambiguity, negotiate trade-offs, and define “done” across engineering, design, analytics, and compliance.
