Line Cook

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections: - Compensation Range: $17.50 - $22.00 / Hour (this is Pay information) - Overview: description of the role and company - Why Join our Team: benefits, perks, etc. - What You'll Do: responsibilities - Your Background: requirements/qualifications - Who We Are: company description 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 (the page already shows it) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include section ONLY when posting has real, specific content for it - Never emit heading followed by filler/placeholder text - 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 Now, let's map the content to appropriate sections: 1. Pay: The posting has "Compensation Range $17.50 - $22.00 / Hour" - this is specific pay info, so include a Pay section. 2. About the role: The "Overview" paragraph describes the role and company. Could be "About the role" or "Overview". The rules mention "About the role" as example heading. I'll use "About the role". 3. Benefits: The "Why Join our Team" section has multiple subsections: "Steady Hours, Flexible Life", "Benefits That Have Your Back", "Grow With Us", "Perks, Recognition & Community". These are benefits/perks. Should I combine into one Benefits section? The rules say "Benefits" as example heading. I'll create a Benefits section with sub-lists or multiple lists. Since it's a list of benefits, I can use

  with nested lists or separate lists. But the rule says use
  • for any list of duties/requirements/benefits. I'll create a Benefits section with multiple
    lists for each category. 4. Responsibilities: "What You'll Do" is clearly responsibilities. 5. Requirements/Qualifications: "Your Background" is requirements/qualifications. Could be "Requirements" or "Qualifications". The rules mention both. I'll use "Requirements" as heading. 6. Company description: "Who We Are" is company info. Could be "About the company" but not in example headings. The rules don't mention company description heading. Might fold into "About the role" or separate. Since it's substantive, I'll include a "About the company" heading? But the example headings don't include that. The rules say "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So only those example headings? It says "e.g." meaning examples, not exhaustive. But "Prefer a few substantive sections over many thin ones." I could include "About the company" as a section. However, the overview already includes company info. The "Who We Are" is more detailed. I'll include it as "About the company" or maybe "Company overview". But to stick to examples, maybe not. I'll include it as a separate section with heading "About the company" since it's substantive. But the rule: "include a section ONLY when the posting has real, specific content for it". The posting has real content for company description. I'll include it. Now, schedule: The posting mentions "Steady Hours, Flexible Life" and "Flexible scheduling with full-time or part-time opportunities". That's schedule info. Should I create a Schedule section? The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule info. So I could create a Schedule section. But the example headings include Schedule. I'll include a Schedule section. But note: "Prefer a few substantive sections over many thin ones." The schedule info is brief. Could be part of Benefits. However, the "Why Join our Team" includes "Steady Hours, Flexible Life" as a subsection. I'll keep Benefits as one section covering all perks, benefits, growth, perks, recognition. And maybe separate Schedule? Let's see. The "Steady Hours, Flexible Life" includes: "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". That's a mix of schedule, pay, meals. The "Benefits That Have Your Back" includes paid vacation, medical, dental, vision, etc. "Grow With Us" includes training, advancement, education. "Perks, Recognition & Community" includes discounts, recognition, HELP Fund, community events, awards. I think it's best to have a Benefits section that includes all these as sub-lists. And a separate Pay section for the compensation range. Schedule could be part of Benefits or separate. Since the rules mention Schedule as example heading, and the posting has specific schedule info, I'll create a Schedule section. But the compensation range is hourly pay, that's Pay. The "Faster Pay" is a benefit (early wage access). That could be in Benefits. Let's structure: - Pay: compensation range - Schedule: flexible scheduling, full-time/part-time, consistent hours - About the role: overview paragraph - Responsibilities: what you'll do list - Requirements: your background list - Benefits: all the benefits, perks, growth, recognition - About the company: who we are But the rules say "Do NOT repeat the job title as a heading (the page already shows it)". The job title is not given in the text, but presumably "Line Cook". The posting starts with "Compensation Range...". No title. So fine. Now, I need to output HTML fragment with

    and

    • and

      . Let's write. First, Pay section:

      Pay

      Compensation range: $17.50 - $22.00 per hour.

      Schedule section:

      Schedule

      • High-volume restaurant with consistent hours
      • Flexible scheduling with full-time or part-time opportunities
      • Faster Pay – access up to 50% of earned wages the next day (exclusions apply)
      • Free shift meals and 25% discount when dining with friends and family
      But "Faster Pay" is more a pay benefit, but it's under "Steady Hours, Flexible Life". I'll keep it in Schedule or Benefits? I'll put in Schedule as it's about pay timing. Or maybe in Benefits. I'll put in Benefits under a "Financial perks" sublist. But to keep simple, I'll include in Schedule. About the role:

      About the role

      With over 250 menu items prepared from scratch daily using fresh, high-quality ingredients, every dish reflects our commitment to culinary excellence in food service and hospitality. Our Line Cooks thrive in a fast-paced, high-volume kitchen, taking ownership and pride in producing delicious dishes through precise cooking techniques, attention to detail, and consistency. While our restaurants are busy and our standards are high, you will love our team spirit and have fun creating memorable food and guest experiences.

      Responsibilities:

      Responsibilities

      • Prepare recipes efficiently using various cooking methods and culinary techniques
      • Read & follow recipes using accurate measurements and weights for consistent execution
      • Demonstrate strong knife skills including chopping, dicing, and slicing
      • Ensure order accuracy through mise en place, proper portioning, and cooking to correct temperatures
      • Wow our guests with beautiful plating, presentation, and garnishing
      • Support opening and closing duties including station setup & breakdown, FIFO (First In, First Out) stocking, cleanliness, and organization
      • Adhere to food safety and sanitation standards, including proper food handling, cross contamination prevention, and food allergy awareness
      • Work well under pressure, multitasking with speed, efficiency, and a sense of urgency
      • Support teamwork through clear, effective communication
      • Follow instructions to uphold high standards
      Requirements:

      Requirements

      • Prior cooking experience in a full-service restaurant is ideal
      • Station experience preferred: Flat Top, Grill, Broil, Fry, Pasta, Sauté, Salad, Pizza, Pantry, Appetizer, Oven or Prep
      • Familiarity with cooking techniques is a plus: roasting, grilling, sautéing, or scratch cooking
      • Proficient with kitchen tools and equipment, with an understanding of back-of-house operations
      • Ability to deliver accurate orders with consistency
      • Knowledge of food safety, sanitation, and food industry standards
      • Dependable, dedicated, and adaptable with a strong work ethic
      • Reliable and punctual team player with a positive, patient attitude
      • Passionate about hospitality and contributing to a positive team culture
      • Ability to lift up to 50 pounds, stand for extended periods, continuously bend, reach and twist
      • Must be at least 18 years old
      Benefits:

      Benefits

      • 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

      Growth & Development

      • 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

      Perks & Recognition

      • 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

      Awards & Recognition

      • Fortune 100 Best Companies to Work For® (since 2014)
      • PEOPLE® Companies That Care (since 2021)
      • Great Place to Work® Certified
      But the rules say use

      for section headings. Should I use

      for subsections? The rules don't forbid, but they say "use

      for section headings". It doesn't say not to use other headings. But to keep semantic, maybe use

      for main sections and

      for subsections. However, the output should be a fragment. I'll use

      for main sections