Teacher - ACE (Accelerating Campus Excellence) - Middle School Pool

The user wants me to convert this job posting into clean semantic HTML following specific rules. Let me analyze the content and structure it appropriately. First, I need to identify the sections: - There's a "Reports to", "Salary", "Duty Days", "FLSA Status", "Locations" metadata at the top - "Transform Education..." intro paragraph - "Application Process" section - "Position Purpose" section - "Essential Duties And Responsibilities" with subsections: Instructional Excellence, Assessment and Data, Classroom and Behavior Management, Family and Community Engagement, Professional Collaboration and Growth, Additional Responsibilities - "Qualifications" with subsections: Education, Certification, Experience, Skills And Abilities - "Physical Demands and Work Environment" - Then boilerplate at the end (application link, social media, EEO statement, etc.) According to rules: - Use

for section headings - Use

• for lists - Use

  for prose - Don't repeat job title as heading - Don't put Job ID/requisition as headings - fold minor metadata into short

  or drop - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, application instructions) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no html/body, no markdown fences Let me structure this: 1. Top metadata: Reports to, Salary, Duty Days, FLSA Status, Locations - these are specific details, should be included. Could be a

  or a small list. Since they're key details, I'll put them in a

  or maybe a

  but the rule says use
  • for lists of duties/requirements/benefits. These are metadata, not duties. I'll use a

    with line breaks or a simple list. Actually, the rule says "fold minor metadata into a short

    or drop it". But salary and duty days are important. I'll include as a

    with strong labels. 2. The "Transform Education..." paragraph - this is intro prose, use

    3. Application Process - this is application instructions, which should be removed per "Remove ... application instructions". But it contains specific process details (submit verifiable student achievement data, data request sheet, etc.). The rule says remove application instructions. However, the data submission requirement is a substantive requirement for applicants. But it's part of application process. I think we should remove the application process section entirely as it's instructions on how to apply. 4. Position Purpose - this is a prose paragraph, use

    under

    Position Purpose

    5. Essential Duties And Responsibilities - this has multiple subsections with bullet points. Each subsection could be an

    but the rule says use

    for section headings. The subsections (Instructional Excellence, Assessment and Data, etc.) are sub-sections. The rule only mentions

    for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So maybe "Essential Duties And Responsibilities" is the main section (Responsibilities), and the subsections could be

    or just bolded within list items. But the rule says use

    for section headings. I think we should treat each major area as a section with

    . However, the example headings given are generic: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". The posting has "Essential Duties And Responsibilities" which maps to Responsibilities. Then within that, there are categories. I could make each category an

    but that might be too many. Alternatively, keep "Essential Duties And Responsibilities" as

    and then use

    with grouped items, maybe using for category labels. But the rule says use
    • for any list of duties/requirements/benefits. The duties are listed under each category. I think best to have one

      Responsibilities

      (or "Essential Duties and Responsibilities") and then a
      with all duties, perhaps grouped with labels. However, the categories are distinct. Let me see the rule: "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So they expect a few high-level sections. The posting has: Position Purpose, Essential Duties And Responsibilities, Qualifications, Physical Demands and Work Environment. That's four sections. I'll use

      for each of those. But "Essential Duties And Responsibilities" has subsections. I could make each subsection an

      but the rule doesn't mention

      . It says use

      for section headings. Maybe I should treat each subsection as a separate

      ? That would be many headings. The rule says "Prefer a few substantive sections over many thin ones." So better to keep as one Responsibilities section with a list that includes all duties, maybe organized with bold category headers within list items. Let me think: The duties are: - Instructional Excellence (4 bullets) - Assessment and Data (3 bullets) - Classroom and Behavior Management (3 bullets) - Family and Community Engagement (3 bullets) - Professional Collaboration and Growth (3 bullets) - Additional Responsibilities (3 bullets) That's 19 bullets. Could be one long list. But the categories are meaningful. I could do:

      Responsibilities

      • Instructional Excellence: Teach district curriculum...
      • Instructional Excellence: Employ rigorous instructional strategies...
      ...
      But that repeats category. Alternatively, use nested lists? But rule says use
      • for any list. Nested lists are okay. But the rule doesn't forbid nested lists. However, the example only shows simple lists. I think a flat list with category labels is fine. Alternatively, make each category an

        ? That would be 6 headings under Responsibilities, which might be too many thin sections. The rule says prefer few substantive sections. So I'll keep one Responsibilities section with a list of all duties, each prefixed by category. Similarly, Qualifications has Education, Certification, Experience, Skills And Abilities. That's four subsections. Could be one Qualifications section with a list. Physical Demands and Work Environment is a list of demands. Now, metadata at top: Reports to, Salary, Duty Days, FLSA Status, Locations. These are specific details. I'll include them in a

        at the beginning, maybe with labels. Salary is given: "Strategic Compensation Plan $88,000 - $100,000 Base Salary". That's a Pay section. The rule says never create Pay section unless posting actually states them. It does state salary. But the rule also says "use

        for section headings (e.g. ... Pay ...)". So I could create a Pay section. However, the salary is part of the metadata block. The rule says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." Salary is not minor metadata; it's important. But the example headings include Pay. I think I should include a Pay section with the salary range. But the metadata also includes Duty Days, FLSA Status, Locations. Those could be in a Details section or folded into a paragraph. Let me decide: I'll create a

        Position Details

        or something? But the rule only lists specific example headings. It says "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So Pay is an example. I could have a Pay section. But the posting doesn't have a separate Pay section; it's in the metadata. I'll include a Pay section with the salary. Also Schedule? Duty Days could be Schedule. FLSA Status could be in Pay or Details. Locations could be in a Locations section? But the rule says never create sections unless posting actually states them. The posting states locations. But the example headings don't include Locations. I'll fold locations into a paragraph. Better to follow the rule: "include a section ONLY when the posting has real, specific content for it". The posting has specific content for Pay (salary range), Schedule (duty days), maybe Benefits? Not mentioned. So I could create Pay and Schedule sections. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state salary and duty days. So I can create Pay and Schedule sections. However, the metadata is at the top in a block. I'll extract them. Let me structure: - Opening paragraph with the "Transform Education..." text. - Then maybe a

        Position Details

        with a

        of Reports to, Salary, Duty Days, FLSA Status, Locations. But the rule says use

        for section headings like those examples. "Position Details" is not in examples. But the rule says "e.g." meaning examples, not exhaustive. I think it's okay to have a Details section. However, the rule also says "fold minor metadata into a short

        or drop it." This metadata is not minor. I'll create a

        Position Details

        with a
        of these items. But the user might expect only the example headings. The instruction: "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should use those standard headings when applicable. The posting has Responsibilities, Qualifications, Skills (under Qualifications), Pay (salary), Schedule (duty days). Benefits not mentioned. Requirements? Qualifications covers requirements. About the role? Position Purpose could be About the role. Thus, I'll map: - Position Purpose -> About the role (or Position Purpose) - Essential Duties And Responsibilities -> Responsibilities - Qualifications -> Qualifications (includes Education, Certification, Experience, Skills And Abilities) - Physical Demands and Work Environment -> maybe Requirements? Or keep as Physical Demands. - Pay -> Pay (salary) - Schedule -> Schedule (duty days, FLSA status) - Locations -> maybe not a heading, fold into Details. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state salary and duty days. So I'll create Pay and Schedule sections. However, the metadata also includes Reports to and Locations. I'll fold those into a short paragraph at the top or into the Position Details. Let me design the HTML fragment: Start with a

        for the transform education paragraph. Then

        Position Details

        with a
        of: - Reports to: Campus Principal - Salary: Strategic Compensation Plan $88,000 - $100,000 Base Salary - Duty Days: 212 (187 + 25 ADSY days) - FLSA Status: Exempt - Locations: William James Middle School | Wedgwood Middle School | Morningside Middle School But the rule says use
        • for any list of duties/requirements/benefits. This is a list of metadata, not duties. But it's a list. I think it's okay. Alternatively, make separate Pay and Schedule sections:

          Pay

          Str