Dishwasher
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 real specific content exists
- 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:
1. Compensation Range: $16.90 - $18.50 / Hour -> This is Pay section. Should include as
Pay
with or
? Probably since it's a single range.
2. Overview: "For those who enjoy rolling up their sleeves..." -> This is About the role. Use
About the role
with .
3. Why Join our Team: This contains multiple subsections: Steady Hours, Flexible Life; Benefits That Have Your Back; Grow With Us; Perks, Recognition & Community; Join an award-winning company. This is Benefits section. Should we break into subsections? The rule says use
for section headings like Benefits. Could include all as a Benefits section with lists. But there are multiple categories. Might keep as one Benefits section with multiple lists or paragraphs. However, the rule says use - for any list of duties/requirements/benefits. So we can create a Benefits section with multiple
for each category.
But the rule: "Prefer a few substantive sections over many thin ones." So maybe combine into one Benefits section with multiple lists.
4. What You'll Do: list of duties -> Responsibilities section.
5. Your Background: list of requirements -> Requirements section (or Qualifications). Use Requirements
or Qualifications
. The rule mentions both. I'll use Requirements.
6. Who We Are: company description. Could be About the company, but the rule says headings like About the role. Might include as a separate section "About the company" but not in the listed headings. The rule says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So "About the company" is not listed. Could fold into About the role? Or maybe omit? The rule says preserve ALL substantive information. So include as a section maybe "About the company" but not in the example list. However, the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., so we can use other headings if needed. But to be safe, maybe include as "About the company" or "Who We Are". I'll include as About the company
.
But note: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is not given in the text, but the posting is for Dishwasher. The page already shows it, so we don't need to include.
Also, there is EEO statement at the end: "We are an equal opportunity employer...". That's boilerplate, should be removed.
Also, the line "To notify of a non-compliant job posting, please send a notice to ats@thecheesecakefactory.com" is application instruction/boilerplate, remove.
Now, let's structure:
- Pay section: compensation range.
- About the role: overview paragraph.
- Benefits: multiple lists.
- Responsibilities: list of duties.
- Requirements: list of requirements.
- About the company: company description.
Check for Schedule: The posting mentions "Flexible scheduling with full-time or part-time opportunities". That could be Schedule section. But the rule says never create Schedule section unless posting actually states them. It does state scheduling info. Could include as Schedule section. But the Benefits section already includes "Steady Hours, Flexible Life" with scheduling info. Might be redundant. I'll include scheduling info in Benefits or create a Schedule section. The rule says "Prefer a few substantive sections over many thin ones." So maybe keep scheduling in Benefits.
But the example headings include Schedule. If the posting has specific schedule info, we can include. The posting says: "High-volume restaurant with consistent hours", "Flexible scheduling with full-time or part-time opportunities to fit your life". That's schedule info. Could create a Schedule section. However, the Benefits section already includes that. I'll include a Schedule section with that info.
But the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. So we can create.
Let's decide sections:
1. Pay
2. About the role
3. Schedule
4. Benefits
5. Responsibilities
6. Requirements
7. About the company
But that's many sections. Some are thin. Schedule only has two bullet points. Could merge into Benefits. I'll merge scheduling into Benefits as part of "Steady Hours, Flexible Life". That's a benefit.
Similarly, "Grow With Us" and "Perks, Recognition & Community" are benefits.
Thus, Benefits section will have multiple sub-lists.
Now, write HTML.
We need to output only HTML fragment, no markdown fences.
Let's craft.
First, Pay:
Pay
Compensation range: $16.90 - $18.50 per hour.
About the role:
About the role
For those who enjoy rolling up their sleeves, this is a great way to join a professional kitchen team in a high volume, full service restaurant, with plenty of opportunities to grow. Our Dishwashers play a vital role in the back of house, taking ownership in ensuring kitchen cleanliness, sanitation, and organization. Working in a fast paced environment, Dishwashers support safe and efficient operations, helping deliver excellent guest experiences.
Benefits:
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
Awards & Recognition
- Fortune 100 Best Companies to Work For® (since 2014)
- PEOPLE® Companies That Care (since 2021)
- Great Place to Work® Certified
But note: the rule says use for section headings. Using for subsections might be okay, but the rule didn't forbid. However, the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we can't use . But to keep it simple, maybe just use for main sections and use with maybe bold labels? But the rule says use - for any list. Could embed the category as a
- with strong? But better to use
for subheadings within Benefits. However, the output is a fragment, and using is fine. But the rule didn't specify. I'll use for subsections within Benefits.
Alternatively, we could make each benefit category a separate ? That would create many sections. The rule says prefer few substantive sections. So keep Benefits as one section with subheadings.
Now Responsibilities:
Responsibilities
- Wash, rinse, and sanitize dishes, plates, glassware, cutlery, kitchen tools, pots, and pans using a commercial dishwasher and 3 compartment sink
- Pre sort, soak, and rinse silverware and utensils to ensure proper cleaning and sanitation
- Safely load and unload a dishwashing machine
- Work with speed, efficiency, and a sense of urgency
- Support opening and closing tasks, including station setup and breakdown
- Follow instructions accurately with consistency and attention to detail
- Adhere to safety, sanitation, and chemical handling procedures
- Complete utility tasks including trash removal and box breakdown
- Perform janitorial duties, including sweeping and mopping to maintain floors
- Communicate effectively as a supportive team player
- Work well under pressure with a positive, patient attitude
- Take pride in being reliable, punctual, and a hard worker
Requirements:
Requirements
- Previous restaurant, kitchen, hospitality, or food service industry experience preferred
- Familiarity with dishwashing operations and cleaning duties, a plus
- Knowledge of sanitation standards, safety practices, and proper equipment use
- Ability to multitask and stay organized in a fast paced environment
- Dependable, adaptable, and dedicated with a strong work ethic
- Passionate about teamwork and contributing to a positive workplace 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
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 real specific content exists - 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: 1. Compensation Range: $16.90 - $18.50 / Hour -> This is Pay section. Should include as
Pay
withor
- ? Probably
- for any list of duties/requirements/benefits. So we can create a Benefits section with multiple
- for each category.
But the rule: "Prefer a few substantive sections over many thin ones." So maybe combine into one Benefits section with multiple lists.
4. What You'll Do: list of duties -> Responsibilities section.
5. Your Background: list of requirements -> Requirements section (or Qualifications). Use
- 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
- Career advancement opportunities – over half of our managers are promoted from within
- No cost GED or Associate Degree programs
- 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
- Fortune 100 Best Companies to Work For® (since 2014)
- PEOPLE® Companies That Care (since 2021)
- Great Place to Work® Certified
- for any list. Could embed the category as a
- with strong? But better to use
for subheadings within Benefits. However, the output is a fragment, and using
is fine. But the rule didn't specify. I'll use
for subsections within Benefits. Alternatively, we could make each benefit category a separate
? That would create many sections. The rule says prefer few substantive sections. So keep Benefits as one section with subheadings. Now Responsibilities:
Responsibilities
- Wash, rinse, and sanitize dishes, plates, glassware, cutlery, kitchen tools, pots, and pans using a commercial dishwasher and 3 compartment sink
- Pre sort, soak, and rinse silverware and utensils to ensure proper cleaning and sanitation
- Safely load and unload a dishwashing machine
- Work with speed, efficiency, and a sense of urgency
- Support opening and closing tasks, including station setup and breakdown
- Follow instructions accurately with consistency and attention to detail
- Adhere to safety, sanitation, and chemical handling procedures
- Complete utility tasks including trash removal and box breakdown
- Perform janitorial duties, including sweeping and mopping to maintain floors
- Communicate effectively as a supportive team player
- Work well under pressure with a positive, patient attitude
- Take pride in being reliable, punctual, and a hard worker
Requirements
- Previous restaurant, kitchen, hospitality, or food service industry experience preferred
- Familiarity with dishwashing operations and cleaning duties, a plus
- Knowledge of sanitation standards, safety practices, and proper equipment use
- Ability to multitask and stay organized in a fast paced environment
- Dependable, adaptable, and dedicated with a strong work ethic
- Passionate about teamwork and contributing to a positive workplace culture
- Ability to lift up to 50 pounds, stand for extended periods, continuously bend, reach and twist
- Must be at least 18 years old
Requirements
orQualifications
. The rule mentions both. I'll use Requirements. 6. Who We Are: company description. Could be About the company, but the rule says headings like About the role. Might include as a separate section "About the company" but not in the listed headings. The rule says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So "About the company" is not listed. Could fold into About the role? Or maybe omit? The rule says preserve ALL substantive information. So include as a section maybe "About the company" but not in the example list. However, the rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., so we can use other headings if needed. But to be safe, maybe include as "About the company" or "Who We Are". I'll include as
About the company
. But note: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is not given in the text, but the posting is for Dishwasher. The page already shows it, so we don't need to include. Also, there is EEO statement at the end: "We are an equal opportunity employer...". That's boilerplate, should be removed. Also, the line "To notify of a non-compliant job posting, please send a notice to ats@thecheesecakefactory.com" is application instruction/boilerplate, remove. Now, let's structure: - Pay section: compensation range. - About the role: overview paragraph. - Benefits: multiple lists. - Responsibilities: list of duties. - Requirements: list of requirements. - About the company: company description. Check for Schedule: The posting mentions "Flexible scheduling with full-time or part-time opportunities". That could be Schedule section. But the rule says never create Schedule section unless posting actually states them. It does state scheduling info. Could include as Schedule section. But the Benefits section already includes "Steady Hours, Flexible Life" with scheduling info. Might be redundant. I'll include scheduling info in Benefits or create a Schedule section. The rule says "Prefer a few substantive sections over many thin ones." So maybe keep scheduling in Benefits. But the example headings include Schedule. If the posting has specific schedule info, we can include. The posting says: "High-volume restaurant with consistent hours", "Flexible scheduling with full-time or part-time opportunities to fit your life". That's schedule info. Could create a Schedule section. However, the Benefits section already includes that. I'll include a Schedule section with that info. But the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. So we can create. Let's decide sections: 1. Pay 2. About the role 3. Schedule 4. Benefits 5. Responsibilities 6. Requirements 7. About the company But that's many sections. Some are thin. Schedule only has two bullet points. Could merge into Benefits. I'll merge scheduling into Benefits as part of "Steady Hours, Flexible Life". That's a benefit. Similarly, "Grow With Us" and "Perks, Recognition & Community" are benefits. Thus, Benefits section will have multiple sub-lists. Now, write HTML. We need to output only HTML fragment, no markdown fences. Let's craft. First, Pay:Pay
Compensation range: $16.90 - $18.50 per hour.
About the role:About the role
For those who enjoy rolling up their sleeves, this is a great way to join a professional kitchen team in a high volume, full service restaurant, with plenty of opportunities to grow. Our Dishwashers play a vital role in the back of house, taking ownership in ensuring kitchen cleanliness, sanitation, and organization. Working in a fast paced environment, Dishwashers support safe and efficient operations, helping deliver excellent guest experiences.
Benefits:Benefits
Steady Hours, Flexible Life
Benefits That Have Your Back
Grow With Us
Perks, Recognition & Community
Awards & Recognition
for section headings. Using
for subsections might be okay, but the rule didn't forbid. However, the rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we can't use
. But to keep it simple, maybe just use
for main sections and use
- with maybe bold labels? But the rule says use
since it's a single range. 2. Overview: "For those who enjoy rolling up their sleeves..." -> This is About the role. Use
About the role
with. 3. Why Join our Team: This contains multiple subsections: Steady Hours, Flexible Life; Benefits That Have Your Back; Grow With Us; Perks, Recognition & Community; Join an award-winning company. This is Benefits section. Should we break into subsections? The rule says use