Portfolio — Technical Staff Editor

This post describes an AI-driven data visualization system built for laboratory environments, combining AWS services with machine learning pipelines. It demonstrates my comfort editing AI/ML subject matter and producing clear prose from technical authors whose primary expertise is not writing.

This post makes a technical argument for an AWS-based approach to remote clinical trial monitoring. The editing challenge was helping the author present a clear, evidence-grounded case for their approach while acknowledging its scope and limitations honestly — the same task described in the Voleon job posting.

A technically dense post on security hardening for Kubernetes clusters. This sample demonstrates that I can work fluently with highly specialized infrastructure content, preserving precision while improving structure and readability for a knowledgeable audience.

A data engineering post aimed at practitioners migrating large-scale data infrastructure. This sample shows range across the data domain — relevant to an organization where quantitative data work is central to everything.

This 158-page style guide was written and compiled for the Technical Communications team at NCBRT, the emergency management training center at Louisiana State University, where I served as Adjunct Editor for nearly eleven years. The guide covers abbreviations, capitalization, citations, grammar, numbers, punctuation, source formatting, and usage specific to emergency management and federal training contexts.

Building it required auditing inconsistencies across years of existing course materials, making judgment calls about contested usage, and writing guidance clearly enough that non-editor subject-matter experts could apply it independently. This is the kind of work Voleon describes as “developing and maintaining editorial standards for the research organization.”

This regional emergency operations plan was produced for FEMA Region 10 in preparation for a Cascadia Subduction Zone seismic event — one of the highest-consequence natural disaster scenarios in North America. The document is multi-agency, multi-author, and structured to be used operationally under crisis conditions, where clarity and precision are not abstract virtues but practical requirements.

The editing challenges were structural as much as stylistic: ensuring consistent terminology across authors, maintaining logical flow across sections written independently, and verifying that cross-references, procedural steps, and role assignments were internally coherent. This sample demonstrates that I can manage large, complex, high-stakes documents where the cost of ambiguity is real.