About
Technical Writer turned Documentation Engineer: 7+ years in API and developer documentation, now focused on automating the pipeline that produces it.
My differentiator isn’t only explaining software. It’s designing the information architecture, components, and workflows that keep that explanation accurate as the product changes, in docs-as-code, on ReadMe and Mintlify, with HTML, CSS, and JavaScript where the platform runs out.
“I bring the writer’s judgment about what readers need, plus the engineering habits to make it repeatable.”
What I do
With a release engineer, built CLI automation that updates API documentation on every release, so docs ship with the product instead of trailing it. Designs Git-based review and publish workflows with explicit publish/no-publish gates.
Built a Claude Code skill that turns raw drafts into publish-ready MDX, and MCP-connector agents that answer stakeholder and customer documentation questions in seconds instead of hours.
Customizes documentation UX with HTML, CSS, and JavaScript; builds reusable MDX component systems on ReadMe and Mintlify, plus a ReadMe-partnered API playground. Also works in GitBook.
REST API references, webhooks, and SDK-adjacent guides. Audits endpoints, versions, and fields against real support feedback, with Postman, Swagger/OpenAPI, and Redoc.
Git, Bitbucket, Markdown/MDX, and CI/CD pipelines: documentation moves through the same review and release discipline as code.
Writes SOPs and delivers training so engineering, product, and leadership teams can run documentation automation on their own. Managed and mentored a team of four technical writers.
Where I stand out
The question that pulled me from writing into engineering: why do the same manual steps repeat on every release, and how do we make them disappear?
Good documentation shows up in support queues and satisfaction scores, not only in page counts.
Tooling only matters if other teams can run it. I present it, document it, and train people until they don’t need me.
Experience
Toolkit
Background
Have documentation that needs to scale?