Project Context
You are the program manager for ShopHub, a global e-commerce marketplace with 38M monthly active users and peak traffic of 120k requests/min during promotions. ShopHub is rolling out “1-Tap Checkout”, a new checkout experience that reduces steps from 5 screens to 2 and introduces tokenized card storage plus address autofill. The feature must launch on Web, iOS, and Android with consistent behavior because marketing plans a single global campaign.
The business goal is to increase conversion and reduce checkout drop-off. Finance estimates a 0.6% absolute conversion lift would translate to ~$18M incremental quarterly revenue. However, the feature touches payments and PII, so the launch must meet PCI requirements and internal privacy standards. Leadership is willing to accept a phased rollout by platform only if the customer experience remains coherent and support burden is controlled.
The cross-functional team is distributed across Seattle and Dublin:
| Function | Team | Notes |
|---|
| Web engineering | 6 engineers | Owns web checkout, feature flags, and experimentation framework |
| iOS engineering | 4 engineers | Release trains every 2 weeks; App Store review adds variability |
| Android engineering | 4 engineers | Faster release cadence but device fragmentation increases QA needs |
| Backend payments | 5 engineers | Owns tokenization, order creation, risk checks; also on-call for incidents |
| Design | 1 lead + 1 content designer | Must ensure parity and accessibility across platforms |
| QA | 1 QA lead + 3 SDETs | Limited automation coverage on mobile flows |
| Legal/Privacy | 1 counsel + 1 privacy analyst | Requires DPIA sign-off before GA |
| Customer Support Ops | 1 manager | Needs macros, training, and escalation paths |
Stakeholder Landscape (Competing Priorities)
- VP Growth Marketing wants a single launch date in 8 weeks to align with a major seasonal campaign and influencer partnerships.
- Head of Payments Engineering is concerned about stability: the backend team is already carrying a 25% on-call load due to fraud spikes and does not want a risky launch during a high-traffic period.
- Mobile PM wants to avoid shipping a degraded experience on iOS/Android (e.g., missing address autofill) because ratings and retention are sensitive.
- Privacy Counsel will block launch if data retention and consent flows are not consistent across platforms.
- Customer Support Ops needs at least 10 business days to update scripts, train agents, and prepare for increased contact rate.
Constraints
- Timeline: 8 weeks to a public GA launch date already tentatively announced internally.
- Release mechanics:
- Web can ship daily behind flags.
- iOS requires App Store review (typically 24–72 hours, occasionally 7+ days) and uses a biweekly release train.
- Android can hotfix faster, but OEM/device variance requires broader regression.
- Compliance & privacy: PCI scope review and a DPIA must be completed before GA; consent copy must be localized for 12 languages.
- Resourcing: No additional headcount approved. Two backend engineers are allocated 30% to fraud incident response.
- Technical dependency: A shared backend “Payment Token Service v2” must be adopted by all clients; web is already migrated, iOS/Android are not.
Deliverables (What You Must Produce)
- A cross-platform launch plan (web/iOS/Android) that includes sequencing, milestones, and decision points.
- A trade-off proposal for what must be identical across platforms at launch vs what can be deferred without harming customer trust.
- A release and risk strategy: feature flags, staged rollout, monitoring, and a rollback plan that works across web and mobile.
- A stakeholder alignment plan: how you’ll handle conflicting priorities (Marketing date vs Engineering risk vs Privacy requirements).
- A Day-0 to Day-14 operational plan: support readiness, incident response, and post-launch measurement.
Complications (Assume These Happen Mid-Project)
- Week 3: Apple App Review rejects the iOS build due to unclear wording around “Save card for faster checkout,” requiring copy changes and resubmission.
- Week 5: Android discovers a critical bug on older devices where address autofill intermittently fails, increasing checkout time and causing a 1.2% drop in completion in internal dogfood.
- Week 6: Privacy flags that web shows consent at a different step than mobile, and demands parity before GA.
Interview Prompt
Walk me through how you would coordinate this launch across web, iOS, and Android. Be specific about:
- How you structure the program (workstreams, owners, operating cadence).
- How you manage cross-platform parity without blocking the entire launch.
- What you do when one platform is behind (e.g., iOS rejection) but others are ready.
- How you design the rollout/rollback so that customers don’t end up in inconsistent states across devices.
- How you communicate status and make go/no-go decisions under uncertainty.
Your answer should include concrete artifacts you would create (e.g., a milestone plan, RACI/DACI, launch checklist, dashboards) and how you’d use them to drive execution.
