SEASONAL SUMMER WORKER

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate. Include a section only when posting has real specific content. So we need to parse the posting. The posting includes: - Intro: "SANTEE COOPER SEASONAL SUMMER WORKER Always Deliver. Take The Lead. Power What’s Next. Looking for a summer opportunity where you can make a difference, gain valuable experience, and be part of a team? Spend your summer with Santee Cooper in a seasonal role where you’ll build skills, work alongside a great team, and help create safe, welcoming spaces for the community we serve." That's prose. Then "Lifeguard Pay: $20/hour" then responsibilities list bullet style: "Responsibilities Include Monitor activities in and around the beach area to ensure safetyEnforce facility rules and regulationsConduct regular safety checks and maintain cleanliness of the areaProvide excellent customer service to guests". Actually they are not separated by line breaks but we can treat as list items. Then "Lifeguard Requirements Lifeguard certificationFirst Aid certificationCPR certificationMust be a full-time high school or college studentMust be at least 16 years old by June 2027". Again list. Then "Landscaper Pay: $15/hour" then responsibilities: "Responsibilities May Include Maintain lawns, landscaping, and outdoor areasMow, trim, edge, and perform general grounds maintenanceAssist with planting, weeding, and other landscaping tasks". Then requirements: "Landscaper Requirements Must be a full-time high school or college studentMust be at least 16 years old by June 2027Keep work areas clean and organizedFollow safety procedures and maintain a safe environmentProvide friendly and professional service to guests and team members". Then final paragraph: "Make Your Summer Count At Santee Cooper, you won’t spend your summer watching from the sidelines. You’ll gain experience, make connections and contribute to work that matters to communities across South Carolina. Bring your ideas. Build your skills. Make connections. Power what’s next. Apply today!" We need to remove application instructions: "Apply today!" is application instruction, should be removed. Also "Make Your Summer Count..." is prose maybe keep but remove "Apply today!". We need to produce sections: maybe we can have sections for each role? The instructions say use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't say we must have separate sections per role, but we can structure accordingly. Since we have two roles (Lifeguard and Landscaper) with different pay and responsibilities/requirements. Could we combine? Probably better to have separate sections for each role, using

  for role name? But they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't forbid using role name as heading? They said do NOT repeat the job title as a heading (the page already shows it). The job title is "Santee Cooper Seasonal Summer Worker". So we shouldn't use that as heading. But we could use "Lifeguard" and "Landscaper" as headings? Those are not the job title; they are sub-roles. Might be okay. However they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should use those standard headings. But we have two distinct roles; maybe we can have a single "About the role" covering both? Could combine but then responsibilities and requirements would be mixed. Better to have separate sections for each role using

  for role name? The instruction didn't explicitly forbid using role names as headings, only the job title. So we can use

  Lifeguard

  and

  Landscaper

  . Then under each we can have subheadings like

  Pay

  ,

  Responsibilities

  ,

  Requirements

  . But they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That implies we should use those exact headings. However we can still nest? Might be confusing. Simplify: Provide sections: About the role (intro), Pay (maybe combined?), Responsibilities (list for both?), Requirements (list for both?). But pay differs per role; we could note both. We could do:

  About the role

  Intro text...

  Pay

  • Lifeguard: $20/hour
  • Landscaper: $15/hour

  Responsibilities

  Lifeguard

  ...

  Landscaper

  ...
  But they said use

  for section headings, not

  . Could use

  for each subsection? Might be okay to have multiple

  sections. Better: Provide separate sections for each role with headings

  Lifeguard

  and

  Landscaper

  . Then under each, use

  Pay

  ,

  Responsibilities

  ,

  Requirements

  . That would be nested headings but still

  . Might be okay. But they said "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect those exact headings. However they also said "Do NOT repeat the job title as a heading (the page already shows it)". So they expect we might have sections like About the role, Responsibilities, Requirements, etc. Not role-specific headings. Thus we should produce a single set of sections: About the role (intro), Pay (maybe combined), Responsibilities (combined list?), Requirements (combined list?), Benefits (if any), Schedule (if any). Since there is no explicit benefits or schedule, we omit those sections. We need to preserve all substantive information. So we need to include both lifeguard and landscaper details within those sections. Thus:

  About the role

  Looking for a summer opportunity where you can make a difference, gain valuable experience, and be part of a team? Spend your summer with Santee Cooper in a seasonal role where you’ll build skills, work alongside a great team, and help create safe, welcoming spaces for the community we serve. Make Your Summer Count At Santee Cooper, you won’t spend your summer watching from the sidelines. You’ll gain experience, make connections and contribute to work that matters to communities across South Carolina. Bring your ideas. Build your skills. Make connections. Power what’s next.

  We removed "Apply today!" and the repeated "Always Deliver. Take The Lead. Power What’s Next." maybe keep as part of intro? The first line "SANTEE COOPER SEASONAL SUMMER WORKER Always Deliver. Take The Lead. Power What’s Next." The job title is Santee Cooper Seasonal Summer Worker; we should not repeat job title as heading but we can keep the tagline as prose? It's not boilerplate; it's part of posting. Could include in About the role paragraph. Thus About the role paragraph: "Santee Cooper Seasonal Summer Worker Always Deliver. Take The Lead. Power What’s Next. Looking for a summer opportunity where you can make a difference, gain valuable experience, and be part of a team? Spend your summer with Santee Cooper in a seasonal role where you’ll build skills, work alongside a great team, and help create safe, welcoming spaces for the community we serve. Make Your Summer Count At Santee Cooper, you won’t spend your summer watching from the sidelines. You’ll gain experience, make connections and contribute to work that matters to communities across South Carolina. Bring your ideas. Build your skills. Make connections. Power what’s next." Now Pay section: we need to list pay for each role. Use
  • .

    Pay

    • Lifeguard: $20/hour
    • Landscaper: $15/hour
    Responsibilities: we need to list responsibilities for each role. Could combine but better to separate.

    Responsibilities

    Lifeguard

    • Monitor activities in and around the beach area to ensure safety
    • Enforce facility rules and regulations
    • Conduct regular safety checks and maintain cleanliness of the area
    • Provide excellent customer service to guests

    Landscaper

    • Maintain lawns, landscaping, and outdoor areas
    • Mow, trim, edge, and perform general grounds maintenance
    • Assist with planting, weeding, and other landscaping tasks
    But they said use

    for section headings, not

    . However we need to differentiate sub-sections. Could we use

    for each responsibility heading? That would be many

    sections. Might be okay but could be considered not following the guideline. The guideline says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests to use those. However using

    might be acceptable as it's still a heading but not

    . The instruction didn't forbid other heading levels, just said use

    for section headings (list). It didn't say you cannot use other headings. Safer to stick to

    only for sections and use

    or

    for content. To differentiate lifeguard vs landscaper responsibilities, we could include a brief intro sentence before each list within the same
    but that mixes. We could do:

    Responsibilities

    Lifeguard:

    ...

    Landscaper:

    ...
    That uses

    for bold labels. That's acceptable. Similarly for Requirements. Thus:

    Requirements

    Lifeguard:

    • Lifeguard certification
    • First Aid certification
    • CPR certification
    • Must be a full-time high school or college student
    • Must be at least 16 years old by June 2027

    Landscaper:

    • Must be a full-time high school or college student
    • Must be at least 16 years old by June 2027
    • Keep work areas clean and organized
    • Follow safety procedures and maintain a safe environment
    • Provide friendly and professional service to guests and team members
    We should also include any qualifications/skills? Not present. Benefits: none mentioned. Schedule: none. Thus final