Technical Writer Program Manager

Amentum Corporation Technical Writer September ***3 – Present

As a technical writer at Amentum working for the U.S. Army Intelligence and Security Command (INSCOM) my assignment was developing user manuals for the Centralized Personnel Data Base (CPDB) manual. There were approximately 15-20 volumes between 20 to 80 pages that I authored without technical help or access to the users and the Program Manager did not allow me access to the Solicitation, so there were no users available for content development.

The manual had not been worked on in over five years and there was almost no content. I used my technical subject-matter expertise and writing skills used to overcome these obstacles. I will use these skills to align closely with the technical writer’s role at General Dynamics Information Technology (GDIT), particularly in reviewing intelligence products. Below is a description of my Amentum role, related to GDIT’s requirements, and describe how the experience is pertinent and transferable.

Responsibilities of a Technical Writer at Amentum (INSCOM/Intelligence Agency) for User Manuals: Content Development for User Manuals: Created clear, concise, and accurate user manuals for systems like the CPDB, a database for managing personnel data within INSCOM and applicable to other Department of Defense (DoD) and intelligence community (IC) customers. Translate complex technical processes (e.g., data entry, querying, reporting) into user guides with a step-by-step instruction for diverse audiences, including analysts, administrators, and non-technical users. There was no collaboration with subject-matter experts (SMEs). I was able to gather the information myself.

Adherence to Agency Standards and Guidelines: Ensured that manuals comply with INSCOM or IC style guides, including specific terminology, formatting, and structure as outlined in agency documentation standards (e.g., Army Technical Manual standards or Intelligence Community Directives like ICD 203). Applied appropriate classification markings (e.g., UNCLASSIFIED, SECRET, TS/SCI) to documents, following IC security guidelines to protect sensitive information.

Editing and Quality Assurance: Reviewed and edited manual content for clarity, logical flow, and grammatical accuracy, ensuring instructions are user-friendly and free of jargon unless required. Verified consistency between text, tables, graphics, and appendices (e.g., screenshots of CPDB interfaces, workflow diagrams) to enhance usability.

Research and Analytical Support: This was a high-visibility project. I researched system functionalities, workflows, and user requirements to ensure manuals reflect current processes and capabilities. Addressed complex documentation challenges, to include documenting evolving system features or integrating new security protocols.

Content Structuring and Usability: Organized content logically, using narrative structures that guides users through processes (e.g., BLUF – Bottom Line Up Front – for executive summaries and/or procedural steps for technical tasks). Used user guide screen shots with ‘red boxes’ on content requiring a user to answer the mandatory documents by inserting screen shot(s) and also inserted links for users to access DoD/Army reference information Enhanced user experience by incorporating visual aids, glossaries specific to the CPDB’s operational context.

GDIT Technical Writer Responsibilities: My Amentum experience is directly applicable to GDIT’s technical writer responsibilities, with the requirement for intelligence product development and review. I reviewed CPDB user manuals for logical flow, clarity, and adherence to INSCOM standards compared to GDIT’s requirement to review intelligence products. Both roles demand rigorous quality checks to ensure content is coherent and meets publication standards. I edited technical manuals to identify inconsistencies, improving readability, and ensuring alignment with operational goals, directly applicable to reviewing analytical reports or intelligence assessments at GDIT.

Ensured Compliance with Agency Style Guides and Terminology: Amentum Experience: Adhering to INSCOM or IC style guides and using specialized terminology (e.g., intelligence or personnel management jargon) is a core task when developing CPDB manuals. Pertinence: This experience translates seamlessly to GDIT’s requirement to enforce agency style guides and subject-matter terminology, as both roles operate within the IC’s strict documentation standards.

Edited Tables, Graphics, and Supplementary Materials: Amentum Experience: Ensured consistency between CPDB manual text and visual elements (e.g., database interface screenshots, flowcharts) aligns with GDIT’s task of editing supplementary materials for intelligence products. Pertinence: The ability to integrate and verify visual content enhances the Amentum writer’s capability to handle GDIT’s requirement for cohesive, accurate intelligence deliverables.

