I build the systems that produce documentation.
Fourteen years in technical writing, most recently as a Documentation Engineer. These days the job is less writing pages and more designing the pipeline, the information architecture, and the tooling that produces them, then verifying the output is actually correct.
Looking for Documentation Engineer roles. Remote.
📄 writing-samples Documentation and information architecture work, 2020 to 2026. Every sample says whether I wrote it, directed it, or designed the system behind it.
🛠️ context-engineering-toolkit The working tools. A multi-stage documentation pipeline, style guides, and the architecture patterns underneath them.
Documentation systems. Multi-stage pipelines where AI handles research, drafting, and verification under direction, with review as a real gate rather than a rubber stamp. Each stage is auditable on its own, so the process can be checked instead of trusted.
Information architecture. Diátaxis restructures, content lifecycle scoring, taxonomy work, and the unglamorous business of deciding what to delete.
Docs for machines. llms.txt, MCP servers, markdown endpoints. Developers now
point AI tools at documentation before they read it themselves, and those tools
need different things than a person skimming a page.