Staff Software Engineer, Money Partnerships

Responsibilities

• 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.

Requirements

• 6+ years of professional software engineering experience, with strong backend expertise.
• Direct, hands-on experience integrating with at least one external financial-partner platform end-to-end, but owning the integration through go-live and steady-state operation. Examples include payment processors, billing/metering platforms, tax engines, KYC/risk vendors, banking-as-a-service providers, or card-issuing platforms.
• Track record of taking integrations from zero-to-one: scoping with the partner, navigating ambiguous specs, and shipping a production-grade integration that you then had to operate.
• Strong system-design instincts in high-correctness domains where money, idempotency, retries, reconciliation, and observability are first-class concerns.
• Comfort working autonomously across organizational boundaries. You can drive a meeting with a partner's engineering team, push back on a bad spec, and still leave with a relationship intact.
• Excellent debugging skills against systems you don't own, including reading partner API behavior from logs, replays, and webhook traces when documentation is wrong or incomplete.

Tools + tech stack: TypeScript, React, Postgres, GraphQL, Node.js.

Nice-to-haves

• Experience with one or more agentic-commerce primitives: Shared Payment Tokens, ACP, UCP, MPP, agent-issued cards, agent wallets, or any production system where a non-human party initiates payment.
• Experience with usage-based billing platforms (Orb, Metronome, Stripe Billing) or payment processors (Stripe, Adyen, Braintree) at the integration level. You've onboarded the vendors in the past.
• Experience operating webhook-driven, eventually-consistent integrations, including reconciliation and replay tooling.
• Experience with multi-party payment flows, marketplace payouts, or platforms where the platform itself is responsible for the financial correctness of third parties.
• You've sat across a table from a partner's engineering team and convinced them to change something in their API.