SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
OpenFX is building infrastructure to enable cross-border payments at scale, moving money as freely as data across time zones and legacy banking systems. The company is backed by top-tier investors (Accel, Lightspeed, NfX) and led by a team with experience from JP Morgan, Goldman Sachs, FalconX, PayPal, Affirm, and other fintech leaders.
As the first Developer Experience Lead, you will own the entire developer-facing surface of OpenFX's platform—from API documentation and integration support to API governance and developer advocacy. This is a foundational role reporting to the Head of Product Growth, with significant influence over how the company scales its developer ecosystem.
Key responsibilities include:
**Drive API Product Adoption**: Own the adoption funnel from API key activation through first API call, first transaction, and expanded endpoint usage. Instrument the funnel, set baselines and targets, and drive cross-functional work to move adoption metrics quarterly.
**Architect the Documentation System**: Build a docs-as-code infrastructure that engineers can contribute to. Measure documentation success by adoption impact, not completeness. Target reducing time-to-first-API-call from ~3 days to under 15 minutes within 90 days.
**Own the OpenAPI Workflow**: Align the OpenAPI spec to production reality and implement contract-first governance. Enforce spec linters in CI as merge blockers, make OpenAPI updates part of engineering's Definition of Done, and automatically detect breaking changes with defined deprecation processes. Act as the First User in product and engineering reviews, pushing back on APIs that are too hard to explain.
**Drive Developer Advocacy**: Write technical content (blog posts on idempotency, sample apps, integration pattern guides) that builds developer trust. Build feedback loops that turn integration friction into product improvements. Represent OpenFX at developer events and conferences as volume justifies.
**Own Integration Triage**: Serve as the technical front door for client integration questions during US business hours. Triage issues as documentation gaps, API design problems, or code bugs. Fix documentation gaps directly and route others to engineering with structured context. Build scalable onboarding playbooks.
Success metrics include: API adoption funnel instrumentation and quarterly growth, time-to-first-API-call under 15 minutes, 40% reduction in instructional support tickets within 90 days, and zero spec drift incidents reaching production.
