Dessert Finisher/Barista
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 (page already shows it).
- Do NOT put Job ID/requisition numbers as headings.
- Preserve ALL substantive information; do NOT invent or summarize away detail.
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
- Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them.
- Prefer a few substantive sections over many thin ones.
- Output ONLY the HTML fragment — no /, no markdown code fences.
Now, let's map the content:
1. Compensation Range: $13.00 - $16.75 / Hour -> This is Pay information. Should create a Pay section with that detail.
2. Overview: "As a Dessert Finisher/Barista..." -> This is About the role. Use
About the role
and for the prose.
3. Why Join our Team: This is essentially Benefits and Perks. It has multiple subsections. The rules say use Benefits heading for benefits. Also there is scheduling info (Steady Hours, Flexible Life) which could be Schedule section. But the rules say only create Schedule section if posting actually states them. It does state scheduling details: "High-volume restaurant with consistent hours", "Flexible scheduling with full-time or part-time opportunities to fit your life". That's schedule info. Also "Faster Pay – access up to 50% of your earned wages the next day" is pay-related. Benefits: "50% off 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". Grow With Us: training, career advancement, GED/Associate Degree programs. Perks, Recognition & Community: perks and discounts, employee recognition, HELP Fund, community events, awards. This is all benefits/perks. Could combine into a Benefits section, but the rules say use Benefits heading. However, the posting has distinct categories. I think we can create a Benefits section that includes all these. But the rules say "Prefer a few substantive sections over many thin ones." So maybe one Benefits section with sub-lists? But we must use
- for lists. Could have multiple
under Benefits. Or we could separate into Benefits and Schedule? The posting has "Steady Hours, Flexible Life" which is schedule. The rules mention Schedule as a possible heading. Since the posting has specific schedule info, we can include a Schedule section. But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule info. So we can create a Schedule section. However, the "Why Join our Team" is a broader section. I think we should break it down into relevant sections: Pay (already have compensation range), Schedule, Benefits, maybe Growth/Development? But the rules only list specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Grow With Us" could be Qualifications? Not exactly. It's about training and advancement. Could be part of Benefits? Or maybe we can include as a separate section but the rules don't have a heading for that. 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, but we should stick to those. However, we can use other headings if needed? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should prefer those. The posting has "Who We Are" which is company description. Could be "About the company" but not in the list. Might omit or include as a section? The rules say "include a section ONLY when the posting has real, specific content for it". The Who We Are is substantive. But the page already shows the company? The user said "the page already shows it" for job title, but not for company. However, the posting includes company info. I think we can include a section "About the company" or "Who We Are". But the rules don't list that. Might be okay to include as a heading. But to be safe, maybe we can include it as a section with heading "About the company". However, the instruction says "use for section headings (e.g. ...)". It doesn't say we cannot use others. But the example list is limited. I think we should stick to the listed headings where possible. For "Who We Are", it's not in the list. Could be considered "About the role"? No. Might be omitted? But the rule says preserve ALL substantive information. So we should include it. Perhaps we can put it under a heading "About the company". I'll include it as a section with About the company
.
Now, "What You'll Do" -> Responsibilities. Use Responsibilities
and - for each bullet.
"Your Background" -> Requirements (or Qualifications). The rules have both Requirements and Qualifications. Could use Requirements. The content includes experience, skills, physical requirements, age. That's requirements. Use
Requirements
and - .
"Who We Are" -> About the company. Use
About the company
and for prose.
Now, the "Why Join our Team" section: We need to extract the specific benefits, schedule, pay details. The compensation range is already at top. The "Faster Pay" is also pay-related. Could include in Pay section. The schedule details: "High-volume restaurant with consistent hours", "Flexible scheduling with full-time or part-time opportunities to fit your life". That's schedule. Benefits: the rest. Also "Grow With Us" includes training, advancement, education programs. That could be considered benefits or professional development. The rules have "Benefits" heading. Could include all under Benefits. But the schedule is separate. I'll create a Schedule section for the scheduling info. For Pay, we have the compensation range and the "Faster Pay" detail. So Pay section will include both.
Let's structure:
- Pay section: compensation range and faster pay.
- Schedule section: consistent hours, flexible scheduling full-time/part-time.
- Benefits section: all the other perks: meals discount, paid vacation/sick, medical/dental/vision, virtual care, training, advancement, GED/degree, perks/discounts, recognition, HELP Fund, community events, awards.
- About the role: overview paragraph.
- Responsibilities: list from "What You'll Do".
- Requirements: list from "Your Background".
- About the company: "Who We Are" paragraph.
We must not include boilerplate: "We are an E-Verify and equal opportunity employer...", "The Cheesecake Factory offers reasonable accommodations...", "#SoCheesecake", "To notify of a non-compliant job posting...". Those are legal/EEO/scam-warning boilerplate. Remove.
Also remove "Why Join our Team" heading as it's not a standard heading; we break its content into Pay, Schedule, Benefits.
Now, ensure we don't create sections with filler. All sections have real content.
Now, write HTML.
Let's draft:
Pay
- Hourly compensation range: $13.00 - $16.75
- Faster Pay – access up to 50% of earned wages the next day (exclusions apply)
Schedule
- High-volume restaurant with consistent hours
- Flexible scheduling with full-time or part-time opportunities
Benefits
- 50% off 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 for personal and professional growth
- Career advancement opportunities – over half of managers 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)
- Opportunities to give back through community and charity events
- Award-winning company: Fortune 100 Best Companies to Work For® (since 2014), PEOPLE® Companies That Care (since 2021), Great Place to Work® Certified
About the role
As a Dessert Finisher/Barista, you’re the friendly face behind our beautiful bakery case, putting the finishing touches on our famous cheesecakes and desserts. You’ll glaze our iconic strawberries, create perfect whipped cream dollops that “wow”, and craft delicious espresso beverages. As part of our high-volume, full-service restaurant team, you’ll support front-of-house operations, taking pride and ownership in delivering consistent quality that elevates the guest experience.
Responsibilities
- Plate and finish desserts with accuracy, attention to detail, and consistent presentation
- Operate an espresso machine to prepare specialty coffee and espresso beverages
- Accurately follow instructions while upholding food safety and food handling standards, with awareness of food allergies
- Label, date, and rotate products following FIFO (First In, First Out) practices
- Work with efficiency, speed, and a sense of urgency in a fast-paced environment
- Maintain organization, cleanliness, and sanitation of work areas
- Complete station setup and breakdown, including stocking and closing tasks
- Support teamwork through clear and effective communication
- Multitask and work well under pressure with a positive attitude
- Deliver
for prose. - Do NOT repeat job title as heading (page already shows it). - Do NOT put Job ID/requisition numbers as headings. - Preserve ALL substantive information; do NOT invent or summarize away detail. - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. - Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. - Prefer a few substantive sections over many thin ones. - Output ONLY the HTML fragment — no /, no markdown code fences. Now, let's map the content: 1. Compensation Range: $13.00 - $16.75 / Hour -> This is Pay information. Should create a Pay section with that detail. 2. Overview: "As a Dessert Finisher/Barista..." -> This is About the role. Use
About the role
andfor the prose. 3. Why Join our Team: This is essentially Benefits and Perks. It has multiple subsections. The rules say use Benefits heading for benefits. Also there is scheduling info (Steady Hours, Flexible Life) which could be Schedule section. But the rules say only create Schedule section if posting actually states them. It does state scheduling details: "High-volume restaurant with consistent hours", "Flexible scheduling with full-time or part-time opportunities to fit your life". That's schedule info. Also "Faster Pay – access up to 50% of your earned wages the next day" is pay-related. Benefits: "50% off 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". Grow With Us: training, career advancement, GED/Associate Degree programs. Perks, Recognition & Community: perks and discounts, employee recognition, HELP Fund, community events, awards. This is all benefits/perks. Could combine into a Benefits section, but the rules say use Benefits heading. However, the posting has distinct categories. I think we can create a Benefits section that includes all these. But the rules say "Prefer a few substantive sections over many thin ones." So maybe one Benefits section with sub-lists? But we must use
- for lists. Could have multiple
- under Benefits. Or we could separate into Benefits and Schedule? The posting has "Steady Hours, Flexible Life" which is schedule. The rules mention Schedule as a possible heading. Since the posting has specific schedule info, we can include a Schedule section. But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule info. So we can create a Schedule section. However, the "Why Join our Team" is a broader section. I think we should break it down into relevant sections: Pay (already have compensation range), Schedule, Benefits, maybe Growth/Development? But the rules only list specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Grow With Us" could be Qualifications? Not exactly. It's about training and advancement. Could be part of Benefits? Or maybe we can include as a separate section but the rules don't have a heading for that. The rules say "use
- for each bullet.
"Your Background" -> Requirements (or Qualifications). The rules have both Requirements and Qualifications. Could use Requirements. The content includes experience, skills, physical requirements, age. That's requirements. Use
Requirements
and- .
"Who We Are" -> About the company. Use
About the company
andfor prose. Now, the "Why Join our Team" section: We need to extract the specific benefits, schedule, pay details. The compensation range is already at top. The "Faster Pay" is also pay-related. Could include in Pay section. The schedule details: "High-volume restaurant with consistent hours", "Flexible scheduling with full-time or part-time opportunities to fit your life". That's schedule. Benefits: the rest. Also "Grow With Us" includes training, advancement, education programs. That could be considered benefits or professional development. The rules have "Benefits" heading. Could include all under Benefits. But the schedule is separate. I'll create a Schedule section for the scheduling info. For Pay, we have the compensation range and the "Faster Pay" detail. So Pay section will include both. Let's structure: - Pay section: compensation range and faster pay. - Schedule section: consistent hours, flexible scheduling full-time/part-time. - Benefits section: all the other perks: meals discount, paid vacation/sick, medical/dental/vision, virtual care, training, advancement, GED/degree, perks/discounts, recognition, HELP Fund, community events, awards. - About the role: overview paragraph. - Responsibilities: list from "What You'll Do". - Requirements: list from "Your Background". - About the company: "Who We Are" paragraph. We must not include boilerplate: "We are an E-Verify and equal opportunity employer...", "The Cheesecake Factory offers reasonable accommodations...", "#SoCheesecake", "To notify of a non-compliant job posting...". Those are legal/EEO/scam-warning boilerplate. Remove. Also remove "Why Join our Team" heading as it's not a standard heading; we break its content into Pay, Schedule, Benefits. Now, ensure we don't create sections with filler. All sections have real content. Now, write HTML. Let's draft:
Pay
- Hourly compensation range: $13.00 - $16.75
- Faster Pay – access up to 50% of earned wages the next day (exclusions apply)
Schedule
- High-volume restaurant with consistent hours
- Flexible scheduling with full-time or part-time opportunities
Benefits
- 50% off 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 for personal and professional growth
- Career advancement opportunities – over half of managers 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)
- Opportunities to give back through community and charity events
- Award-winning company: Fortune 100 Best Companies to Work For® (since 2014), PEOPLE® Companies That Care (since 2021), Great Place to Work® Certified
About the role
As a Dessert Finisher/Barista, you’re the friendly face behind our beautiful bakery case, putting the finishing touches on our famous cheesecakes and desserts. You’ll glaze our iconic strawberries, create perfect whipped cream dollops that “wow”, and craft delicious espresso beverages. As part of our high-volume, full-service restaurant team, you’ll support front-of-house operations, taking pride and ownership in delivering consistent quality that elevates the guest experience.
Responsibilities
- Plate and finish desserts with accuracy, attention to detail, and consistent presentation
- Operate an espresso machine to prepare specialty coffee and espresso beverages
- Accurately follow instructions while upholding food safety and food handling standards, with awareness of food allergies
- Label, date, and rotate products following FIFO (First In, First Out) practices
- Work with efficiency, speed, and a sense of urgency in a fast-paced environment
- Maintain organization, cleanliness, and sanitation of work areas
- Complete station setup and breakdown, including stocking and closing tasks
- Support teamwork through clear and effective communication
- Multitask and work well under pressure with a positive attitude
- Deliver
- .
"Who We Are" -> About the company. Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, but we should stick to those. However, we can use other headings if needed? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should prefer those. The posting has "Who We Are" which is company description. Could be "About the company" but not in the list. Might omit or include as a section? The rules say "include a section ONLY when the posting has real, specific content for it". The Who We Are is substantive. But the page already shows the company? The user said "the page already shows it" for job title, but not for company. However, the posting includes company info. I think we can include a section "About the company" or "Who We Are". But the rules don't list that. Might be okay to include as a heading. But to be safe, maybe we can include it as a section with heading "About the company". However, the instruction says "use
for section headings (e.g. ...)". It doesn't say we cannot use others. But the example list is limited. I think we should stick to the listed headings where possible. For "Who We Are", it's not in the list. Could be considered "About the role"? No. Might be omitted? But the rule says preserve ALL substantive information. So we should include it. Perhaps we can put it under a heading "About the company". I'll include it as a section with
About the company
. Now, "What You'll Do" -> Responsibilities. UseResponsibilities
and - for each bullet.
"Your Background" -> Requirements (or Qualifications). The rules have both Requirements and Qualifications. Could use Requirements. The content includes experience, skills, physical requirements, age. That's requirements. Use