We provide IT Staff Augmentation Services!

Technical Writer Resume

2.00/5 (Submit Your Rating)

SUMMARY:

Twenty - nine years’ experience in technical writing, editing, and desktop publishing. Objective is to provide timely, accurate, polished, professional deliverables and communications which enhance impact, comprehension, clarity, and contractual compliance.

AREAS OF PERFORMANCE:

Technical Publications Management

Technical Writing

Technical Editing

Desktop Publishing

PROFESSIONAL EXPERIENCE:

Confidential

Technical Writer

Responsibilities:

  • Instituted a documentation process including editing, tracking, and version control of all TUMULT documentation.
  • Edited and re-wrote systems engineering documents such as Version Description Documents (VDDs), Installation Manuals, and Configuration Manuals to ensure correct grammar, spelling, syntax, style, flow, organization, and correct content, as well as compliance with NSA/DoD documentation standards.
  • Edited and inserted charts, tables, and graphics.
  • Maintained version control of all deliverables. Updated documents based on engineering diagrams, technical information from pamphlets/reports, and consultations with the engineers. Interviewed Subject Matter Experts (SMEs) to verify/clarify technical content of deliverables.
  • Interpreted complex information for editing and re-writing purposes.
  • Advised systems engineering staff regarding quality and effectiveness of text and graphics to communicate technical information.
  • Developed and authored “Guide to Programming to the Flexible User Interface (FUI) Application Programming Interface (API) for Intuitive project.

Confidential

Technical Writer

Responsibilities:

  • Instituted a documentation process including editing, tracking, and version control of all METAWAVE documentation.
  • Edited and re-wrote systems engineering documents such as Concepts Of Operation (CONOPs), Acquisition Logistics Support Plans (ALSPs), and Risk Management Plans (RMPs) to ensure correct grammar, spelling, syntax, style, flow, organization, and correct content, as well as compliance with NSA/DoD documentation standards.
  • Edited and inserted charts, tables, and graphics.
  • Maintained version control of all deliverables.
  • Updated documents based on engineering diagrams, technical information from pamphlets/reports, and consultations with the engineers.
  • Interviewed Subject Matter Experts (SMEs) to verify/clarify technical content of deliverables.
  • Interpreted complex information for editing and re-writing purposes.
  • Advised systems engineering staff regarding quality and effectiveness of text and graphics to communicate technical information.

Confidential

Technical Writer

Responsibilities:

  • Instituted a documentation process including writing, editing, tracking, and configuration control of all Confidential documentation.
  • Developed and authored the REDRIDGE Systems Test Plan, REDRIDGE Users Guide, and the Confidential 2006 and 2007 End Of Year Reports.
  • Edited and re-wrote systems engineering documents such as Concepts Of Operation (CONOPs), Acquisition Logistics Support Plans (ALSPs), and Risk Management Plans (RMPs) to ensure correct grammar, spelling, syntax, style, flow, and organization, as well as correct content.
  • Edited and inserted charts, tables, and graphics.
  • Interviewed Subject Matter Experts (SMEs) to verify/clarify technical content of deliverables.
  • Interpreted complex information for editing and re-writing purposes.
  • Advised systems engineering staff regarding quality and effectiveness of text and graphics to communicate technical information.
  • Re-wrote Standard Operating Procedures (SOPs) for all Confidential activities.

Confidential

Technical Writer

Responsibilities:

  • Involved in all stages of documentation—from scheduling through delivery. Worked closely with scheduler, technical leads, and program management to monitor the status and review of documents, and ensured that the documentation was completed in a timely manner. Reviewed all CDRLs and documentation Configuration Items (CIs), as well as informal documents such as briefings, working papers, and trade studies.
  • Edited and re-wrote systems engineering documents to ensure correct grammar, spelling, syntax, style, flow, and organization, as well as correct content.
  • Edited and inserted charts, tables, and graphics.
  • Interviewed Subject Matter Experts (SMEs) to verify/clarify technical content of deliverables. Interpreted complex information for editing and re-writing purposes.
  • Advised systems engineering staff regarding quality and effectiveness of text and graphics to communicate technical information.
  • Assisted authors in determining target audiences.
  • Ensured that documents “flowed” by re-writing them to improve organizational clarity and logic.
  • Formatted classification portion marking.
  • Ensured that all technical documentation complied with Confidential and customer standards, formats, and configuration management requirements. Scanned documents and modified them in Microsoft® Word.
  • Researched the Internet and Government Intranet for definitions of technical terms and proprietary markings, e.g., trademarks and copyright symbols.
  • Trained the Confidential team by presenting briefings on the process and procedures for generating CIs and non-CIs.
  • Performed Data Management (DM) including managing the Reference Library; storing, retrieving, and reporting on program documentation; maintaining a log of all program documentation for tracking compliance with Confidential contract CDRL requirements; assigning identification numbers to documents for tracking and retrieval; and establishing and maintaining CDRL and non-CDRL document templates (including appropriate template styles), filename structure, and distribution lists.
  • Developed and authored the Trailblazer Software Users Manual (SUM).
  • Researched Trailblazer system software descriptions for inclusion in the SUM.
  • Coordinated the ILS team’s efforts to develop multi-use information.
  • Coordinated software and systems engineering demos presented to ILS.
  • Developed the Enterprise21 deliverables process and briefed all Enterprise21 personnel on the process.
  • Launched a campaign to advertise the use of Technical Publications (TP) including creating advertising flyers and posters, and a TPT portfolio.
  • Designed TPT Service Request system to allow users to enter their documentation requests online.
  • Developed Enterprise21 Style Guide, Writer’s Checklist, and Enterprise21 Deliverable template. Involved in all stages of documentation—from planning through release.
  • Interviewed Subject Matter Experts (SMEs) and systems engineers to verify/clarify the technical content of deliverables.
  • Interpreted complex information for editing and re-writing purposes.
  • Assisted authors in determining target audiences.
  • Ensured that documents “flowed” by re-writing them to improve organizational clarity and logic.
  • Developed glossaries of Government acronyms and definitions.
  • Verified format of classification portion marking. Scanned and modified documents.
  • Controlled and managed documents throughout their lifecycle.
  • Ensured that all technical documentation complied with Enterprise21 and customer standards, formats, and configuration management requirements.
  • Created and maintained document/presentation templates.
  • Formatted web documents for entry into the Dynamic Object Oriented Requirements System (DOORS) database.
  • Briefed Enterprise21 management on changes in the TP process. Trained new TPT members, and managed and approved their work.

We'd love your feedback!