Technical Writer · Scientific Editor
Documentation grounded in domain knowledge.
I write technical documentation for software and APIs and edit scientific manuscripts for publication in peer-reviewed journals. Thirteen years and more than 2,400 edited manuscripts taught me when precision is non-negotiable and when plain language serves the reader better.
Portfolio
End-user guide for a Salesforce CRM (customer relationship management) implementation, covering record creation for accounts, contacts, cases, and Chatter posts. Numbered task-based procedures with annotated screenshots and document conventions defined up front.
View documentAPI reference for a surf conditions data service: endpoint description, path and query parameters, an example request, and a full response schema with field-level definitions. Adapted and extended from Tom Johnson's Documenting APIs course exercise.
View documentField reference covering six corrosion types for engineers in marine and infrastructure construction. Each entry gives identification cues, at-risk conditions, and mitigation options, with a quick-reference comparison table. In progress.
Coming soonAbout
I am a technical writer and scientific editor based in Toronto. My background is in bioengineering (M.S., University of Illinois Chicago) and I spent 13 years at Cactus Communications editing more than 2,400 peer-reviewed manuscripts across materials science, engineering, physical sciences, and life sciences.
That editing background shapes how I approach technical writing: I am attentive to audience calibration, information hierarchy, and the difference between what subject-matter experts assume readers know and what readers actually need. I am also a published peer-reviewed author.
Contact