Cook (Part-Time)

We need to output HTML fragment with sections only when content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. From posting: - Intro: "As the team at Zaxbys expands..." etc. Could be "About the role" content. - "Cooks are directly responsible..." description of duties. That's responsibilities. - "Why work at Zax?" then list: FREE Meals On Shift & 50% Off Meals Off Shift, Flexible Schedule, Early Access to Pay, Opportunities to Advance, Benefits, Recognition Program, Employee Referral Program, 401(k) With Employer Match (additional eligibility requirements), Additional Benefits for Full-Time Team Members: Medical, Dental, and Vision Insurance, Short and Long-Term Disability, Employer-Paid Life Insurance. That's benefits. - "Job Duties and Responsibilities" then list many duties. - "Job Qualifications" then list: Must be 16 years of age or older; Part-time: Available to work 9 to 28 hours per week; Full-time: Available to work 32 to 40 hours per week. - "Capability Requirements" then list physical capabilities. - There's no explicit Pay or Schedule sections beyond mention of flexible schedule and early access to pay (but schedule is mentioned in benefits? Actually flexible schedule is a benefit; schedule details are part-time/full-time hours). The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include Schedule if we have specific schedule info: part-time 9-28 hrs, full-time 32-40 hrs. That's schedule specifics. So we can create a Schedule section with that info. Pay: they mention Early Access to Pay but no actual pay rate. Not specific. So we should not create Pay section. Skills: maybe not explicit; we could omit. Qualifications: we have age requirement and availability; also capability requirements could be under Qualifications or Requirements. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We have: - About the role: intro paragraph about Zaxbys and cooking role. - Responsibilities: list of duties (the long list under Job Duties and Responsibilities). Also earlier sentence "Cooks are directly responsible..." could be part of responsibilities. - Requirements: maybe the capability requirements (physical). Or we could treat "Job Qualifications" as Requirements. But we have both Job Qualifications and Capability Requirements. Could combine into Requirements section (or Qualifications). The headings list includes both Requirements and Qualifications. We need to decide which to use. Since we have both "Job Qualifications" (age, availability) and "Capability Requirements" (physical). We could put age/availability under Qualifications, and physical capabilities under Requirements. Or we could put all under Requirements and skip Qualifications. But we should follow headings: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include both Requirements and Qualifications if we have content. Thus: - Requirements: physical capabilities (sit, stand, walk, lift, etc.) - Qualifications: age requirement, availability (part-time/full-time hours). Could also include "Must be 16 years of age or older" and availability. - Benefits: list of benefits. - Schedule: part-time/full-time hours (though we already used availability in Qualifications; but schedule is separate). Might duplicate. Perhaps better to put schedule info in Schedule section and not duplicate in Qualifications. Qualifications could just be age requirement. But the posting says "Must be 16 years of age or older" and then part-time/full-time availability. That's schedule info. So we could put age under Qualifications, and schedule under Schedule. That seems reasonable. Thus: Qualifications: Must be 16 years of age or older. Schedule: Part-time: 9 to 28 hours per week; Full-time: 32 to 40 hours per week. Requirements: physical capabilities list. Responsibilities: duties list. About the role: intro paragraph. Benefits: list. We should not include Skills (no content). Not include Pay. Now format. We need to use

