Ropes Course Attendant
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.
We need to include a section only when posting has real specific content for it. So we need to decide which sections to include.
We have:
- Pay: The posting says "Pay: $16.00" and also "Estimated Salary Range: - $16.00 annual base salary". So we have pay info. Should we include a Pay section? Yes, we have specific pay amount. So include
Pay
with maybe $16.00 per hour? Actually it says $16.00 (maybe per hour). The posting says "Pay: $16.00". Also "Estimated Salary Range: - $16.00 annual base salary". That seems contradictory: $16.00 annual base salary is too low; maybe it's hourly. We'll just output the pay as given: $16.00. We'll not invent.
- Benefits: The posting lists "Benefits: Medical, Dental, and Vision insurance Health savings account Telehealth resources Life insurance 401K with employer match Paid vacation time off Paid parental leave". So we have benefits. So include
Benefits
with - items.
- Responsibilities / Duties: There's a block "Essential Duties & Responsibilities" with many bullet-like sentences. We'll turn each sentence into
- . Use
Responsibilities
(or maybe "Essential Duties & Responsibilities" but we need to use allowed headings; we can use Responsibilities). Provide list.
- Qualifications & Skills: There's "Basic Qualifications & Skills" block with bullet-like sentences. We'll split into maybe Requirements and Skills? The allowed headings include Requirements, Qualifications, Skills. We could combine into one section "Requirements" or separate. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications and Skills into one section "Requirements". Or we could have "Qualifications" and "Skills" separate if there is enough content. Let's see content: Must be 18 years or older; Some High School education or equivalent; Must be comfortable being at heights of 30 feet or more for extended periods of time; Flexibility regarding scheduling based on business demands; Experience utilizing basic math skills with ability to add, subtract multiply and divide; Proven customer service skills and communication skills; able to read and interpret English language manuals relating to safety, operations, and procedures; Successful completion of a criminal background check and drug screen.
These are qualifications/requirements. Could be split: Requirements (education, age, background check) and Skills (math, customer service, communication, ability to read manuals, comfort at heights, flexibility). But we can combine into one section "Requirements". Since we prefer few sections, we can have one section "Requirements" with - for each.
We also have some introductory prose about role: "At Great Wolf, the Ropes Course Attendant ensures customer safety and satisfaction while guests navigate across bridges and ropes to Howlers Peak. The Ropes Course attendant is responsible for guest registration, supplying equipment, education, and adherence to proper safety protocol." That's about the role. Could be placed under a section "About the role". We have heading About the role allowed. So we can include
About the role
with containing that prose.
Also there are some perks sections: "Join our Pack: Grow your career: A great place to start or advance your career with cross-training, scholarship fund, and talent development programs at all levelsGreat Perks: Take advantage of exclusive perks for you, your family, and friends – including discounted vacations and employee referral incentivesLearn While You Earn: Gain access to Great Wolf University for on-the-job training, functional, and leadership trainingPrioritize Your Well-Being: We offer flexible scheduling, access to a holistic wellness program and technology, and support through our Employee Assistance Program and Employee Relief FundCelebrate Your Uniqueness: Join a team that cheers for diversity and inclusion through programs that make everyone feel welcome and recognized." This is basically benefits/perks but we already have Benefits section. Could incorporate into Benefits or maybe a separate "Perks" section but not in allowed headings. Since we have Benefits, we could include those perks as part of Benefits list. However the Benefits section currently lists medical etc. The perks are separate: career growth, scholarship fund, talent development, discounted vacations, referral incentives, training programs, flexible scheduling, wellness program, EAP, relief fund, diversity inclusion. Those are also benefits/perks. We could combine them into Benefits section as additional list items. The instruction: "Use
- for any list of duties/requirements/benefits". So we can include all benefits/perks under Benefits.
Thus Benefits section will have list items: Medical, Dental, and Vision insurance; Health savings account; Telehealth resources; Life insurance; 401K with employer match; Paid vacation time off; Paid parental leave; Cross-training; Scholarship fund; Talent development programs; Discounted vacations; Employee referral incentives; Access to Great Wolf University (on-the-job training, functional, leadership training); Flexible scheduling; Access to holistic wellness program and technology; Employee Assistance Program; Employee Relief Fund; Diversity and inclusion programs.
We need to ensure we don't duplicate. Also we need to preserve all substantive information; we should not invent.
Now we need to decide about Schedule section: The posting mentions "flexible scheduling" as a perk, but not a specific schedule. No explicit schedule details like full-time/part-time, shift times. So we should not create a Schedule section because we don't have specific schedule info. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. We have Pay and Benefits, but not Schedule. So omit Schedule.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce something like:
About the role
At Great Wolf, the Ropes Course Attendant ensures customer safety and satisfaction while guests navigate across bridges and ropes to Howlers Peak. The Ropes Course attendant is responsible for guest registration, supplying equipment, education, and adherence to proper safety protocol.
Pay
for prose. We need to include a section only when posting has real specific content for it. So we need to decide which sections to include. We have: - Pay: The posting says "Pay: $16.00" and also "Estimated Salary Range: - $16.00 annual base salary". So we have pay info. Should we include a Pay section? Yes, we have specific pay amount. So include
Pay
with maybe$16.00 per hour? Actually it says $16.00 (maybe per hour). The posting says "Pay: $16.00". Also "Estimated Salary Range: - $16.00 annual base salary". That seems contradictory: $16.00 annual base salary is too low; maybe it's hourly. We'll just output the pay as given: $16.00. We'll not invent. - Benefits: The posting lists "Benefits: Medical, Dental, and Vision insurance Health savings account Telehealth resources Life insurance 401K with employer match Paid vacation time off Paid parental leave". So we have benefits. So include
Benefits
with- items. - Responsibilities / Duties: There's a block "Essential Duties & Responsibilities" with many bullet-like sentences. We'll turn each sentence into
- . Use
Responsibilities
(or maybe "Essential Duties & Responsibilities" but we need to use allowed headings; we can use Responsibilities). Provide list. - Qualifications & Skills: There's "Basic Qualifications & Skills" block with bullet-like sentences. We'll split into maybe Requirements and Skills? The allowed headings include Requirements, Qualifications, Skills. We could combine into one section "Requirements" or separate. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications and Skills into one section "Requirements". Or we could have "Qualifications" and "Skills" separate if there is enough content. Let's see content: Must be 18 years or older; Some High School education or equivalent; Must be comfortable being at heights of 30 feet or more for extended periods of time; Flexibility regarding scheduling based on business demands; Experience utilizing basic math skills with ability to add, subtract multiply and divide; Proven customer service skills and communication skills; able to read and interpret English language manuals relating to safety, operations, and procedures; Successful completion of a criminal background check and drug screen. These are qualifications/requirements. Could be split: Requirements (education, age, background check) and Skills (math, customer service, communication, ability to read manuals, comfort at heights, flexibility). But we can combine into one section "Requirements". Since we prefer few sections, we can have one section "Requirements" with- for each.
We also have some introductory prose about role: "At Great Wolf, the Ropes Course Attendant ensures customer safety and satisfaction while guests navigate across bridges and ropes to Howlers Peak. The Ropes Course attendant is responsible for guest registration, supplying equipment, education, and adherence to proper safety protocol." That's about the role. Could be placed under a section "About the role". We have heading About the role allowed. So we can include
About the role
withcontaining that prose. Also there are some perks sections: "Join our Pack: Grow your career: A great place to start or advance your career with cross-training, scholarship fund, and talent development programs at all levelsGreat Perks: Take advantage of exclusive perks for you, your family, and friends – including discounted vacations and employee referral incentivesLearn While You Earn: Gain access to Great Wolf University for on-the-job training, functional, and leadership trainingPrioritize Your Well-Being: We offer flexible scheduling, access to a holistic wellness program and technology, and support through our Employee Assistance Program and Employee Relief FundCelebrate Your Uniqueness: Join a team that cheers for diversity and inclusion through programs that make everyone feel welcome and recognized." This is basically benefits/perks but we already have Benefits section. Could incorporate into Benefits or maybe a separate "Perks" section but not in allowed headings. Since we have Benefits, we could include those perks as part of Benefits list. However the Benefits section currently lists medical etc. The perks are separate: career growth, scholarship fund, talent development, discounted vacations, referral incentives, training programs, flexible scheduling, wellness program, EAP, relief fund, diversity inclusion. Those are also benefits/perks. We could combine them into Benefits section as additional list items. The instruction: "Use
- for any list of duties/requirements/benefits". So we can include all benefits/perks under Benefits.
Thus Benefits section will have list items: Medical, Dental, and Vision insurance; Health savings account; Telehealth resources; Life insurance; 401K with employer match; Paid vacation time off; Paid parental leave; Cross-training; Scholarship fund; Talent development programs; Discounted vacations; Employee referral incentives; Access to Great Wolf University (on-the-job training, functional, leadership training); Flexible scheduling; Access to holistic wellness program and technology; Employee Assistance Program; Employee Relief Fund; Diversity and inclusion programs.
We need to ensure we don't duplicate. Also we need to preserve all substantive information; we should not invent.
Now we need to decide about Schedule section: The posting mentions "flexible scheduling" as a perk, but not a specific schedule. No explicit schedule details like full-time/part-time, shift times. So we should not create a Schedule section because we don't have specific schedule info. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. We have Pay and Benefits, but not Schedule. So omit Schedule.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce something like:
About the role
At Great Wolf, the Ropes Course Attendant ensures customer safety and satisfaction while guests navigate across bridges and ropes to Howlers Peak. The Ropes Course attendant is responsible for guest registration, supplying equipment, education, and adherence to proper safety protocol.
Pay
- for any list of duties/requirements/benefits". So we can include all benefits/perks under Benefits.
Thus Benefits section will have list items: Medical, Dental, and Vision insurance; Health savings account; Telehealth resources; Life insurance; 401K with employer match; Paid vacation time off; Paid parental leave; Cross-training; Scholarship fund; Talent development programs; Discounted vacations; Employee referral incentives; Access to Great Wolf University (on-the-job training, functional, leadership training); Flexible scheduling; Access to holistic wellness program and technology; Employee Assistance Program; Employee Relief Fund; Diversity and inclusion programs.
We need to ensure we don't duplicate. Also we need to preserve all substantive information; we should not invent.
Now we need to decide about Schedule section: The posting mentions "flexible scheduling" as a perk, but not a specific schedule. No explicit schedule details like full-time/part-time, shift times. So we should not create a Schedule section because we don't have specific schedule info. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. We have Pay and Benefits, but not Schedule. So omit Schedule.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce something like:
- for each.
We also have some introductory prose about role: "At Great Wolf, the Ropes Course Attendant ensures customer safety and satisfaction while guests navigate across bridges and ropes to Howlers Peak. The Ropes Course attendant is responsible for guest registration, supplying equipment, education, and adherence to proper safety protocol." That's about the role. Could be placed under a section "About the role". We have heading About the role allowed. So we can include