Skip to main content

About

I write documentation that people bet on. For eight years that meant validated laboratory systems at a GSK vaccine manufacturing site in Marietta, Pennsylvania, where I worked onsite through Alphanumeric Systems as a technical writer and computer system validation engineer.

The output: more than 100 controlled documents, thousands of pages in total. Validation plans. User requirements specifications. Risk assessments. IQ/OQ test protocols and validation summary reports. SOPs and work instructions. Change records, deviation investigations, root cause analyses, and CAPA documentation. Every one went through formal review and approval, and the set held up through internal audits and FDA inspection preparation. I also served as the site's change control coordinator, which means I ran the review pipeline other writers only submit to.

Before that I spent ten years at Lancaster General Health (Penn Medicine) supporting clinical imaging and PACS/DICOM systems, using Epic daily from its 2007 go-live and training co-workers on it. Two decades total of standing between complicated systems and the people who need to use them correctly.

Why developer documentation​

Because it is the same job with better tools. A URS is an API contract written for a different audience. A test protocol is a tutorial with signatures. Change control is a pull request with more meetings. This site is my working proof: content in Markdown, changes through pull requests, prose linted against the Google developer style guide, links checked, builds gated, deploys automated. The details are in How this site is built.

Credentials​

  • M.S., Data Analytics, Western Governors University, 2025
  • B.S., Cybersecurity and Information Assurance, Western Governors University, 2024
  • ITIL Foundation (AXELOS), 2024
  • Claris certifications at Expert level (2026): App Developer for Claris FileMaker Pro, App Developer for Claris Connect, Claris FileMaker Server Administrator
  • CompTIA A+, Network+, Security+, CySA+, PenTest+ (2024); Linux Essentials (2024)

The security stack is not decoration. It means I can document authentication flows, access models, and audit requirements without needing an engineer to explain them first.

Contact​