• for any list of duties/requirements/benefits. For prose use

  . We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: EEO line at end: "Zax LLC is an equal opportunity employer..." remove. Also remove duplicated lines. Now craft HTML. Start with

  About the role

  then

  ... intro.

  Intro: "As the team at Zaxbys expands, we're saving a seat for you!To our guests, Zaxbys is more than just a place to eat – it’s a place to have fun, spend time with friends, and enjoy great food.To our team members, Zaxbys is an indescribably great place to work!Cooks are directly responsible for creating a great guest experience by consistently serving quality food in a timely manner." We need to keep punctuation; there are missing spaces after exclamation? The original: "As the team at Zaxbys expands, we're saving a seat for you!To our guests, Zaxbys is more than just a place to eat – it’s a place to have fun, spend time with friends, and enjoy great food.To our team members, Zaxbys is an indescribably great place to work!Cooks are directly responsible for creating a great guest experience by consistently serving quality food in a timely manner." We should keep as is but maybe add spaces for readability? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Adding spaces is not changing substantive info, just formatting. Probably okay. But we could keep exactly as given, but it's hard to read. I'd add spaces after punctuation for readability but not change meaning. Might be considered altering? Safer to keep exactly as given but we can add spaces because they are not substantive? The instruction says do not invent or summarize away detail; adding spaces is not inventing detail. I think it's fine. We'll output:

  About the role

  As the team at Zaxbys expands, we're saving a seat for you! To our guests, Zaxbys is more than just a place to eat – it’s a place to have fun, spend time with friends, and enjoy great food. To our team members, Zaxbys is an indescribably great place to work. Cooks are directly responsible for creating a great guest experience by consistently serving quality food in a timely manner.

  Now Responsibilities: we need to list duties. The posting includes a paragraph "Cooks are directly responsible..." but we already used that. Then there is a heading "Job Duties and Responsibilities" then a list of items each starting with a verb. We'll combine all duty statements into a list. List items: - Complete all training requirements including: - Zaxbys Back of House Development Plan - Hands-on stations training - Any additional training required by Zax LLC - Provide friendly, enthusiastic service for all guests - Maintain awareness of current promotions - Enthusiastically represent the Zaxbys brand - Assist with guest service and front of house operations - Prepare menu items according to company standards and in a safe and sanitary manner - Ensure food and beverages are handled according to safety regulations and guidelines - Safely operate food preparation and cooking equipment - Maintain product levels in assigned stations in order to be prepared for immediate needs - Prepare and cook food items according to company standards - Accurately assemble and package guest orders - Maintain a clean and safe working environment - Keep work areas clean and organized - Maintain equipment and inform management of maintenance needs - Assist with inventory and storage management - Receive and stock incoming inventory deliveries - Hold and store food items following food safety guidelines - Inform management when inventory is needed - Clean and organize storage areas - Other responsibilities - Complete all tasks with a sense of urgency, in a timely manner - Work safely and follow all safety guidelines and procedures - Other duties as assigned We need to preserve the nested list for training requirements. Use
  • for any list. For nested list we can have
    • Complete all training requirements including:
      • Zaxbys Back of House Development Plan
      • Hands-on stations training
      • Any additional training required by Zax LLC
    etc. Now Requirements: physical capabilities list. Items: - Sit, stand, and walk continuously - Occasionally stoop, bend, crouch, or climb, including the use of ladders - Frequently lift, push, pull, and carry up to 50 pounds, including lifting overhead - Continuous use of hands and wrists for grasping and fine manipulation - Communicate proficiently through speech, reading, and writing - Maintain effective audio-visual perception and judgement to observe and respond to the environment - Work in an environment that features hot and cold temperature variations and exposure to food allergens - Operate and work safely with restaurant equipment including, but not limited to, knives, fryers, and potentially hazardous equipment Now Qualifications: Must be 16 years of age or older. Now Schedule: Part-time: Available to work 9 to 28 hours per week; Full-time: Available to work 32 to 40 hours per week. Now Benefits: list from "Why work at Zax?" and "Additional Benefits for Full-Time Team Members". Items: - FREE Meals On Shift & 50% Off Meals Off Shift - Flexible Schedule - Early Access to Pay - Opportunities to Advance - Benefits (maybe generic? but we already have benefits section; this line maybe redundant; but we can keep as "Benefits" but it's vague; maybe skip? The posting says "Benefits" as a bullet; but we already have a Benefits section; we could include it as a bullet but it's redundant. Better to keep as is? It says "Benefits" as a bullet; but that's just a heading; we could treat as a bullet but it's vague. Might be considered filler? It's not specific. Might be better to omit because it's not substantive. However the instruction: preserve ALL substantive information; do not invent or summarize away detail. The bullet "Benefits" is not substantive; it's just a label. Could be considered filler. I'd omit it. - Recognition Program - Employee Referral Program - 401(k) With Employer Match (additional eligibility requirements) - Additional Benefits for Full-Time Team Members: Medical, Dental, and Vision Insurance - Short and Long-Term Disability - Employer-Paid Life Insurance We could break "Additional Benefits for Full-Time Team Members" as a heading? But we only have Benefits section; we can include sub-items. Thus list: - FREE Meals On Shift & 50% Off Meals Off Shift - Flexible Schedule - Early Access to Pay - Opportunities to Advance - Recognition Program - Employee Referral Program - 401(k) With Employer Match (additional eligibility requirements) - Medical, Dental, and Vision Insurance (for full-time team members) - Short and Long-Term Disability (for full-time team members) - Employer-Paid Life Insurance (for full-time team members) We need to preserve the info that these are for full-time team members. The posting says "Additional Benefits for Full-Time Team MembersMedical, Dental, and Vision InsuranceShort and Long-Term DisabilityEmployer-Paid Life Insurance". So we can note that. Now we need to ensure we don't include any boilerplate like EEO line. Now produce HTML. Check that we