Senior Advisor, Police Intelligence & Operational Integration

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 (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

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

  for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 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 (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") 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: - Company description: CTP is a privately held small business based in Herndon, VA. They provide program management services for government and private clients, deliver technical assistance programs in over 100 countries. They provide specific solutions or full lifecycle support including course and curriculum design, expert instruction, logistics support, monitoring & evaluations, knowledge management, strategic planning, program management, and staffing services. - About The Role: CTP, on behalf of Veloxxity, is seeking a Senior Advisor, Police Intelligence & Operational Integration to serve as Veloxxity's senior operational advisor and mentor to the Barbados Police Service (BPS), helping the service use Digital Horizon capabilities to strengthen intelligence, improve interdiction, advance investigations, and reduce crime. The advisor will connect police leadership, investigators, intelligence personnel, and frontline users with the Veloxxity technical team. Drawing on senior law enforcement command experience, the advisor will help BPS translate technology into effective policing practices while ensuring that operational experience directly informs the design and improvement of Digital Horizon. - What You Will Do: This is a long list of responsibilities broken into sub-sections: 1. Build a Shared Operational Approach 2. Mentor Intelligence-Led Policing and Investigations 3. Integrate Digital Horizon into Daily Police Work 4. Serve as the Operational Link to Veloxxity's Technical Team 5. Guide Operational Testing and Continuous Improvement 6. Strengthen Leadership Practices and Coordination 7. Build Sustainable BPS Capability - Principal Work Products: List of 6 items - Expected Outcomes: List of 8 items - Preferred Qualifications: What We Are Looking For - list of 4 items - Measures of Success: One sentence - Other Information: Location (Significant international travel required), Company Benefits (list), Compensation (Salary range based upon experience, but this is a mid-level role), Security Clearance (SECRET security clearance preferred, must have ability to obtain), Travel/Sponsorship (Travel Yes, Work Authorization Candidate must be a US Citizen. No sponsorships provided) - Application Procedure: Boilerplate - should be removed I need to structure this into semantic HTML with appropriate sections. Let me think about the sections: 1. About the role (or Company Overview) - could combine company description and role description 2. Responsibilities (or What You Will Do) - the main duties 3. Principal Work Products 4. Expected Outcomes 5. Qualifications (or Preferred Qualifications) 6. Measures of Success 7. Other Information (Location, Benefits, Compensation, Security Clearance, Travel/Sponsorship) But note: The rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use those standard headings where appropriate. Also: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The posting has real content for Benefits, Compensation, Security Clearance, Travel/Sponsorship. So I should include those. But "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states Benefits, Compensation (Pay), and Travel/Sponsorship (Schedule-ish). So I can include Benefits, Pay, and maybe Schedule/Travel. However, the posting says "Salary range based upon experience, but this is a mid-level role." That's not a specific salary range, but it's stated. The rule says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Salary range based upon experience" is similar to "commensurate with experience". Should I include a Pay section? The posting does have a "Compensation" heading with that text. It's not a specific range, but it's what the posting says. I think I should include it as a

  under a Pay heading, but the rule says never create Pay section unless the posting actually states them. It does state it, albeit vaguely. I'll include it but maybe combine with other info. Similarly, Benefits are listed specifically. Travel/Sponsorship is specific. I'll structure as: -

  About the role

  with company description and role description in

  -

  Responsibilities

  with the "What You Will Do" items as a list of sub-sections? But the rule says use
  • for any list of duties. The "What You Will Do" has 7 major areas, each with bullet points. I could make each major area a

    ? But the rule only mentions

    for section headings. It doesn't forbid

    , but says "use

    for section headings". I think I should keep it to

    for main sections, and within Responsibilities, use

    • for the bullet points. However, the "What You Will Do" has sub-headings like "Build a Shared Operational Approach", "Mentor Intelligence-Led Policing and Investigations", etc. Those are sub-sections. I could make them

      or just include them as bold text within list items? The rule says "use

      • for any list of duties/requirements/benefits". The duties are listed under each sub-heading. I think the best is to have a

        Responsibilities

        then for each sub-area, maybe a

        Build a Shared Operational Approach

        followed by
        • ... But that might not be semantic. Alternatively, I could make each sub-area a separate

          ? But that would be many

          s. The rule says "Prefer a few substantive sections over many thin ones." So maybe keep Responsibilities as one section with the sub-areas as nested lists? But HTML doesn't have nested headings in

          . I could do:

          Responsibilities

          • Build a Shared Operational Approach
            • Establish trusted working relationships...
            ...
          ...
          But that's nested lists. That's acceptable HTML. However, the rule says "use
          • for any list of duties/requirements/benefits". It doesn't forbid nested lists. I think that's fine. But the posting also has "Principal Work Products" and "Expected Outcomes" which are lists. They could be separate sections. "Preferred Qualifications" is a list. "Measures of Success" is a single sentence. "Other Information" includes Location, Benefits, Compensation, Security Clearance, Travel/Sponsorship. I could make separate sections for Benefits, Pay, Security Clearance, Travel. But the rule says "use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can have Benefits, Pay, Schedule (or Travel). However, "Schedule" might not be appropriate; "Travel" is more like travel requirements. The posting has "Travel/Sponsorship" with "Travel Yes" and "Work Authorization Candidate must be a US Citizen. No sponsorships provided." That could go under a "Travel & Authorization" section or similar. I'll create sections: 1. About the role 2. Responsibilities 3. Principal Work Products 4. Expected Outcomes 5. Qualifications 6. Measures of Success 7. Benefits 8. Pay 9. Security Clearance 10. Travel & Authorization But that's many sections. Some are thin. The rule says "Prefer a few substantive sections over many thin ones." So maybe combine Benefits, Pay, Security Clearance, Travel & Authorization into an "Other Information" section with sub-headings? But the rule says use

            for section headings like Benefits, Pay, Schedule. It doesn't say I must separate them, but it's an example. I think it's okay to have separate

            for each if they have content. However, "Pay" only has "Salary range based upon experience, but this is a mid-level role." That's thin. "Security Clearance" has one line. "Travel & Authorization" has two lines. "Benefits" has a list. So maybe combine into one "Additional Information" section with

            Additional Information

            and then use

            for each? But the rule says use

            for Benefits, Pay, Schedule. It's ambiguous. I think I'll follow the examples: create separate

            for Benefits, Pay, Security Clearance, and Travel (or Schedule). But Security Clearance and Travel aren't in the example list. The example list includes "Benefits, Pay, Schedule". So I'll create Benefits, Pay, and maybe Schedule for travel? But Schedule usually means work schedule. The posting has "Travel/Sponsorship". I'll create a "Travel & Authorization" section. But the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states Benefits, Compensation (Pay), and Travel/Sponsorship. So I can create those three. Security Clearance is also stated. I'll include it as a separate section or combine with Travel. Let me decide: I'll create: -

            About the role

            -

            Responsibilities

            -

            Principal Work Products

            -

            Expected Outcomes

            -

            Qualifications

            -

            Measures of Success

            -

            Benefits

            -

            Pay

            -

            Security Clearance

            -

            Travel & Authorization

            That's 10 sections. Some are thin but they have specific content. The rule says "include a section ONLY when the posting has real, specific content for it". Each has real content. So okay. Now, I need to remove boilerplate: Application Procedure, EEO statement, etc. The posting ends with "Application Procedure ... CTP is an Equal Opportunity Employer". That's boilerplate, remove. Also remove "NO PHONE CALLS PLEASE..." etc. Now, write the HTML. I'll start with About the role: combine company description and role description. Company description: "CTP is a privately held small business based in Herndon, VA. We provide program management services for government and private clients and deliver