Technical Communication

3+ years creating developer documentation, API references, and information architecture for Amazon SageMaker AI—delivering high-quality technical content for major feature launches.

Documentation Methodology

At AWS, I practiced a docs-as-code workflow, treating documentation with the same rigor as software engineering. My documentation process involved:

  • Source control: All documentation maintained in GitFarms (AWS internal Git), with pull request reviews, version history, and branch-based development
  • Structured authoring: Oxygen XML Editor for DITA-based content, enabling content reuse, conditional processing, and consistent information architecture
  • Code validation: Deep-diving into source code, testing examples, and working directly with engineering teams to validate every procedure and code sample
  • Continuous delivery: Documentation shipped alongside feature releases, with automated builds and publishing pipelines

Tools & Platforms

Documentation Stack

Authoring: Oxygen XML Editor, DITA, Markdown
Source control: GitFarms (Git), code review workflows
AI tools: Custom-built documentation pipelines using Claude, MCP, and Python (see AI-Powered Tools)
Analytics: SQL and Python for documentation health metrics analysis
Collaboration: Quip, Wiki, cross-team review processes

AI-Powered Tools

Beyond documentation, I designed and built AI-powered tools to automate complex workflows. These tools handled drafting, ticket resolution, and editorial review, achieving measurable time savings and consistency improvements.

View AI-Powered Tools →

Featured Projects

The following projects demonstrate different aspects of technical communication at AWS, from product how-to guides to architecture documentation and cross-functional process work:

Skills Demonstrated

Docs-as-Code DITA/XML Oxygen XML Editor Git Workflows API Documentation Developer Documentation Information Architecture AI/ML Documentation Cross-functional Collaboration Content Strategy Documentation Metrics