Senior Technical Writer, API Documentation at OpenFX

, , -

Full Time

Start Date

Immediate

Expiry Date

16 Apr, 26

Salary

0.0

Posted On

16 Jan, 26

Experience

5 year(s) or above

Remote Job

Yes

Telecommute

Yes

Sponsor Visa

Skills

API Documentation, Information Architecture, Markdown, Git, CI/CD, Financial Services, REST APIs, Technical Writing, Engineering Fluency, Documentation Standards, OpenAPI, Feedback Loops, Interactive Documentation, Multimedia Skills, Complex Concepts, Developer Adoption

Industry

Financial Services

Description

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 Senior Technical Writer to establish world-class API documentation and act as the translator between complex financial engineering and external developer adoption. We have built a world-class financial engine, but we need documentation that matches it. This is a foundational role where you will own the documentation ecosystem from the ground up; architecting information systems, defining content standards, and directly influencing how global financial institutions integrate with our infrastructure. You'll 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 Architect the System: You will own the Information Architecture and the words. You will 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 doesn't collapse under its own weight in two years. Own the Stack: You own the build- out of the API doc platform, while engineers build the APIs. You select the tech stack and implement tooling that enables engineers to contribute documentation efficiently while maintaining quality standards. Define the "Mental Models": You translate internal engineering logic into external developer understanding. You won't just document endpoints; you will explain concepts. You will write the definitive guides on handling idempotency, asynchronous webhooks, and multi-currency settlement states. Own the OpenAPI Workflow: You will implement and enforce a "Design First" or strictly governed "Code First" workflow where OpenAPI/Swagger specs are treated as a product contract. You ensure automated reference generation from these workflows are accurate, typed, and complete. Drive API Design Feedback: You will sit in Product, Engineering and Design reviews. You are the "First User." If an API is too hard to explain in writing, it is too hard to use. You will have the authority to push back on engineering to improve parameter naming and consistency before code hits production. You will create feedback loops between customer integration challenges and documentation improvements. What Success Looks Like Launch V1 Developer Portal: A public API doc portal (References + Guides + Changelog) is live, searchable, and accurate. Expand Coverage: 100% of public endpoints have accurate request/response examples in at least three languages Deflection Rate: You reduce "Instructional" support tickets (questions asking "how do I do X?") by 40%. Integration Velocity: Partner with Product and Engineering to drive the "Time to First API Call" down to

Responsibilities

You will own the documentation ecosystem, architecting information systems and defining content standards. Additionally, you will translate complex engineering concepts into understandable documentation for developers.