Documentation and Data Delivery Specialist

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting includes description about company, role, responsibilities, requirements, preferred attributes, schedule, benefits, location, travel, relocation assistance, position contingent upon award of contract, etc. We need to preserve all substantive info, not invent. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Thank you for your interest..." intro and closing lines? Those are boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The intro "Thank you for your interest in employment with Torch Technologies." is not exactly those categories but could be considered boilerplate? It's not EEO, but it's generic thank you. Might be considered part of the posting but not substantive? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The intro is not substantive about the job; it's a generic thank you. Likely we should drop it. Similarly the closing "Thank you for your interest in Torch Technologies." also drop. Also "Applying To Torch Technologies Only those candidates invited for an interview will be contacted..." is application instructions, drop. Also EEO statement drop. Also "Torch Technologies, Inc. participates in E-Verify..." drop. Also "If you are a qualified individual..." drop. We need to keep: company description (employee-owned, Great Place To Work, etc.) maybe as About the role? Actually "About the role" heading is for role description, not company. Could use "About the role" for role summary. Could also include company info under About the role? Might be okay. But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide which sections to include based on content. We have: - Role description: "Torch Technologies is seeking a motivated Documentation and Data Delivery Specialist to support the development, management, transfer, and delivery of complex customer-required documentation and presentations. The ideal candidate will possess experience working across both Linux and Windows systems, with strong proficiency in Microsoft Office products, including Word, Excel, and PowerPoint. This individual will work closely with engineers to create professional, accurate, reader-friendly customer products and ensure deliverables are appropriately packaged, transferred, and delivered. The ideal candidate will possess excellent communication skills, both oral and written, and the ability to work effectively in a collaborative team environment. The candidate must also be flexible and willing to support general administrative activities as organizational and mission needs dictate." That's a mix of responsibilities and requirements. We can split: About the role (summary), Responsibilities (list), Requirements (list), Qualifications (maybe education), Skills (maybe technical), Benefits, Schedule. We have responsibilities list: "Some Of The Primary Responsibilities Will Include Documentation Development & Formatting: Design, develop, edit, format, and maintain professional customer documentation, reports, spreadsheets, presentations, and other deliverables using Microsoft Word, Excel, and PowerPoint. Engineering Team Collaboration: Work closely with engineers and technical personnel to collect, organize, refine, and present technical information in clear, accurate, and reader-friendly customer products. Cross-Platform File Management: Create, organize, manipulate, archive, unarchive, transfer, and maintain files and documentation across Windows and Linux environments. Customer Product Delivery: Package, validate, and deliver complex customer-required documentation and presentations in accordance with project, customer, and organizational requirements. Document Quality Assurance: Review documentation and presentations for completeness, consistency, formatting, readability, and accuracy prior to customer delivery. Data and File Transfer Support: Support the secure movement and management of documents, data packages, and associated files between Linux and Windows systems. Administrative Support: Perform general administrative tasks in support of the organization, including assisting with travel coordination and arrangements for engineers and analysts." We have requirements list: "Job Requirements US Citizenship. Bachelor’s Degree or equivalent experience. Related experience can be substituted in lieu of a degree. Experience using Linux and basic Linux terminal commands. Ability to perform basic Linux and Windows file-system operations, including file creation, navigation, copying, moving, organizing, archiving, and unarchiving. Experience and proficiency working in Windows environments. Strong experience using Microsoft Office products, including Microsoft Word, Excel, and PowerPoint. Demonstrated ability to design, develop, format, and deliver professional, customer-ready, and reader-friendly products using Microsoft Word, Excel, and/or PowerPoint. Ability to work closely with engineers and technical personnel to develop, refine, package, transfer, and deliver complex customer documentation and presentations. Must be flexible and willing to perform general administrative duties, including assisting with travel planning and coordination for organizational engineers and analysts. Strong written and verbal communication skills. Ability to work effectively within a diverse team environment and maintain attention to detail while managing multiple customer deliverables. Must have an active security clearance or the ability to obtain and maintain a security clearance." Preferred Attributes: "Preferred Attributes Bachelor’s degree in English, mathematics, science, engineering, or a related technical discipline. Extensive Linux terminal experience and demonstrated expertise with Linux command-line tools. Python programming knowledge and expertise. Experience automating routine file-management, documentation, data-processing, or delivery activities using Python or Linux scripting tools. Experience supporting technical documentation, engineering deliverables, data packages, or customer-facing products in a secure environment." Schedule: "Schedule: M-F; 8-5 Work Location: Customer-site Travel: Yes, up to 10% Relocation Assistance Available: No Position Contingent Upon Award of Contract: No" Benefits: "Benefits Torch Technologies is proud to offer a stable and professional work environment, a competitive salary, and an excellent, comprehensive benefit package including: ESOP participation, 401(k) match, medical, dental, vision, life insurance, short-term disability, long-term disability, flexible spending accounts, Health Saving Accounts and Health Reimbursement Accounts, EAP, education assistance, paid time off, and holidays." Pay: Not explicitly stated; they mention competitive salary but no numbers. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. They do state schedule (M-F; 8-5) and benefits (list). Pay not given specific number, just "competitive salary". That is vague; rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "competitive salary" is similar to placeholder; we should not create Pay section. So omit Pay. We have Schedule: we have explicit schedule M-F; 8-5. Also work location, travel, relocation assistance, position contingent upon award of contract. Those are not schedule but could be included under Schedule section? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only those headings allowed. We cannot add other headings like Work Location, Travel, etc. We need to incorporate that info somewhere else, maybe within About the role or Responsibilities? But we must preserve ALL substantive information. We cannot drop work location, travel, relocation assistance, position contingent upon award of contract. We need to embed them somewhere within allowed sections. Perhaps we can add them to About the role paragraph (since it's about the role). Or we could add them to Responsibilities? But they are not responsibilities. Better to add to About the role description. Thus About the role will include: company description, role summary, plus schedule details, work location, travel, relocation assistance, position contingent upon award of contract. But we must not repeat job title as heading. Already not. Now we need to decide which sections to include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. Possibly also Qualifications (education) separate from Requirements? The posting has Bachelor’s Degree or equivalent experience; also Preferred Attributes includes Bachelor’s degree in specific fields. Could treat Qualifications as education/degree requirements. Requirements could be experience, skills, clearance. Skills could be technical proficiencies (Linux, Windows, MS Office, Python, etc.). But we must not invent sections that are thin. Let's see content: - Requirements list includes: US Citizenship, Bachelor’s Degree or equivalent experience, related experience can be substituted, Linux experience, Linux terminal commands, Windows file-system ops, Windows proficiency, MS Office experience, ability to design/develop/deliver using MS Office, ability to work with engineers, flexibility for admin duties, strong written/verbal communication, ability to work in diverse team, attention to detail, active security clearance or ability to obtain. - Preferred Attributes list includes: Bachelor’s degree in English, math, science, engineering, or related technical discipline; extensive Linux terminal experience; Python programming knowledge; experience automating routine tasks using Python/Linux scripting; experience supporting technical documentation in secure environment. We could treat Requirements as mandatory, Preferred Attributes as Qualifications? Or Qualifications as education/degree? But we already have degree in Requirements. Might be okay to have Requirements include all mandatory, and Qualifications include preferred attributes (education, Linux, Python, etc.). However we need to avoid duplication. Alternatively, we could have Requirements (mandatory), Qualifications (preferred), Skills (technical proficiencies). But we need to ensure each section has substantive content. Let's propose: - About the role: company description, role summary, schedule, work location, travel, relocation assistance, position contingent upon award of contract. - Responsibilities: the bullet list of primary responsibilities. - Requirements: mandatory job requirements (US Citizenship, degree or equivalent experience, Linux experience, Windows file-system ops, Windows proficiency, MS Office experience, ability to design/develop/deliver using MS Office, ability to work with engineers, flexibility for admin duties, strong written/verbal communication, ability to work in diverse team, attention to detail, active security clearance or ability to obtain). - Qualifications: preferred attributes (Bachelor’s degree in specific fields, extensive Linux terminal experience, Python programming knowledge, experience automating routine tasks using Python/Linux scripting, experience supporting technical documentation in secure environment). - Skills: maybe we could list technical skills: proficiency in Microsoft Office (Word, Excel, PowerPoint), Linux and Windows systems, file management, documentation development, etc. But that overlaps with Requirements and Qualifications. Might be thin. Could omit Skills section if content would be thin. However we have many technical skills already covered. The instruction: Prefer a few substantive sections over many thin ones. So we could omit Skills if it would be thin. But we need to ensure we don't lose substantive info. The technical skills are already in Requirements and Qualifications. So we can skip Skills. - Benefits: list of benefits. - Schedule: we have schedule M-F; 8-5. Also we could include work location etc but we already placed them in About the role. So Schedule section will just have the schedule. Now we must ensure we don't create sections with filler like "not specified". We have real content for each. Now produce HTML fragment:

About the role

Torch Technologies is a 100% employee-owned, Certified Great Place To Work and named Best Places to Work in Huntsville/Madison County, headquartered in Huntsville, AL. The team provides superior research, development, and engineering services to the Federal Government and Department of War. As one of the nation’s top 100 defense companies, services directly support the men and women who serve the country. Corporate mission: “Lighting the Pathway of Freedom”. As a Certified Evergreen ESOP, committed to grow and sustain the company for the next 100 years.

Torch Technologies is seeking a motivated Documentation and Data Delivery Specialist to support the development, management, transfer, and delivery of complex customer-required documentation and presentations. The ideal candidate will possess experience working across both Linux and Windows systems, with strong proficiency in Microsoft Office products, including Word, Excel, and PowerPoint. This individual will work closely with engineers to create professional, accurate, reader-friendly customer products and ensure