Technical Writing

From 2021 to 2026 I was a Technical Writer / CAD Engineer at Vantor (formerly Maxar Technologies), working with SMEs, software engineers and satellite operators to write API documentation, API specifications and UI documentation for every user level, for both commercial and government customers. I used a “docs-as-code” approach (Markdown, Docusaurus, Fern, OpenAPI and Git) for the API docs and MadCap Flare and MadCap Capture for the UI docs, and I led the team’s adoption of AI, both in how we wrote and in how customers read our docs.

Results

• Rewrote the API docs for 3 platforms and the UI docs for 5, giving them one cohesive style and user experience. Customer feedback was 100% positive.
• Cut publishing and editing time by 33% with reusable content and auto-generated content across every platform.
• Made the docs readable by AI. I added pipelines that serve the documentation to AI chatbots and agents through llms.txt files and raw Markdown, raising AI parsing accuracy from 32% to 91%.
• Brought the docs onto classified networks. I created SIPRNet and JWICS instances of government-contracted documentation sites, enabling real-time satellite-imagery support for high-value customers.

This website, as you might be able to tell, has been hand-made by me using Astro. I’ve taken great care to create a useful header with a dark mode toggle (a necessity for me), I’ve sprinkled in examples of custom formatting throughout (drop-downs, hyperlinks, iframes, dynamically loading content, a “contact me” page, etc.), and I’ve even left some easter eggs (hint: check the 404 page).

To view specific examples of my technical writing content, feel free to peruse the public links in the table below. I was the primary author for content specified in the “Primary Authored Pages” column, I created every screenshot in any UI docs, and I was a contributor and reviewer on all other pages within these websites.

* All Unclassified Private sites have been redacted. They can be discussed upon request, but cannot be exposed to data scraping. Other sites may exist but cannot be discussed.

How I work

• Docs-as-code. API and developer docs live in Markdown in Git, go through pull-request review like any other code, and publish with Docusaurus or Fern from OpenAPI specifications.
• UI docs in MadCap. Task-based help for web applications in MadCap Flare, with every screenshot captured and annotated in MadCap Capture.
• AI-ready by default. Docs that people and AI agents can both read: llms.txt, raw Markdown endpoints and MCP servers.
• Written for the customer. Everything I write is user-facing and built for customer and contractor enablement, and I fold user feedback back into the docs.
• Science background. A physics degree and a Ph.D. in engineering make me comfortable digging into the technical detail with engineers and satellite operators and turning it into plain language.

Toolkit

Docusaurus Markdown MadCap Flare MadCap Capture Fern OpenAPI GitHub VS Code Python SQL HTML Astro MCP servers Linux JIRA SAP Microsoft Office ArcGIS QGIS

Other writing

• Journalism. Long-form reporting for The Bold, CU Boulder’s student media, after graduate coursework in journalism.
• Research papers. 14 publications, including 12 peer-reviewed papers, across cosmology, HCI, biomedical engineering, physics education and virology. See the publication list.
• Teaching materials. The open-source Rock, Paper, Physics! activity booklets.