Meat Cutter

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. The posting includes description of role (day in the life) which could be "About the role" or maybe "Responsibilities". There's a "What You Bring To The Table" list of skills/qualities. There's "Requirements" list. There's "Why You Will Choose Us" includes benefits and values. There's also "Our Values". There's no explicit Pay or Schedule specifics (though schedule mentioned: Availability to work early mornings, evenings, weekends, holidays). That's schedule info. So we can include Schedule section with that detail. Benefits: they list inclusive work culture, competitive wages paid weekly, flexible work schedules, associate discounts, leaders invested in training, health and welfare benefits, vacation/PTO. So we can include Benefits section with those items. Pay: they mention competitive wages paid weekly, but that's more benefit; no specific pay amount. Since we should not create Pay section unless posting actually states them. It says "Competitive Wages paid weekly" which is a statement about pay but not a specific number. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive Wages paid weekly" is not filler; it's a statement. Could be considered substantive. However they also said "Prefer a few substantive sections over many thin ones." Might combine Pay into Benefits? But they said include a section ONLY when posting has real, specific content for it. The posting does mention wages. So we could include Pay section with that line. However they also said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive wages paid weekly, so we can include Pay. Schedule: they state availability to work early mornings, evenings, weekends, holidays. That's schedule. So include Schedule. Now we need to decide headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role: the initial paragraph describing day in the life. Could be About the role. Responsibilities: maybe the duties like preparing meat, interacting with customers, maintaining department, using equipment, monitoring freshness, maintaining clean work areas, etc. Could be responsibilities. Qualifications: maybe the "What You Bring To The Table" list? That seems like skills/qualifications. Could be Skills. Requirements: the list under Requirements. Benefits: the "Why You Will Choose Us" bullet list. Pay: competitive wages paid weekly. Schedule: availability to work early mornings, evenings, weekends, holidays. We must not repeat job title as heading. Not include Job ID etc. We must use

