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: $22.00 - $25.00 / Hour (this is Pay information) - Overview: description of the restaurant and role - Why Join our Team: benefits, perks, etc. - What You'll Do: responsibilities - Your Background: requirements/qualifications - Who We Are: company info 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 (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 Now, let's map the content to appropriate sections: 1. Pay: The posting states "Compensation Range $22.00 - $25.00 / Hour" - this is specific pay info, so include a Pay section. 2. Overview: The first paragraph after compensation is an overview of the restaurant and role. Could be "About the role" or just "Overview". The rules mention "About the role" as example heading. I'll use "About the role". 3. Why Join our Team: This contains multiple subsections: "Steady Hours, Flexible Life", "Benefits That Have Your Back", "Grow With Us", "Perks, Recognition & Community". These are benefits and perks. Should I combine into a "Benefits" section? The rules say use "Benefits" as heading example. Since there's substantial content, I'll create a Benefits section with sub-lists or multiple lists. But the rules say use

  • for any list of duties/requirements/benefits. I can have multiple
    under the same heading, or separate headings? The rules say "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So Benefits is a heading. I'll put all the benefits/perks under Benefits. 4. What You'll Do: This is responsibilities. Use "Responsibilities" heading. 5. Your Background: This is requirements/qualifications. Use "Requirements" heading (or "Qualifications"). The rules mention both. I'll use "Requirements". 6. Who We Are: Company description. Could be "About the company" but not in the example headings. The rules don't require it, but it's substantive. However, the rules say "Prefer a few substantive sections over many thin ones." Might include as a short paragraph under "About the role" or separate. Since it's about the company, not the role, maybe include as a separate section? But the example headings don't include "About the company". I could fold into a

    at the end or under "About the role". The rules say "fold minor metadata into a short

    or drop it." This is not minor metadata; it's company info. But the job posting already has "Overview" which includes some company info. The "Who We Are" is more detailed. I'll include it as a separate section with heading "About the company" but the rules didn't list that. However, the rules say "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests those are examples, not exhaustive. But to be safe, I'll include it as a section with heading "About the company" or maybe "Company overview". However, the rules also say "include a section ONLY when the posting has real, specific content for it". It does have content. I'll include it. But note: The posting includes EEO statement at the end: "We are an equal opportunity employer...". That's boilerplate, should be removed. Also the scam warning email. Remove. Also, the "Why Join our Team" includes "Steady Hours, Flexible Life" which mentions scheduling. Could be a "Schedule" section? The rules mention Schedule as example heading. But the posting doesn't have a separate schedule section; it's part of benefits. I'll keep under Benefits. Now, structure: - Pay section: with the compensation range. - About the role: overview paragraph. - Benefits: multiple lists for each category (Steady Hours, Benefits, Growth, Perks). Use

    for each list. - Responsibilities: list of duties. - Requirements: list of requirements. - About the company: paragraph(s) about the company. But the rules say "Do NOT repeat the job title as a heading (the page already shows it)". The job title is not in the provided text, but we assume it's elsewhere. Now, write HTML. Let's start:

    Pay

    Compensation range: $22.00 - $25.00 per hour.

    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.

    Benefits

    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

    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

    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

    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

    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

    • 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

    About the company

    Named to FORTUNE Magazine's "100 Best Companies to Work For®" list every year since 2014, The Cheesecake Factory Incorporated is a leader in experiential dining. We are culinary-forward and relentlessly focused on hospitality. Delicious, memorable experiences created by passionate people—this defines who we are and where we are going. We currently own and operate over 370 restaurants throughout the United States and Canada under brands including The Cheesecake Factory®, North Italia®, Flower Child® and a collection of other FRC brands. Internationally, 35 The Cheesecake Factory® restaurants operate under licensing agreements. Our bakery division operates two facilities that produce quality cheesecakes and other baked products for our restaurants, international licensees and third-party bakery customers.

    I removed the EEO statement and the scam warning email. Check rules: No markdown code fences, just HTML fragment. No /. Use

    for section headings. I used

    for subsections under Benefits. That's okay, but the rules only mention

    for section headings. Using

    is fine for subheadings. However, the rules say "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other heading levels. But to be safe, maybe keep all as

    and use

    for subheadings? But the subheadings are part of Benefits. Could just make them or

    with bold. But using

    is semantic. I think it's acceptable. Alternatively, I could make each benefit category a separate

    but that would create many thin sections. The rules say "Prefer