Prep 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 appropriate sections:
1. Pay: The posting has "Compensation Range $16.25 - $21.50 / Hour" - this is specific pay info, so include a Pay section.
2. Overview: This is "About the role" - I'll use
About the role
with a for the overview text.
3. Why Join our Team: This contains benefits, perks, scheduling info. This maps to Benefits section. It has multiple subsections: "Steady Hours, Flexible Life", "Benefits That Have Your Back", "Grow With Us", "Perks, Recognition & Community". I should include all substantive content. Since it's all benefits/perks, I'll put under a Benefits heading with sub-lists or multiple lists.
4. What You'll Do: Responsibilities - use
Responsibilities
with - for each bullet.
5. Your Background: Requirements/Qualifications - use
Requirements
with - for each bullet.
6. Who We Are: Company description - could be "About the company" but the rules don't specify that heading. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Who We Are" is company info, not directly listed. Could fold into a short
at the end or omit? The rules say preserve ALL substantive information. But also "Prefer a few substantive sections over many thin ones." The company description is substantive but not a standard heading. I could include it as a
after the sections, or maybe under "About the role"? But "About the role" is for the role overview. The company description is separate. I think I'll include it as a
at the end without a heading, or maybe under a generic heading? The rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." so maybe other headings allowed? But better to stick to those. I'll include the company description as a
after the sections, maybe with a heading "About the company"? But not in the list. The rules: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says "e.g." meaning examples. However, to be safe, I'll include it as a
without a heading, or maybe under "About the role"? The overview already covers the role. The "Who We Are" is about the company. I'll add a
About the company
? But the rules didn't list that. I think it's okay to include a heading for company info if it's substantive. But the instruction: "include a section ONLY when the posting has real, specific content for it". The posting has "Who We Are" with specific content. I'll include it as a section with heading "About the company". However, the allowed headings list doesn't include it. But the rule says "e.g." so it's not exhaustive. I'll include it.
But also note: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". The posting ends with EEO statement and contact for non-compliant job posting. That's boilerplate, should remove.
Also "The Cheesecake Factory offers reasonable accommodations..." is EEO boilerplate, remove.
Now, let's structure:
- Pay section: Pay
with Compensation Range: $16.25 - $21.50 / Hour
- About the role: About the role
with Overview text...
- Benefits: Benefits
with multiple lists for each subsection? The "Why Join our Team" has four subsections. I'll create a list for each, maybe with subheadings? But rules: use - for any list of duties/requirements/benefits. Could use nested lists or separate lists with bold labels? Better to keep flat: each benefit as a list item, but there are categories. I'll include each category as a list item with bold category and then sub-items? But
- only. Could do:
- 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
...
But that's messy. Better to have separate lists for each category, but still under Benefits heading. I'll use multiple each preceded by a Category
? But rules say use - for any list. Could do:
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
... etc.
That seems appropriate.
- Responsibilities: Responsibilities
with - for each bullet.
- Requirements:
Requirements
with - for each bullet.
- About the company:
About the company
with for the description.
Now, check for any Schedule section: The posting mentions "Steady Hours, Flexible Life" and "Flexible scheduling with full-time or part-time opportunities". That's schedule info, but it's under Benefits. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state schedule info, but it's part of benefits. Could create a Schedule section? But the schedule info is not a separate section; it's under "Why Join our Team". I'll keep it under Benefits.
Also, the posting has "Compensation Range" which is Pay. Good.
Now, remove boilerplate: The last paragraph about equal opportunity employer, reasonable accommodations, and the email for non-compliant job posting. Remove.
Also, the job title "Prep Cook" is not to be repeated as heading. The page already shows it. So no heading for job title.
Now, write HTML.
Let's draft:
Pay
Compensation Range: $16.25 - $21.50 / Hour
About the role
With a commitment to scratch cooking using fresh, high-quality ingredients, our Prep Cooks prepare hundreds of recipes for our delicious dishes. You’ll work alongside a supportive kitchen team in a fast paced, full-service restaurant, taking ownership and pride in food preparation, attention to detail, and consistency. Our Prep Cooks are passionate team players who support back-of-house operations and help create memorable dining experiences for our guests.
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
- Follow a prep list while completing tasks efficiently with speed and a sense of urgency
- Read and follow recipes using accurate measurements, weights, and portioning for consistent recipe execution
- Prepare ingredients using strong knife skills including chopping, dicing, and slicing
- Use a variety of cooking methods and culinary techniques including boiling, broiling, roasting, sauteing, frying, and grilling
- Prep ingredients for 200+ menu items including sauces, dressings, and soups
- Operate kitchen equipment such as ovens, fryers, broilers, flat tops, grills, tilt
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 has "Compensation Range $16.25 - $21.50 / Hour" - this is specific pay info, so include a Pay section. 2. Overview: This is "About the role" - I'll use
About the role
with afor the overview text. 3. Why Join our Team: This contains benefits, perks, scheduling info. This maps to Benefits section. It has multiple subsections: "Steady Hours, Flexible Life", "Benefits That Have Your Back", "Grow With Us", "Perks, Recognition & Community". I should include all substantive content. Since it's all benefits/perks, I'll put under a Benefits heading with sub-lists or multiple lists. 4. What You'll Do: Responsibilities - use
Responsibilities
with- for each bullet.
5. Your Background: Requirements/Qualifications - use
Requirements
with- for each bullet.
6. Who We Are: Company description - could be "About the company" but the rules don't specify that heading. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Who We Are" is company info, not directly listed. Could fold into a short
at the end or omit? The rules say preserve ALL substantive information. But also "Prefer a few substantive sections over many thin ones." The company description is substantive but not a standard heading. I could include it as a
after the sections, or maybe under "About the role"? But "About the role" is for the role overview. The company description is separate. I think I'll include it as a
at the end without a heading, or maybe under a generic heading? The rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." so maybe other headings allowed? But better to stick to those. I'll include the company description as a
after the sections, maybe with a heading "About the company"? But not in the list. The rules: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says "e.g." meaning examples. However, to be safe, I'll include it as a
without a heading, or maybe under "About the role"? The overview already covers the role. The "Who We Are" is about the company. I'll add a
About the company
? But the rules didn't list that. I think it's okay to include a heading for company info if it's substantive. But the instruction: "include a section ONLY when the posting has real, specific content for it". The posting has "Who We Are" with specific content. I'll include it as a section with heading "About the company". However, the allowed headings list doesn't include it. But the rule says "e.g." so it's not exhaustive. I'll include it. But also note: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". The posting ends with EEO statement and contact for non-compliant job posting. That's boilerplate, should remove. Also "The Cheesecake Factory offers reasonable accommodations..." is EEO boilerplate, remove. Now, let's structure: - Pay section:Pay
withCompensation Range: $16.25 - $21.50 / Hour
- About the role:About the role
withOverview text...
- Benefits:Benefits
with multiple lists for each subsection? The "Why Join our Team" has four subsections. I'll create a list for each, maybe with subheadings? But rules: use- for any list of duties/requirements/benefits. Could use nested lists or separate lists with bold labels? Better to keep flat: each benefit as a list item, but there are categories. I'll include each category as a list item with bold category and then sub-items? But
- only. Could do:
- 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 ...
- each preceded by a
- for any list. Could do:
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
Responsibilities
with- for each bullet.
- Requirements:
Requirements
with- for each bullet.
- About the company:
About the company
withfor the description. Now, check for any Schedule section: The posting mentions "Steady Hours, Flexible Life" and "Flexible scheduling with full-time or part-time opportunities". That's schedule info, but it's under Benefits. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state schedule info, but it's part of benefits. Could create a Schedule section? But the schedule info is not a separate section; it's under "Why Join our Team". I'll keep it under Benefits. Also, the posting has "Compensation Range" which is Pay. Good. Now, remove boilerplate: The last paragraph about equal opportunity employer, reasonable accommodations, and the email for non-compliant job posting. Remove. Also, the job title "Prep Cook" is not to be repeated as heading. The page already shows it. So no heading for job title. Now, write HTML. Let's draft:
Pay
Compensation Range: $16.25 - $21.50 / Hour
About the role
With a commitment to scratch cooking using fresh, high-quality ingredients, our Prep Cooks prepare hundreds of recipes for our delicious dishes. You’ll work alongside a supportive kitchen team in a fast paced, full-service restaurant, taking ownership and pride in food preparation, attention to detail, and consistency. Our Prep Cooks are passionate team players who support back-of-house operations and help create memorable dining experiences for our guests.
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
- Follow a prep list while completing tasks efficiently with speed and a sense of urgency
- Read and follow recipes using accurate measurements, weights, and portioning for consistent recipe execution
- Prepare ingredients using strong knife skills including chopping, dicing, and slicing
- Use a variety of cooking methods and culinary techniques including boiling, broiling, roasting, sauteing, frying, and grilling
- Prep ingredients for 200+ menu items including sauces, dressings, and soups
- Operate kitchen equipment such as ovens, fryers, broilers, flat tops, grills, tilt
- for each bullet.
- About the company:
Category
? But rules say use
- only. Could do:
- for any list of duties/requirements/benefits. Could use nested lists or separate lists with bold labels? Better to keep flat: each benefit as a list item, but there are categories. I'll include each category as a list item with bold category and then sub-items? But
- for each bullet.
6. Who We Are: Company description - could be "About the company" but the rules don't specify that heading. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Who We Are" is company info, not directly listed. Could fold into a short