ALL-SOURCE ANALYST AND PRODUCTION

We need to output HTML fragment with sections only when there is real specific content. We have sections: About the role, Responsibilities, Qualifications (maybe split into Required and Preferred?), Benefits, Pay (Target Salary Range). Also maybe "Details" includes salary and benefits. We need to follow rules: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to output only HTML fragment, no /, no markdown fences. We need to decide which sections to include. We have: - About the role: paragraph describing role. - Responsibilities: list of duties. - Qualifications: required and preferred. Could be combined under Qualifications with sub-lists? The rule says use

  • for any list of duties/requirements/benefits. So we can have a Qualifications section with two sub-lists: Required Qualifications and Preferred Qualifications. Could also separate into Requirements and Skills? But we can just have Qualifications. - Benefits: there is a Benefits Statement with list of benefits. - Pay: Target Salary Range: $112,000 - $179,000. Also mention overtime, shift differential, discretionary bonus. That's specific content, so we should include Pay section. - Schedule: not mentioned. No schedule info. So we should not include Schedule. - Requirements: maybe we could have Requirements section separate from Qualifications? But we already have Qualifications. The instruction list includes Requirements as possible heading. But we can combine. We need to avoid filler like "commensurate with experience". Not present. We need to remove boilerplate: EEO, application statements, etc. Also remove "About Peraton" paragraph? The instruction says preserve ALL substantive information; do not invent or summarize away detail. The "About Peraton" is company overview; is that substantive? It might be considered boilerplate but it's about the company. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Peraton" is not explicitly listed as boilerplate to remove, but it's generic marketing. However, we might keep it as part of "About the role"? Actually there is a separate "About The Role" heading after the company description. The "About Peraton" paragraph is likely considered company overview, not required for the job posting. The instruction says preserve ALL substantive information; do not invent or summarize away detail. The company overview might be considered substantive? Usually they'd want to keep it? But the instruction about sections: use headings for About the role, Responsibilities, etc. They didn't list "About the company". So maybe we should omit the "About Peraton" paragraph because it's not a section heading we are supposed to use. However, they said preserve ALL substantive information; do not invent or summarize away detail. If we drop it, we are losing information. But maybe they consider that as boilerplate that can be removed? Not explicitly listed. However, typical job posting cleanup often removes the company overview. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not say remove company overview. So we should keep it. But where to put it? Could be a

    before sections. There's no heading for it, but we can just output a paragraph. Thus final HTML: start with a

    containing the About Peraton paragraph. Then

    About The Role

    with paragraph. Then

    Responsibilities

    with
    • ... each responsibility. Then

      Qualifications

      with maybe two subheadings? But we cannot add extra headings not in list? The instruction only says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow the pattern. Could we include

      for Required and Preferred? Not specified. Safer to keep Qualifications as one section with two

      lists, each preceded by a

      indicating Required Qualifications and Preferred Qualifications. That's acceptable. Then

      Benefits

      with
      • list of benefits. Then

        Pay

        with paragraph containing salary range and additional compensation info. We must not include Schedule. We must not include any filler like "commensurate with experience". Not present. We need to ensure we preserve all substantive information from the posting: Let's extract. About Peraton paragraph: "Peraton is a next-generation national security company that drives missions of consequence spanning the globe and extending to the farthest reaches of the galaxy. As the world's leading mission capability integrator and transformative enterprise IT provider, we deliver trusted, highly differentiated solutions and technologies to protect our nation and allies. Peraton operates at the critical nexus between traditional and nontraditional threats across all domains: land, sea, space, air, and cyberspace. The company serves as a valued partner to essential government agencies and supports every branch of the U.S. armed forces. Each day, our employees solve the most daunting challenges that our customers face. Visit peraton.com to learn how we're keeping people around the world safe and secure." About The Role paragraph: "Peraton is looking for a skilled All-Source Analyst to support USCYBERCOM J2 intelligence production at Fort Meade, MD. You will conduct multi-source analysis to assess, interpret, forecast, and explain national security issues, producing finished intelligence products that directly inform USCYBERCOM leadership and the broader Intelligence Community. This is a high-visibility role where your analysis will reach General Officer and Flag Officer audiences." Responsibilities list (bullet points): - Conduct all-source analysis from multiple intelligence disciplines to assess, interpret, forecast, and explain national security issues and cyber threats - Research, evaluate, and deconflict single-source classified reporting, technical intrusion data, finished intelligence, and open-source information - Categorize and characterize cyber threats and malware to identify trends and changes in adversary tactics, techniques, and procedures (TTPs) - Produce intelligence products adhering to ICD 203 standards, requiring minimal corrections from DIA analytic reviewers - Provide all-source JIPOE support to offensive and defensive cyber operations (OCO/DCO) planning and execution - Develop and present intelligence briefings and slides to USCYBERCOM staff up to General Officer/Flag Officer level - Establish and maintain communications with IC counterparts, USCYBERCOM service components, DHS/NCSD, CERTs, and Information Assurance Centers - Produce bulletins and briefs on TTP changes and technical trends in cyber threats directed at DoDIN and U.S. critical infrastructure - Support cyber-related exercise scenario development, white cell participation, and role-playing activities - Respond promptly to J2 and USCYBERCOM staff Requests for Information (RFIs) Qualifications Required: - Active Top Secret/Sensitive Compartmented Information (TS/SCI) clearance with Polygraph required - 12+ years of relevant experience, including work within the last 2 years. - Master's degree in a related field, or a Bachelor's plus 5 additional years of senior-level experience (17 years total). - Meet the DOD 8140 requirements for All-Source Analyst (Advanced). - Working knowledge of all-source analytic concepts, IC/DoD classification guidelines, and structured analytic techniques - Demonstrated ability to produce timely, logical, and concise analytic reports, assessments, and briefing materials in Microsoft Office formats - Proficiency evaluating and synthesizing multiple sources of information, recognizing nuances and resolving contradictions - Strong verbal and written communication skills with demonstrated grammar proficiency - Understanding of intelligence collection capabilities and limitations across technical sensors and HUMINT sources - Fort Meade, MD (primary duty location); CONUS and OCONUS travel may be required as mission dictates Preferred Qualifications: - Experience with Tripwire Analytic Capability, Intellipedia, Palantir, MIDB, SURGE, or CyberCOP - Familiarity with Target Knowledge Base, Cyber Threat Matrix, AMHS, WISE, Network Knowledge Base, FoxTrail, CENTAUR, ispace, or Pathfinder - Experience entering validated entity information into MIDB or SURGE - Background in cyber threat analysis, malware characterization, or DoDIN defense - Experience producing products in accordance with ICD 203, 206, 208, and 209 standards Details: includes Target Salary Range: $112,000 - $179,000. Also statement about salary determination, overtime, shift differential, discretionary bonus. Benefits Statement: list of benefits. We need to include Benefits section with list: medical, dental, vision, life, health savings account, short/long term disability, EAP, parental leave, 401(k), paid time off (PTO) for vacation, and company paid holidays. Also note that full listing can be viewed at URL. Should we include the URL? It's substantive. Probably include as part of benefits list? Could be a

        after list. Pay section: include salary range and additional compensation info. We must not include application statements, EEO, etc. Now construct HTML. We'll start with a

        for About Peraton. Then

        About The Role

        ...

        Then

        Responsibilities

        with each
        • . Then

          Qualifications

          maybe we include a

          for Required Qualifications heading? Could use but not heading. We'll just put a

          Required Qualifications:

          then
          . Then similarly for Preferred. Alternatively, we could have two sections: Requirements and Skills? But we have both required and preferred. The instruction list includes Requirements and Skills as possible headings. Could split:

          Requirements

          for required qualifications, and

          Skills

          for preferred? But preferred includes experience and familiarity, not exactly skills. Might be better to keep Qualifications. We'll do:

          Qualifications

          Required Qualifications:

          ...

          Preferred Qualifications:

          ...
          That preserves info. Then

          Benefits

          with each benefit. After list, maybe a

          for URL:

          For a full listing of available benefits, visit https://www.careers.peraton.com/benefits.

          But we must not add extra tags like ? It's allowed; it's HTML. The instruction didn't forbid anchors. It's fine. Then

          Pay

          Target Salary Range: $112,000 - $179