Jobs · OTHR · California

Varsity Coach - High School Wrestling, Venture Academy, County Operated Schools and Programs

San Joaquin County Office of Education · Stockton, CA · 1 wk ago
OTHRFull-time
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. The posting has: - About The Employer (SJCOE mission) - Job Summary (knowledge, experience, abilities) - Requirements / Qualifications (detailed requirements, stipend, certifications, application materials, contact info) - Comments and Other Information (nondiscrimination policy - duplicated) 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 - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/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 /, no markdown code fences Now, let's structure: 1. About the Employer - there's a paragraph about SJCOE mission. This could be "About the Employer" or "About the Organization". The rule says use headings like "About the role", but "About the Employer" is not listed. However, the rule says "e.g." so it's not exhaustive. I'll use

    About the Employer

    with a

    . 2. Job Summary - this contains knowledge, experience, abilities. Could be "Job Summary" or "About the Role". The rule says "About the role" as example. I'll use "Job Summary" as heading since that's what the posting uses. 3. Requirements / Qualifications - this is a long section with many details. It includes: - Looking for hard worker willing to build program - Work alongside Athletic Director - Practice/meet locations - Knowledge of rules, experience preferred - Schedule: M-TH daily, plus Fridays and Saturdays - Knowledge of injuries, coaching techniques, child psychology - Ability to work in multi-ethnic setting - Instill teamwork, commitment, discipline - Paid stipend position with Venture Academy - NFHS coaching certification online classes (cost responsibility of coach) - Required documents: 3 letters of recommendation (within 3 years), resume, letter of introduction attached to EdJoin application - Hard copies/faxes not acceptable - Contact for assistance: phone number - CPR/First Aid and Concussion certification preferred but not necessary prior to employment - Fingerprint clearance and TB test required - Contact info for Jim Sells This is a mix of requirements, qualifications, schedule, pay (stipend), benefits? Not really benefits. There's a stipend mentioned, so maybe "Pay" section? But it's a stipend position, not detailed pay. The rule says never create Pay section unless posting actually states them. It says "This is a paid stipend position with Venture Academy." That's a pay mention. But not detailed. Could include in Requirements/Qualifications or separate "Compensation" section. The example headings include "Pay". I'll include a "Compensation" or "Pay" section with that info. Also schedule: "Ability to meet with team each day M-TH and conduct practices or manage meets. There will also be meets and some practices on Fridays and Saturdays." That's schedule info. Could be "Schedule" section. But the rule: never create Pay/Schedule/Benefits sections unless posting actually states them. The posting does state schedule (M-TH, Fridays, Saturdays) and pay (paid stipend). So I can create those sections. However, the posting also has "Requirements / Qualifications" as a heading. I'll break it down into multiple sections: "Requirements", "Qualifications", "Schedule", "Compensation", "Application Requirements", "Contact Information". But the rule says prefer a few substantive sections over many thin ones. So maybe combine. Let's think: The user wants semantic HTML with h3 for section headings. The examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I'll create: - About the Employer (from "About The Employer") - Job Summary (from "Job Summary") - Requirements (from "Requirements / Qualifications" but split) - Qualifications (maybe combine with Requirements) - Schedule (from schedule details) - Compensation (stipend) - Application Requirements (documents, certifications, background checks) - Contact Information (Jim Sells) But the rule: include section ONLY when real, specific content. All have content. Also need to remove duplicated nondiscrimination policy (appears twice). That's boilerplate EEO, remove. Also remove "Comments and Other Information" heading and the nondiscrimination text. Also remove "Letter of Introduction (Cover Letter)Letter(s) of Recommendation (3 Professional Letters of Recommendation - Signed by Author)Resume" - that's application instructions, but it's part of required documents. I'll include in Application Requirements. Also remove "If you have trouble attaching your documents, please call 209-468-9189 for assistance." That's application instruction, but could be part of contact. Now, let's write HTML. I'll start with

    About the Employer

    then

    ...mission...

    Then

    Job Summary

    with
      of bullet points? The job summary is prose with semicolons. Could be a paragraph or list. The rule: use
      • for any list of duties/requirements/benefits, and

        for prose. The job summary is a list of knowledge/abilities. I'll make it a list. Similarly, Requirements/Qualifications: many bullet points. I'll parse the text. Original Job Summary: "Knowledge of rules and regulations of sport; successful coaching experience and/or active participation in sport preferred; Ability to meet with team each day M-TH and conduct practices or manage meets. Knowledge of care and prevention of sports injuries, coaching techniques and child adolescent psychology; Demonstrated ability to work in a multi-ethnic setting; Demonstrated ability to instill teamwork, commitment and discipline." That's a list of items separated by semicolons. I'll make each a list item. Requirements/Qualifications section has multiple paragraphs. I'll break into logical groups. Let's outline: 1. About the Employer 2. Job Summary 3. Requirements 4. Qualifications (maybe combine with Requirements) 5. Schedule 6. Compensation 7. Application Requirements 8. Contact Information But the rule says "Requirements" and "Qualifications" are separate example headings. The posting has "Requirements / Qualifications" as one heading. I'll split into "Requirements" and "Qualifications" if distinct. However, the content mixes both. I'll keep as "Requirements & Qualifications" or just "Requirements". The example headings include both. I'll use "Requirements" and "Qualifications" as separate sections if content allows. Looking at content: "Looking for a hard worker who is willing to put in the time to build a program and provide a fun, engaging environment with the students." That's a requirement. "Work alongside the Athletic Director to create a vision for the program and can effectively communicate to players, parents, and other coaches, while also demonstrating the ability to handle administrative tasks in collaboration with the Athletic Director." That's a duty/responsibility. "The team and coaching staff will have the opportunity to practice in our on-campus designated wrestling practice room, while meets are held in the school’s gymnasium." That's facility info. "Knowledge of rules and regulations of sport; successful coaching experience and/or active participation in sport preferred; Ability to meet with team each day M-TH and conduct practices or manage meets. There will also be meets and some practices on Fridays and Saturdays." This repeats job summary but adds Fridays/Saturdays. "Knowledge of care and prevention of sports injuries, coaching techniques and child adolescent psychology; Demonstrated ability to work in a multi-ethnic setting; Demonstrated ability to instill teamwork, commitment and discipline." Repeats job summary. "This is a paid stipend position with Venture Academy." Compensation. "Coach must also complete required NFHS coaching certification online classes – some of which cost money and are the responsibility of the coach to handle on their own time." Certification requirement. "Three Letter(s) of Recommendation (within the last three years), Resume, and Letter of Introduction must be attached to your EdJoin application to be considered. Hard copies and faxes are not acceptable. If you have trouble attaching your documents, please call 209-468-9189 for assistance." Application requirements. "Valid CPR/First Aid certification, and Concussion certification preferred, but not necessary prior to employment." Certification preferences. "Selected candidates must pass fingerprint clearance and provide current TB test results." Background check. "For additional information, please contact: Jim Sells, Venture Academy Athletic Director 209-227-2287 jsells@sjcoe.net" Contact. Thus, I'll create sections: - About the Employer - Job Summary - Responsibilities (maybe for the duties like work alongside AD, build program) - Requirements (knowledge, experience, abilities) - Schedule (M-TH, Fri, Sat) - Compensation (paid stipend) - Certifications & Training (NFHS, CPR/First Aid, Concussion) - Application Requirements (documents, application process) - Background Checks (fingerprint, TB) - Contact Information But that's many sections. The rule: prefer a few substantive sections over many thin ones. So combine where appropriate. I'll combine Requirements and Qualifications into one "Requirements & Qualifications" section with list items. Schedule separate. Compensation separate. Certifications & Training separate. Application Requirements separate. Contact separate. But the example headings don't have "Certifications & Training" or "Application Requirements". However, the rule says "e.g." so we can use other headings. But they said use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those if possible. But we can add others if needed? The instruction: "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those. I'll try to map. - About the Employer -> About the role? Not exactly. But "About the Employer" is fine. - Job Summary -> About the role? Could be "About the Role". But the posting has "Job Summary". I'll use "Job Summary". - Responsibilities: there are some duties: "Work alongside the Athletic Director to create a vision for the program and can effectively communicate to players, parents, and other coaches, while also demonstrating the ability to handle administrative tasks in collaboration with the Athletic Director." Also "Looking for a hard worker who is willing to put in the time to build a program and provide a fun, engaging environment with the students." That's more of a requirement. I'll put duties under Responsibilities. - Requirements: knowledge, experience, abilities. - Qualifications: certifications, education? The posting doesn't have formal education requirements. It has certifications preferred. Could be "Qualifications". - Schedule: explicit schedule. - Pay: stipend. - Benefits: none mentioned. - Skills: maybe "Skills" for coaching techniques, child psychology, etc. But the rule: never create Pay/Schedule/Benefits sections unless posting actually states them.

Similar jobs