Location: Miami, FL | London, UK | Remote (US)

The Problem and the Role

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.

We are seeking a Developer Experience Lead, who will report to the head of Product Growth, to own the entire developer-facing surface of our platform, from documentation to integration support to API governance. We have built a world-class financial engine, but how external developers experience that engine has no owner. This role fills that gap.

This is a foundational role. You will be the first hire in this function. You will architect the documentation ecosystem from the ground up, define the processes that keep it accurate as the platform evolves, and directly support the clients who integrate with our APIs. Over time, you will shape how Developer Experience operates as a discipline at OpenFX, influencing product decisions, integration strategy, and the developer journey end-to-end.

You will set the bar higher than industry standards, building a knowledge system that turns complex FX liquidity and cross-border payment flows into a Hello World integration in under 15 minutes.

What You'll Actually Do & Own

• 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 information architecture and the words. You design the taxonomy that scales from a simple Quickstart guide to complex Treasury Operations references. You determine how we version, layer, and present information so it does not collapse under its own weight as the platform grows. You build it on 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.
• 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.
• Instructional support tickets: reduced 40% within 90 days, with 42% of onboarding support requests as the baseline.
• Spec drift: no spec drift incidents that reach production. The OpenAPI spec stays aligned to production as the platform evolves.
• 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.
• 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)

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.
• 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.
• 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.
• 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.
• 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.
• 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

• 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.

Why This Role?

• 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.
• 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.
• 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. 
• 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.
• 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. 

We are seeking a Staff Software Engineer to join the KSAT Architecture Team — the engineering powerhouse behind our core product. This is a full-stack role requiring mastery of a Ruby on Rails backend, modern front-end technologies (Vue 3+, Svelte), and complex AWS infrastructure. As a Staff Engineer, you are a technical leader in day-to-day operations. This is not a people-management role; instead, you will drive direction through architectural ownership, high-impact code contributions, and cross-team influence. You will navigate a platform ecosystem & microservices, many of which are deployed across 6 AWS regions, ensuring we meet rigorous FedRAMP Moderate, SOC 2, and ISO 27001 standards.This individual in this role is responsible for developing new and exciting products for KnowBe4’s customers, alongside other engineers in a fast-paced, agile development environment.

Requirements:

• Architectural Leadership: Own the evolution of major subsystems, including GraphQL APIs, event-driven service communication (EventBridge/SQS), and data scaling.
• Full-Stack Development: Deliver primary technical contributions across Ruby/Rails APIs, SvelteKit/TypeScript frontends, and AWS serverless infrastructure.
• Scaling Operations: Optimize our serverless background processing framework, currently supporting 400+ Lambda-backed workers.
• Data Strategy: Architect multi-tenant patterns across MySQL, PostgreSQL, DynamoDB, and Redis while maintaining strict tenant isolation and compliance.
• Cross-Functional Coordination: Translate strategic goals into technical roadmaps, collaborating with Product, Security, and Infrastructure teams.
• Mentorship: Set the bar for code quality and architectural patterns through rigorous reviews and technical guidance for senior engineers.

Qualifications:

• BS + 10 years of experience OR
• MS + 5 years of experience OR
• Ph.D. + 4 years of experience
• Backend & Systems: 5+ years of scaling production Ruby on Rails apps. Expertise in GraphQL (batch loading, complexity management) and relational database tuning (MySQL/Postgres) for high-traffic multi-tenant systems.
• Frontend Mastery: Proficiency in modern frameworks (Vue Preferred, Sveltekit or React) and strict TypeScript. Proven ability to lead large-scale frontend migrations using Vite and Tailwind CSS.
• Cloud: Deep experience with AWS (ECS/Fargate, Lambda, EventBridge, S3). Strong proficiency with Terraform for Infrastructure-as-Code and GitLab CI/CD.
• Distributed Systems: Experience designing event-driven architectures and managing asynchronous processing at scale.
• Leadership: Demonstrated experience at the Staff level—writing Architecture Decision Records (ADRs) and building for compliance-regulated environments (FedRAMP/SOC 2).