I write API docs that reduce support tickets, not just word counts.
I specialize in REST API reference documentation, developer onboarding, and docs-as-code for billing infrastructure and SaaS platforms. 7 years turning complex systems into documentation engineers actually use. Recently writing about AI-augmented documentation workflows and editorial systems for developer content.
| Outcome | Metric | Project |
|---|---|---|
| Developer support tickets | ↓ 58% | Chargebee API reference rebuild |
| Time-to-first-API-call | ↓ 88% (3.2 days → 4 hrs) | Chargebee onboarding redesign |
| Docs coverage | ↑ 3× | Chargebee developer hub |
| Editorial review cycles | ↓ 40% | Internet Brands style guide |
| Endpoints documented | 160+ | Chargebee billing API |
| Help articles built from zero | 80+ | Clarity Wave help center |
| Repo | What it is |
|---|---|
editorial-systems-developer-content |
Framework for building developer content programs that compound (2025) |
ai-augmented-docs-playbook |
Practical playbook on integrating AI tools into documentation workflows (2025) |
tyra-miles-portfolio |
Portfolio site — case studies, writing samples, live demos |
api-documentation-samples |
Real writing samples: OpenAPI spec, quickstart, error reference |
documentation-style-guide |
Production-ready style guide built from scratch (adopted across 4 product lines) |
Doc tools: OpenAPI 3.1 · Docusaurus · Mintlify · ReadMe.io · Postman
Workflow: Git · GitHub · Markdown · MDX · docs-as-code · Claude · ChatGPT · GitHub Copilot
Platforms: Confluence · Notion · Intercom · Jira · Linear · Figma
Scripting: Python (lint automation, doc generation) · YAML · JSON
Open to senior remote technical writing and content roles, including API documentation, developer experience, and technical content for developer audiences. Available for full-time and contract engagements.
🌐 Portfolio · 📧 tyratech23@gmail.com · 📍 Downey, CA (Remote)