Staff Software Engineer, Money Partnerships

Replit Replit · Enterprise · Foster City, CA · Hybrid · Engineering

Staff Software Engineer on Replit's Money team responsible for zero-to-one product engineering of financial partnerships, integrating billing platforms, payment processors, agentic-commerce protocols, and tax/compliance vendors. The role involves scoping, designing, building, shipping, and operating these integrations, owning the technical relationship with partners, and building observability for partner-facing flows. Requires strong backend expertise, experience with financial integrations, system design in high-correctness domains, and autonomous work across organizational boundaries.

What you'd actually do

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.

Skills

Required

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

Nice to have

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

What the JD emphasized

  • external financial-partner platform end-to-end
  • zero-to-one
  • operate it
  • operate
  • agentic-commerce protocols
  • agentic-commerce primitives
  • agent-issued cards
  • agent wallets
  • non-human party initiates payment
  • partner-facing flows
  • partner incident response
  • partner's engineering team