Quality Assurance Technical Writer
Resume:
VICTOR KING
Houston, TX *****
POSITION DESIRED Senior Technical Writer
EDUCATION
Graduate Studies, English University of Houston, 1986. Completed course work for MA in English but did not complete thesis. Taught English two semesters as Teaching Assistant.
BA, English University of Houston, 1983. Minor in French.
OVERALL WORK EXPERIENCE
Project Management Throughout my career as a Technical Writer, I have:
* Worked under minimal supervision.
* Created and managed documentation development schedules.
* Created documents from “scratch.”
* Edited new and existing documentation.
* Prioritized multiple assignments as needed.
* Worked directly with subject-matter experts and other team members.
* Gathered information by using the product being documented.
* Followed corporate standards.
* Tested the accuracy of the documentation against the final product.
Hardcopy Documentation Following corporate documentation standards defined in templates, I used FrameMaker to produce various types of hardcopy documentation. Using the defined attributes of the templates, I formatted each source file as I composed it. Despite the restrictions imposed on format, I was responsible for determining such matters as content, organization, style, and presentation. I was also responsible for setting up the “book” file for every multiple-file document I produced. Book files are used to coordinate documents that have multiple source files. Whenever possible, I used electronic cross-references (instead of hard-coded references) because FrameMaker updates them automatically when the document is regenerated.
The documents I created contained numerous graphical images that were processed and imported using such applications as PhotoShop, MS Photo Editor, Hijack, and Snagit. Most of the graphics required editing, cropping, or conversion to other formats.
Each hardcopy document I produced was submitted for technical and editorial review, multiple times if possible.
I also used Word to produce and maintain User Guides, Functional Specifications, and other documents.
Training Manuals I created and maintained numerous Training Manuals (and other procedural documents such as Installation and Implementation Guides) with clear learning objectives, step-by-step descriptions of procedures, and student exercises supported by relevant graphics. Documents intended to accompany projector presentation were structured accordingly.
Documents were created or maintained for the following clients:
* Exxon
* BMC Software
* Open Solutions
* Schlumberger
Online Help I used WebWorks combined with FrameMaker to produce Windows-based context-sensitive online Help systems. This approach enables the writer to use one set of source files for both hardcopy documentation and online Help. As the hardcopy documentation is written using FrameMaker, context IDs are inserted in the text that link to corresponding points in the user interface. The FrameMaker source files are converted to HTML using WebWorks. The resulting HTML output files are then placed in the Help folder of the software package. When a user clicks a Help button on the interface, the Help system is invoked and the corresponding HTML documentation is positioned for viewing.
I used RoboHelp with Word to produce Windows-based context-sensitive online Help systems. This approach is similar to the WebWorks approach but displays Help in pop-up windows and requires source files in Word format. Using RoboHelp also requires the creation or importation of all Help text, graphics, and hypertext links.
Time-sensitive Documents I produced many “time-sensitive” documents such as Technical Bulletins, which are often given the highest priority and must be completed as soon as possible. I produced many such time-sensitive documents in a timely fashion by stopping work on other projects, quickly gathering information from the appropriate sources, documenting the issue using predefined templates, and conducting quick reviews of the finished document. Finalized documents were then converted to PDF format and posted on the company Web site.
HTML Authoring and Conversion I created HTML documents (such as User Guides and Technical Bulletins) to post on company Web sites and to document applications with browser-based interfaces. Some of the documents were produced using native HTML and HTML authoring tools (such as DreamWeaver), while others were produced by converting FrameMaker and Word source files to HTML format.
PDF Conversion I converted documents such as User Guides and Technical Bulletins to PDF format by using Acrobat Distiller. To accomplish this, I defined a postscript printer, printed the document specifying postscript output, and used Distiller to convert the postscript file to a PDF file. Converted documents were then posted on the company Web site.
SPECIFIC WORK EXPERIENCE
Contract Technical Writer Schlumberger 05/2010 – 11/2010. Converted, reformatted, and updated oil exploration training manuals from A4 to A5 format. Used the latest versions of FrameMaker, Word, and Adobe Professional to produce smaller but highly effective manuals.
Staff/Contract Technical Writer Open Solutions (previously “Bisys”) 04/2004 – 04/2010. Initially, I worked for 9 months as a contract Technical Writer. Then, I was hired by the client company and worked 5 years, 3 months as a staff Technical Writer. Wrote various documents (such as user guides, reference guides, release bulletins, and customer surveys) for client use on the Open Solutions corporate intranet.
* Gathered information for documentation by:
– Reviewing technical specifications.
– Interviewing subject matter experts.
– Reviewing government regulations.
– Researching relevant information on the Internet.
* Conducted reviews and solicited information (with deadlines) throughout the development cycle.
* Produced from “scratch” many bulletins from 5 to 50 pages, and several manuals from 300 to 800 pages.
Staff Technical Writer PentaSafe, 04/2000 – 07/2002. Wrote hardcopy documentation and online help for software. Created and maintained user guides, reference manuals, installation guides, release notes, and functional specifications.
* Created Documentation Development Plans to specify deliverable documents and to provide a development schedule with milestones.
* Gathered information for documentation by:
– Interviewing Software Development, Quality Assurance, and Product Support representatives.
– Operating the software from prototype through completion.
– Evaluating the product through Usability Testing.
* Conducted reviews and solicited information (with deadlines) throughout the product development cycle.
* Produced from scratch hardcopy documents 300-800 pages in a development period of 5 months.
* When hardcopy documents were finalized, converted them to HTML to be posted on the company Web site.
Staff Technical Writer BMC Software, 03/1993 – 04/2000. Wrote and maintained hardcopy documentation and online help for software. Created and maintained user guides, reference manuals, installation guides, release notes, white papers, and functional specifications.
* Created documentation development plans to specify deliverable documents and to provide a development schedule with milestones.
* Gathered information for documentation by:
– Interviewing software development, quality assurance, and product support representatives.
– Operating the software product from the time of first availability (prototype) through completion.
– Evaluating the product through usability testing.
* Conducted reviews and solicited information (with deadlines) throughout the product development cycle
* Produced from “scratch” several hardcopy documents as long as 300-800 pages in a development period of 6 months
* When hardcopy documents were finalized, I converted them to HTML to be posted on the company Web site.
* Developed online Help using RoboHelp.
Contract Technical Writer Exxon, 03/1989 – 11/1992. Wrote and maintained user guides and reference manuals for Computer Operations center.
* Interviewed Computer Operations personnel regarding their job responsibilities.
* Observed the performance of all computer operation procedures normally conducted.
* Inspected the physical console of all relevant computer and peripheral devices.
* Documented all computer operation procedures according to job title.
* Produced from “scratch” and maintained several user guides based on the job titles of Computer Operations. personnel ranging from 150 to 400 pages long.
* The development period for each manual ranged from 2 to 6 months.
* Used Word for Windows version 2 to produce all manuals.
SOFTWARE/HARDWARE USED
Technical Writing Tools I have used the following software and hardware tools to produce documentation:
Software
Hardware
* Word for Windows (through Version 2007)
* Macintosh Computers
* FrameMaker (through Version 9)
* Personal Computers
* RoboHelp
* iSeries (AS/400)
* Webworks
* Mainframe systems
* Adobe Acrobat Reader and Distiller
* Various printers
* DreamWeaver, FrontPage
* Adobe Professional
* Visio
* Snagit
* PhotoShop
* MS Photo Editor, Hijack, Paint
* Excel
* PowerPoint
* Access
* Documentum
* Terminal Emulators for AS/400 & OS/390
* Lotus Notes
* OS/400 Panel Groups
* TSO (OS/390)
Experience with Environments I have worked in and created documentation for the following computer environments:
* Windows
* Unix
* HTML
* MQSeries (middleware)
* iSeries (AS/400)
* OS/2
* Client/Server
* DB2
* iSeries Navigator
* MVS
1 of 4
Contact this candidate