Technical writer. Regulated systems, APIs, docs-as-code.
For eight years I wrote the controlled documentation for validated laboratory systems at a GSK vaccine manufacturing site: validation plans, requirements specifications, risk assessments, test protocols, SOPs, change records, and root cause investigations. More than 100 documents and thousands of pages, every one through formal review and approval, and the set held up through internal audits and FDA inspection preparation.
Then I learned Git and recognized the whole thing. Document control is docs-as-code with heavier tooling: one source of truth, reviewed changes, reasons attached to every revision, history that never lies. Now I write developer-facing documentation on the modern toolchain, with the discipline the regulated world beat into me.
j-arndt.github.io is my portfolio and my working proof. It runs like a production documentation project: Markdown in a public repo, every change through a pull request, and CI that lints prose with Vale against the Google developer style guide, checks structure and links, and fails the build on any broken reference.
Three entry points, depending on what you are hiring for:
| You need | Read |
|---|---|
| API documentation | FileMaker Data API reference, built on a hand-authored OpenAPI 3.1 specification |
| Tutorials and onboarding | Qdrant in Docker: a first vector search |
| Conceptual and architecture writing | Anatomy of an audit trail |
The short version of the pivot is an essay: Change control was docs-as-code before Git.
- Eight years as a technical writer and computer system validation engineer, onsite at a GSK vaccine manufacturing site through Alphanumeric Systems
- Ten years supporting clinical imaging and PACS/DICOM systems at Lancaster General Health (Penn Medicine), using Epic daily from its 2007 go-live
- M.S. in Data Analytics and B.S. in Cybersecurity and Information Assurance, Western Governors University
- ITIL Foundation; CompTIA A+, Network+, Security+, CySA+, and PenTest+; Linux Essentials; Claris certifications at Expert level (App Developer for Claris FileMaker Pro, App Developer for Claris Connect, Claris FileMaker Server Administrator)
The security and data credentials are not decoration. They mean I can document authentication flows, access models, audit requirements, and data pipelines without waiting for an engineer to translate.
Reach me at [email protected] or on LinkedIn. Lancaster, Pennsylvania, working remote.