Engineering Manager

Responsibilities:

• Run the Growth pod of roughly 6 to 10 engineers and QA across frontend, backend, and integrations. You own the roadmap, the delivery, and the standards.
• Own the API as a product. Land the V3 overhaul, our largest and most cross-dependent programme, while V2 stays supported. Ship client-facing API.
• Bring onboarding in-house. Move the client onboarding experience off third-party tools onto OpenFX, and build the rules engine that replaces global policy with dynamic KYB and KYC requirements by jurisdiction and customer segment.
• Extend onboarding to new segments: self-serve signup through to first trade with no sales touch, enterprise (large entities, directors, UBO, bespoke verification), channel partners and platform-of-platforms, multi-product onboarding across banking and payments, and eventually agent-based customers.
• Own the activation surface: digital signatures, in-product activation checklists, recovery and lifecycle client comms, and a self-serve notification centre.
• Own the marketing site as a growth surface, partnering with Brand Design and the visual explainers that both generate market intelligence and give sales what they need to close.
• Run the product development process credibly. Take work from discovery through solution, design, and RFC validation into delivery and beta, own or assign RFCs, and hold the design-ready and delivery-ready gates so nothing enters a sprint half-shaped.
• Manage a dependency-saturated roadmap. Compliance, Legal, Platform, Payments, Banking, Currencies, TPV, Client Trading, Brand Design, and GTM all sit on your critical path. Sequencing around them is a core part of the job, not an interruption to it.
• Own the interface with GTM and Product: one intake for growth and sales requests, joint prioritisation with the Growth PM, and an expedite lane whose cost in displaced work is explicit rather than silently absorbed.
• Stay hands-on. You review designs, and you still write and ship code, debug production, and set the implementation bar by example, including the standard for AI-assisted development.
• Hold the bar where correctness is not optional: identity and KYC deduplication, idempotency on quote and trade paths, permission and compliance boundaries, money precision and rounding.
• Hire and grow the team: close open roles, grow your team, run 30-60-90 ramps, set explicit performance expectations, and act on them early.

Requirements:

• EM-level scope: 2 or more years managing a full team of 5 or more, with a Tech Lead or senior IC reporting in, on top of a strong individual contributor track record.
• Still writes code. You can design an API, model a schema, and produce idiomatic, runnable, tested code. Design fluency without hands-on ability is not enough at this level.
• Experience owning a public or partner-facing API as a product, including versioning and running an old and a new major version side by side.
• Shipped client-facing product end to end, including the unglamorous parts: migrations, deprecations, and error states.
• Has delivered against Compliance and Legal as hard dependencies, not as a review step at the end. Onboarding at OpenFX is a compliance surface first and a product surface second.
• Comfortable running a stage-gated product process: discovery, solution and design validation, RFC, delivery without letting it slow the team down or become box-ticking.
• Can take a one-line placeholder and turn it into shaped, sized, sequenced work. A large share of the forward roadmap is deliberately undefined.
• Demonstrated hiring and performance management, including at least one underperformance case you saw through to an outcome.
• Has worked directly with Product and a commercial or GTM function, and can say no with a reason that holds.
• High agency: operates with low oversight on ambiguous problems, in a demanding environment.
• Can articulate and enforce a correctness bar under commercial time pressure.

What helps you stand out:

• Fintech, payments, or another regulated domain where onboarding is a compliance surface.
• KYB and KYC in production, and replacing a vendor onboarding or verification workflow with an in-house build.
• Jurisdiction-aware or segment-aware policy engines, where requirements are configuration rather than code branches.
• Developer experience work: API documentation, SDKs, sandbox environments, webhook delivery, or developer funnels.
• Activation and lifecycle engineering: in-product onboarding checklists, transactional and lifecycle comms, notification preferences.
• Marketing site or growth-experiment engineering in partnership with Brand Design.
• Growth instrumentation and analytics tooling, and comfort reading a funnel yourself.
• Onboarding for enterprise entities (directors, UBO) or for channel partners and platform-of-platforms models.