Technical writing • content architecture • applied AI
Complex systems, made usable.
I build the documentation, tools, and operating systems that help people understand technical products and help technical teams deliver them.
What would you like to explore?
Start with the capability most relevant to your need. Many projects cross more than one discipline.

API & Developer Documentation
OpenAPI and Swagger, developer portals, authentication, code samples, API testing, tutorials, and information architecture.
SINCH • ORBIS • AWS

Agentic AI & Automation
Human-reviewed agents, MCP-connected workflows, AI-assisted validation, structured automation, and tools built around real operational problems.
JOB SURGE • PATTERN PACK BUILDER • Q CLI

Documentation Strategy & Systems
Content architecture, governance, reusable templates, documentation lifecycles, analytics, findability, and durable knowledge systems.
META • AWS • T.D. WILLIAMSON

Technical Project Leadership
Discovery, requirements, stakeholder alignment, launch coordination, intake design, delivery planning, mentoring, and measurable improvement.
50+ SMES • 15 LAUNCHES • CROSS-FUNCTIONAL DELIVERY

Software Development & Prototypes
Python, Django, JavaScript, HTML/CSS, React, APIs, data models, interface prototypes, and code-adjacent tools that make ideas testable.
PYTHON • JAVASCRIPT • DJANGO • REACT • CSS
10+ years
Technical documentation
15
AWS feature launches
4-5K
API reference lines in ~4 weeks
100+
Legacy tickets closed in 2 weeks
Selected case studies
A closer look at how I investigate, build, validate, and deliver.
AWS IoT documentation
Led developer documentation across various features within AWS IoT and compute services. I coordinated requirements and reviews with more than 50 engineering, product, and technical SMEs. Worked as customer zero to test early builds, identify bugs and missing requirements, and influence implementation across approximately 15 feature launches.
- Source-informed conceptual and procedural documentation
- JSON and CLI validation
- Information architecture aligned to product workflows
- Cross-functional delivery involving 50+ SMEs
Meta knowledge system
Turned more than 20 fragmented source documents and interviews with ten SMEs into a structured 20-page wiki for a 150-person business operations organization. Created reusable layouts and governance standards for approximately 25 teams, and built an AI-powered recommendation workflow estimated to reduce manual research by three hours per user.
- Content architecture and reusable layouts
- Governance standards review and guidance
- Six-month strategy delivered in under three months
- AI-powered recommendation workflow
API documentation systems
Standardized OpenAPI and Swagger definitions across the Sinch SMS and Numbers API surface and validated code samples across seven languages. At Orbis, documented approximately 56 endpoints for an initial API launch, including authentication, JWT handling, errors, versioning, events, and try-it-out functionality.
Job Surge
Designed a local-first, human-reviewed job discovery system that searches multiple sources, verifies active listings, applies evidence-based fit rules, tracks history, and produces a decision-ready dashboard without automatically submitting applications.
Note: Private repository.
C2C Pattern Pack Builder
Building an end-to-end production tool that transforms a one-pixel source pattern into validated written instructions, countable graphs, branded documents, PDFs, listing imagery, quality checks, and a packaged Etsy deliverable.
Note. Private repositiory. The implementation demonstrates product thinking, validation logic, adaptive rendering, document generation, and workflow automation.
Well-Oiled
A full-stack technical resource planning application built with Python and Django, including secure login, ORM-backed data, documentation management, front-end forms, custom CSS, and a Google Maps JavaScript API integration.
The throughline
Whether I’m documenting an API, designing an agentic workflow, or coordinating a complex launch, my approach is the same: understand the real system, find the gaps, test the assumptions, and build something people can actually use.
