Head Coach -Girls Wrestling

Here's a thinking process: 1. **Analyze User Request:** - **Goal:** Reformat a job posting into clean, well-structured semantic HTML. - **Rules:** - Use `

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

• ` for lists of duties/requirements/benefits - Use `

  ` for prose - Do NOT repeat job title as heading (already shown) - Do NOT put Job ID / requisition numbers as headings - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - IMPORTANT: 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") - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Analyze the Provided Text:** Let me carefully go through the text and identify sections, headings, lists, prose, and boilerplate to remove. Text: Assignment Type SeasonalStipend Schedule2026-2027 High School Coaches Salary Schedule Placement based on years of coaching experience.BenefitsEmployee Benefits | Kent School District All coaching positions are posted as open until filled. Any applicants that apply within 5 days of initial posting are guaranteed consideration per the Coaches collective bargaining agreement. Requirements Persons applying for paid coaching positions must meet district and WIAA requirements including a valid background check. Applicants for head coaching positions must be at least 21 years of age. Applicants for assistant coaching positions must be at least 19 years of age. They must also have a valid first aid and CPR card. The following procedures must be followed to apply for paid coaching positions: Complete the KSD online application process including professional reference forms.Annually complete the WIAA general rules clinic, the WIAA-approved rule clinic for the sport being coached, and the KSD Vector Training requirements prior to the beginning of the sports season.Have successfully completed Concussion recognition and management with Return to Play Protocols training as required by Washington State Law that must be renewed every three (3) years.Have successfully completed Sudden Cardiac Arrest Awareness and Training as required by Washington State Law that must be renewed every three (3) years.Before the beginning of the third year of coaching, a member school coach (paid or volunteer) must complete a school district-approved Coaching Principles training, or complete the NFHS Coaches Fundamentals Course, or attend all sessions of the WIAA Coaches School, or other Coaches School as approved by the WIAA or the local school district. After initial completion, coaches will be required to repeat this training every three (3) yearsBuilding athletic directors will monitor the applicant pool for their open positions and contact applicants as necessary.If hired, the paid coach must read and sign the KSD Coaches Manual. About Kent School District Mission: Our mission explains our fundamental purpose as an organization. Kent School District's mission is successfully preparing all students for their futures. Vision: Our vision captures the future we seek to create for our students. Kent School District's vision is to produce graduates who are globally competitive learners. Through equitable access to high quality academic, social, and applied learning, students are ready to excel in college, careers, and in life. Values: Our core values drive our culture and answer the question, "How do we want to act, consistent with our mission, along the path toward achieving our vision?" Specific values are at the heart of our culture because they are levers that drive us towards achieving shared vision. Throughout this plan, three core values are prioritized: Equity: Student equity is ensuring that access to quality staff, courses, resources, activities, services and opportunities are provided for all students to succeed and grow based on their individual needs. Excellence: As a system and individuals, we strive for excellence through the intentional creation of student-centered and efficient actions that operate with coherence. Community: Partnership with our community prioritizes proactive involvement of those impacted by school district priorities and decision-making. Kent School District Strategic Plan Kent School District Non-Discrimination Statement Let me parse this carefully. It seems like a job posting for High School Coaches in Kent School District. I need to extract relevant parts and structure them as per rules. First, identify what to remove: - "Assignment Type SeasonalStipend Schedule2026-2027 High School Coaches Salary Schedule Placement based on years of coaching experience." This seems like metadata/header stuff. The rule says: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." Also "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This line seems like assignment type, stipend, schedule, placement - might be metadata. I'll fold into a short

  or drop if not substantive enough. But "Placement based on years of coaching experience" could be part of salary schedule. The rule says: "Prefer a few substantive sections over many thin ones. IMPORTANT: 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") and never create Pay/Schedule/Benefits sections unless the posting actually states them." So I need to check if there's actual Pay/Schedule/Benefits content. The text says: "BenefitsEmployee Benefits | Kent School District" - this seems like a section header. But then it says "All coaching positions are posted as open until filled. Any applicants that apply within 5 days of initial posting are guaranteed consideration per the Coaches collective bargaining agreement." That's application info. I need to remove application instructions per rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So I should remove the procedural application steps. Let me re-read the rules carefully: - "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" - "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." - "Preserve ALL substantive information; do NOT invent or summarize away detail." - "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." - "IMPORTANT: 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") and never create Pay/Schedule/Benefits sections unless the posting actually states them." - "Prefer a few substantive sections over many thin ones." - "Output ONLY the HTML fragment — no /, no markdown code fences." So I need to parse the text, identify real sections with specific content, and output only those as HTML fragment with h3, ul/li, p. Remove application instructions, boilerplate, etc. Let me break down the text into parts: - "Assignment Type SeasonalStipend Schedule2026-2027 High School Coaches Salary Schedule Placement based on years of coaching experience." -> This looks like metadata. I'll fold into a short

    or drop. The rule says "fold minor metadata into a short

    or drop it." I think I can include it as a

    at the beginning, but need to be careful not to create a heading for it. Maybe just a

    at the very start, but the rule says "Output ONLY the HTML fragment — no /". I can just have the relevant sections. I'll consider if this is substantive enough. "Placement based on years of coaching experience" is specific. I'll maybe put it in a

    without a heading, or fold into one of the sections. But the rule says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." So I'll put it as a

    maybe at the top, but I need to see if there's a better way. Actually, the text starts with "Assignment Type SeasonalStipend Schedule2026-2027 High School Coaches Salary Schedule Placement based on years of coaching experience." This could be considered the job title and schedule info. Since I shouldn't repeat job title as heading, and this is metadata, I'll fold into a

    . But I need to preserve substantive info. I'll maybe include it as a

    at the start, then sections. - "BenefitsEmployee Benefits | Kent School District" -> This indicates a Benefits section. But rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Does it state benefits? It says "BenefitsEmployee Benefits | Kent School District" but then doesn't list any specific benefits. It just says "Employee Benefits | Kent School District". That might be just a label, not actual benefit content. The rule says never create a section unless the posting actually states them (real, specific content). Since there's no list of benefits, just a label, I should not create a "Benefits" section. I'll skip it. - "All coaching positions are posted as open until filled. Any applicants that apply within 5 days of initial posting are guaranteed consideration per the Coaches collective bargaining agreement." -> This is application info. Rule: "Remove ... application instructions." So I should remove this. - "Requirements Persons applying for paid coaching positions must meet district and WIAA requirements including a valid background check." -> This is a "Requirements" section content. Rule: use

    for section headings (e.g. ... Requirements ...). So I can have a Requirements section with

    Requirements

    and then list items. But need to check if there's actual specific content. Yes, there are specific requirements listed later. I'll structure as a section. - "Applicants for head coaching positions must be at least 21 years of age. Applicants for assistant coaching positions must be at least 19 years of age. They must also have a valid first aid and CPR card." -> These are specific requirements. I'll include them under Requirements or maybe Qualifications. The rule mentions "Qualifications" as a possible heading. I'll decide. The text says "Requirements" then lists age and certifications. I'll make a Requirements section with those points. - "The following procedures must be followed to apply for paid coaching positions: ..." -> This is application instructions. Rule: remove. So I'll delete the entire bullet list starting with "Complete the KSD online application process..." etc. - "About Kent School District Mission: ..." then "Vision:", "Values:", "Kent School District Strategic Plan", "Kent School District Non-Discrimination Statement" -> These are boilerplate about the district. Rule: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This seems like district overview boilerplate. I need to decide if I should include "About the role" or similar