Line Cook
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 sections:
1. Pay: The posting has "Compensation Range $16.50 - $21.75 / 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 and perks. Should I combine into a Benefits section? The rules say "Benefits" as example heading. I'll create a Benefits section with sub-lists.
4. Responsibilities: "What You'll Do" is clearly responsibilities.
5. Requirements/Qualifications: "Your Background" lists requirements. Could be "Requirements" or "Qualifications". The rules mention both. I'll use "Requirements" as heading.
6. Schedule: The posting mentions "Flexible scheduling with full-time or part-time opportunities" and "Steady Hours". That's schedule info. Could include a Schedule section.
7. Company info: "Who We Are" is company description. Could be "About the company" but not in example headings. The rules don't list "About the company" as example, but "About the role" is. Might include as a section? The rules say "include a section ONLY when the posting has real, specific content for it". It has content. But the example headings don't include company. However, the user didn't forbid other headings. 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 they say "Prefer a few substantive sections over many thin ones." I think including company info is okay, but maybe fold into About the role? The Overview already includes some company info. The "Who We Are" is more detailed. I'll include a "About the company" section? But the rules didn't list it. However, the posting has substantive content. I'll include it as "About the company" or "Company overview". But to stay close to examples, maybe "About the role" can encompass company? The Overview is about the role and company. The "Who We Are" is separate. I'll create a "Company" section? Let's see: 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 input, but presumably "Line Cook". The page already shows it. So we don't need to repeat.
I'll structure as:
- Pay
- About the role
- Benefits
- Responsibilities
- Requirements
- Schedule (if specific)
- Company (maybe)
But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states pay, benefits, and schedule (flexible scheduling). So include all three.
Now, for Benefits: The posting has multiple categories. I'll create a Benefits section with subheadings? But the rules say use for section headings, and - for lists. Could use nested lists or just combine into one list. But the content is rich. I'll use
for Benefits, then maybe for subcategories? The rules only mention for section headings. They didn't forbid . But to keep simple, I'll use for main sections and within Benefits, use with maybe grouped items. However, the content has distinct categories: "Steady Hours, Flexible Life", "Benefits That Have Your Back", "Grow With Us", "Perks, Recognition & Community". I could make each a separate ? But that would be many thin sections. The rules say "Prefer a few substantive sections over many thin ones." So better to have one Benefits section with sub-lists. I'll use Benefits
then maybe for each category? But the rules didn't specify . I think it's okay to use for subsections. However, the instruction says "use for section headings". It doesn't say you cannot use other headings. But to be safe, I'll keep only for main sections. For subcategories, I'll use or just list items with bold labels. But the content is better structured with subheadings. I'll use for subcategories within Benefits. That's still semantic HTML.
Alternatively, I could make each category a separate section: "Schedule & Flexibility", "Health & Wellness Benefits", "Growth & Development", "Perks & Recognition". But that might be too many. The rules say "Prefer a few substantive sections over many thin ones." So I'll keep one Benefits section with sub-lists.
Let's decide: I'll create a Benefits section with an introductory paragraph, then use for each category, maybe with a label for each category. But the content is list items. I'll do:
Benefits
...
Schedule & Flexibility
...
Health & Wellness
...
Growth & Development
...
Perks & Recognition
...
But the rules didn't mention . However, it's still semantic HTML. I think it's acceptable.
Now, for Schedule: The posting mentions "Flexible scheduling with full-time or part-time opportunities to fit your life" and "Steady Hours". That's schedule info. Could be part of Benefits or separate Schedule section. The rules have Schedule as example heading. Since it's mentioned, I'll include a Schedule section.
But the "Steady Hours, Flexible Life" is under "Why Join our Team". It's a benefit. I'll include in Benefits.
Now, let's extract content.
Pay: "Compensation Range $16.50 - $21.75 / Hour"
About the role: The Overview paragraph: "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: Multiple bullet points. I'll parse each subsection.
"Why Join our Team" has:
- 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: "What You'll Do" list.
Requirements: "Your Background" list.
Company: "Who We Are" paragraph.
Also, there is EEO statement at the end: "We are an equal opportunity employer... reasonable accommodations..." This is boilerplate, should be removed.
Also, "To notify of a non-compliant job posting..." is boilerplate.
Now, I need to output HTML fragment.
Let's write.
First, Pay section:
Pay
Compensation range: $16.50 - $21.75 per hour.
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.
Benefits:
Benefits
Schedule & Flexibility
- 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
Health & Wellness
- 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
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 sections: 1. Pay: The posting has "Compensation Range $16.50 - $21.75 / 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 and perks. Should I combine into a Benefits section? The rules say "Benefits" as example heading. I'll create a Benefits section with sub-lists. 4. Responsibilities: "What You'll Do" is clearly responsibilities. 5. Requirements/Qualifications: "Your Background" lists requirements. Could be "Requirements" or "Qualifications". The rules mention both. I'll use "Requirements" as heading. 6. Schedule: The posting mentions "Flexible scheduling with full-time or part-time opportunities" and "Steady Hours". That's schedule info. Could include a Schedule section. 7. Company info: "Who We Are" is company description. Could be "About the company" but not in example headings. The rules don't list "About the company" as example, but "About the role" is. Might include as a section? The rules say "include a section ONLY when the posting has real, specific content for it". It has content. But the example headings don't include company. However, the user didn't forbid other headings. 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 they say "Prefer a few substantive sections over many thin ones." I think including company info is okay, but maybe fold into About the role? The Overview already includes some company info. The "Who We Are" is more detailed. I'll include a "About the company" section? But the rules didn't list it. However, the posting has substantive content. I'll include it as "About the company" or "Company overview". But to stay close to examples, maybe "About the role" can encompass company? The Overview is about the role and company. The "Who We Are" is separate. I'll create a "Company" section? Let's see: 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 input, but presumably "Line Cook". The page already shows it. So we don't need to repeat.
I'll structure as:
- Pay
- About the role
- Benefits
- Responsibilities
- Requirements
- Schedule (if specific)
- Company (maybe)
But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states pay, benefits, and schedule (flexible scheduling). So include all three.
Now, for Benefits: The posting has multiple categories. I'll create a Benefits section with subheadings? But the rules say use for section headings, and - for lists. Could use nested lists or just combine into one list. But the content is rich. I'll use
for Benefits, then maybe for subcategories? The rules only mention for section headings. They didn't forbid . But to keep simple, I'll use for main sections and within Benefits, use with maybe grouped items. However, the content has distinct categories: "Steady Hours, Flexible Life", "Benefits That Have Your Back", "Grow With Us", "Perks, Recognition & Community". I could make each a separate ? But that would be many thin sections. The rules say "Prefer a few substantive sections over many thin ones." So better to have one Benefits section with sub-lists. I'll use Benefits
then maybe for each category? But the rules didn't specify . I think it's okay to use for subsections. However, the instruction says "use for section headings". It doesn't say you cannot use other headings. But to be safe, I'll keep only for main sections. For subcategories, I'll use or just list items with bold labels. But the content is better structured with subheadings. I'll use for subcategories within Benefits. That's still semantic HTML.
Alternatively, I could make each category a separate section: "Schedule & Flexibility", "Health & Wellness Benefits", "Growth & Development", "Perks & Recognition". But that might be too many. The rules say "Prefer a few substantive sections over many thin ones." So I'll keep one Benefits section with sub-lists.
Let's decide: I'll create a Benefits section with an introductory paragraph, then use for each category, maybe with a label for each category. But the content is list items. I'll do:
Benefits
...
Schedule & Flexibility
...
Health & Wellness
...
Growth & Development
...
Perks & Recognition
...
But the rules didn't mention . However, it's still semantic HTML. I think it's acceptable.
Now, for Schedule: The posting mentions "Flexible scheduling with full-time or part-time opportunities to fit your life" and "Steady Hours". That's schedule info. Could be part of Benefits or separate Schedule section. The rules have Schedule as example heading. Since it's mentioned, I'll include a Schedule section.
But the "Steady Hours, Flexible Life" is under "Why Join our Team". It's a benefit. I'll include in Benefits.
Now, let's extract content.
Pay: "Compensation Range $16.50 - $21.75 / Hour"
About the role: The Overview paragraph: "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: Multiple bullet points. I'll parse each subsection.
"Why Join our Team" has:
- 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: "What You'll Do" list.
Requirements: "Your Background" list.
Company: "Who We Are" paragraph.
Also, there is EEO statement at the end: "We are an equal opportunity employer... reasonable accommodations..." This is boilerplate, should be removed.
Also, "To notify of a non-compliant job posting..." is boilerplate.
Now, I need to output HTML fragment.
Let's write.
First, Pay section:
Pay
Compensation range: $16.50 - $21.75 per hour.
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.
Benefits:
Benefits
Schedule & Flexibility
- 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
Health & Wellness
- 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
- for lists. Could use nested lists or just combine into one list. But the content is rich. I'll use
for Benefits, then maybe
for subcategories? The rules only mention
for section headings. They didn't forbid
. But to keep simple, I'll use
for main sections and within Benefits, use
- with maybe grouped items. However, the content has distinct categories: "Steady Hours, Flexible Life", "Benefits That Have Your Back", "Grow With Us", "Perks, Recognition & Community". I could make each a separate
- 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
- 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
- World-class training designed to support your personal and professional growth
? But that would be many thin sections. The rules say "Prefer a few substantive sections over many thin ones." So better to have one Benefits section with sub-lists. I'll use
Benefits
then maybefor each category? But the rules didn't specify
. I think it's okay to use
for subsections. However, the instruction says "use
for section headings". It doesn't say you cannot use other headings. But to be safe, I'll keep only
for main sections. For subcategories, I'll use or just list items with bold labels. But the content is better structured with subheadings. I'll use
for subcategories within Benefits. That's still semantic HTML. Alternatively, I could make each category a separate
section: "Schedule & Flexibility", "Health & Wellness Benefits", "Growth & Development", "Perks & Recognition". But that might be too many. The rules say "Prefer a few substantive sections over many thin ones." So I'll keep one Benefits section with sub-lists. Let's decide: I'll create a Benefits section with an introductory paragraph, then use
- for each category, maybe with a label for each category. But the content is list items. I'll do:
Benefits
...
Schedule & Flexibility
- ...
Health & Wellness
- ...
Growth & Development
- ...
Perks & Recognition
- ...
. However, it's still semantic HTML. I think it's acceptable. Now, for Schedule: The posting mentions "Flexible scheduling with full-time or part-time opportunities to fit your life" and "Steady Hours". That's schedule info. Could be part of Benefits or separate Schedule section. The rules have Schedule as example heading. Since it's mentioned, I'll include a Schedule section. But the "Steady Hours, Flexible Life" is under "Why Join our Team". It's a benefit. I'll include in Benefits. Now, let's extract content. Pay: "Compensation Range $16.50 - $21.75 / Hour" About the role: The Overview paragraph: "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: Multiple bullet points. I'll parse each subsection. "Why Join our Team" has: - 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: "What You'll Do" list. Requirements: "Your Background" list. Company: "Who We Are" paragraph. Also, there is EEO statement at the end: "We are an equal opportunity employer... reasonable accommodations..." This is boilerplate, should be removed. Also, "To notify of a non-compliant job posting..." is boilerplate. Now, I need to output HTML fragment. Let's write. First, Pay section:
Pay
Compensation range: $16.50 - $21.75 per hour.
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.
Benefits:Benefits
Schedule & Flexibility
Health & Wellness
Growth & Development