Verified and Applied Classification Markings per IC Guidelines: Pertinence: Directly correlates with GDIT’s need to verify classification markings on intelligence products, ensuring compliance with ICD 710 and other security standards.

Guides Teams in Researching and Addressing Analytical Challenges: Researching CPDB functionalities and addressing documentation challenges (e.g., documenting new features or resolving user confusion) involves guiding teams through complex technical issues. Pertinence: This experience equips the Amentum writer to lead GDIT teams in undertaking analytical challenges, such as clarifying ambiguous intelligence data or integrating new source material into reports.

Key Transferable Skills and Pertinence

Attention to Detail, IC Familiarity - style guides directly apply to GDIT’s IC-focused environment. Collaboration: I was able to create 1,800+ pages of content without access to incumbent personnel, SME or a statement of work (SOW). Analytical Thinking: Researching system processes at Amentum and refining analytical content at GDIT both demand critical thinking to solve complex problems. Adaptability: Both roles require agility in handling evolving requirements, such as new system updates (Amentum) or shifting intelligence priorities (GDIT).

As a technical writer at Amentum developing CPDB user manuals for INSCOM enables me to be well-prepared for GDIT’s technical writer role due to shared responsibilities in content creation, editing, compliance, and collaboration within the IC.

NoVA Technology LLC Technical Writer/Proposal Manager 2018 – 2022

Led technical writing for CenturyLink (now Lumen Corporation) on high-value proposals, including:

oNational Reconnaissance Office (NRO): Authored the $1.6B proposal, the largest in CenturyLink’s history.

oDefense Information Systems Agency (DISA) Defense Research Engineering Network (DREN): Secured a $650M recompete, CenturyLink’s largest contract.

oVeterans Affairs (VA): Contributed to a $1.9B pipeline by supporting two contract wins on the T4 NG vehicle.

Played a key role in securing CenturyLink’s largest contracts for three consecutive years, including winning both the first and second largest awards in one year.

Acted as an SME for the proposals, providing technical expertise and ensuring compliance with Request for Proposal (RFP) requirements.

MILVETS Systems Technology Technical Writer/Proposal Manager 2014 – 2017

Managed a $900M pipeline as Proposal Manager for a Service-Disabled Veteran-Owned Small Business (SDVO-SB) on the General Services Administration (GSA) Alliant Small Business (ASB) GWAC.

Directed proposal development for high-value opportunities, including:

o$400M civilian agency contract

o$250M U.S. Army contract

o$200M, $35M, and $25M Defense Intelligence Agency (DIA) opportunities

Successfully multitasked and delivered compliant submissions under tight deadlines.

Served as an SME for high-value opportunities, ensuring technical accuracy and compliance with RFP requirements.

Siemens Government Technology Technical Writer/Proposal Manager 2012

Revitalized the proposal department, reversing a record of 41 losses out of 44 submissions and winning six contracts projected to generate $230M in profit over 15 years via the GSA GWAC for Energy Savings Performance Contracts (ESPC).

Developed standardized proposal templates for technical, management, and past performance responses, streamlining the preparation of complex, 1,500+ page submissions.

Acted as an SME for the proposal department, providing technical expertise and ensuring compliance with RFP requirements.

Vizada Corporation Technical Writer/Proposal Manager 2010 – 2011

Built a new proposal department from the ground up, including a SharePoint site, for a company acquired by European Aerospace Defense Systems (EADS).

Won a $60M contract for Swift Broadband communications on the Global Hawk program for the DoD.

Documented 28 Satellite Communications (SATCOM) processes and procedures (10-30 pages each) for an international RFP.

Identified and resolved a critical RFP issue with DISA, preventing significant overpayment and briefing engineers on the solution.

Served as an SME for the proposal department, providing technical expertise and ensuring compliance with RFP requirements.

Certifications:

Shipley Proposal and Shipley Capture

Northern Virginia Community College: MS Office Suite and Certified Web Master

Education: Bachelor of Science (BS), University of Maryland

Clearance: Active TS/SCI and Yankee White Clearances

Contact this candidate