Grill Server

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to parse the posting. Content: - Classic Club, located in Palm Desert, CA, is pleased to announce an excellent career opportunity for a part-time Grill Server! We are seeking a driven individual who is eager to learn, contribute, and grow within a fast-paced hospitality-focused property organization. As part of Troon, you will contribute to a global leader in golf and community management. Role Type: Seasonal (Position will last 6 months or less) Compensation: $16.90 - $17.90 per hour depending on experience - Minimum Qualifications: Must be 21 years of age or older. Minimum of one year of cooking experience. Experience managing and upholding safe working conditions. Understanding of safety, sanitation, and food handling procedures. Understands functions of Point of Sale (POS) and phone systems. Demonstrates proper cash handling and turn-in standards. Understands and demonstrates proper side work and cleanliness standards. Demonstrates proper service sequence with guests. Understands dining room flow mechanics. Understands reservation procedures. Understands how to communicate banquet information and take preliminary bookings. Must be dependable. Must be able to work well in a fast-paced environment. Must be able to work in a team environment. Must be able to take direction. Must pass a background screening. Responsibilities will include both front-of-house and back-of-house tasks - Benefits & Other Compensation: This position includes eligibility for the following benefits, subject to applicable plan terms: Healthcare Benefits – Medical (if determined by the ACA measurement)Retirement Benefits – 401(k) with employer match (19 years of age and older)Additional Compensation – Eligibility for Service Charge, Employee Meals Eligibility for benefits and the specific terms, conditions, and offerings are governed by the applicable plan of documents and company policies, which may be amended at the Company’s discretion. - About Troon: Founded in 1990 and headquartered in Scottsdale, AZ, Troon is the world’s largest professional club management company, that specializes in services in golf, hospitality, and residential communities. With more than 900 locations in 45+ states and 27+ countries, Troon is a leading employer in hospitality. Guided by values that emphasize being infectiously energetic, consciously kind, and humbly prosperous, Troon offers professionals the opportunity to grow and succeed within a globally respected organization. Learn more at www.troon.com. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have: - About the role: Could be the introductory paragraph describing role: "Classic Club ... part-time Grill Server! We are seeking a driven individual ...". Also mention role type seasonal, etc. Could be "About the role". We'll include that. - Responsibilities: The line "Responsibilities will include both front-of-house and back-of-house tasks". That's vague but it's a statement. However we need to avoid filler placeholder. It's not a list but it's a statement. Could we include as a

