The Career

I’m a Technical Writer specializing in Docs-as-Code methods and environments and Developer Experience (DX). I help connect complex engineering requirements to user success by translating raw, technical specifications into clear, impactful documentation.

I work well in Agile environments, utilizing Git-based workflows and API testing to ensure technical accuracy. My goal is to reduce support overhead and accelerate developer onboarding through precision and clarity.


The Stack

Documentation and Markup

Markdown/MDX Static Site Generators YAML Content Strategy HTML/CSS

Version Control and Workflows

Git-based Workflows Docs-as-Code PR and Code Reviews

API Documentation

OpenAPI GraphQL AsyncAPI Postman API Design & Lifecycle

Developer Tools

Command Line (CLI) VS Code JSON YAML

Project Management

Jira Confluence Agile/Scrum Engineering Collaboration

Content Quality and AI

Style Linting Style Guide Authorship Vale Prompt Engineering AI-Assisted Drafting and Review LLM Orchestration

Documentation is a product. I believe in Docs-as-Code methodologies to integrate in the engineering lifecycle. Using version control, automated style linting, and peer reviews, I can ensure that the documentation is as well-tested and polished as the software itself.


The Process

I view documentation as a high-value product, not as an afterthought. My workflow includes:

  • Active Exploration. I not only write about features, I also use them. I test APIs and run scripts locally to find the points of friction. I ask questions with the end user in mind to discover what may otherwise get overlooked during the design process.
  • Engineering Collaboration. I integrate myself into the development lifecycle and work closely with developers. I manage peer reviews through Git-based pull requests, ensuring that Subject Matter Experts (SMEs) verify the technical accuracy of the docs before they reach publication.
  • Scalable Governance. I connect industry standards with team-specific needs. I follow established guides (like Microsoft or Google), but I also author and facilitate custom technical style guides around engineering and documentation workflows. Utilizing automated style linting and Markdown templates, I ensure a consistent brand voice is maintained across the entire product.

The Human

The Editor in Chief Jack
Jack

When I’m not diving deep into Markdown or API specifications, you’ll find me engaging in:

  • Tabletop and Collaborative Gaming. I love getting deep into complex game mechanics and rules. Whether navigating a campaign as a player or reading the rulebook, gaming is a wonderful exercise in collaborative problem-solving, communication, and engagement with users.
  • Global Exploration. I’m a frequent traveler that wants to see as much of the world as possible. Visiting new countries and immersing in cultures keeps me adaptable and reminds me why localization and accessibility truly matter in documentation.
  • Coffee and Cats. I am fueled by well-crafted brews and supervised by my editor-in-chief, Jack (pictured). He’s a tough and demanding editor, but he keeps my morale high.

I bring this same curiosity and the spirit of collaboration to every team. I don’t just write guides and API docs, I also help build the rulebook for your product’s success.