API Documentation Technical Copywriter Needed

I need a seasoned technical copywriter who can take our existing code-level comments, Postman collections, and early Swagger drafts and turn them into clear, developer-friendly API documentation. The audience is software engineers who will integrate our REST and WebSocket endpoints, so accuracy, concise explanations, and real-world usage examples are critical.

You’ll be working entirely remotely and will interface with our lead engineer via Slack and GitHub. Expect to receive raw JSON responses, authentication flow diagrams, and feature notes; your task is to weave these into polished reference pages and short “how-to” guides. Markdown will be the primary format, with occasional OpenAPI specs that must stay perfectly in sync with the live codebase.

Deliverables:
• A complete set of Markdown files covering endpoint references, authentication, error handling, and versioning
• Two quick-start guides that compile and run successfully with our sample repo
• Pull-request summaries that highlight any ambiguities or missing edge cases you discover during the write-up

Acceptance criteria:
• All examples compile or execute against the staging environment without modification
• Terminology aligns with the existing codebase naming conventions
• Flesch–Kincaid grade ≤ 12 while preserving technical accuracy

If you have a track record of writing API docs for developers and can demonstrate attention to detail, I’m ready to get started right away.