Curriculum vitae · 2026
Profile
I turn sprawling technical knowledge into documentation that developers can find, trust and act on.
Twelve years across editorial, product writing and docs leadership. I build the structures behind good pages: content models, style systems, review workflows and the habits that keep them healthy. I am looking to lead a documentation or content design team inside a platform company that treats docs as part of the product.
Selected work
Reference pages were organised by endpoint, which meant newcomers had to know the answer before they could find it. I mapped the most common jobs and restructured the reference so each one starts from a task.
ResultSupport now links to docs pages instead of rewriting answers by hand.
Terminology drifted between teams and releases. I wrote a lean style guide with a controlled vocabulary, then wired it into pull request linting so writers and engineers see guidance where they work.
ResultOne vocabulary across the console, docs and error messages.
Working with backend engineers, I audited the platform's error catalogue and rewrote each message to name the cause, the likely fix and a link to deeper guidance.
ResultThe catalogue became a template later adopted by two other squads.
Experience
Capabilities
Education
Dissertation on plain-language instructions in technical manuals.
Journey mapping and research methods applied to documentation.
Writing and structuring content for assistive technologies.
Contact
Write to hello@orinyonder.example
Happy to share writing samples and a portfolio walkthrough. References available on request.