I research, write, and design technical and business communications.
Yes, that includes straight-up technical writing: Help systems, documentation, user and quick start guides, SOPs, and training materials.
It also means client/customer and internal communications: what stakeholders need to know, now, not when the documentation is updated. Product launches, release updates, client technical advisories, incident messaging, root cause analyses, internal memos. It means technically accurate but business-aware support for sales, account management, and customer services.
I've worked for a giant fintech and in small SaaS asset management startups. I'm West Coast. I'm a former magazine writer and editor who's accustomed to fighting for the attention of distracted audiences. So I use every tool available to communicate: words, illustrations, and videos, in whatever format and delivery method that will best convey the message.
Help authoring: Flare, RoboHelp, Help & Manual, FrameMaker
Multimedia: Acrobat Pro, InDesign, Photoshop, Captivate; TechSmith SnagIt, Camtasia
Web authoring/CMS: Markdown, HTML/CSS/JavaScript, WordPress, SharePoint
Marketing/CRM: Silverpop/Acoustic, Marketo, Salesforce.com
Project Management: JIRA, VersionOne/digital.ai; basic Git & GitHub
Microsoft Office: Word, Excel, PowerPoint, Visio; VBA
Most samples below come from my first years as a technical writer, in the days of BlackBerries and flip phones, when I worked as a team of one for several SaaS startups. From 2011 to 2022 I worked for the payments division of a Fortune 500 company, but am prohibited from sharing samples. I have included a link to the firm's API developer site serving one of many products I helped launch.
