Baseball Instructor

We need to output HTML fragment with sections: About the role? Actually the posting includes "About The Ymca" (organization description) then "Position Summary". We need headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each section heading. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID. Remove boilerplate etc. We need to preserve all substantive info. Let's parse content. Sections present: - About The Ymca (organization description). Could map to "About the role"? Actually "About the role" is about the position, but we have "Position Summary". Could treat "About the role" as the position summary. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings if they exist. We have: - Position Summary: description of role, duties overview. That could go under "About the role". We'll put that content. - Responsibilities: list of duties (Leads and participates..., Prepares..., Organizes..., Serves..., Promotes..., Contributes..., Abuse Risk Management Functions...). That's a list. - Qualifications: includes "QUALIFICATIONS: Highschool diploma or G.E.D. (or degree in progress) Experience working with children Knowledge of the relevant sport Within 30 days of hire, completion of CPR for Professional Rescuers (with AED) and First Aid Certifications". Also earlier there is "Position Summary" includes part-time hours etc. Also "Work Environment & Physical Demands" maybe could be under Requirements? Not exactly. There's no explicit "Requirements" heading but we have qualifications and maybe physical demands could be considered requirements. We could put physical demands under "Requirements". The instruction: Use sections only when posting has real specific content. We have content for Responsibilities, Qualifications, Benefits. Also we have schedule: "This is a part-time in-person position located at the YMCA. This position typically requires 2 - 5 hours per week." That's schedule info. So we can create a Schedule section. Pay: Not mentioned. So we omit Pay section. Skills: Not explicitly listed; maybe knowledge of sport etc is under qualifications. Could we create Skills? Probably not needed if no explicit skills list. We'll omit. About the role: we have Position Summary plus maybe About the Ymca description? The "About The Ymca" is organization description, not role. But we could include that under About the role? Might be okay but it's about organization. However instruction: "About the role" heading example; we can put position summary there. The organization description could be considered part of "About the role"? Might be stretching but we need to preserve all substantive info. We could include a brief paragraph about the YMCA under About the role or maybe we could create a separate section? Not allowed headings beyond those listed. So we must fit organization description somewhere; maybe under About the role as introductory context. That seems acceptable. Thus sections:

About the role

About The Ymca Established locally in 1944, the YMCA of Southern Nevada is one of the region’s longest-serving and most-respected nonprofit organizations. We are committed to helping people of all ages, abilities, backgrounds, and income levels – ensuring everyone has the opportunity to reach their full potential with dignity and that no one is turned away due to the inability to pay. From childcare to senior programs; sports to education; fitness centers to chronic disease management; and swim lessons to feeding the hungry, the Y is truly for all in its cause of holistically strengthening the foundations of this community.

Position Summary The YMCA of Southern Nevada is looking for a youth baseball instructor for all YMCA locations. You will supervise groups of children and teach them simple sports skills. You will help build skills, confidence and a love of the game! Our youth baseball program teaches the fundamentals of hitting, throwing, catching, fielding, and teamwork and is taught in ages 3 to 6 and 7 to 13-year-old age groups. This is a part-time in-person position located at the YMCA. This position typically requires 2 - 5 hours per week.

Then Responsibilities:

Responsibilities

• Leads and participates in group sports activities focusing on skill development, teamwork, and sportsmanship.
• Prepares and delivers weekly lesson plans tailored to age and ability level.
• Organizes monthly scrimmages to reinforce learning in a fun, game-like setting.
• Serves as a positive role model for program participants.
• Promotes safety as an overriding objective in all programming efforts.
• Contributes to a positive work environment.
• Adheres to policies related to boundaries with children.
• Attends required abuse risk management training.
• Reports suspicious or inappropriate behaviors and policy violations.
• Follows mandated abuse reporting requirements.
• Adheres to job specific abuse risk management responsibilities.

Qualifications:

Qualifications

• Highschool diploma or G.E.D. (or degree in progress)
• Experience working with children
• Knowledge of the relevant sport
• Within 30 days of hire, completion of CPR for Professional Rescuers (with AED) and First Aid Certifications

We might also include Work Environment & Physical Demands under Requirements? But we don't have a Requirements heading. Could we add a Requirements section for physical demands? The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can include Requirements if we have content. We have physical demands description. Let's put that under Requirements. Thus:

Requirements

