Ruby on RailsSQLRubyRailsProduct ManagementCommunicationSales
About this role
Role Overview
Own the Payments Engine roadmap: Define and execute the product roadmap for payment creation, processing, and settlement.
Prioritize features that improve reliability, reduce latency, increase success rates, and unlock new use cases across corridors and rails.
Drive payment performance: Own key engine health metrics — success rate, latency (TTFT, end-to-end), RFI rate, failure root causes.
Identify bottlenecks, partner with Engineering to resolve them, and translate improvements into OFI and BFI outcomes.
Shape API and protocol capabilities: Define requirements for the OFI Payments API and BFI quoting/settlement protocols.
Balance developer experience with compliance requirements and network reliability.
Own the spec process from problem to launch.
Build engine observability and control: Drive investments in payment monitoring, alerting, and operational tooling that give Circle and its partners real-time visibility into payment health and the ability to act on anomalies.
Partner across the network: Work closely with BFI partners, OFI integrations, Compliance, and Operations to understand where the engine creates friction and remove it — unblocking volume, reducing manual intervention, and improving SLAs.
Requirements
5+ years in Product Management at a payments, fintech, or financial infrastructure company
Experience owning platform or infrastructure products — APIs, processing pipelines, settlement systems, or developer-facing capabilities
Strong analytical skills — comfortable diagnosing payment failures, interpreting latency distributions, and building data-driven cases for prioritization; SQL or equivalent data fluency
Track record of shipping reliability or performance improvements with measurable impact (e.g., success rate, p99 latency, error rate reduction)
Experience working cross-functionally with Engineering, Operations, Compliance, and BD/Sales to drive outcomes in ambiguous, fast-moving environments
Ability to operate at both the strategic level (roadmap, architecture trade-offs, partner SLAs) and the tactical level (debugging a failed payment, unblocking a specific corridor, writing a precise spec)
Clear, structured communication — can produce decision-ready documents, technical specs, and cross-functional alignment materials