Tactical Networks Systems Engineer

We need to output HTML fragment with sections: Responsibilities, Required Qualifications, Desired Qualifications? The posting includes "Desired Qualifications #nowhiring" but then after that there is "Overview Overview ..." etc. The "Desired Qualifications" heading appears but there is no content after it? Actually after "Desired Qualifications #nowhiring" there is "Overview Overview ..." So the desired qualifications section is empty (just heading). According to rules: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we should not include Desired Qualifications section because it has no specific content. Also we should not include Pay/Schedule/Benefits unless posting actually states them. The posting includes "Posted Salary Range USD $85,950.00 - USD $134,280.00 /Yr." That's compensation info. Should we include a Pay section? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state salary range, so we can include a Pay section. However we need to check if they want Pay heading (

Pay

) with content. The content is the salary range. Also maybe they want to include that as a

. Also there is no explicit Benefits or Schedule. So we omit those. We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we will have headings: Responsibilities, Required Qualifications, Pay. Possibly also "Overview" but that's not a standard heading; but we could treat as "About the role"? The posting includes "Overview Overview Noblis and our wholly owned subsidiaries..." That's company overview. Should we include a section? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings if appropriate. The overview could be considered "About the role" or maybe "About the company". But they didn't list About the company as example; they listed About the role. However we could still include an

About the role

with the overview content. But the rule: "Prefer a few substantive sections over many thin ones." The overview is substantive. Could include as About the role. However the overview is about Noblis, not the role. Might be better to treat as "About the role"? The role description is already in Responsibilities. The overview is about company. Could be considered "About the role"? Not exactly. But we could still include it as a section; but the instruction says use those headings for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but suggests using those. I'd include an

About the role

with the overview paragraphs (Noblis description, Why Work at Noblis, Commitment to Non-Discrimination, Total Rewards). However many of those are boilerplate (EEO, etc.) which we need to remove: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we need to strip EEO, Commitment to Non-Discrimination, etc. Also "Total Rewards" section includes benefits description; but we already have Pay section; we could include Benefits? The posting includes Total Rewards describing health, life, disability, financial, retirement benefits, paid leave, professional development, tuition assistance, work-life programs. That's benefits info. According to rule: we should include Benefits section only if posting actually states them. It does state benefits. So we should include a Benefits section with that content. However we need to remove boilerplate like EEO etc. The Total Rewards section seems substantive. So we can include Benefits. Also there is "Remote/hybrid status is subject to change based on Noblis and/or government requirements." That's maybe Schedule? Not exactly schedule. Could be considered Schedule? Not really. There's no explicit schedule (e.g., full-time, part-time). So we omit Schedule. We also have "Compensation at Noblis is determined by various factors..." That's more compensation detail; could be part of Pay section. We need to preserve all substantive information, not invent or summarize away detail. So we need to include the salary range, the description of compensation factors, etc. We need to remove duplicated lines, boilerplate, legal, EEO, etc. Also remove "Posted Salary Range USD $85,950.00 - USD $134,280.00 /Yr." we keep. We need to remove "Overview Overview" duplication? The text starts with "Overview Overview Noblis and our wholly owned subsidiaries..." It seems duplicated word "Overview". We should keep the content but maybe remove the duplicate word? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Duplicated lines: maybe the word "Overview Overview" is a duplicated line? It's duplicated word within same line. We could keep just one "Overview". Safer to keep the content but maybe correct duplication? I'd keep "Overview Noblis and our wholly owned subsidiaries..." Removing one "Overview". However we must not invent or summarize away detail; removing a duplicate word is okay as it's not substantive. I'd just start with "Overview Noblis and our wholly owned subsidiaries...". Now we need to format using

for each section heading,

