OpenFX - Developer Experience Lead

Miami (USA), London (UK), Dubai (UAE), Bengaluru (India)1mo ago

Remote Staff NA Banking Fintech Developer Experience Engineer Developer Relations Lead Solidity Developer Documentation B2B OpenAPI Governance Slack

Requirements

• 5+ years owning a developer-facing API product or platform. B2B or infrastructure. You drove a measurable adoption outcome, not just shipped pages. You can point to the integration experience you built, the funnel you owned, and the metric you moved. • 5+ years owning a developer-facing API product or platform. • Direct client integration work. You have sat on integration calls with B2B or institutional clients, diagnosed friction live, and fed it back into product changes (not just documentation updates). You know what breaks during real integrations, not what should break in theory. • Direct client integration work. • Product instinct for API design. You have opinions on endpoint design, parameter naming, authentication UX, error response formats, idempotency keys, and SDK ergonomics. You have opinions on these calls and get changes shipped before code hits production. • Product instinct for API design. • Engineering fluency. You read code well enough to extract logic independently. You understand distributed system concepts (latency, rate limiting, idempotency, eventual consistency, async patterns). You can sit in a code review and have something useful to say. • Engineering fluency. • Contract-first governance experience. You have implemented or enforced OpenAPI workflows where the spec is treated as a product contract, not a generated artifact. • Financial services or fintech context. You know the difference between authorized and settled. You have worked on payments, trading, or banking APIs. • Financial services or fintech context. • Agent Experience instinct. You have shipped or experimented with MCP servers, agent-native SDKs, llms.txt, evaluation suites for LLM-driven API consumption, or other agent-readable API patterns. You have a point of view on what Developer Experience looks like when AI agents are first-class consumers. • Preferred • Preferred • Interactive docs experience: code playgrounds, Try It Now, in-browser sandbox. • Multimedia documentation skills: video tutorials, sequence diagrams, architecture diagrams that complement written documentation. • Developer advocacy or DevRel experience: you have written technical content for an external developer audience, shipped sample apps, or represented a product at developer events.

Responsibilities

• Drive API Product Adoption • You own API adoption as a measurable outcome. You instrument the funnel from API key activation to first API call to first transaction to expanded endpoint usage. You set the baseline, define the targets, and drive the cross-functional work to move the number. Every quarter, more developers are activated, more endpoints are used, and integrations go deeper. This is what you are accountable for, not pages shipped. • Architect the Documentation System • Documentation is the primary adoption surface. You own the docs-as-code infrastructure that engineers can contribute to. You measure documentation by whether it moves adoption, not by completeness for its own sake. • Own the OpenAPI Workflow • Your first technical priority is aligning the OpenAPI spec to production reality. Then you implement and enforce a contract-first governance model where the spec is treated as a product contract, not a generated afterthought. Spec linters run in CI as merge blockers. OpenAPI updates are part of engineering's Definition of Done. Breaking changes are detected automatically and routed through a defined deprecation process. You sit in Product and Engineering reviews as the First User: if an API is too hard to explain in writing, it is too hard to use, and you have the authority to push back before code ships. • Drive Developer Advocacy • You are the external voice of OpenFX inside the developer community and the internal voice of the developer inside OpenFX. You write technical content that earns developer trust: deep-dive blog posts on idempotency under retries, sample apps that demonstrate real cross-border payment flows, integration pattern guides for PSP, neo-bank, and treasury use cases. You build feedback loops that turn integration friction into product changes. As volume justifies, you represent OpenFX at developer-focused events, conferences, and partner enablement sessions. You are the reason developers choose OpenFX over a competitor whose docs they could not understand. • Own Integration Triage • You are the technical front door for client integration questions during US business hours. You triage whether each issue is a documentation gap, an API design problem, or a code bug. You fix documentation gaps directly and route the rest to engineering with structured context. You build the repeatable onboarding playbook that turns one-off Slack threads into a scalable process. You partner with GTM, who owns the client relationship; you own the developer experience surface that surfaces during integration. • What Success Looks Like • API Product Adoption: You own the adoption funnel from API key activation to first API call to first transaction to expanded endpoint usage. You instrument it, set the baseline, define the target, and drive the cross-functional work to move the number. This is the metric you are accountable for. • API Product Adoption: • Time to First API Call: Drops from around 3 days to under 15 minutes within 90 days. You own the Quickstart, code snippets, and onboarding tutorials that make this speed possible, and you advocate for the product changes needed to remove the rest of the friction. • Time to First API Call: • Instructional support tickets: reduced 40% within 90 days, with 42% of onboarding support requests as the baseline. • Instructional support tickets: • Spec drift: no spec drift incidents that reach production. The OpenAPI spec stays aligned to production as the platform evolves. • Spec drift: • V1 Developer Portal: a public API doc portal (References, Guides, Changelog, sample apps) is live, searchable, and built on docs-as-code infrastructure. 100% of public endpoints have accurate request and response examples. • V1 Developer Portal: • Developer advocacy presence: a published cadence of technical content (deep-dive guides, sample apps, integration patterns) that builds developer trust and drives inbound adoption. Establish the baseline, grow it quarterly. • DX roadmap: a written plan for SDK strategy, portal evolution, adoption analytics, and Agent Experience foundations and expansion (CLI, MCP) • DX roadmap:

Benefits

• Foundational Ownership: You are the first hire in this function. You define the hiring standards, the voice, and the culture of Developer Experience at OpenFX. As the function scales, you lead the team. • Foundational Ownership: • Greenfield Architecture: You are building the DX product from the ground up. You build the system right the first time, selecting the stack, the taxonomy, and the governance model from scratch. • Greenfield Architecture: • The Frontier of Finance: You will learn the inner workings of global finance (FX liquidity, settlement, treasury), and you will apply them to the new payment stack as well as the legacy rails of the past. Our technology is novel; you teach developers how to think about the future of money and define the vocabulary of the industry. • The Frontier of Finance: • Where This Role Grows: The next milestone is Agent Experience. AI agents are becoming first-class consumers of APIs alongside human developers. As Developer Experience matures, you lead the expansion into agent-native tooling: MCP servers that expose OpenFX as agent-callable tools, SDKs and CLIs designed for both human and autonomous consumption, semantically structured documentation that LLMs can parse natively, evaluation suites that test whether agents can invoke OpenFX correctly from natural language, and sandboxing patterns that let agents transact safely. Few companies have a clear owner for what Agent Experience means at the API layer. You define this discipline at OpenFX, and you do it from a foundation of human Developer Experience that already works. • Where This Role Grows: • The Team: You are joining a team of ex-Stripe, J.P. Morgan, and Kraken alumni. We are backed by Accel, Atomico, M13, Northzone, Pantera, and we believe that our APIs are core to our product. • The Team: