Senior Backend Engineer (L5) -Payments

About the company

OpenFX is a fintech infrastructure startup that provides a stablecoin-native network and API-based solutions for instant, 24/7 cross-border foreign exchange and payments.

About this role

<p></p> <h3>About Us</h3> <p>OpenFX is on a mission to move money as freely as data, unrestricted by time zones, banking hours, or legacy systems. We are building the infrastructure that will power the next generation of cross-border payment systems for institutions. The team's execution has been exceptional, and we're scaling at a remarkable pace. Our stellar early team comes with experience in companies like J.P. Morgan, Goldman Sachs, FalconX, PayPal, Affirm, Polygon, Kraken, Nium &amp; others. We're backed by Accel, Lightspeed, NfX and other top-tier investors.</p> <h3>Role Overview</h3> <p>We're hiring a Staff Software Engineer for our Payments team. This is the senior-most individual contributor role on the systems that move money across borders — payment orchestration, corridor and partner integrations, FX and quoting, the payment lifecycle from initiation to settlement confirmation, and the regulated controls (safeguarding, transaction monitoring) that our EU licenses demand.</p> <p>It is a hands-on technical leadership role on the money path, where a new corridor is only as good as its failure handling, and a regulatory control is only as good as the evidence it produces. The cost of a defect is measured in real money, stuck customer payments, or a finding from a regulator.</p> <p>You will report to an Engineering Manager and work closely with engineers, product, compliance, and partnerships across the company. You will set the technical direction for payments, lead the hardest corridor and orchestration problems, and raise the bar for how we build.</p> <p>This role requires someone who has built and operated payment or other correctness-critical systems in production, ideally against external partners whose behavior you do not control. If your experience is limited to systems where occasional data inconsistency is acceptable, where every dependency was internal and well-behaved, or where you have not owned something end to end for a meaningful stretch, this will be a stretch.</p> <h3>Key Responsibilities</h3> <ul> <li>Own the technical direction for payments: payment orchestration, corridor and partner integrations, FX and quoting, lifecycle modelling (statuses, webhooks, returns, recalls), and settlement confirmation.</li> <li>Design the corridor expansion architecture: turn new-corridor launches (EUR, MXN, COP, AED, and beyond) from bespoke integration projects into configuration-driven, repeatable capability — standardized partner adapters, corridor config over code, and a rigorous definition of launch-ready.</li> <li>Lead the engineering of regulated controls: safeguarding flows (segregation, sweeps, coverage reconciliation) and transaction monitoring pipelines, built so that every control produces an audit trail that stands up to regulators and auditors.</li> <li>Define and maintain the standards for money-path code — idempotency, exactly-once effects, consistency guarantees under partner failure, safe retries against external systems, and backward-compatible API evolution.</li> <li>Own resilience against partners: degraded-mode behavior, failover and routing across redundant partners, cut-off handling, and reconciliation as a first-class design concern rather than an afterthought.</li> <li>Own the reliability and observability bar for payment flows, and lead incident response when money is stuck or a partner is down.</li> <li>Lead architecture reviews for new corridors, partner integrations, and high-risk changes where correctness and auditability matter most.</li> <li>Mentor senior engineers and help set what great looks like when hiring.</li> <li>Partner across product, compliance, risk, and banking partnerships, translating technical trade-offs for non-engineering audiences — including why a corridor cannot launch until its returns path is real.</li> </ul> <h3>What We Are Looking For</h3> <p><strong>Must-haves:</strong></p> <ul> <li>Significant experience as a senior or staff-level backend engineer, with a track record of owning complex systems in production.</li> <li>Has built or operated payment systems in production — orchestration, partner integrations, or payment lifecycle systems — with a working grasp of money-path failure modes: duplicates, partial failures, cut-off misses, stuck or lost payments.</li> <li>Has integrated external banking, payment, or FX partners and lived through the messy reality: sandbox-vs-production drift, certificate and credential churn, undocumented behavior, partner outages.</li> <li>Sound judgment on correctness under failure — retries against external systems, idempotency, exactly-once effects, and safe handling of critical data.</li> <li>Deep expertise in distributed systems and a strong grasp of reliability, performance, and scalability trade-offs.</li> <li>Excellent technical communication and the ability to lead initiatives across teams without formal authority.</li> <li>Fluency in a modern TypeScript / Node backend stack and cloud infrastructure.</li> </ul> <p><strong>What helps you stand out:</strong></p> <ul> <li>Cross-border payments experience: corridor launches, FX, SWIFT/SEPA or local clearing schemes in any of our target markets (EU, LATAM, Middle East, APAC).</li> <li>Experience building safeguarding, transaction monitoring, sanctions screening, or other regulated controls in an EMI/PI, PSD2, or MiCAR-style environment.</li> <li>Multi-partner orchestration: routing, partner health scoring, and failover on live money flows.</li> <li>Experience with durable workflow or orchestration engines for long-running, multi-step payment processes.</li> <li>Stablecoin or digital-asset settlement rails alongside fiat.</li> <li>A strong observability practice on financial or other high-stakes flows.</li> </ul> <h3>What Success Looks Like</h3> <ul> <li>New corridors launch on a repeatable, configuration-driven foundation — each launch is faster and safer than the last, and none destabilizes existing corridors.</li> <li>Safeguarding and t