• Own the product backlog and keep priorities clear, current, and actionable • Facilitate Agile ceremonies: backlog grooming, sprint planning, stand-ups, and retrospectives • Track progress against goals, communicating updates clearly to stakeholders • Oversee testing and validation to ensure features meet acceptance criteria • Collaborate with UX/UI designers to align user experience with business intent • Document, analyze, and iterate based on user feedback and performance metrics

• Define and launch a unified merchant experience platform • Own merchant onboarding and self-service experiences • Ship AI-powered agents and workflows • Own permissions, entitlements, and shared services • Break big problems into small releases and iterate based on feedback • Partner across product teams to drive adoption

• Define the integrations and platform strategy and roadmap — the surface area that determines whether customers trust our data enough to run their GTM on it • Make reliability a product outcome, not an afterthought: uptime, data freshness, and accuracy customers never have to think about — and fast, legible triage when something does break • Ship AI agent workflows and APIs that move real GTM work across customer systems end-to-end: enrichment, sync, signal-to-action — not demos, production • Own a small set of customer relationships directly, and turn what you learn — especially where integrations make or break a renewal — into product bets the whole company can rally behind • Partner with engineering and design to make complex capabilities feel simple — self-serve integration setup a non-technical RevOps lead can actually configure, sync behavior a data team can actually trust • The instinct to complete the swing — shipping is the midpoint, not the finish line, and you'll own the work through migrations, deprecations, enablement, and the Sales and CS feedback loop that turns features into retained revenue • Raise the bar on product craft across the team — through the work you ship and the way you operate

• Own and sequence the net-new supplier integration pipeline against the booking-coverage goal, making the trade-off calls on what ships next • Run partner technical calls, defining exactly what each integration needs • Partner tightly with the senior integration engineers to unblock builds and chase partner side issues to the finish when an API doesn't work as documented • Co-own the booking-coverage number with the supplier GM and partner closely on the supplier sales side • Turn one-off integrations into reusable interfaces and patterns so each new partner ships faster than the last • Manage many partners in parallel, sequencing dependencies and delays across a concurrent roadmap