• for any list of duties/requirements/benefits, and

  for prose. We need to decide which content is list vs prose. Responsibilities: The responsibilities are a paragraph then a list of specific responsibilities after "The specific responsibilities of this position include, but are not limited to:" followed by a list. So we can have a

  for the introductory paragraph, then a

  • for each bullet. Required Qualifications: It's a paragraph with bullet-like options separated by periods? Actually it's: "Bachelor's Degree + 5 years of experience OR Associate's Degree + 8 years of experience OR High School Diploma + 11 years of experience. Proficiency in Microsoft Project, Word, and ExcelExperience with CANES, ADNS, and ACS systemsMust possess and maintain CompTIA Security+ CEMust be proficient in software development including security, scripting, and automationMust be proficient in system sustainment processes including cyber security remediation, patch management, and lifecycle planning for EOL/EOS hardware and software components.Must maintain certifications relevant to system sustainment and cyber security to include CompTIA Security+ CE, PMP, CCNA, ITIL, and/or Microsoft certified training in Windows Server administration.Active Secret Security ClearanceUS Citizenship". This is a run-on without punctuation. We need to parse into list items. Could treat each sentence as a list item. But we need to use
    • for any list of duties/requirements/benefits. So we can make a list. We need to preserve all substantive information; we can break into items: - Bachelor's Degree + 5 years of experience OR Associate's Degree + 8 years of experience OR High School Diploma + 11 years of experience. - Proficiency in Microsoft Project, Word, and Excel - Experience with CANES, ADNS, and ACS systems - Must possess and maintain CompTIA Security+ CE - Must be proficient in software development including security, scripting, and automation - Must be proficient in system sustainment processes including cyber security remediation, patch management, and lifecycle planning for EOL/EOS hardware and software components. - Must maintain certifications relevant to system sustainment and cyber security to include CompTIA Security+ CE, PMP, CCNA, ITIL, and/or Microsoft certified training in Windows Server administration. - Active Secret Security Clearance - US Citizenship We should keep the "OR" phrasing inside first item. Now Benefits: The Total Rewards section includes: "At Noblis we recognize and reward your contributions, provide you with growth opportunities, and support your total well-being. Our offerings include health, life, disability, financial, and retirement benefits, as well as paid leave, professional development, tuition assistance, and work-life programs. Our award programs acknowledge employees for exceptional performance and superior demonstration of our service standards. Full-time and part-time employees working at least 20 hours a week on a regular basis are eligible to participate in our benefit programs. Other offerings may be provided for employees not within this category. We encourage you to learn more about our total benefits by visiting the Benefits page on our Careers site." We need to remove boilerplate? This seems substantive. We'll keep as prose or list? It's not a list but we can make a

      . Could also list benefits as

      • . The instruction: "Use
        • for any list of duties/requirements/benefits". So we should convert benefits to a list. Let's extract list items: - health benefits - life benefits - disability benefits - financial benefits - retirement benefits - paid leave - professional development - tuition assistance - work-life programs - award programs acknowledge employees for exceptional performance and superior demonstration of service standards (maybe separate) - Full-time and part-time employees working at least 20 hours a week on a regular basis are eligible to participate in our benefit programs. - Other offerings may be provided for employees not within this category. - Encouraged to learn more about total benefits by visiting Benefits page on Careers site. But we need to preserve all substantive information; we can keep as prose if not a clear list. However the instruction says use list for any list of benefits. The benefits are enumerated in a sentence: "Our offerings include health, life, disability, financial, and retirement benefits, as well as paid leave, professional development, tuition assistance, and work-life programs." That's a list. Then there is additional info about award programs, eligibility, other offerings, encouragement to learn more. Those could be separate paragraphs. We'll do:

          Benefits

          then
          • for the core offerings, then

            for the rest. Pay section: We have salary range and compensation determination details. We'll make

            Pay

            then

            with salary range and maybe another

            for compensation factors. Now we need to ensure we don't include any heading without real content. We'll have sections: Responsibilities, Required Qualifications, Benefits, Pay. Possibly also About the role? But we already have overview content; we could incorporate overview into a section like "About the role" or "About Noblis". However the overview includes "Why Work at Noblis", "Commitment to Non-Discrimination" (which we need to remove), "Total Rewards" (we already used for Benefits). The "Why Work at Noblis" is also substantive but maybe could be part of About the role. However we already used Benefits for Total Rewards; the "Why Work at Noblis" is about culture, passion, etc. Could be included as a section like "About the role" or "Company Overview". Since we have no explicit heading for that, but we could create

            About the role

            with that content. However the rule says "Prefer a few substantive sections over many thin ones." Adding another section may be thin but it's substantive. However we already have four sections; adding a fifth may be okay. But we need to check if the overview content is duplicated elsewhere? Not really. It's about Noblis mission, culture, etc. It's substantive. We need to remove boilerplate: "Commitment to Non-Discrimination" (EEO) and "EEO is the Law | E-Verify | Right to Work". Also "Remote/hybrid status is subject to change based on Noblis and/or government requirements." That's not boilerplate but maybe schedule? Not needed