This job requires the following physical demands. Reasonable accommodation may be made. You will need sufficient strength, agility and mobility to supervise program activities in a wide variety of indoor and outdoor locations. You will need to sit; use hands to finger, handle, or feel objects, tools, or controls; and talk or hear. You will need to reach with hands or arms. You will also need to stand; walk; climb or balance; and stoop, kneel, crouch, or crawl. You will occasionally need lift and/or move up to 20 pounds. The noise level is usually moderate.

Benefits: We have benefits list: Paid time off, 10% Retirement Contribution* and access to our 403(b) retirement savings account, Free YMCA membership and discounts on all programs, Rain - Instant Pay Benefit, Join a supportive team and an organization recognized as a Nevada Top Workplace, Make a meaningful impact in your community, Automatic retirement contributions are made to employees 21 years or older after contributing 1,000 hours of service in each of two years., Our Culture... Actually the culture paragraph maybe not benefits but could be included under Benefits? The instruction: include Benefits section only when posting has real specific content. We have benefits list. We'll include those bullet points. Thus:

Benefits

• Paid time off
• 10% Retirement Contribution* and access to our 403(b) retirement savings account
• Free YMCA membership and discounts on all programs
• Rain - Instant Pay Benefit
• Join a supportive team and an organization recognized as a Nevada Top Workplace
• Make a meaningful impact in your community
• Automatic retirement contributions are made to employees 21 years or older after contributing 1,000 hours of service in each of two years.

We might also include culture description? Could be separate but not a standard heading. Could be omitted? It's substantive but not under any allowed heading. Could we put under About the role? Might be okay to add a paragraph about culture after benefits? But we must not invent headings. Could add a

after benefits for culture? The instruction: Output ONLY the HTML fragment. It didn't forbid extra paragraphs not under headings? It says use

for section headings (list). Use

• for any list of duties/requirements/benefits, and

  for prose. So we can have prose paragraphs outside headings? Probably okay but better to keep under headings. Culture could be considered part of Benefits? Not really. Could be part of About the role? Might be okay to add a paragraph under About the role after position summary describing culture. But we already used About the role for org description and position summary. Could add another paragraph there. Let's add a paragraph under About the role after position summary: "Our Culture Our mission and core values are brought to life by our culture. In the Y, we strive to live our cause of strengthening communities with purpose and intentionality every day. We are welcoming: we are open to all. We are a place where you can belong and become. We are genuine: we value you and embrace your individuality. We are nurturing: we support you in your journey to develop your full potential. We are determined: above all else, we are on a relentless quest to make our community stronger, beginning with you. We are service driven: we go above and beyond to keep people coming back and apply a listen-first and solution-oriented approach to resolving conflicts. We are safety focused: we are proactive in keeping everyone safe and respond promptly to incidents as a team." That is prose, so

  . Schedule section:

  Schedule

  This is a part-time in-person position located at the YMCA. This position typically requires 2 - 5 hours per week.

  But we already mentioned that in position summary; but we can still include schedule section with that detail. Avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's present in original? It appears twice; we could keep both but maybe better to not duplicate. However we already included schedule in About the role position summary. If we also create Schedule section, we would duplicate. Might be okay but maybe better to move schedule detail to Schedule section and remove from About the role to avoid duplication. But we need to preserve all info; we can keep it in Schedule section and not repeat elsewhere. Let's adjust: In About the role we will keep org description and position summary but maybe shorten position summary to not include schedule details. Let's extract schedule: "This is a part-time in-person position located at the YMCA. This position typically requires 2 - 5 hours per week." We'll put that under Schedule. Then About the role position summary will be: "The YMCA of Southern Nevada is looking for a youth baseball instructor for all YMCA locations. You will supervise groups of children and teach them simple sports skills. You will help build skills, confidence and a love of the game! Our youth baseball program teaches the fundamentals of hitting, throwing, catching, fielding, and teamwork and is taught in ages 3 to 6 and 7 to 13-year-old age groups." Thus we avoid duplication. Now Benefits section we have list; also there is a line "Our Culture ..." which we already placed under About the role as prose after position summary. Now check for any other info: "WHY WORK HERE?" heading we turned into Benefits. Good. Now ensure we didn't include boilerplate like EEO etc. Not present. Now produce HTML fragment with sections in logical order: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. Could also put Schedule after Benefits. Let's craft. Note: Use

  for each heading. Use

  for prose, <