We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate, navigation, EEO, etc. Must preserve all substantive info.
We need to parse the posting.
Key info:
- Title: Line Cooks (but we don't repeat as heading)
- Type: Full Time - Dinner Shift
- Company: The White Chocolate Grill
- Location: 7000 E Mayo Blvd Bldg 6 Phoenix, AZ 85054 (corner of Scottsdale Rd and Mayo Blvd)
- Pay: $24.00 - $28.00 based on experience and schedule availability
- Description: The White Chocolate Grill in North Scottsdale is now hiring linecooks to join our exceptional back-of-house team. We’re looking for experienced individuals who are comfortable in high-volume from scratch kitchens. We are looking for grill, assemble and flat-top experience, ideally serving 300-500 covers per shift.
- Compensation: Hourly Rate: $24-$28
- Benefits: Paid Sick Time: available to all employees in accordance with Company policy and applicable law; Employee Referral Program; Health Insurance: available to fulltime employees after a 60day measurement period, starting as low as $50/paycheck; Schedules: Saturdays and Sundays are required, 4pmCL 46 days a week preferred (maybe typo: "4pmCL"? Might be "4pm-Close"? We'll keep as is); Meal Discounts: 50% off fullpriced menu items when you come in and dine; Opportunities: Growth and advancement, a third of our managers started in hourly positions; Early nights: We close at 9:00pm!
- Requirements: Grill, flattop, or assemble Experience; Scratchkitchen background with two years or more of experience; Strong knife skills and attention to recipe details; Ability to work in a clean and fastpaced environment; Ability to learn the menu food offerings and sell food in 712 minutes (maybe typo: "sell food in 7-12 minutes"? We'll keep as is); Must be at least 18 years old; Looking for longterm employment, not a seasonal role; Ability to walk for long periods of time; Ability to climb stairs; Ability to lift, push, pull or carry objects up to 40lbs; Ability to move about the restaurant and remain standing for an 4 8 hour shift (maybe "4-8 hour shift"); Availability to work Holidays and Weekends; Work in a noisy and fastpaced environment; Work indoors and/or outdoors, exposed to hot and/or cold.
- Application Process: instructions (to be removed)
- Equal Opportunity Employer boilerplate (to be removed)
We need to produce sections: About the role (description), Responsibilities (maybe from description?), Requirements, Qualifications (maybe overlapping), Skills, Benefits, Pay, Schedule.
We must not invent sections with filler. Use only if content exists.
We have description paragraph: "The White Chocolate Grill in North Scottsdale is now hiring linecooks to join our exceptional back-of-house team. We’re looking for experienced individuals who are comfortable in high-volume from scratch kitchens. We are looking for grill, assemble and flat-top experience, ideally serving 300-500 covers per shift." That's about the role.
Responsibilities: maybe not explicitly listed; but we could infer duties: grill, assemble, flat-top, serving covers, etc. However we should not invent. The posting includes "We are looking for grill, assemble and flat-top experience, ideally serving 300-500 covers per shift." That's more like requirements. There's no explicit responsibilities list. Could we treat that as responsibilities? Might be okay but risk of inventing. Better to only include sections where there is explicit content. The posting has a "Requirements" section with bullet-like list. Also "Benefits" section. Also "Pay" (Compensation). Also "Schedule" (Saturdays and Sundays required, 4pmCL 46 days a week preferred, early nights close at 9:00pm). Also maybe "Qualifications" could be same as Requirements? But we should not duplicate. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But they ask to use headings for those specific names if content exists. We could put Requirements as a section, and maybe Qualifications as another if there is distinct content. The posting has "Requirements" heading and list. There's no separate "Qualifications". So we will have Requirements.
Skills: maybe we can extract from requirements: grill, flattop, assemble experience, scratch kitchen background, knife skills, ability to work clean/fastpaced, learn menu, etc. Those are skills. Could create Skills section. But we must not invent; we can pull from the requirements list. That's okay.
Benefits: we have list.
Pay: we have.
Schedule: we have.
About the role: we have description.
Thus sections: About the role, Responsibilities? Not present. Could we treat the description as About the role and maybe Responsibilities as the duties (like grill, assemble, flat-top, serving covers). But that's not explicitly labeled. Safer to omit Responsibilities if not explicit. However we might include Responsibilities as the list of duties: "grill, assemble and flat-top experience, ideally serving 300-500 covers per shift." That's more like expectations. But it's under description. I'd include Responsibilities as a section with that content.
But the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine About the role and Responsibilities into one? But they ask to use headings for those specific names if content exists. We could have About the role (description) and Responsibilities (the specific duties). That's two sections.
Qualifications: maybe we can treat Requirements as Qualifications. But we already have Requirements. Could we have both Requirements and Qualifications? Might be thin. Better to have Requirements only.
Skills: we can extract skill items.
Thus final sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule.
Check each for real content.
About the role: paragraph from description.
Responsibilities: maybe "We are looking for grill, assemble and flat-top experience, ideally serving 300-500 covers per shift." That's a responsibility/expectation. Could also include "comfortable in high-volume from scratch kitchens". But that's more about role. We'll keep responsibilities as that sentence.
Requirements: list as given.
Skills: we can list: Grill experience, Flattop experience, Assemble experience, Scratch kitchen background, Strong knife skills, Attention to recipe details, Ability to work in clean and fast-paced environment, Ability to learn menu food offerings, Ability to sell food in 7-12 minutes (or 712 minutes? We'll keep as given), Ability to walk for long periods, Ability to climb stairs, Ability to lift/push/pull/carry up to 40 lbs, Ability to move about restaurant and remain standing for 4-8 hour shift, Availability to work holidays and weekends, Ability to work in noisy and fast-paced environment, Ability to work indoors/outdoors exposed to hot/cold.
But many of these are also requirements. Might be duplication. However we can still include Skills as subset.
Pay: "$24.00 - $28.00 based on experience and schedule availability"
Schedule: "Saturdays and Sundays are required, 4pmCL 46 days a week preferred; Early nights: We close at 9:00pm!" Also maybe "4pmCL" unclear but keep.
Benefits: list: Paid Sick Time: available to all employees in accordance with Company policy and applicable law; Employee Referral Program; Health Insurance: available to fulltime employees after a 60day measurement period, starting as low as $50/paycheck; Meal Discounts: 50% off fullpriced menu items when you come in and dine; Opportunities: Growth and advancement, a third of our managers started in hourly positions; Early nights: We close at 9:00pm! (but early nights already in schedule; maybe duplicate). We'll keep as given.
We must not include boilerplate like EEO, application instructions, etc.
Now produce HTML fragment.
Structure:
About the role
...
Responsibilities
(if multiple items). We have one sentence; could be
but they said use