2026-2027 SY - Teacher - Social Studies; Free Rent/Utilities - Secondary

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 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: Title: Teacher – Social Studies - Secondary Work Location: Thoreau Middle Work Hours: 7.5 hours/Day Contract Length: 194 Days Minimum Salary: $60,633.00 Maximum Salary: $84,868.00 Supervisor: Principal General Job Description: (prose) Essential Duties and Responsibilities: (list of items grouped under subcategories: Planning and Preparation, Creating an Environment for Learning, Teaching for Learning, Professionalism) Additional Duties And Responsibilities: (list) Qualifications: (prose) Physical Requirements: (prose) Equipment/Technology Handled: (prose) Work Environment: (prose) Terms of Employment: (prose) I need to structure this into sections. The user mentioned headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But I should only include sections that have real content. From the posting, I can see: - General Job Description -> could be "About the role" - Essential Duties and Responsibilities -> "Responsibilities" - Additional Duties And Responsibilities -> could be part of Responsibilities or separate - Qualifications -> "Qualifications" - Physical Requirements -> could be "Requirements" or part of Qualifications - Equipment/Technology Handled -> could be "Skills" or "Requirements" - Work Environment -> could be "Work Environment" or "Schedule" - Terms of Employment -> includes salary, contract length, PSLF, transcript requirement -> could be "Pay" and "Schedule" and "Benefits" But the rules: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state salary range, contract length, work hours, PSLF program. So I can include Pay and Schedule sections. Benefits: PSLF is a benefit, but it's mentioned in Terms of Employment. Could include a Benefits section. But the user says "Prefer a few substantive sections over many thin ones." So I should combine where appropriate. Let me plan sections: 1. About the role (General Job Description) 2. Responsibilities (Essential Duties and Additional Duties) 3. Qualifications (Qualifications, Physical Requirements, Equipment/Technology) 4. Work Environment (Work Environment) 5. Pay (Salary range) 6. Schedule (Work Hours, Contract Length) 7. Benefits (PSLF) But note: The posting has "Terms of Employment" which includes salary, work calendar, PSLF, transcript requirement. I could split. Also, there is metadata: Work Location, Supervisor. Could fold into a short

  at top or in About the role. The user says: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So I can include a brief introductory paragraph with location, hours, contract length, supervisor, salary range? But salary range might go to Pay section. Better: Create a short

  with key metadata: location, hours, contract length, supervisor. Then sections. Let me structure:

  Work Location: Thoreau Middle. Work Hours: 7.5 hours/Day. Contract Length: 194 Days. Supervisor: Principal.

  Then sections. But the user says "use

  for section headings". So I'll use

  for each section. Now, for Responsibilities: The essential duties are grouped into subcategories. I could either list all as a single list, or preserve subcategories. The rule: "Use

  • for any list of duties/requirements/benefits". It doesn't forbid subheadings within a section. But the heading levels: only

    for section headings. Could use

    for subcategories? The user didn't specify, but they said "use

    for section headings". Might be okay to use

    for subcategories, but to be safe, I could incorporate subcategories as part of list items or use nested lists. However, the example in the user message doesn't show subheadings. I think it's fine to use

    for subcategories within a section, but the instruction says "use

    for section headings". It doesn't forbid other headings. But to keep it simple, I'll make each subcategory a separate list with a bold label? Or just include the subcategory as a list item with strong text? The rule: "Use

    • for any list of duties/requirements/benefits". I can do:
      • Planning and Preparation: Demonstrates knowledge of content, Design of coherent instruction, ...
      ...
      But that might be messy. Better to have separate lists for each subcategory, each preceded by a

      with the subcategory name? Or use

      ? I think using

      is acceptable as it's semantic HTML. The user didn't explicitly forbid it. However, they said "use

      for section headings". That might imply only h3 for headings. But they didn't say "only h3". I'll use h4 for subcategories within Responsibilities. Alternatively, I can flatten the list: include all duties as a single list, but that loses structure. The posting has clear subcategories. I'll preserve them with h4. Let me check the instruction again: "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." It doesn't mention subheadings. But it's common to have subheadings. I'll use

        for subcategories within Responsibilities. Now, for Qualifications: The posting has "Qualifications:" paragraph, then "Physical Requirements:", "Equipment/Technology Handled:", "Work Environment:", "Terms of Employment:". I could make separate sections: Qualifications, Physical Requirements, Equipment/Technology, Work Environment, Pay, Schedule, Benefits. But that's many thin sections. The user says "Prefer a few substantive sections over many thin ones." So I should combine. I'll create: - About the role (General Job Description) - Responsibilities (Essential Duties and Additional Duties) - Qualifications (Qualifications, Physical Requirements, Equipment/Technology) - Work Environment (Work Environment) - Pay (Salary range) - Schedule (Work Hours, Contract Length) - Benefits (PSLF) But Terms of Employment also includes "All applicants must upload copies of official transcripts...". That's an application requirement, not a benefit. Could be part of Qualifications or a separate note. The user says remove application instructions. "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So the transcript upload requirement is an application instruction, should be removed. Also "Terms of Employment: Salary and work calendar established yearly by the district." That's generic. The salary range is given at top. So I'll include salary range in Pay section, contract length in Schedule, PSLF in Benefits. Now, let's write HTML. First, a paragraph with metadata:

        Work Location: Thoreau Middle. Work Hours: 7.5 hours/Day. Contract Length: 194 Days. Supervisor: Principal.

        Then sections. Section 1: About the role

        About the role

        The Secondary teacher will provide guidance and instructional experiences that are academically and developmentally appropriate for students. The teacher is held accountable to the New Mexico Teacher Competencies and Domains. The teacher will also deliver State and District curriculum and provide equal educational opportunities for all students.

        Section 2: Responsibilities

        Responsibilities

        Essential Duties

        • Planning and Preparation: Demonstrates knowledge of content; Design of coherent instruction; Setting Instructional Outcomes; Demonstrating knowledge of resources; Demonstrating knowledge of Students; Designing of Student Assessment.
        • Creating an Environment for Learning: Creating an environment of respect and rapport; Organizing physical space within learning environment; Establishing a culture for learning; Managing classroom procedures; Managing student behavior.
        • Teaching for Learning: Communicating with students in a manner that is appropriate to their culture and level of development; Using questioning and discussion techniques to support classroom discourse; Engaging students in learning; Assessment in instruction; Demonstrating flexibility and responsiveness.
        • Professionalism: Communicating with families; Participating in a professional community; Reflecting on teaching; Demonstrating professionalism; Growing and developing professionally; Follow board policies and administrative rules and regulations.

        Additional Duties

        • Manage time appropriately
        • Maintain accurate and complete records of grades and attendance as required by the school district
        • Report progress or lack thereof to parents in a timely manner
        • Attend and participate in faculty, professional meetings, educational conferences, and teacher training workshops
        • Complete duties (hall, bus, etc.) as assigned
        • Leave adequate preparations for a substitute
        • Take precautions to protect equipment, materials, and facilities
        • Actively and appropriately participates and collaborates in school teams/committees
        • Support district initiatives
        • Demonstrate public relations skills
        • Use and apply appropriate conflict resolution skills
        • Use diagnostic data to improve instructional programs
        • Be available to parents, students, administration and peers outside the school day
        • Attend and sponsor extracurricular activities
        • Report suspected child abuse and neglect
        • Complete Safe Schools training as directed by the District
        • Be responsible for students on field trips
        • Act as a good role model within the context of the school
        • Supervise educational assistants, practicum students, student teachers, and high school vocational lab/volunteer students
        • Follow district and school procedures
        • Accept other responsibilities as deemed necessary by the principal
        Section 3: Qualifications

        Qualifications

        A BA degree, valid New Mexico teaching license with endorsements as needed. Such alternatives to the above qualifications as the Board may find appropriate and acceptable.