Prep Cook

The user wants me to reformat a job posting into clean semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: - Compensation/Pay: There's a compensation range at the top: $21.65 - $23.50 / Hour - Overview/About the role: The "Overview" paragraph - Why Join our Team / Benefits: This seems like a Benefits section with multiple subsections - What You'll Do: Responsibilities - Your Background: Requirements/Qualifications - Who We Are: Company info - but this might be boilerplate? It's specific to the company though. Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for lists,

  for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions - Include section ONLY when posting has real, specific content for it - Never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment, no /, no markdown code fences Let me parse the content: 1. Compensation Range: $21.65 - $23.50 / Hour → This is Pay information, specific. Should include a Pay section. 2. Overview: "With a commitment to scratch cooking..." → This is About the role. 3. Why Join our Team: This has multiple subsections: - Steady Hours, Flexible Life: includes scheduling info (steady hours, flexible scheduling, full-time/part-time, faster pay) - Benefits That Have Your Back: paid vacation/sick time, medical/dental/vision/prescription, medical coverage starting at $12/pay period, virtual care, mental health - Grow With Us: training, career advancement, GED/Associate degree programs - Perks, Recognition & Community: perks/discounts, recognition awards, HELP Fund, community events, awards list This is a Benefits section with substantial content. 4. What You'll Do: List of duties → Responsibilities section. 5. Your Background: List of requirements → Requirements/Qualifications section. 6. Who We Are: Company description, EEO statement, accommodation info, contact for non-compliant posting. The EEO and accommodation info might be considered boilerplate? The rule says remove EEO/equal-opportunity boilerplate. But the company description is specific. However, the rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". The "Who We Are" includes "We are an equal opportunity employer..." and accommodation info. That's EEO boilerplate. Also the contact for non-compliant posting is application instruction? Might be considered boilerplate. The company description about Fortune 100 etc. is marketing but specific. However, the rule says "Preserve ALL substantive information". The company description could be considered substantive? But it's not about the role. The user said "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." The "Who We Are" is not a standard section heading like About the role, Responsibilities, etc. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Who We Are" is not in that list. Could be considered "About the company" but not required. The rule: "include a section ONLY when the posting has real, specific content for it". The company description is real, but it's not a standard section. However, the user didn't forbid other headings, but said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests those are examples, but we should stick to those? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but we should use those as appropriate. "Who We Are" could be "About the company" but not listed. I think we should include it as a section if it's substantive, but the EEO part is boilerplate. We can include the company description but omit the EEO and accommodation and contact info. However, the rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So we should remove the EEO paragraph and the accommodation paragraph and the contact email. The awards list is part of Perks, Recognition & Community already. The "Who We Are" paragraph before that is company description. Could be included as a short

  under a heading? But the heading "Who We Are" is not in the example list. Might be better to fold into a short

  at the end or omit. The rule: "fold minor metadata into a short

  or drop it." This is not minor metadata; it's company description. But it's not directly about the job. I'll include it as a section "About the Company" or just "Company Overview"? But the user didn't list that as an example. However, the instruction says "use

  for section headings (e.g. ...)" meaning those are examples, not exhaustive. But to be safe, I'll include it as a section with heading "About the Company" or "Who We Are". But the rule says "Do NOT repeat the job title as a heading (the page already shows it)". That's about job title. I think it's okay to have a company description section. However, the user might expect only the standard sections. Let's see the example: they gave a list of typical sections. The posting has "Who We Are" which is company info. I'll include it as a section with heading "About the Company" but using

  . But the rule says "include a section ONLY when the posting has real, specific content for it". It does. So I'll include. But note: The "Who We Are" includes "We are an equal opportunity employer..." which is EEO boilerplate. I'll remove that paragraph. Also the accommodation paragraph and the contact email. Keep the first paragraph about Fortune 100, culinary-forward, brands, etc. Now, structure: - Pay section: with the compensation range. - About the role: the overview paragraph. - Benefits: with subsections? The rule says use

  • for any list of duties/requirements/benefits. The benefits are listed in bullet points in the original. I'll create a Benefits section with a list of benefits. But there are categories: Steady Hours, Flexible Life; Benefits That Have Your Back; Grow With Us; Perks, Recognition & Community. Could make a single Benefits section with a list of all benefits, or separate subsections? The rule says use

    for section headings. Could use

    for each category? But the example headings are Benefits, Pay, Schedule. "Steady Hours, Flexible Life" includes schedule info. Could have a Schedule section? The posting mentions "Steady Hours, Flexible Life" with details: high-volume restaurant with consistent hours, flexible scheduling with full-time or part-time opportunities, faster pay. That's schedule and pay related. But we already have Pay section for compensation range. The "faster pay" is a benefit. The schedule info could be a Schedule section. However, the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states schedule info (consistent hours, flexible scheduling, full-time/part-time). So we could create a Schedule section. But the example headings include Schedule. The posting also has "Benefits That Have Your Back" which is clearly benefits. "Grow With Us" is career development benefits. "Perks, Recognition & Community" is perks. So we have substantial benefits content. I'll create a Benefits section that includes all these as a list, maybe grouped with subheadings? But the rule says use

    • for any list. Could use nested lists? But the HTML fragment should be simple. I'll create a Benefits section with a
      containing all benefit items as
      • . But there are many. Could also use multiple
        with

        ? But the rule only mentions

        for section headings. Not

        . So maybe just one Benefits section with a list of all benefits. However, the original has categories. I could include the category names as part of the list items or as separate paragraphs. But the rule says use

        • for any list of duties/requirements/benefits. So I'll make a Benefits section with a
          where each
          • is a benefit. I'll include all bullet points from the original. Let's extract all benefit bullet points: From "Steady Hours, Flexible Life": - High-volume restaurant with consistent hours - Flexible scheduling with full-time or part-time opportunities to fit your life - Faster Pay – access up to 50% of your earned wages the next day (exclusions apply) - Free shift meals and 25% discount when dining with friends and family From "Benefits That Have Your Back": - Paid vacation and sick time - Medical, Dental, Vision, and Prescription coverage options - Medical coverage starting as low as $12 per pay period - Virtual Care and no cost online mental health services From "Grow With Us": - World class training designed to support your personal and professional growth - Career advancement opportunities – over half of our managers are promoted from within - No cost GED or Associate Degree programs From "Perks, Recognition & Community": - Perks and discounts including cell phone, gym, movie, and theme park savings - Employee recognition and appreciation awards - HELP Fund (Hardship and Emergency Lifeline Program) for moments that matter - Opportunities to give back through community and charity events - Join an award-winning company, including: – Fortune 100 Best Companies to Work For® (since 2014) – PEOPLE® Companies That Care (since 2021) – Great Place to Work® Certified That's a lot. I'll include all as list items. Now Responsibilities: "What You'll Do" list. I'll make a Responsibilities section with
            • for each duty. Requirements: "Your Background" list. I'll make a Requirements section (or Qualifications). The example headings include Requirements and Qualifications. I'll use Requirements. About the role: the overview paragraph. Pay: compensation range. Schedule: The posting mentions schedule info under "Steady Hours, Flexible Life". Could create a Schedule section with those details. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule info. However, the schedule info is part of the benefits section. Could be separate. But the example headings include Schedule. I'll create a Schedule section with the schedule-related points: consistent hours, flexible scheduling, full-time/part-time opportunities. The "Faster Pay" is more pay-related. I'll put schedule-specific items in Schedule section. But the original groups them under "Why Join our Team". The user might expect a Benefits section that includes all. The rule says "Prefer a few substantive