Catering Specialist- Hays Farm

We need to output HTML fragment with sections: Benefits, Wage Information? Actually we need to follow rules: Use

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. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the job posting text. Given text: "Benefits Offered | Wage Information High-Paying Tip Pool!FREE Delicious Meals on every shift!No late nights, no early mornings!Flexible Schedule!Great Environment!Career Path to Ownership!The option to get paid daily! Plus, once you're eligible: Medical, Dental, Vision, and Disability Insurance options!Paid Time Off potential!401k program with employer match! We get it – you want a flexible job you’re excited about, co-workers you enjoy, and work you can be proud of. You can find that at Taziki’s. Experience is great, but not required - we can teach you everything you need! Job Summary: Be a Taziki’s Ambassador to customers for our service, our menu, our story, and our cultureProvide exceptional customer service face-to-face or over the phonePrepare, assemble, and check catering ordersDeliver and set up catering ordersEnsure the catering vehicle is clean and stocked with suppliesKnow menu items, packaging, and pricing with the ability to communicate them effectively Understand POS and Advanced Order systemDrive safely at all times; abiding by all traffic lawsComply with applicable Health Department standards Qualifications: Must be 21 years of ageFlexible scheduleEnergeticPrior food service experience preferredMust have reliable transportationLeadership, guest service, and verbal communication skills with guests/team membersAbility to thrive in a fast-paced environment, balancing multiple tasks and prioritiesDemonstrate sound decision-making and problem-solving skillsHave and maintain a clean driving record All Employees Must: Understand and abide by all company standards and policies (provided in your handbook) Obtain a Food Manager’s certification shortly after beginning employment Your Working Conditions/ Hours: Mornings Afternoons Evenings Weekends &/ or holidays (depending on events) Your Physical Requirements: (with or without a reasonable accommodation) Standing Walking Reaching Carrying/ Lifting up to 30 pounds Wiping Driving Taziki’s is an Equal Opportunity Employer Company Overview Taziki's Café is a fast-casual restaurant brand with more than 90 locations in 17 states. Our menu is Mediterranean-inspired with a Southern flair, and our mission is to create an environment that combines modern Mediterranean fare with meaningful human connection. We are a family of big-hearted foodies committed to making an impact in our communities!" We need to remove boilerplate: "Taziki’s is an Equal Opportunity Employer" is EEO boilerplate, remove. Also maybe "Company Overview" is not a required heading; we can keep as prose? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only create sections for those headings if there is substantive content. The posting includes "Benefits Offered | Wage Information" which is a combined heading. We can treat that as Benefits and Pay? Actually "Benefits Offered | Wage Information" includes both benefits and wage info. The text after that includes many bullet-like statements: "High-Paying Tip Pool!FREE Delicious Meals on every shift!No late nights, no early mornings!Flexible Schedule!Great Environment!Career Path to Ownership!The option to get paid daily! Plus, once you're eligible: Medical, Dental, Vision, and Disability Insurance options!Paid Time Off potential!401k program with employer match! We get it – you want a flexible job you’re excited about, co-workers you enjoy, and work you can be proud of. You can find that at Taziki’s. Experience is great, but not required - we can teach you everything you need!" Thus we have benefits and wage info. We can create a Benefits section (list) and maybe a Pay section? The wage info includes "High-Paying Tip Pool!" and "option to get paid daily!" but not explicit wage numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits and wage info (though vague). So we can include Benefits and Pay sections. However we need to avoid filler like "commensurate with experience". The text includes "High-Paying Tip Pool!" which is a benefit/wage. Also "FREE Delicious Meals on every shift!" etc. So we can list those as bullet points. We also have Job Summary (responsibilities). That could be under Responsibilities heading. The text after "Job Summary:" includes a list of duties. So we can create a Responsibilities section with

  • . Qualifications: after "Qualifications:" includes list. So we can create Qualifications section. Also there is "All Employees Must:" which could be considered Requirements? Might be part of Qualifications or Requirements. Could combine with Qualifications or separate Requirements. The instruction: Use headings like Requirements, Qualifications, Skills. We have Qualifications already. "All Employees Must:" could be considered Requirements. We'll create a Requirements section for those. Also "Your Working Conditions/ Hours:" includes schedule info: Mornings Afternoons Evenings Weekends &/ or holidays (depending on events). That's schedule info. So we can create a Schedule section. Also "Your Physical Requirements:" includes list: Standing Walking Reaching Carrying/ Lifting up to 30 pounds Wiping Driving. That's physical requirements; could be part of Requirements or maybe a separate section like Physical Requirements but not in allowed headings. Could fold into Requirements. We should avoid creating sections with filler. We have substantive content for Benefits, Pay (maybe), Responsibilities, Qualifications, Requirements, Schedule. We need to decide which headings to use. The allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have: - Benefits: yes. - Pay: we have wage info (High-Paying Tip Pool, option to get paid daily). Could be considered Pay. We'll include Pay. - Responsibilities: yes (Job Summary). - Qualifications: yes. - Requirements: we have "All Employees Must:" and physical requirements. - Schedule: yes (Working Conditions/Hours). - Skills: not explicitly listed; maybe we could infer from Qualifications but better not to create if not explicit. We'll skip Skills. - About the role: we have a company overview paragraph; could be About the role. The posting includes "Company Overview" after EEO line. That's substantive about the company. Could be About the role. We'll include About the role. Thus we will have sections: About the role, Benefits, Pay, Responsibilities, Qualifications, Requirements, Schedule. We need to ensure we don't repeat job title as heading (not needed). Remove boilerplate: EEO line removed. Also remove duplicated lines? Not seeing duplicates. We need to preserve all substantive information. Let's extract each piece. First, About the role: The company overview: "Taziki's Café is a fast-casual restaurant brand with more than 90 locations in 17 states. Our menu is Mediterranean-inspired with a Southern flair, and our mission is to create an environment that combines modern Mediterranean fare with meaningful human connection. We are a family of big-hearted foodies committed to making an impact in our communities!" Also maybe the earlier sentence: "We get it – you want a flexible job you’re excited about, co-workers you enjoy, and work you can be proud of. You can find that at Taziki’s. Experience is great, but not required - we can teach you everything you need!" That's more about the job; could be part of About the role or Benefits. But we already have Benefits section; we could keep that sentence in Benefits? It's about flexible job etc. Might be better to put in About the role as description. However the instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The sentence is specific enough. We'll include it in About the role. Thus About the role paragraph: combine both. Now Benefits: list items: - High-Paying Tip Pool! - FREE Delicious Meals on every shift! - No late nights, no early mornings! - Flexible Schedule! - Great Environment! - Career Path to Ownership! - The option to get paid daily! - Medical, Dental, Vision, and Disability Insurance options! (once eligible) - Paid Time Off potential! - 401k program with employer match! We need to keep exclamation marks? Probably keep as is. We need to format as
    • each. Pay: The wage information includes "High-Paying Tip Pool!" and "The option to get paid daily!" but those are already in Benefits. Might be overlapping. However the heading "Benefits Offered | Wage Information" suggests both. To avoid duplication, we could treat Benefits section as the list of benefits, and Pay section maybe just mention "High-Paying Tip Pool!" and "option to get paid daily!" but those are already in benefits. Could we split? The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Benefits and Pay into one Benefits section? But the instruction says we can create Pay section only if posting actually states them. It does state wage info (High-Paying Tip Pool, option to get paid daily). However we already have those in benefits list. To avoid duplication, we could keep Benefits section with all benefit-like items, and Pay section maybe just note "High-Paying Tip Pool; option to get paid daily". But that duplicates. Better to combine into Benefits section and not create Pay section to avoid thin sections. However the instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state them, but we can still choose not to create Pay if we incorporate into Benefits? The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Pay section and keep Benefits only. That seems acceptable. Thus we will have Benefits section only. Now Responsibilities: from Job Summary: list: - Be a Taziki’s Ambassador to customers for our service, our menu, our story, and our culture - Provide exceptional customer service face-to-face or over the phone - Prepare, assemble, and check catering orders - Deliver and set up catering orders - Ensure the catering vehicle is clean and stocked with supplies - Know menu items, packaging, and pricing with the ability to communicate them effectively - Understand POS and Advanced Order system - Drive safely at all times; abiding by all traffic laws - Comply with applicable Health Department standards We'll put each as
    • . Qualifications: list: - Must be 21 years of age - Flexible schedule - Energetic - Prior food service experience preferred - Must have reliable transportation - Leadership, guest service