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 transaction volume monthly and is backed by top-tier investors including Accel, Lightspeed, and NFX. The team includes veterans from JP Morgan, Goldman Sachs, PayPal, Affirm, and other leading fintech and infrastructure companies.
The Application Platform pod owns the foundational layer that all other teams build upon: the API gateway, authentication and session security, admin surfaces, API standards and governance, identifier schemes, and production observability. This role manages the critical intersection where security requirements (strong customer authentication, mTLS, session controls), product velocity (weekly shipping), compliance needs (auditors, cyber insurers), and engineering discipline (deployment hygiene, drift prevention) must be balanced.
As Engineering Manager, you will lead a team of 8-15 engineers and QA with a Tech Lead reporting to you. Key responsibilities include owning the API gateway and edge layer (routing, plugins, rate limiting, mTLS, HMAC, rollout strategy with exercised rollback paths); authentication and session security (strong customer auth, re-authentication, device gating, session revocation, credential management); API standards and governance (standards documentation, enforcement, versioning, identifier schemes, realistic review processes); making security review predictable through scoped RFC sign-offs with named owners and dates; staying hands-on by reviewing designs, writing and shipping code, debugging production, and setting implementation standards; raising operational maturity (incident command, deployment hygiene, delivery metrics, audit logging, alerting); and hiring and growing the team.
You must have 2+ years managing a full team of 5+ engineers with a Tech Lead or senior IC reporting to you, backed by a strong backend or infrastructure IC track record. You still write production code—designing APIs, modeling schemas, and producing idiomatic, tested code. You have owned a shared platform, gateway, or authentication system with internal teams as customers. You have deep expertise in API design, authentication, and distributed systems failure modes (blast radius, concurrency, idempotency). You understand the operational and security constraints of payment systems and can navigate competing priorities without sacrificing either speed or safety.
