SUPERVISORY SECURITY SPECIALIST

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules: 1. Use

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

• for lists of duties/requirements/benefits, and

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

  or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: The posting has: - Summary (description of role) - Duties (list of responsibilities) - Requirements (conditions of employment) - Qualifications (specialized experience requirements) - Education (no education substitution) - Additional Information (various details) - Benefits mention (generic federal benefits) I need to structure this into appropriate sections. The user mentioned specific section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. From the content: - "Summary" -> About the role - "Duties" -> Responsibilities - "Requirements" -> Requirements (conditions of employment) - "Qualifications" -> Qualifications (specialized experience) - "Education" -> could be part of Qualifications or separate - "Additional Information" -> various details, some could be Requirements, some Benefits, some Schedule - "Benefits" mentioned at the end but generic I should create sections only where there's real content. Let me map: 1. About the role (from Summary) 2. Responsibilities (from Duties) 3. Requirements (from Conditions of employment) 4. Qualifications (from Qualifications section) 5. Education (from Education section) 6. Additional Information (from Additional Information) - but this has many sub-points. Some are conditions of employment, some are schedule, some are benefits, etc. The Additional Information section contains: - Opt-in for resume sharing - DoD Priority Placement Program - Additional vacancies - Tentative offer rescission conditions - Federal annuitant information - ICTAP applicants - Military Spouse Preference - PPP applicants - Uncommon tour (nights, weekends, holidays) -> Schedule - Overtime/night differential -> Pay/Schedule - Relocation incentive -> Benefits - Security access requirements (SSBI, polygraph) -> Requirements - Mission Essential designation - SPeD position designation - SFPC prerequisite - Commitment statement - Benefits (generic federal benefits) I need to decide which sections to create. The rules say: include a section ONLY when the posting has real, specific content for it. Never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does mention: - Schedule: "This position is subject to work an uncommon tour, including nights, weekends, and holidays to meet mission requirements. Overtime or night differential pay and/or unusual duty hours may be required." - Pay: "Overtime or night differential pay" mentioned, but no specific pay range. - Benefits: "Certain incentives (such as Relocation) may be authorized... A relocation incentive may be authorized." Also generic federal benefits mentioned. But the rules say: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state schedule information (uncommon tour, nights, weekends, holidays). It mentions overtime/night differential pay. It mentions relocation incentive. It mentions generic federal benefits. However, the user said: "Prefer a few substantive sections over many thin ones." So maybe I should fold schedule into Requirements or Additional Information, and benefits into a Benefits section if there's specific content. Let me think about the structure: - About the role (from Summary) - Responsibilities (from Duties) - Requirements (from Conditions of employment + security clearance requirements from Additional Information) - Qualifications (from Qualifications section) - Education (from Education section) - Additional Information (remaining items like ICTAP, MSP, PPP, etc.) - Schedule (from uncommon tour mention) - Benefits (from relocation incentive and federal benefits mention) But the rules say: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state schedule and benefits (relocation incentive, federal benefits). Pay is mentioned only as "overtime or night differential pay" but no salary range. I think I'll create: 1. About the role 2. Responsibilities 3. Requirements (combining Conditions of employment and security requirements) 4. Qualifications 5. Education 6. Additional Information (for the hiring program details) 7. Schedule (for uncommon tour) 8. Benefits (for relocation incentive and federal benefits) But the user said "Prefer a few substantive sections over many thin ones." So maybe combine Schedule and Benefits into Additional Information? Or keep them separate if they have specific content. Let me check the example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Skills is not present in this posting. I'll create sections for: About the role, Responsibilities, Requirements, Qualifications, Education, Additional Information, Schedule, Benefits. But Education is very short: "There is no education substitution for this series/grade combination." That's a single sentence. Could be part of Qualifications. Similarly, Additional Information has many disparate items. Some are conditions of employment (already in Requirements), some are hiring programs (ICTAP, MSP, PPP), some are schedule, some are benefits. I think the best approach is to follow the natural sections of the posting: Summary, Duties, Requirements, Qualifications, Education, Additional Information. Then within Additional Information, extract Schedule and Benefits if they have specific content. But the user wants semantic HTML with h3 headings for standard sections. Let me map: - Summary -> About the role - Duties -> Responsibilities - Requirements (Conditions of employment) -> Requirements - Qualifications -> Qualifications - Education -> could be part of Qualifications or separate - Additional Information -> Additional Information (but this is not a standard heading; the user listed specific headings) The user said: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they gave examples, not an exhaustive list. I can use other headings if needed, but should prefer those. I'll use: - About the role - Responsibilities - Requirements - Qualifications - Education - Additional Information - Schedule - Benefits But Education is thin. Maybe merge into Qualifications. Let me draft the HTML. First, About the role: from Summary paragraph. Responsibilities: from Duties list (bullet points). Requirements: from Conditions of employment (bullet points). Also include security clearance requirements from Additional Information (SSBI, polygraph, etc.)? The Conditions of employment already includes "You will be required to obtain and maintain an interim and/or final Top Secret/SCI security clearance..." and "The incumbent is required to successfully complete a Counter-Intelligence scope polygraph on a recurring basis." Also SPeD certification requirements. So Requirements section can include all those. Qualifications: from Qualifications section (specialized experience bullets). Education: from Education section. Additional Information: the rest (opt-in, DoD Priority Placement, additional vacancies, tentative offer, federal annuitant, ICTAP, MSP, PPP). These are more about hiring process and programs. Schedule: from "This position is subject to work an uncommon tour, including nights, weekends, and holidays to meet mission requirements. Overtime or night differential pay and/or unusual duty hours may be required." Benefits: from "Certain incentives (such as Relocation) may be authorized to eligible selectees. A relocation incentive is generally a single payment intended to offset some of the relocation costs experienced by the selectee. A relocation incentive may be authorized." And the generic federal benefits paragraph. Pay: not specifically stated beyond overtime/night differential, so no Pay section. Now, I need to remove boilerplate: "Help" links, "Opens in a new window", "Learn more about federal benefits", "Review our benefits", "Contact the hiring agency", etc. Also remove duplicated lines (SPeD mentioned twice). Remove application instructions (how to apply, etc.). The posting doesn't have explicit application instructions beyond the ICTAP documentation requirement. Also remove "Additional Information Cont'd" heading. Now, write HTML. I'll start with

  About the role

  then

  for the summary. Then

  Responsibilities

  then
  • for each duty. Then

    Requirements

    then
    • for each condition of employment. Then

      Qualifications

      then

      for the intro, then

      • for each specialized experience. Then

        Education

        then

        for the statement. Then

        Additional Information

        then
        • for each point (opt-in, DoD Priority Placement, etc.) Then

          Schedule

          then

          for the uncommon tour. Then

          Benefits

          then

          for relocation incentive and federal benefits. But the user said: "never emit a heading followed by filler/placeholder text". All these have real content. Also, "Do NOT repeat the job title as a heading" - the job title is "SUPERVISORY SECURITY SPECIALIST" but it's in the summary. I won't repeat it as a heading. "do NOT put Job ID / requisition numbers as headings" - none present. Now, let's write the HTML fragment. I need to be careful to preserve ALL substantive information. Don't summarize. Let me extract the exact text. Summary: "You will serve as a SUPERVISORY SECURITY SPECIALIST in the SPECIAL PROGRAMS BRANCH of the FLEET CAPABIITIES and FORCE DEVELOPMENT DIRECTORATE of COMMANDER US FLEET FORCES COMMAND." Duties: 9 bullet points. Requirements: Conditions of employment: 15 bullet points (including the two SPeD certifications, but they are duplicated). I'll include each unique requirement. Qualifications: "To qualify for the GS-15, your resume must demonstrate at least one year of specialized experience at or equivalent to the GS-14 grade level or pay band in the Federal service or equivalent experience in the private or public sector. Specialized experience must demonstrate the following:" then 5 bullet points. Also the note about experience referring to paid/unpaid, and OPM link. Education: "There is no education substitution for this series/grade combination." Additional Information: multiple paragraphs. I'll break into list items. Schedule: "This position is subject to work an uncommon tour, including nights, weekends, and holidays to meet mission requirements. Overtime or night differential pay and/or unusual duty hours may be required." Benefits: "Certain incentives (such as Relocation) may be authorized to eligible selectees. A relocation incentive is generally a single payment intended to offset some of the relocation costs experienced by the selectee. A relocation incentive may be authorized." And the federal benefits paragraph. Now, I'll write the HTML. Note: The user said "Output ONLY the HTML fragment — no /, no markdown code fences." So just the HTML tags. Let's begin.