Jobs · OTHR · Virginia

26-27 Lacrosse Coach

St. Catherine's School · Richmond, VA · 1 mo ago
On-siteOTHRTemporary
We need to output HTML fragment with sections: About the role? Not present. Responsibilities? We have Essential Responsibilities. Requirements? Yes. Benefits? The posting says "Benefits No benefits are included with this position". That's a statement but it's essentially saying no benefits. According to rule: never create Benefits section unless posting actually states them. It states "Benefits No benefits are included with this position". That is stating there are no benefits. Should we include a Benefits section? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Benefits: "No benefits are included with this position". That is stating them (i.e., stating there are none). Should we include a Benefits section with that content? The rule says "Prefer a few substantive sections over many thin ones." Also "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')". Here the content is "No benefits are included with this position". That's specific content (states none). So we could include a Benefits section with a

stating that. However, we might consider that it's essentially a statement of no benefits, which might be considered filler? But it's not placeholder like "N/A". It's a definite statement. I'd include Benefits section. Pay: Expected Salary Range: $2,500 - $3,500 based on position. That's specific. So include Pay section. Schedule: Typical practice times are from 3:45 pm - 5:30 pm on weekdays. Also season runs from late-February through early May. That's schedule info. So include Schedule section. We also have Supervisor etc. Might be metadata; we can fold into a short

or drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a short

for supervisor etc? But they said prefer few substantive sections. Might combine metadata into a

under maybe About the role? But we don't have About the role. Could create a

with supervisor and position status etc. However, they said "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 we can include a

for supervisor and position status etc. But we need to decide if we want a separate section for that. Probably better to include a short

after the heading? But we shouldn't create a heading for metadata. So we can just include a

containing that info. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We'll include those that have content. We have Responsibilities (Essential Responsibilities). We'll make

Responsibilities

