CORRECTIONAL SERGEANT - 10202026-81832

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections: - Job Information (metadata like dates, salary, location, department) - Qualifications (Education and Experience, Necessary Special Qualifications) - Overview - Responsibilities - Competencies (KSA's) - includes Competencies, Knowledges, Skills, Abilities, Tools & Equipment Rules: - Use

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

• for lists,

  for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short

  or drop - Preserve ALL substantive information; do NOT invent or summarize - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include section ONLY when posting has real, specific content — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's map the content: Job Information section: Opening/Closing dates, Salary (monthly/annually), Job Type, City/State, Department, Location of position, MVR screening, criminal background check. This is metadata. Should I include as a section? The rules say "fold minor metadata into a short

  or drop it." But salary, dates, location are substantive. However, the user said "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." This is not Job ID but job details. The example headings include "Pay" and "Schedule". The posting has Salary and Job Type (Full-Time). Could create a "Pay" section with salary, and "Schedule" with job type? But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state salary and job type. However, the example headings are suggestions. The user says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those if relevant. But the posting has "Overview" which is like "About the role". "Qualifications" is a heading. "Responsibilities" is a heading. "Competencies (KSA's)" includes multiple subcategories: Competencies, Knowledges, Skills, Abilities, Tools & Equipment. Could be a "Skills" section or "Qualifications" but Qualifications already used for education/experience. Might create a "Competencies" section. Let's decide sections: 1. Overview (from "Overview" paragraph) 2. Qualifications (from "Qualifications" with Education and Experience, and Necessary Special Qualifications) 3. Responsibilities (from "Responsibilities" list) 4. Competencies (from "Competencies (KSA's)" with sub-lists) Also, the job information metadata: Opening/Closing dates, Salary, Job Type, Location, Department, MVR, background check. Could be a "Job Details" section? But the rules say "fold minor metadata into a short

  or drop it." However, salary and dates are important. The user example includes "Pay" and "Schedule". I think we should include a "Pay" section with salary, and maybe "Schedule" with job type (Full-Time). But the posting also has location, department, etc. Could be a "Job Details" section with a paragraph. But the instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." This suggests we can include a short paragraph for metadata. However, the user also says "include a section ONLY when the posting has real, specific content for it". The metadata is real and specific. But we must avoid thin sections. Maybe combine into a "Job Details" section with a paragraph and a list? But the rules say use

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

    for prose. Metadata could be a list. Let's see: The posting has "Job Information" as a heading in the source. But we are not to repeat job title. The job title is "Correctional Sergeant" (implied). The page already shows it. So we shouldn't include job title. I'll create sections: - Overview (prose) - Qualifications (with two subsections: Education and Experience, Necessary Special Qualifications) - but we need to use

    for section headings. Could have one Qualifications section with two lists? Or separate headings? The rules say use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So "Qualifications" is a heading. Under it, we can have prose and lists. - Responsibilities (list) - Competencies (with sub-lists: Competencies, Knowledges, Skills, Abilities, Tools & Equipment) - could be a "Skills" section? But the heading "Competencies (KSA's)" is specific. Might use "Competencies" as heading. - Pay (salary) and Schedule (job type) maybe combined into "Job Details" but the example includes Pay and Schedule as separate. Since the posting states salary and job type, we can include Pay and Schedule sections. However, the posting also has location, department, opening/closing dates. Those could be in a "Job Details" paragraph. But the rules: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state salary and job type. So we can create Pay and Schedule sections. But the posting also states location, department, etc. Could be a "Location" section? Not in example. The example headings are just examples. We can create a "Job Details" section with a paragraph. I think the best is to include a "Job Details" section with a paragraph summarizing the metadata: opening/closing dates, salary, job type, location, department, MVR screening, background check. That's substantive. But the user said "fold minor metadata into a short

    or drop it." So maybe just a paragraph at the top? However, the output should be HTML fragment with sections. The user didn't say we cannot have a "Job Details" section. But they said "Prefer a few substantive sections over many thin ones." So maybe we can incorporate the metadata into a short paragraph before the sections? But the output is only HTML fragment, no requirement for order. Usually job postings have a summary at top. Let's look at the example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting has Overview (About the role), Responsibilities, Qualifications (Requirements), Competencies (Skills). It has Pay (salary) and Schedule (Full-Time). It has Benefits? Not mentioned. So we can include Pay and Schedule sections. But the posting also has "Tools & Equipment" under Competencies. That's part of KSA. I'll structure as:

    Overview

    ...

    Qualifications

    Education and Experience

    ? But rules say use

    for section headings. Not

    . So maybe keep as

    for main sections only. Subsections could be

    but not specified. The rules only mention

    for section headings. Could use

    for each sub-section? That would create many headings. Better to keep Qualifications as one section with two lists. Similarly, Competencies could be one section with multiple lists. Let's do:

    Overview

    ...

    Qualifications

    Education and Experience: ...

    • ...

    Necessary Special Qualifications:

    • ...

    Responsibilities

    • ...

    Competencies

    Competencies:

    • ...

    Knowledges:

    • ...

    Skills:

    • ...

    Abilities:

    • ...

    Tools & Equipment:

    • ...

    Pay

    Monthly: $5,151.00; Annually: $61,812.00

    Schedule

    Full-Time

    Job Details

    Opening Date: 10/20/2026 12:00AM Central Time; Closing Date: 11/02/2026 11:59PM Central Time; Location: Memphis, TN; Department: Correction; Position Location: Department of Correction, Shelby County. A Motor Vehicle Records (MVR) screening will be conducted prior to employment. This position requires a criminal background check.

    But the rules say "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." The metadata includes opening/closing dates, location, department. That's not Job ID. It's job details. Could be a short paragraph. But we already have Pay and Schedule sections. The Job Details section might be thin. However, it's substantive. Alternatively, we could include the metadata in a paragraph at the beginning of the fragment, but the user wants sections. The instruction: "Output ONLY the HTML fragment". It doesn't forbid a leading paragraph without heading. But they said "use

    for section headings". So maybe we should not have a headingless paragraph. Could wrap in a ? Not allowed. Better to include as a section "Job Details" with a paragraph. But the user said "include a section ONLY when the posting has real, specific content for it". The metadata is real and specific. So okay. Now, check for boilerplate: The posting includes "A Motor Vehicle Records (MVR) screening will be conducted prior to employment. This position requires a criminal background check. Therefore, you may be required to provide information about your criminal history in order to be considered for this position." That's part of qualifications? It's in the Job Information section. It's relevant. Also, "Qualifications" section includes "Necessary Special Qualifications" which is a list of requirements. That's good. Now, ensure we preserve ALL substantive information. Do not summarize. Let's extract each part. Overview: "The Correctional Sergeant performs correctional supervisory work of average difficulty and performs related work as required. An employee in this class supervises correctional work at a state correctional facility involving the custody, transportation, and rehabilitation of inmates, and may be assigned to work any shift. This class differs from that of Correctional Corporal in that an incumbent of the latter is responsible for acting as assistant shift supervisor or shift supervisor." Responsibilities: list of 10 items (bulleted in source). We'll make each a

    . Competencies (KSA's): Competencies: Decision Quality, Builds Effective Teams