Resume

Technical Writer at FUJIFILM SonoSite, Inc. (Writing Assistance contractor)
Greater Seattle Area | Computer Software
Summary

o Fifteen years of experience writing customer-facing product documentation.
o Experienced in writing for multiple audiences: IT administrators, developers, and end-users, as well as sonographers and other users of ultrasound machines. Online help recognized as “excellent” in a product review (NetworkWorld, 2000).
o Breadth of industry knowledge: software for healthcare, medical research, customer relationship management (CRM), and network management, as well as ultrasound machines.
o Proven expertise in managing documentation projects from start to finish.
o Advanced skills in Adobe Acrobat, Adobe FrameMaker, Madcap Flare, and Office.
o Knowledgeable about updating UI text strings in localized software code bases using TFS and other tools.

Experience
Technical Writer @ Fujifilm Sonosite (2014 - Present)
Writing Assistance, Inc

Develop CSS stylesheet for WebHelp and PDF outputs from Flare source files. Contribute to user experience design related to portable ultrasound devices. Help with technical writing needs.

Technical Writer @ Microsoft Research (2013 - 2014)
Steyer Associates

* Reviewed UX workflow and text labels for sourcing tools; developed mockups and proposed text edits.
* Wrote Help content for sourcing and compliance tools.
* Delivered Help content and internal documentation via internal SharePoint sites.
* Reviewed Microsoft Research releases for geopolitical compliance.

Technical Writer @ Caradigm, a Microsoft / GE joint venture (2012 - 2013)
Idea Entity

* Wrote customer-facing documentation for Amalga V3 healthcare enterprise product line.
* Developed content model for documenting user interface modules used by administrators.
* Collaborated with other UA team members on single-source XML content files to ensure intelligent reuse.
* Worked with UX design team to provide consistent UI text and error messaging.
* Reviewed UI text strings and provided .resx file edits for check-in.
* Reviewed and provided detailed feedback on testable stories, specifications, and other developer, test, and PM materials.

Technical Writer @ Microsoft Health Solutions Group (2008 - 2012)
Idea Entity

* Wrote customer-facing documentation for medical research product (Pharos) and Amalga healthcare enterprise product at Health Solutions Group (HSG).
* Managed all stages of Pharos documentation from planning to publication.
* Assisted team with MadCap Flare tool questions.

Editor (2009 - 2010)
Professional manuscript editing services (self)

Performed structural edit and line edit for nonfiction manuscript; reviewed author changes and worked with author to resolve publisher queries; kept book on schedule. Facing the Khmer Rouge by Ronnie Yimsut (2010, Rutgers University Press). See http://rutgerspress.rutgers.edu/acatalog/facing_the_khmer_rouge.html.

Sr. Technical Writer (2006 - 2008)
Onyx Software (Consona CRM)

* Researched and led implementation of documentation plans and other best practices.
* Managed all stages of documentation projects from planning to publication.
* Wrote content for CRM end users, administrators, and developers.
* Edited content written by non-native English speakers.
* Applied topic-typing principles to completely redesign the outline of a 150-topic Help project for maximum usability.
* Developed publication procedures for MadCap Flare and other tools.
* Led efforts to standardize terminology and syntax across product documents, revamping the departmental style guide in the process.

Sr. Technical Writer (2001 - 2006)
Siemens Medical Ultrasound

* Created and maintained online help files in five languages across several software versions, despite shifting software requirements.
* Outlined and wrote a 90-page user guide for imaging software.
* Researched, outlined, wrote, and edited backwards-compatible user documentation for several ultrasound products (often simultaneously ).
* Created content modules for re-use across products, reducing translation costs.
* Interviewed clinical specialists to establish accepted terminology and expected workflow for new concepts, such as 3D imaging.
* Edited user interface text for accepted terminology and consistency; revised syntax where needed to facilitate translation.
* Coordinated documentation reviews for several simultaneous projects and resolved queries from translators.
* Learned to use new ultrasound products from hands-on experience; designed “workflow tests” to confirm my assumptions about the software’s design.
* Achieved consensus on departmental style guide.

Technical Writer (1998 - 2001)
Vixel Corporation

* Sole writer of user documentation for company products (switches, hubs, and software).
* Planned user documentation sets for new products and product releases.
* Single-sourced online help, PDFs, and printed guides for each product line.
* Wrote detailed print specifications for print vendors and fedexed with hard copies of documents; sent electronic files to print vendor’s .ftp site.
* Reviewed textual elements of user interfaces (for both the software suite and the command line interfaces for the hubs and switches) and championed consistent terminology to simplify customer’s experiences.

Technical Writer (1997 - 1998)
Boeing

Wrote procedures and documented call center processes; facilitated meetings.

Technical Editor Intern (1996 - 1997)
University of Washington Department of Bioengineering

Under direction of James B. Bassingthwaighte, edited articles submitted to the Annals of Bioengineering.

Technical Editor (1997 - 1997)
Space Labs Medical
Skills & Expertise

