Platform Service Strategy & Governance 

• Define the vision and roadmap for platform-level microservices — identifying which capabilities should be built as platform services from day one vs. evolved from module-specific implementations. 

• Own the API contract strategy: define standards for versioning, backward compatibility, and breaking change governance across all services. 

• Establish the principles and governance model for how existing module-level services get backported into shared platform services over time. 

• Lead net-new platform service builds in partnership with architecture and engineering, from discovery through adoption. 

• Champion developer experience — ensure internal engineering teams have the documentation, contracts, and tooling they need to build confidently against platform services. 

Data Architecture & Monetization Strategy 

• Partner with Analytics and Architecture to define and evolve the Snowflake lakehouse strategy — bringing product and commercial context to a technically-led initiative. 

• Own the data product identification process: determine which enriched datasets are monetizable and valuable to FI, ERP, and other strategic partners. 

• Define data governance requirements for regulated partner use cases, including data lineage, access controls, residency considerations, and consent frameworks. 

• Work with commercial and partnerships teams to translate data product identification into viable partner offerings. 

Performance, Scalability & International Readiness 

• Serve as the product voice in architecture’s platform performance and reliability workstream — ensuring prioritization reflects real business impact, not just technical preference. 

• Build line of sight into end-of-month latency, load, and scalability gaps; push for honest diagnosis and meaningful remediation timelines. 

• Define the product requirements for international expansion readiness — multi-geography, multi-currency, and increased volume support — targeting late 2026 / early 2027. 

Required 

• 5–8+ years of product management experience, with meaningful time in platform, infrastructure, or API-focused product roles. 

• Deep enough technical fluency to engage credibly with architecture and engineering on microservices patterns, API design, and distributed systems tradeoffs — you don’t need to write code, but you need to understand the decisions. 

• Demonstrated experience with data strategy in a product context — data pipelines, data warehousing, or data product development. 

• Track record of influencing without authority across engineering, data, and business teams. 

• Comfort operating in ambiguity — this role requires building structure where little exists today. 

Strongly Preferred 

• Experience with Snowflake or comparable cloud data platforms in a product or strategy capacity. 

• Familiarity with data monetization, data sharing, or partner data product models — particularly with FIs or ERP ecosystem partners. 

• Experience with API governance, API versioning strategies, or developer platform products. 

• Background in fintech, B2B SaaS, or collaborative commerce platforms nice to have. 

• Exposure to regulatory and compliance considerations around data sharing (SOC 2, data residency, financial data regulations). 

Organizational Change Management 

This is not just a technical or strategic role. You are coming into an organization mid-transformation — a monolith culture evolving toward microservices, and a data strategy that has started but needs more thought. You will need to: 

• Build credibility and trust with engineering and architecture leaders who have strong technical opinions. 

• Drive cultural change around platform-first thinking without having direct authority over the teams doing the work. 

• Maintain executive alignment and surface honest performance signals, even when they are uncomfortable.