About the role
<h2><span style="font-size: 10pt;">The Role</span></h2> <p><span style="font-size: 10pt;">You’ll own a slice of how merchants experience capital from Pipe. Servicing flows, money movement rails that make them work in the five countries we serve - US, UK, CA, AUS and NZ, and the APIs, and integrations. This means partner-facing APIs for offer surfacing and acceptance, split payout logic with partners like Uber Eats and Housecall Pro, and bank rail integrations that move dollars in and out at scale. It’s where product design, credit logic, partner engineering, and payments infrastructure meet. And where a lot of Pipe’s economics get made.</span></p> <p><span style="font-size: 10pt;">You’ll own measurable outcomes and high stakes interactions with our partners, not just ship features. Expected metrics include partner integration adoption and growth, and positive internal rate of return on the flows you touch. You’ll work directly with engineering, design, risk, capital markets, and partner success and you’ll be expected to have a point of view, not just synthesize others’.</span></p> <p><strong><span style="font-size: 10pt;">What you’ll do</span></strong></p> <ul> <li style="font-size: 10pt;"><span style="font-size: 10pt;">Own the end-to-end product lifecycle for merchant capital UX, partner-facing APIs, and the servicing and money movement flows underneath them.</span></li> <li style="font-size: 10pt;"><span style="font-size: 10pt;">Develop and maintain a prioritized roadmap tied to specific conversion, adoption, money movement, and margin outcomes.</span></li> <li style="font-size: 10pt;"><span style="font-size: 10pt;">Partner directly with engineering on API and rails design; webhook patterns, idempotency, reconciliation, failure handling, partner sandbox experience, and the operational realities of working with payment providers. You should have opinions here, not just relay them.</span></li> <li style="font-size: 10pt;"><span style="font-size: 10pt;">Run user and partner research: talk to merchants, sit with partner engineering teams, watch real usage.</span></li> <li style="font-size: 10pt;"><span style="font-size: 10pt;">Write specs tight enough that engineering can build from them and product reviews can challenge them.Define, monitor, and analyze metrics yourself; pulling your own SQL when you need to.</span></li> <li style="font-size: 10pt;"><span style="font-size: 10pt;">Drive cross-functional alignment across Engineering, Design, Risk, Legal, Marketing, Capital Markets and Partner Success.</span></li> </ul> <p><s