Technical Writer – 26-038

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, E-Verify repeated, etc. But we need to keep security clearance requirement, salary range, benefits mention, etc. We need to parse the description. Key info: - Job type: FULL-TIME (maybe schedule? but schedule not given; we can include schedule if we have info: full-time). The rule: include Schedule section only if posting actually states them. It says JOB TYPE: FULL-TIME. That's schedule info. So we can include a Schedule section with "Full-time". However we must avoid filler like "not specified". It's specified. - Must possess active Secret clearance with ability to obtain TS/SCI. That's a requirement. - Competitive salary, comprehensive benefits and a company that cares! Then later Salary Range: $95K-115K. Also mention base salary and excellent benefits package. - Benefits: "competitive salary, comprehensive benefits", "excellent benefits package". Not specific details but we can include Benefits section with "Competitive salary and comprehensive benefits package" maybe but that's somewhat generic. However rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive salary, comprehensive benefits" is somewhat vague but it's actual statement. Might be acceptable. However we also have specific salary range, so we can put Pay section with "$95K-115K". Benefits section can mention "comprehensive benefits package" (though not detailed). Might be okay. - About the role: we have description: "As a growing Department of Defense Contractor, AUSGAR Technologies has an exciting opportunity for a Technical Writer to join our team of smart and innovative technical team members at NIWC PAC – Seaside in the Point Loma area of San Diego, CA. Will develop the basis for support for a new system. Create and maintain high-quality technical documentation in support of multiple programs within a fast-paced and dynamic environment. This role requires exceptional writing skills, meticulous attention to detail and the ability to effectively prioritize and manage multiple tasks simultaneously. Must be able to adapt to changing requirements and maintain a high level of performance under pressure." That's good for About the role. - Responsibilities: list of duties: Technical Documentation Development, CDRL Compliance, Style Guide Adherence, Requirements Gathering & Analysis, Multi-Program Support, Quality Assurance, Configuration Management, Adaptability, Style Guide Addendums. Also Compliance Considerations (but that's similar). We'll combine. - Requirements: Security Clearance, Experience (minimum 3 years technical writing preferably DoD/IC), Writing Skills, Software Proficiency, Communication Skills, Organizational Skills, Adaptability. - Desired Qualifications: XML-based authoring tools (DITA), Agile, multimedia training materials. Could go under Qualifications or Skills. We'll put Qualifications. - Skills: maybe list software proficiency etc. But we already have skills in Requirements. Could separate Skills section for technical skills: Microsoft Word, Adobe FrameMaker, InDesign, version control systems, XML/DITA, Agile, multimedia training. - Pay: Salary Range: $95K-115K. - Benefits: Competitive salary, comprehensive benefits, excellent benefits package. Could phrase as "Competitive salary and comprehensive benefits package". - Schedule: Full-time. We must not repeat job title. Must not include Job ID / requisition numbers as headings. The posting includes "Technical Writer - 26-038 – San Diego, CA". We should not include that as heading. We can maybe include location in About the role? Already mentioned location. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep specifics like list of documentation types: test procedures, test plans, user manuals, system documentation (SRS, SPS, CONEMP), training materials, installation guides, SOPs, white papers. Also mention CDRL compliance, DoD style guide, reference material. We need to ensure we don't lose any detail. Let's structure:

About the role

... (prose)

Responsibilities

• Create, revise and maintain technical documentation including test procedures, test plans, user manuals, system documentation (Software Requirements Specification (SRS), Software Product Specification (SPS), Concept of Employment (CONEMP)), training materials, installation guides, standard operating procedures (SOPs) and white papers.
• Ensure all deliverables meet Contract Data Requirements List (CDRL) requirements.
• Comply with the Department of Defense writing and style guide.
• Collaborate with subject matter experts (SMEs), engineers, and other stakeholders to gather information for accurate documentation.
• Support documentation requirements for multiple programs (e.g., ICADS Inc 2 and Inc 3), managing priorities to meet deadlines.
• Review and edit documentation for clarity, accuracy, consistency and grammatical correctness.
• Maintain proper version control and configuration management of all documentation.
• Adapt to changing project requirements, priorities and deadlines.
• Develop style guide addendums as needed for consistency (not a government deliverable).

Requirements

• Active Secret clearance with ability to obtain Top Secret/Sensitive Compartmented Information (TS/SCI) clearance.
• Minimum of 3 years of experience in technical writing, preferably within the Department of Defense (DoD) or Intelligence Community (IC).
• Demonstrated proficiency in writing clear, concise and grammatically correct technical documentation.
• Proficiency in using word processing software (e.g., Microsoft Word), desktop publishing software (e.g., Adobe FrameMaker, InDesign) and version control systems.
• Excellent communication and interpersonal skills, with ability to collaborate with technical and non-technical stakeholders.
• Strong organizational skills and ability to manage multiple tasks simultaneously in a high-ops tempo environment.
• Proven ability to adapt to changing priorities and requirements.

