How would you run the first 90 days after taking over Tax

Problem Statement Description

Product context: Stripe is financial infrastructure for internet businesses; its products include payments, Checkout, Billing, Connect, Radar, Issuing, Terminal, and tax tools.

You have just taken over product leadership for Stripe Tax, with a focus on platform businesses that need to help their merchants calculate, collect, report, and remit taxes across jurisdictions. These customers operate complex marketplaces, SaaS platforms, and multi-party payment flows where tax accuracy, developer integration quality, compliance confidence, and business continuity are critical.

The interview asks how you would run your first 90 days in this role. Your response should frame how you would quickly understand the product, customers, team, operating cadence, technical and regulatory dependencies, and business priorities before deciding where to focus execution. The scope is not to redesign Stripe Tax or propose a single feature, but to show how you would establish clarity, momentum, and accountability in a high-stakes financial infrastructure product.

You should account for Stripe’s environment: global compliance obligations, API-first developer experience, merchant trust, platform growth, reliability expectations, and competitive pressure from payments and commerce infrastructure providers. The plan should show how you would balance learning, prioritization, delivery, risk management, and stakeholder alignment across product, engineering, legal, compliance, sales, support, operations, and go-to-market teams.

The experience should consider:

- How you would assess the current state of Stripe Tax across customer adoption, revenue contribution, reliability, compliance coverage, integration friction, and support burden

- Which customers, internal teams, dashboards, incidents, roadmap artifacts, and operational reviews you would use to build context

- How you would identify the most important execution priorities for platform businesses versus other Tax customer segments

- How you would sequence the first 30, 60, and 90 days without disrupting ongoing commitments or regulatory obligations

- What owners, decision forums, dependencies, and communication cadences you would establish

- How you would define go/no-go criteria for roadmap changes, launches, compliance expansions, or reliability improvements

- How you would manage launch risk, incident readiness, rollback plans, customer communication, and internal escalation paths

- How you would demonstrate early impact while preserving long-term strategic flexibility

The goal is to present a structured 90-day operating plan that shows executive judgment, product rigor, cross-functional leadership, and the ability to run a mission-critical Stripe product where customer trust, developer experience, compliance, and business outcomes all matter.