CRM, Medical Software, Online Help, Technical Writing, Software Documentation, MadCap Flare, RoboHelp, FrameMaker, Technical Documentation, SnagIt, Technical Communication, SharePoint, Content Management, HTML, Software Development Life Cycle, Agile Methodologies, Visual Studio, XML, MSTP, Chicago Manual, Dreamweaver, Illustrator, Microsoft Office, Pagemaker, Photoshop, Microsoft Word, Microsoft Publisher, Visio, Quadralay WebWorks Publisher, Single Sourcing, Structured Authoring, Release Notes, Manuals, User Experience, Technical Editing, Content Development, Publications, Adobe Acrobat, Web Content, Online Help Development, Editing, User Assistance, Information Architecture

Education
University of Washington (1995 - 1997)
Bachelor's of Science, Technical Communications

Specialized in biochemistry.

Recommendations
I worked with Pamela for about a year at Caradigm. We wrote and maintained a very large documentation set for a healthcare information system. The programming platform provides access to clinical data through a service-oriented architecture (SOA). In other words, the product was highly technical.

Pamela had a strong grasp of development plans across a number of feature team areas, and was a go-to resource when the team needed to consolidate intelligence. For example, when we had to change terminology across the platform--several times. Pamela owned the master taxonomy spreadsheet, without which we would have descended into utter Babel.

Aside from a solid technical product knowledge, the most remarkable talent I observed was the quickness with which she turned out material--and it was solid, accurate content. While many writers tend to overthink their feature areas; Pamela has a bias toward action and is highly productive.
Kudos to Pamela! I believe you are the first of our laid-off team to net a job, and without a break in employment. Sounds like you will enjoy it; I know you will do well.
I worked with Pamela for over a year, on a team of about a dozen writers, to document a healthcare enterprise product.

I found Pamela to be a highly skilled and observant writer. She was always prepared and up to date on issues surrounding the behavior of the features she was assigned to document. In fact, Pamela often surfaced issues before they were known by the rest of the team.

When the product was in a state of flux, Pamela played a crucial role in facilitating taxonomy discussions among UX, PMs, and writers, and drove those discussions to a resolution. She reported taxonomy decisions to her teammates in a clear and succinct manner.

One area of Pamela’s expertise was the UI modules for administrators. Pamela helped to ensure consistency across these modules by driving technical and editorial review of the UI and error message text.

Pamela is also extremely knowledgeable about MadCap Flare, the publishing tool we used for single-sourcing. Pamela was always available to research, test, and otherwise help troubleshoot issues. She also came up with ways to leverage common procedure steps using snippets.

Pamela is a quiet leader with a great sense of humor; her working style is steady and pleasant. As an editor, I appreciated her responsiveness and willingness to negotiate. Above all, she is a great collaborator. I would welcome the chance to work with her again.
I know Pamela through the Society of Technical Communication, and a casual conversation with her about some challenges I was having with Framemaker resulted in her offering to spend some time and lend me a hand. The time she spent revealed the pitfalls I was having made a difference in my success with the program. Her willingness to impart her knowledge, which I was unable to reciprocate, shows Pamela's exceptional character and desire to see those she comes in contact with succeed. Based on my impression, she's the sort of colleague I wish I'd had in my corner in all my years of planning. I highly recommend her, and hope her present or future employers are appreciative and deserving of her talents.
I worked with Pamela for almost three years in the Technical Communications department at Consona Corporation. In addition to completing assignments of the highest quality at lightening speed, she designed many templates and created our editing checklists. When it came to evaluating new tools, everyone was impressed with Pamela’s input, especially the vendor. They called her their “canary in the coalmine,” she was so detailed in her assessments. Pamela’s passion for quality documentation starts and ends with users. She is their advocate in team meetings and they are lucky to have her on their side, and I hope that someday I am lucky enough to work with her again.
In the 2.5 years that I've worked with Pamela, she's never ceased to amaze me. Pamela is self-motivated and resourceful, and attacks every task--no matter how big or small the challenge--with alacrity. She has strong analytical skills and a keen eye for detail. Her writing is impeccable: her initial drafts, in fact, rival the quality of other writers' final drafts. Pamela is just as skilled in the other phases of the information development life cycle, from requirements gathering through delivery, and her efforts demonstrate how genuinely interested she is in helping users become more efficient. Pamela has been a huge asset and inspiration for our team. Her relentless pursuit of excellence has enhanced the quality of our team and our deliverables considerably. In short, Pamela is an exceptional technical writer and editor, and I'd be happy to work with her again.
Pamela impressed me with her leadership, attention to detail, and knowledge of writing styles and standards. Pamela's attention to detail made her an excellent peer reviewer and editor. Her knowledge of writing styles and standards gave her the authority to make critical comments without seeming nitpicking or burdensome. Her leadership enabled her to contribute almost immediately to the standards steering group at our company. Pamela takes her work seriously and I believe it shows.