SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
OpenFX is building infrastructure to move money as freely as data across borders, unrestricted by time zones or legacy systems. The company processes billions in monthly transaction volume and is backed by top-tier investors including Accel, Lightspeed, and NFX.
You will establish and lead a new Payments pod of 8–15 engineers and QA, owning three interconnected domains end-to-end:
**Corridor Expansion**: Build a repeatable playbook for launching new payment corridors (EUR, MXN, COP, AED, and beyond). Move from bespoke projects to standardized partner integration patterns, corridor configuration frameworks, and clear launch-readiness criteria covering rails, cut-offs, FX mechanics, fees, returns, and reconciliation. Own the reliability of live corridors—settlement timeliness, failure handling, partner degradation, and runbooks that keep money moving when partners degrade.
**License Operationalization**: Translate EU regulatory obligations into running systems. Engineer safeguarding of customer funds (segregation, sweep flows, coverage reconciliation, and controls) and transaction monitoring (rules, alerting, case handoff). Build for evidence—every control must produce audit trails satisfying regulators, auditors, and partners. Partner with Compliance and Legal to negotiate scope and sequencing rather than absorbing requirements wholesale.
**Payments Product**: Own the payments product surface across API and GUI—payment initiation, quoting, tracking, statuses, webhooks, returns, recalls, reporting, and dashboard experiences for operations and finance users. Ship features weekly with discipline the money path demands: idempotency, exactly-once ledger effects, backward-compatible API evolution, and rollout strategies with exercised rollbacks.
**Leadership & Execution**: Run the pod with a Tech Lead reporting to you. Own roadmap, standards, and on-call posture. Stay hands-on—review designs, write and ship code, debug production, and set the implementation bar by example. Raise operational maturity through incident command, deployment hygiene, delivery metrics, and alerting. Hire, grow the team, run ramps, keep on-call sustainable, and act on performance early.
**Must-haves**: 2+ years managing a full team of 5+, with a Tech Lead or senior IC reporting in, backed by strong backend IC experience. Still writes code—design APIs, model schemas, produce idiomatic tested code. Built or operated payment systems in production (orchestration, ledgers, settlement, reconciliation) with working grasp of failure modes (duplicates, partial failures, cut-off misses, stuck settlements). Integrated banking, payment, or FX partners and lived through sandbox-vs-production drift, credential churn, partner outages, degraded-mode operation. Deep on distributed systems correctness where money is involved: idempotency, exactly-once effects, concurrency, reconciliation as first-class design. Worked directly with compliance, risk, or regulators and can negotiate scope. Run high-reliability systems.
