Technical Writer: Documentation, API References, Guides

I am a technical writer and turn scattered materials into documentation that both developers and regular users trust. I work directly with your code, pull requests, Postman collections, messenger conversations and short calls with engineers, and deliver clean structured text that explains not just what a function does, but why and when to apply it. My focus is developer documentation, API references, integration guides, user and admin instructions, how-to articles. Accuracy comes first for me: I verify every endpoint, parameter, response code and error message against the real product before publishing so readers don't hit a step that silently doesn't work.

You get more than just proofread text. I think through structure: what goes into quick start and what goes into reference, write in a unified tone and provide a reusable style guide. I deliver in Markdown, reStructuredText, AsciiDoc or directly into your docs-as-code pipeline, work freely with Git, OpenAPI and Swagger specifications, static site generators and diagramming tools. I add commented code examples, sample requests and responses, sequence diagrams and screenshots where they really matter, and keep everything versioned so updates come easily.

Whether you're launching a public API, introducing a new SDK or finally documenting the internal tool that lives in one engineer's head — I'll assess the scope, gather requirements from stakeholders and deliver a complete documentation package on time. Send me what you have and I'll honestly tell you what's missing and how to fill the gaps.

— Documentation for developers and quick start guides
— REST and GraphQL API references from OpenAPI/Swagger specifications
— User guides, admin guides and how-to articles
— Docs-as-code in Markdown, reST or AsciiDoc with Git
— Editing, restructuring and style guides for existing documentation