for section headings. Use

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

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: cookie/navigation/legal/EEO etc. There's none. We need to output only HTML fragment. Let's extract details. About the role (prose): "As a Meat Cutter, your day is centered around preparing fresh meat products and maintaining a high standard of quality. You work with a variety of cuts, preparing beef, poultry, and other items for display while ensuring products are trimmed, packaged, and labeled correctly. Along the way, you interact with customers, answer questions, and accommodate special cut requests to help them find exactly what they need. Another part of the role is keeping the department organized, stocked, and operating smoothly. You’ll use equipment such as knives, grinders, and saws to prepare products, monitor freshness, and maintain clean work areas that meet food safety standards. Between preparing products, maintaining displays, and following safety procedures, the work stays steady making it a good fit for someone who values precision, consistency, and hands‑on food preparation." That's a paragraph. Responsibilities: could be bullet list of duties: preparing fresh meat products, trimming, packaging, labeling, interacting with customers, answering questions, accommodating special cut requests, keeping department organized, stocked, operating smoothly, using equipment (knives, grinders, saws, wrapping equipment), monitoring freshness, maintaining clean work areas meeting food safety standards, maintaining displays, following safety procedures. But many of these are already in the prose. To avoid duplication, we could keep prose as About the role and responsibilities as bullet list summarizing duties. However we must preserve all substantive information; we can split but ensure not to lose detail. Could keep About the role as prose covering day, and Responsibilities as bullet list of specific duties. Ensure we don't omit any detail. Let's list responsibilities: - Preparing fresh meat products (beef, poultry, other cuts) for display - Trimming, packaging, and labeling products correctly - Interacting with customers, answering questions, accommodating special cut requests - Keeping the department organized, stocked, and operating smoothly - Using equipment such as knives, grinders, saws, and wrapping equipment following safety guidelines - Monitoring freshness and maintaining clean work areas that meet food safety standards - Maintaining displays - Following safety procedures That seems comprehensive. Now Requirements: list: - Must be 18 years of age or older - Prior meat cutting or food preparation experience required - Ability to operate power equipment such as saws, grinders, and slicers following training and safety guidelines - Knowledge of meat cuts and preparation techniques required - Ability to work in refrigerated environments and maintain sanitation standards - Availability to work early mornings, evenings, weekends, and holidays - Compliance with company policies including food safety, sanitation, and dress standards Now Qualifications/Skills: The "What You Bring To The Table" list includes: - Customer Interaction Skills: Clear communication when assisting customers and fulfilling special cut requests - Meat Cutting Skills: Experience trimming, cutting, and preparing meat products using standard techniques - Equipment Use: Handling knives, grinders, saws, and wrapping equipment following safety guidelines - Attention to Detail: Accuracy in portioning, packaging, labeling, and maintaining product quality - Product Knowledge: Familiarity with meat cuts, preparation methods, and cooking recommendations - Sanitation Awareness: Knowledge of cleaning procedures and safe food handling practices - Organization & Time Management: Managing workflow while maintaining clean and orderly work areas - Merchandising Awareness: Maintaining well-stocked and visually consistent meat displays - Operational Awareness: Following company policies, safety requirements, and regulatory guidelines - Physical Capability: Comfort with standing for extended periods, working in cold environments, and lifting up to 75 lbs. We could treat this as Skills section. Or Qualifications. The instruction: Use headings like Skills, Qualifications. We'll decide to put this as Skills. Now Benefits: list from "Why You Will Choose Us": - Inclusive work culture built on belonging - Competitive Wages paid weekly - Flexible work schedules - Associate discounts - Leaders invested in your training, career growth & development - Health and welfare benefits for eligible employees (Medical, Dental, 401k and more!) - Vacation / Paid Time Off Also "Our Values" list but that's not benefits; could be separate section but we don't have a heading for values. Could include under Benefits? Might be extra but we can include as part of Benefits or maybe as a separate section "Values". However we only have allowed headings list; we could add a section for Values if we want, but instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings. Safer to stick to those. Values could be omitted? But we must preserve ALL substantive information. The values are substantive. Could we incorporate them into Benefits or About the role? They are separate statements about company values. Could we add a section "Values" as

  ? The instruction didn't explicitly forbid other headings, but gave examples. It said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the expected headings; but we could still add others if needed. However to be safe, we could incorporate values into Benefits or About the role as a bullet list under Benefits? Might be okay. But we already have Benefits list; we could add another bullet list for Values under Benefits? Might be confusing. Alternatively, we could create a section "Values" as

  and still follow instruction? The instruction didn't say you cannot use other headings, just that you should use

  for section headings (e.g., those). It's ambiguous. I'd lean to include Values as its own section because it's substantive and not covered elsewhere. The instruction says "Prefer a few substantive sections over many thin ones." Adding Values adds another section, making more sections. But we already have many sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. That's 7. Adding Values makes 8. Still okay. But we must not create Pay/Schedule/Benefits sections unless posting actually states them. They do. So fine. Now Pay: we have "Competitive Wages paid weekly". That's a statement. We'll put that as a

  under Pay heading. Schedule: we have "Availability to work early mornings, evenings, weekends, and holidays". That's schedule. Now we need to ensure we don't repeat info. For example, "Competitive Wages paid weekly" appears also in Benefits list. If we put it in both Benefits and Pay, that's duplication. We should avoid duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication but we should avoid repeating same detail unnecessarily. Better to put wages only in Pay section, and not duplicate in Benefits. However Benefits list includes "Competitive Wages paid weekly". If we remove it from Benefits, we lose that benefit detail. But we still have it in Pay. The benefit is still preserved. So we can omit from Benefits list to avoid duplication. However the Benefits section may then lack that item; but it's okay because we still have the info elsewhere. The instruction: "Prefer a few substantive sections over many thin ones." Having Pay separate may be thin but it's specific. Alternatively, we could keep wages only in Benefits and not have Pay section. But we have schedule info separate; we could combine Pay and Benefits? The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state wages, so we could have Pay. But we could also incorporate wages into Benefits and not have Pay. Which is better? The instruction: "Prefer a few substantive sections over many thin ones." Having both Benefits and Pay may be thin. But we already have Benefits with multiple items; Pay would be just one line. Might be thin. Better to incorporate wages into Benefits and not have a separate Pay section. However the instruction also says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't say we must create them if they exist; we can choose not to. So we can omit Pay section and keep wages in Benefits. Similarly, Schedule: we have schedule info; we could keep it as its own section or incorporate into Benefits? There's also "Flexible work schedules" in Benefits. The schedule detail about availability to work early mornings, evenings, weekends, holidays is more specific than flexible work schedules. Could be part of Benefits or Schedule. If we make Schedule section, we have that detail. Benefits already includes "Flexible work schedules". That's somewhat overlapping but not same. Could keep both. But to