This is a zero-to-one Product Engineering role on Replit's Money team. You'll bring our financial partnerships alive from scoping to integrating and operating them so that the builders on Replit, and the Apps and Agents they ship can transact reliably anywhere in the world
Money at Replit isn’t traditional payments. Builders are publishing apps that earn revenue. Agents are spending and being paid for work. New protocols for agentic commerce now exist to power the future of commerce: Shared Payment Tokens, the Agentic Commerce Protocol (ACP), the Universal Commerce Protocol (UCP), the Machine Payments Protocol (MPP). Replit is one of the platforms that will define what they look like in practice and lower the barrier to entry
To make any of that real, we need someone who can sit between Replit engineering and our financial partners including billing platforms, payment processors, agentic-commerce protocol partners, tax and compliance vendors to turn signed contracts into live, reliable integrations. You'll be the engineer partners ask for, and the engineer the rest of Replit relies on when a new monetization surface needs to ship
This role is a fit if you like writing code and you also like being in the room when a partnership is being scoped, because you know that the design decisions made in that room are the ones that bind the integration for years
Take financial partnerships from zero-to-one: scope the integration with the partner, pressure-test data and protocol specs, design the system, build it, ship it, and operate it
Own the technical relationship with Replit's financial partners across the full lifecycle: billing platforms, payment processors, agentic-commerce protocol partners, tax/compliance vendors, KYC/risk providers
Build and maintain Replit's integrations with agentic-commerce protocols (ACP, UCP, MPP) and Shared Payment Tokens, so Replit Agents and the apps Replit users ship can transact across AI surfaces
Design the abstractions that let other Replit engineers monetize new products without each one having to relearn the partner stack; clear seams, versioned interfaces, and integrations that age gracefully
Build the observability layer for partner-facing flows: webhook reliability, reconciliation, latency SLOs, partner-incident response, and the dashboards that let us see partner failures before users do
Drive partner-side incident response when integrations degrade, including escalation paths, post-incident reviews with the partner, and the eng work to harden the integration so the same class of failure doesn't recur
Represent Replit in technical reviews with partners: API design feedback, protocol input, joint roadmaps. Bring what you learn back into Replit's monetization architecture
Partner closely with finance, accounting, data, legal, and BD so the integrations you build produce auditable financial data, satisfy contractual SLAs, and unlock the commercial deals behind them