Technical Writer - US

Photon

About The Position

Translate complex technical concepts into clear, client‑ready documentation for developers and partners Produce and maintain API docs, SDK guides, integration walkthroughs, and FAQs Ensure docs are accurate, consistent, and aligned with product behavior and supported use cases Apply a developer-first mindset: clarity, examples, edge cases, and common pitfalls Create content that supports self-service integration and reduces support dependency Partner closely with product, engineering, and developer experience teams Intake requirements from specs, APIs, and source code—not just verbal guidance Iterate quickly based on technical reviews and feedback Follow established style guides, terminology, and information architecture End‑to‑end integration guides (getting started → advanced flows) Reference documentation (API endpoints, parameters, errors) Code samples and diagrams (where appropriate) Update and version docs alongside product releases Faster developer onboarding and time to first transaction Fewer “how do I integrate?” support questions Documentation that is publish‑ready, scalable, and reusable across teams and channels

Requirements

Proven experience as a technical writer for APIs, platforms, or developer products
Strong understanding of REST APIs, JSON, authentication flows, and webhooks
Experience documenting integration guides and reference documentation
Comfortable working from technical specs, API definitions, and source code
Able to collaborate effectively with engineering and product teams
Track record of producing clear, high-quality, externally published documentation

Nice To Haves

Prior exposure to payments, fintech, or B2B SaaS platforms a plus
Familiarity with developer portals / docs-as-code workflows (e.g., Git, Markdown, OpenAPI)

Responsibilities

Translate complex technical concepts into clear, client‑ready documentation for developers and partners
Produce and maintain API docs, SDK guides, integration walkthroughs, and FAQs
Ensure docs are accurate, consistent, and aligned with product behavior and supported use cases
Apply a developer-first mindset: clarity, examples, edge cases, and common pitfalls
Create content that supports self-service integration and reduces support dependency
Partner closely with product, engineering, and developer experience teams
Intake requirements from specs, APIs, and source code—not just verbal guidance
Iterate quickly based on technical reviews and feedback
Follow established style guides, terminology, and information architecture
End‑to‑end integration guides (getting started → advanced flows)
Reference documentation (API endpoints, parameters, errors)
Code samples and diagrams (where appropriate)
Update and version docs alongside product releases