Qualifications

• Experience with Extensible Markup Language (XML)-based authoring tools (e.g., Darwin Information Typing Architecture (DITA)).
• Familiarity with Agile development methodologies.
• Experience creating multimedia training materials.

Skills

Technical skills include Microsoft Word, Adobe FrameMaker, Adobe InDesign, version control systems, XML/DITA authoring, Agile practices, and multimedia training development.

Pay

Salary range: $95K–$115K (based on qualifications, experience, skills, education, certifications and location).

Benefits

Competitive salary and comprehensive benefits package as part of total compensation.

Schedule

Full-time position.

We need to ensure we didn't include any boilerplate like EEO, E-Verify repeated. We kept mention of E-Verify? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. E-Verify is mentioned twice; it's not exactly EEO but it's a compliance statement. Might be considered boilerplate? The instruction says remove duplicated lines, but E-Verify is a statement about employment eligibility verification. It's not exactly EEO but could be considered legal boilerplate. However it's also a substantive piece? The job posting includes "We use E-Verify to electronically confirm the employment eligibility of newly hired employees." That's a statement about company practice. Might be considered boilerplate but it's not EEO. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." E-Verify could be considered legal boilerplate. Safer to remove it. We already didn't include it. We also removed "AUSGAR Technologies, Inc., an equal opportunity employer" etc. We kept "Competitive salary, comprehensive benefits and a company that cares!" but we turned into Benefits section. We must not repeat job title as heading. We didn't. We must not put Job ID/requisition numbers as headings. We didn't. We must preserve all substantive information. Did we miss any? Let's check original text for any other details: - "Will develop the basis for support for a new system." We included in About the role? Not explicitly. We said "Will develop the basis for support for a new system." Should include that. Let's add to About the role. - "Create and maintain high-quality technical documentation in support of multiple programs within a fast-paced and dynamic environment." Included. - "This role requires exceptional writing skills, meticulous attention to detail and the ability to effectively prioritize and manage multiple tasks simultaneously." Included. - "Must be able to adapt to changing requirements and maintain a high level of performance under pressure." Included. - "Technical Documentation Development: Create, revise and maintain a variety of technical documentation, including but not limited to test procedures, test plans, user manuals, system documentation (Software Requirements Specification (SRS), Software Product Specification (SPS), Concept of Employment (CONEMP), training materials, installation guides, standard operating procedures (SOPs) and white papers." We captured. - "CDRL Compliance: Ensure all deliverables meet Contract Data Requirements List (CDRL) requirements." Captured. - "Style Guide Adherence: Comply with the Department of Defense writing and style guide (provided upon request)." Captured. - "Requirements Gathering & Analysis: Collaborate with subject matter experts (SMEs), engineers, and other stakeholders to gather information necessary for creating accurate and comprehensive documentation." Captured. - "Multi-Program Support: Simultaneously support documentation requirements for several programs (i.e. ICADS Inc 2 and Inc 3), managing priorities to meet deadlines effectively." Captured. - "Quality Assurance: Thoroughly review and edit documentation for clarity, accuracy, consistency and grammatical correctness." Captured. - "Configuration Management: Maintain proper version control and configuration management of all documentation." Captured. - "Adaptability: Quickly adapt to changing project requirements, priorities and deadlines." Captured. - "Style Guide Addendums: As specific tasks may require, develop additional style guide addendums for consistency. Creation of such is not a deliverable to the Government." Captured. - "Compliance Considerations Quality Assurance: The Contractor is responsible for ensuring the quality of all deliverables meets defined Government standards." This is similar to Quality Assurance; we could add but it's duplicate. Might be okay to skip as duplicate. - "CDRL Compliance: All documentation must adhere to specified CDRL requirements." Duplicate. - "DoD Style Guide: Writing must follow the Department of Defense writing and style guide." Duplicate. - "Reference Material: All documentation must be based on and compliant with reference material provided (examples provided upon request)." Not captured. We should add a responsibility about reference material. - In Requirements: "Security Clearance: Active Secret clearance with the ability to obtain a Top Secret/Sensitive Compartmented Information (TS/SCI) clearance." Captured. - "Experience: Minimum of 3 years of experience in technical writing, preferably within the Department of Defense (DoD) or Intelligence Community (IC)." Captured. - "Writing Skills: Demonstrated proficiency in writing clear, concise and grammatically correct technical documentation." Captured. - "Software Proficiency: Proficiency in using word processing software (e.g., Microsoft Word), desktop publishing software (e.g., Adobe FrameMaker, InDesign)