Project Background

You are the program manager for Shopify’s Billing Platform organization. Shopify processes subscription billing and usage charges for 2.3M+ merchants globally, with peak traffic during major commerce events. The org is migrating from a legacy monolith billing service (“BillMonolith”) to a new event-driven platform (“LedgerNext”) to reduce incident rates and enable faster product launches (e.g., tiered pricing, regional tax rules, and invoice customization).

The migration is already underway and has executive visibility because it blocks a Q2 revenue initiative: “Usage-Based Add-ons”, projected to add $18M ARR if launched by June 30. The CTO has mandated zero downtime and no merchant-facing invoice discrepancies above a strict threshold.

The cross-functional team is distributed across 5 teams (Billing Core, Payments Integrations, Data Platform, Risk & Compliance, Merchant Admin UI) totaling 22 engineers, plus 1 designer, 2 PMs, 1 analytics lead, and you as the program manager. The migration plan is organized into 10 workstreams (data backfill, dual-write, reconciliation, UI cutover, tax engine integration, etc.) and is tracked in Jira, but leadership is frustrated: weekly updates are inconsistent, and it’s unclear whether the program is truly on track.

Stakeholder Landscape

• VP Engineering, Commerce Platform wants a crisp view of schedule risk and dependencies; she is considering reassigning engineers from other initiatives but needs evidence.
• Director of Billing Engineering is focused on technical correctness and wants to slow down cutover until reconciliation is “perfect.”
• Head of Product, Monetization is pushing to accelerate because the Usage-Based Add-ons launch depends on LedgerNext being the system of record.
• Compliance (SOX + PCI) requires auditable controls: change management, access reviews, and documented reconciliation results.
• Customer Support Operations wants advance notice and clear runbooks; they are measured on ticket volume and time-to-resolution.

These stakeholders have competing priorities: speed to unlock revenue vs. conservatism to avoid billing errors and compliance findings.

Constraints

What You Need to Deliver (Candidate Task)

Create a practical approach for tracking actuals vs. plan and reporting variances that drives decisions (not just reporting). Your answer should include the following deliverables:

1. A tracking system design: what artifacts you will use (e.g., integrated plan, milestone burndown, earned value-like measures, RAID log), and how you will reconcile Jira “activity” with true progress.
2. A variance model: define what “plan” means (baseline vs rolling forecast), what you consider an acceptable variance, and how you categorize variance (scope, schedule, resourcing, dependency, quality/compliance).
3. A weekly reporting template (structure + key fields) that can be consumed by both engineering leads and executives in under 5 minutes.
4. A decision and escalation mechanism: what triggers a trade-off conversation, who is in the room, and how you ensure actions are assigned and followed through.
5. A worked example: assume Week 4 actuals show dual-write is 60% complete vs 85% planned, reconciliation defect rate is 2.5x target, and one dependency slipped by 10 days. Show exactly how you would report this and what corrective actions you would propose.

Complications (Realistic Curveballs)

1. Scope pressure mid-flight: The Monetization PM asks to add a “merchant invoice PDF customization” feature into the migration cutover because “it’s easiest while we’re touching billing.” Engineering estimates it at 3 engineer-weeks plus QA.
2. Key dependency slip: Data Platform announces the Kafka migration will freeze schema changes for 3 weeks starting in Week 6, which impacts LedgerNext event topics.
3. Quality surprise: During backfill validation, analytics finds that 0.6% of historical invoices have inconsistent tax rounding rules between systems, and Compliance says you must document the remediation.

Your goal is to demonstrate how you would set up tracking, quantify and communicate variances, and drive alignment on corrective actions and trade-offs—while maintaining credibility with both engineering and business leadership.