Work samples
These are examples of how I work as a Senior Technical Writer. Use these when trying to recruit me. The PDFs show the content as it was at the time of writing.
⭐️ Plan Stage Documentation Leadership
Technical writing stage lead role
2024-currently
Served as Technical Writing Stage Lead for GitLab's Plan stage, managing documentation strategy and execution across multiple product groups (Project Management, Product Planning, and Knowledge). Led comprehensive documentation improvements, including epics work items GA cleanup, UI text consistency projects, and systematic backlog management. Successfully balanced immediate feature documentation needs with strategic architecture planning for work item types evolution.
User Experience Documentation & Feature Guidance
Feature documentation and user guidance
2025
Created comprehensive documentation for linking epics feature, collaborating with Product Planning PM to develop practical use cases that increase user adoption. Drafted and implemented new section in Iterations documentation showcasing the two most likely use cases and their benefits, making the feature more accessible to users. Used AI tools efficiently while maintaining quality through expert review.
Cross-Functional UI Text & Accessibility Leadership
UX writing and accessibility improvement
2025
Improved user experience through accessible, clear interface text that enhanced usability while reducing code complexity. Modified Vue.js code to remove unnecessary step numbers from field labels and fix accessibility issues. The merge request was accepted without revisions, with the frontend maintainer noting it "removes a lot of unneeded code".
Documentation Architecture & Information Structure Innovation
Strategic documentation restructuring
2024
Led strategic documentation restructuring for work item types to reduce maintenance burden and improve scalability as GitLab expanded its product offerings. Created comprehensive epic outlining architectural changes and proposed new navigation structure to address growing complexity in work items documentation. This foundational work enables GitLab's documentation to scale effectively as the product evolves.
Style Guide Development & Process Documentation
Technical terminology standardization
2024
Created standardized guidance for describing object relationships across GitLab's expanding feature set. Developed documentation for terms like "child", "parent", "ancestor", and "descendant" to ensure consistent terminology for user comprehension and translation ease. This work was particularly important for upcoming features that allow users to relate more types of objects to one another.
MicroStrategy Cloud Platform documentation
End-user docs: infrastructure
2019
This page describes the features and infrastructure of each cloud offering within the MicroStrategy Cloud Platform. The descriptions are visibly divided in style and specificity - starting with more high-level business blurbs followed by technical details and infrastructure diagrams (prepared by a graphic designer) hidden behind expandable sections.
MicroStrategy Cloud Platform documentation
End-user docs: procedure
2019
This page provides two simple procedures for starting and stopping a cloud environment.
Straal documentation
End-user docs
2017
While working at Straal, I created their end-user documentation from scratch. It contains a mix of explanations of how the card payment ecosystem works, and how to use Straal services. It combines high-level business narrative, while remaining down-to-earth, like end-user documentation should.
Straal documentation
API reference
2017
While working at Straal, I also updated and streamlined their existing API Reference. This document is highly technical and centered around the API endpoints and request workloads served by this API.
Benerator Cumberpy
readme
2017
This is a README of my silly Python package. I wrote it in reStructuredText, because it works better than Markdown when uploading packages to the Python Package Index.