? The rule: Use

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

  for prose. So we can put that sentence in a

  . But we need to see if there are more specific responsibilities listed elsewhere. The qualifications list includes many duties like "Understands functions of POS", "Demonstrates proper cash handling", etc. Those could be considered responsibilities or requirements. The posting lumps them under Minimum Qualifications. We need to decide sections. We have Minimum Qualifications list (many items). That could go under Requirements or Qualifications. The posting says "Minimum Qualifications:" then list. So we can put that under Requirements (or Qualifications). We'll choose Requirements. We also have "Benefits & Other Compensation:" which includes Healthcare Benefits – Medical (if determined by the ACA measurement) Retirement Benefits – 401(k) with employer match (19 years of age and older) Additional Compensation – Eligibility for Service Charge, Employee Meals. That's specific enough to create Benefits section. Pay: Compensation: $16.90 - $17.90 per hour depending on experience. That's specific, so we can create Pay section. Schedule: Role Type: Seasonal (Position will last 6 months or less). That's schedule info. So we can create Schedule section. Skills: Not explicitly listed separate; maybe we could extract some skills like POS, phone systems, cash handling, service sequence, dining room flow, reservation procedures, banquet communication, teamwork, dependability, fast-paced, direction taking. But those are already in qualifications. The rule: Prefer a few substantive sections over many thin ones. We could combine skills into Requirements or Qualifications. Since we already have Requirements section for qualifications, we might not need separate Skills. But we need to decide which sections to include: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. That's six sections. Could also include Qualifications but we already have Requirements. The instruction says use headings for those specific names if content exists. We can choose to include Requirements and not Qualifications (or vice versa). Since the posting says Minimum Qualifications, we could use Qualifications heading. But we also have Responsibilities separate. Let's map: - About the role: intro paragraph. - Responsibilities: we have a statement "Responsibilities will include both front-of-house and back-of-house tasks". That's not a list but we could still put as

  . However we might also incorporate some of the qualification items as responsibilities? But they are under Minimum Qualifications. To avoid thin sections, maybe we combine Responsibilities into About the role? But the instruction: include a section ONLY when the posting has real, specific content for it. The Responsibilities section currently only has that vague sentence. Is that considered real specific content? It's a statement but not detailed. Might be considered filler? It's not placeholder like "commensurate with experience". It's a real statement about responsibilities. I'd say it's okay to include. - Requirements: we could put the Minimum Qualifications list there. - Benefits: we have specific benefits. - Pay: we have compensation. - Schedule: we have role type seasonal. We could also include Qualifications but that would duplicate Requirements. Better to stick with one. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Now we need to format. Use

  for each section heading. Inside each section, use

  for prose,

  • for lists. For About the role: prose paragraph(s). We'll combine the intro sentences: "Classic Club, located in Palm Desert, CA, is pleased to announce an excellent career opportunity for a part-time Grill Server! We are seeking a driven individual who is eager to learn, contribute, and grow within a fast-paced hospitality-focused property organization. As part of Troon, you will contribute to a global leader in golf and community management." Also maybe include role type? But role type goes to Schedule. We'll keep About the role as above. Responsibilities: we have sentence: "Responsibilities will include both front-of-house and back-of-house tasks." We'll put in

    . Requirements: list of Minimum Qualifications items. We'll create

    with each item as
    • . Need to preserve all items exactly as written. Let's extract the list: - Must be 21 years of age or older. - Minimum of one year of cooking experience. - Experience managing and upholding safe working conditions. - Understanding of safety, sanitation, and food handling procedures. - Understands functions of Point of Sale (POS) and phone systems. - Demonstrates proper cash handling and turn-in standards. - Understands and demonstrates proper side work and cleanliness standards. - Demonstrates proper service sequence with guests. - Understands dining room flow mechanics. - Understands reservation procedures. - Understands how to communicate banquet information and take preliminary bookings. - Must be dependable. - Must be able to work well in a fast-paced environment. - Must be able to work in a team environment. - Must be able to take direction. - Must pass a background screening. We'll keep each as
    • . Benefits: we have Healthcare Benefits – Medical (if determined by the ACA measurement) Retirement Benefits – 401(k) with employer match (19 years of age and older) Additional Compensation – Eligibility for Service Charge, Employee Meals. Also note that eligibility governed by plan documents. We'll put as
      with each benefit as
      • . Could combine into one sentence? Better to list. Thus: - Healthcare Benefits – Medical (if determined by the ACA measurement) - Retirement Benefits – 401(k) with employer match (19 years of age and older) - Additional Compensation – Eligibility for Service Charge, Employee Meals We could also add note about eligibility governed by plan documents as a

        after list. Pay: we have Compensation: $16.90 - $17.90 per hour depending on experience. We'll put in

        . Schedule: Role Type: Seasonal (Position will last 6 months or less). We'll put in

        . Now ensure we don't include boilerplate like About Troon (that's company info). Should we include About Troon? It's not one of the headings list; but we could include as About the role? Already used. About Troon is company overview, not role. According to rules, we should remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Troon is not boilerplate but it's company description. The instruction didn't explicitly say to remove company description, but we have limited sections. Could we add an "About the company" section? Not in allowed headings list. The allowed headings are only those eight. So we should not include About Troon as a heading. We could incorporate that info into About the role? But that would be mixing. Better to omit it, as it's not required to preserve all substantive information? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must preserve all substantive information. If we omit About Troon, we lose substantive info. However we could include it as a paragraph under About the role? But About the role is supposed to be about the role, not company. But we could still include it as part of About the role section; the heading is About the role, but we can include extra info. The instruction: "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not strict that those are the only allowed headings? It says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the expected headings. It also says "include a section ONLY when the posting has real, specific content for it". So we could have sections for those headings only. If we include company info, we need a heading; but none of the allowed headings fit company info except maybe About the role (but that's not accurate). However we could treat About the role as also including company context. The instruction didn't forbid adding extra content under those headings. So we can put the Troon description under About the role as extra paragraph. Thus About the role will contain: the introductory paragraph about the position, plus the Troon description. Let's craft: About the role:

        Classic Club, located in Palm Desert, CA, is pleased to announce an excellent career opportunity for a part-time Grill Server! We are seeking a driven individual