Technical writing: turning complex ideas into clear, compelling documentation.
I write and structure documentation for APIs, SDKs, internal tooling, and user-facing product guides. Your engineers ship faster; your customers get answers faster.
Specialties
API docs • Guides • Tutorials
Tools
Markdown • OpenAPI • Git
Outcome
Less friction, fewer tickets
Documentation audit snapshot
ExampleTop fixes
Before
“Where do I get my API key?”
“Why is this endpoint returning 401?”
After
Clear auth section + examples
Troubleshooting with copy/paste fixes
Need docs that match how developers actually build? I can plug into your repo and ship PR-based docs.
Flexible engagements: one-off docs, monthly retainers, or a documentation overhaul.
Reference, auth guides, pagination, errors, rate limits, examples.
Step-by-step flows, onboarding, troubleshooting, release notes.
Navigation, doc sets, style guides, consistency across pages.
A selection of technical writing samples that demonstrate my ability to explain complex concepts clearly, accurately, and with the end user in mind.
A “first successful request” flow with auth, minimal setup, and common error fixes.
View sample →
Method-by-method reference with parameters, return values, examples, and edge cases.
View sample →
“If you see X, do Y” guidance with decision trees, logs, and known limitations.
View sample →
“Our API docs went from ‘good luck’ to a clean quickstart + reference. Support tickets dropped noticeably.”
— Product Lead
“PR-based docs made it easy for engineering to review. The structure is now consistent across the site.”
— Engineering Manager
Tell me what you’re building and what “done” looks like. I’ll reply with next steps and a rough estimate.
Typical turnaround
Small updates: 2–5 days • New sections: 1–2 weeks
What helps most
Repo access, a sample request, and who the audience is.