Hello, I'm Arnaud Hervy
I'm a technical writer working on developer-facing products: APIs, CLI tools, SDKs, and platforms. I work best where developers struggle to understand how something actually works, and where documentation needs to turn that into a usable path.
What kind of technical writer I am
I write for developers integrating an API, configuring a tool, or debugging something that is not working as expected. That often means dealing with incomplete specs, unclear behavior, and undocumented edge cases.
I focus on structure before wording: navigation, hierarchy, and the path a developer follows to reach first success. If the structure is wrong, adding more content usually makes things worse.
How I work with product and engineering
I work closely with engineers, product managers, and support to understand how a feature actually behaves, not just how it was designed.
I spend time identifying where users get blocked, what assumptions are wrong, and what needs to be explained before release.
I ask practical questions: what is the user trying to do, what must they know first, which terms are overloaded, what examples are realistic, and what failure states need to be documented.
What I work with
I work comfortably across docs-as-code and help-center environments, using tools common in developer documentation teams:
- OpenAPI, Mintlify, Markdown, Astro, GitHub, and Postman
- API references, quickstarts, authentication guides, error docs, and migration docs
- Docs architecture, content audits, terminology cleanup, and release docs