then
  • items. We have Requirements (Requirements and Qualifications). We'll make

    Requirements

    then list. We have Benefits: "No benefits are included with this position". We'll make

    Benefits

    then

    . We have Pay: Expected Salary Range: $2,500 - $3,500 based on position. We'll make

    Pay

    then

    . We have Schedule: Typical practice times are from 3:45 pm - 5:30 pm on weekdays. The season runs from late-February through early May. We'll make

    Schedule

    then

    possibly with two sentences. We might also include About the role? Not present. Could skip. We also have Position Overview etc. That could be considered About the role? The Position Overview describes the program. Could be used as About the role. But rule: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not mandatory list. We could include About the role if we have content. The Position Overview: "St. Catherine's School seeks coaches at the JV and Middle School levels to join a very established program with the help and support of our Varsity staff. We have both head and assistant coach positions available." That's substantive. So we could make About the role section. But we need to avoid thin sections. About the role would be a couple sentences. That's okay. We also have Skills? Not explicitly listed but maybe implied in responsibilities. Not needed. Qualifications? Already covered in Requirements. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. We'll output HTML fragment. We need to preserve all substantive information. Let's extract details. About the role: Position Overview paragraph: "St. Catherine's School seeks coaches at the JV and Middle School levels to join a very established program with the help and support of our Varsity staff. We have both head and assistant coach positions available." Also maybe include supervisor etc? But we said fold minor metadata into short

    . We could include a

    after About the role containing supervisor, position status, etc. But that might be considered metadata. Let's include a short

    after About the role: "Supervisor: Director of Athletics and Strategic Partnerships. Position Status: Salaried, exempt, temporary - based on seasonal sport." That's minor metadata. But we must not create a heading for that. So just a

    . Responsibilities: list items: - Plan, organize, and lead effective lacrosse practices, training sessions, and competitions that support the development of student-athletes - Teach and reinforce fundamental lacrosse skills, game strategies, teamwork, sportsmanship, and a strong understanding of the game - Supervise student-athletes during practices, games, team activities, and travel in accordance with School policies and safety expectations - Create a positive, inclusive, and developmentally appropriate team environment that reflects the School's mission and values - Prepare and manage practice plans, game strategies, lineups, and other team-related activities - Set a tone of professionalism among coaches, athletes, and parents Requirements: list: - High school diploma or equivalent required - Have lacrosse playing and/or coaching experience - Strong communication skills - Demonstrate strong leadership skills Benefits:

    No benefits are included with this position.

    Pay:

    Expected Salary Range: $2,500 - $3,500 based on position

    Schedule:

    Typical practice times are from 3:45 pm - 5:30 pm on weekdays. The season runs from late-February through early May.

    We might also include note about travel? That's under PHYSICAL DEMANDS AND WORK ENVIRONMENT and TRAVEL. Travel: "Limited sports-related travel may be needed." That's substantive. Should we include a Travel section? Not in the list of headings but we could add a

    Travel

    if we want. However, the instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

    for section headings (e.g. ...)". It implies we should use those headings for those sections if present. Travel is not in the list but could be considered a section. However, they said "Prefer a few substantive sections over many thin ones." Travel is a single sentence; maybe we can fold into Schedule or About the role? Could add to Schedule

    also mention travel. But better to keep separate? Might be considered thin. I'd incorporate into Schedule

    as additional sentence: "Typical practice times are from 3:45 pm - 5:30 pm on weekdays. The season runs from late-February through early May. Limited sports-related travel may be needed." Physical demands also substantive but not in list; could be omitted? It's substantive but not required heading. Could be omitted? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to preserve physical demands info. Where to put? Could add a

    Physical Demands

    but not in the example list. However, they said use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g., suggests those are examples, not exclusive. So we could add Physical Demands as a heading if we want. But they also said "Prefer a few substantive sections over many thin ones." Physical demands is a few sentences; could be its own section. Might be okay. But we need to decide. The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should use those headings for those categories if present. It doesn't forbid other headings, but the examples are typical sections. Physical demands is not typical but could be included. However, they also said "Prefer a few substantive sections over many thin ones." Adding Physical Demands adds another section; but it's substantive. We could also fold physical demands into About the role or Responsibilities? Not really fitting. Could add a

    Physical Demands and Work Environment

    . That seems appropriate. Similarly, we have "Note: This position description has been designed..." that's boilerplate; we should remove. Also "PHYSICAL DEMANDS AND WORK ENVIRONMENT" heading in original; we can keep content but not the heading as we will use our own

    . We also have "CONDITIONAL OFFERS" and "EQUAL EMPLOYMENT OPPORTUNITY STATEMENT" which are boilerplate to remove. Thus final sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule, Physical Demands (maybe). Also we might include Skills? Not present. We need to ensure we don't create empty sections. Let's draft HTML:

    About the role

    St. Catherine's School seeks coaches at the JV and Middle School levels to join a very established program with the help and support of our Varsity staff. We have both head and assistant coach positions available.

    Supervisor: Director of Athletics and Strategic Partnerships. Position Status: Salaried, exempt, temporary - based on seasonal sport.

    Responsibilities

    • Plan, organize, and lead effective lacrosse practices, training sessions, and competitions that support the development of student-athletes
    • Teach and reinforce fundamental lacrosse skills, game strategies, teamwork, sportsmanship, and a strong understanding of the game
    • Supervise student-athletes during practices, games, team activities, and travel in accordance with School policies and safety expectations
    • Create a positive, inclusive, and developmentally appropriate team environment that reflects the School's mission and values
    • Prepare and manage practice plans, game strategies, lineups, and other team-related activities
    • Set a tone of professionalism among coaches, athletes, and parents

    Requirements

    • High school diploma or equivalent required
    • Have lacrosse playing and/or coaching experience
    • Strong communication skills
    • Demonstrate strong leadership skills

    Benefits

    No benefits are included with this position.

    Pay

Similar jobs

Lacrosse Coach

BUCS Super RugbyLocation, WV· 1 mo ago
apply on bucs.org.uk

Lacrosse Coach

BUCS Super RugbyLocation, WV· 3 mo ago
apply on bucs.org.uk

Lacrosse Coach

TOCA FootballRocky River, OH· 3 mo ago
Educationapply on tocafootball.com