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). The job title is "Dessert Finisher/Barista" but not in the text? Actually the posting starts with "Compensation Range...". The title might be implied. We'll not include a heading for title.
- Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. There's no Job ID here.
- 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. The posting includes EEO statement at the end ("We are an E-Verify and equal opportunity employer...") and contact for non-compliant posting. That's boilerplate, should be removed.
- 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.
Now, map content to sections:
1. Pay: Compensation Range $14.50 - $17.25 / Hour. That's specific, so include Pay section.
2. About the role: The "Overview" paragraph describes the role. Could be "About the role" heading.
3. Benefits: The "Why Join our Team" includes multiple subsections: "Steady Hours, Flexible Life", "Benefits That Have Your Back", "Grow With Us", "Perks, Recognition & Community". These are all benefits/perks. Could combine into a Benefits section with sub-lists? But the rule says use
for section headings like Benefits. Could have one Benefits section with multiple sub-lists? However, the instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have a Benefits heading and then list items. But the content has distinct categories. Could we use subheadings? The rule only mentions for section headings. It doesn't forbid using but the example only shows . Probably we should keep it flat: one Benefits section with multiple bullet groups? But the rule says "Use - for any list of duties/requirements/benefits". So we can have a Benefits section with multiple
lists, each preceded by a bold label? But that might not be semantic. Alternatively, we could create separate sections for each category? But the example headings are limited. The user said "Prefer a few substantive sections over many thin ones." So maybe combine all benefits into one Benefits section with multiple lists.
But the posting has "Why Join our Team" with four subsections. Each has bullet points. We'll create a Benefits section and include all those bullet points as separate lists, maybe with a leading for the category name? Or we can use for category then . That's acceptable.
4. Responsibilities: "What You'll Do" is a list of duties. That's Responsibilities.
5. Requirements/Qualifications: "Your Background" lists requirements. Could be "Requirements" or "Qualifications". Use "Requirements".
6. Company info: "Who We Are" describes the company. Could be "About the Company" but not in the example headings. The example headings include "About the role". Might not need a separate section; but it's substantive. However, the rule says include a section ONLY when the posting has real, specific content for it. It does have content. But the example headings don't include "About the Company". Could we use "About the role"? That's different. Might be okay to include as a section with heading "About the Company"? But the instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning those are examples, not exhaustive. But we should stick to those typical headings. "Who We Are" is company description, maybe not needed. However, it's substantive and could be included as "About the Company". But the user might expect only those headings. I'll include it as a section with heading "About the Company" but that's not in the list. Safer to include as "About the role"? No, that's about the role. I think we can include a section "Company Overview" or similar. But the rule: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings. But to be safe, I'll include it as a section with heading "About the Company". However, the user might want only those headings. Let's see: The posting has "Who We Are" which is company info. It's not boilerplate; it's specific. I'll include it as a section with heading "About the Company". But the instruction says "Do NOT repeat the job title as a heading (the page already shows it)". That's fine.
Now, schedule: The posting mentions "Steady Hours, Flexible Life" and "Flexible scheduling with full-time or part-time opportunities". That's schedule info. Could create a Schedule section. But the rule says never create Schedule section unless the posting actually states them. It does state scheduling info. So we can include a Schedule section.
But the "Why Join our Team" includes "Steady Hours, Flexible Life" which is about schedule. Could be part of Benefits or separate Schedule. Since there is a Schedule heading example, we can create a Schedule section.
Let's structure:
- Pay
- About the role
- Responsibilities
- Requirements
- Benefits
- Schedule
- About the Company (optional)
But we need to avoid thin sections. Schedule has only a couple lines. Might be okay.
Let's parse each part.
**Pay**: "Compensation Range $14.50 - $17.25 / Hour" -> Pay
Compensation Range: $14.50 - $17.25 per hour
**About the role**: The "Overview" paragraph. -> 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**: "What You'll Do" list. Each bullet is a duty. -> 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 exceptional service to ensure guest satisfaction
**Requirements**: "Your Background" list. -> Requirements
- Previous restaurant, hospitality, barista, or food service industry experience preferred
- Familiarity with beverage preparation and food handling, a plus
- Knowledge of food safety and sanitation practices
- Adaptable, patient, and able to thrive in a high volume environment
- Dependable, reliable, punctual, and dedicated with consistent work habits
- Team player with a passion for hospitality 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
**Benefits**: The "Why Join our Team" section has four subsections. We'll include all as bullet lists under Benefits. Could separate with bold labels. For semantic HTML, we can use ? But rule says use for section headings. It doesn't forbid for subsections. But to keep simple, we can use
Steady Hours, Flexible Life
... etc. That's acceptable.
Let's list each:
- 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)
- 50% off 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
We'll include all.
**Schedule**: The "Steady Hours, Flexible Life" includes scheduling info. But we already put that under Benefits. Could create a separate Schedule section with the scheduling bullet points. However, the rule says prefer a few substantive sections over many thin ones. Since scheduling is part of benefits, maybe keep under Benefits. But there is a Schedule heading example. The posting does mention scheduling explicitly. I'll create a Schedule section with the relevant bullets: "High-volume restaurant with consistent
for prose. - Do NOT repeat job title as heading (page already shows it). The job title is "Dessert Finisher/Barista" but not in the text? Actually the posting starts with "Compensation Range...". The title might be implied. We'll not include a heading for title. - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. There's no Job ID here. - 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. The posting includes EEO statement at the end ("We are an E-Verify and equal opportunity employer...") and contact for non-compliant posting. That's boilerplate, should be removed. - 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. Now, map content to sections: 1. Pay: Compensation Range $14.50 - $17.25 / Hour. That's specific, so include Pay section. 2. About the role: The "Overview" paragraph describes the role. Could be "About the role" heading. 3. Benefits: The "Why Join our Team" includes multiple subsections: "Steady Hours, Flexible Life", "Benefits That Have Your Back", "Grow With Us", "Perks, Recognition & Community". These are all benefits/perks. Could combine into a Benefits section with sub-lists? But the rule says use
for section headings like Benefits. Could have one Benefits section with multiple sub-lists? However, the instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have a Benefits heading and then list items. But the content has distinct categories. Could we use subheadings? The rule only mentions for section headings. It doesn't forbid using but the example only shows . Probably we should keep it flat: one Benefits section with multiple bullet groups? But the rule says "Use - for any list of duties/requirements/benefits". So we can have a Benefits section with multiple
lists, each preceded by a bold label? But that might not be semantic. Alternatively, we could create separate sections for each category? But the example headings are limited. The user said "Prefer a few substantive sections over many thin ones." So maybe combine all benefits into one Benefits section with multiple lists.
But the posting has "Why Join our Team" with four subsections. Each has bullet points. We'll create a Benefits section and include all those bullet points as separate lists, maybe with a leading for the category name? Or we can use for category then . That's acceptable.
4. Responsibilities: "What You'll Do" is a list of duties. That's Responsibilities.
5. Requirements/Qualifications: "Your Background" lists requirements. Could be "Requirements" or "Qualifications". Use "Requirements".
6. Company info: "Who We Are" describes the company. Could be "About the Company" but not in the example headings. The example headings include "About the role". Might not need a separate section; but it's substantive. However, the rule says include a section ONLY when the posting has real, specific content for it. It does have content. But the example headings don't include "About the Company". Could we use "About the role"? That's different. Might be okay to include as a section with heading "About the Company"? But the instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning those are examples, not exhaustive. But we should stick to those typical headings. "Who We Are" is company description, maybe not needed. However, it's substantive and could be included as "About the Company". But the user might expect only those headings. I'll include it as a section with heading "About the Company" but that's not in the list. Safer to include as "About the role"? No, that's about the role. I think we can include a section "Company Overview" or similar. But the rule: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings. But to be safe, I'll include it as a section with heading "About the Company". However, the user might want only those headings. Let's see: The posting has "Who We Are" which is company info. It's not boilerplate; it's specific. I'll include it as a section with heading "About the Company". But the instruction says "Do NOT repeat the job title as a heading (the page already shows it)". That's fine.
Now, schedule: The posting mentions "Steady Hours, Flexible Life" and "Flexible scheduling with full-time or part-time opportunities". That's schedule info. Could create a Schedule section. But the rule says never create Schedule section unless the posting actually states them. It does state scheduling info. So we can include a Schedule section.
But the "Why Join our Team" includes "Steady Hours, Flexible Life" which is about schedule. Could be part of Benefits or separate Schedule. Since there is a Schedule heading example, we can create a Schedule section.
Let's structure:
- Pay
- About the role
- Responsibilities
- Requirements
- Benefits
- Schedule
- About the Company (optional)
But we need to avoid thin sections. Schedule has only a couple lines. Might be okay.
Let's parse each part.
**Pay**: "Compensation Range $14.50 - $17.25 / Hour" -> Pay
Compensation Range: $14.50 - $17.25 per hour
**About the role**: The "Overview" paragraph. -> 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**: "What You'll Do" list. Each bullet is a duty. -> 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 exceptional service to ensure guest satisfaction
**Requirements**: "Your Background" list. -> Requirements
- Previous restaurant, hospitality, barista, or food service industry experience preferred
- Familiarity with beverage preparation and food handling, a plus
- Knowledge of food safety and sanitation practices
- Adaptable, patient, and able to thrive in a high volume environment
- Dependable, reliable, punctual, and dedicated with consistent work habits
- Team player with a passion for hospitality 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
**Benefits**: The "Why Join our Team" section has four subsections. We'll include all as bullet lists under Benefits. Could separate with bold labels. For semantic HTML, we can use ? But rule says use for section headings. It doesn't forbid for subsections. But to keep simple, we can use
Steady Hours, Flexible Life
... etc. That's acceptable.
Let's list each:
- 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)
- 50% off 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
We'll include all.
**Schedule**: The "Steady Hours, Flexible Life" includes scheduling info. But we already put that under Benefits. Could create a separate Schedule section with the scheduling bullet points. However, the rule says prefer a few substantive sections over many thin ones. Since scheduling is part of benefits, maybe keep under Benefits. But there is a Schedule heading example. The posting does mention scheduling explicitly. I'll create a Schedule section with the relevant bullets: "High-volume restaurant with consistent
for section headings. It doesn't forbid using but the example only shows . Probably we should keep it flat: one Benefits section with multiple bullet groups? But the rule says "Use - for any list of duties/requirements/benefits". So we can have a Benefits section with multiple
lists, each preceded by a bold label? But that might not be semantic. Alternatively, we could create separate sections for each category? But the example headings are limited. The user said "Prefer a few substantive sections over many thin ones." So maybe combine all benefits into one Benefits section with multiple lists.
But the posting has "Why Join our Team" with four subsections. Each has bullet points. We'll create a Benefits section and include all those bullet points as separate lists, maybe with a leading for the category name? Or we can use for category then . That's acceptable.
4. Responsibilities: "What You'll Do" is a list of duties. That's Responsibilities.
5. Requirements/Qualifications: "Your Background" lists requirements. Could be "Requirements" or "Qualifications". Use "Requirements".
6. Company info: "Who We Are" describes the company. Could be "About the Company" but not in the example headings. The example headings include "About the role". Might not need a separate section; but it's substantive. However, the rule says include a section ONLY when the posting has real, specific content for it. It does have content. But the example headings don't include "About the Company". Could we use "About the role"? That's different. Might be okay to include as a section with heading "About the Company"? But the instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning those are examples, not exhaustive. But we should stick to those typical headings. "Who We Are" is company description, maybe not needed. However, it's substantive and could be included as "About the Company". But the user might expect only those headings. I'll include it as a section with heading "About the Company" but that's not in the list. Safer to include as "About the role"? No, that's about the role. I think we can include a section "Company Overview" or similar. But the rule: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings. But to be safe, I'll include it as a section with heading "About the Company". However, the user might want only those headings. Let's see: The posting has "Who We Are" which is company info. It's not boilerplate; it's specific. I'll include it as a section with heading "About the Company". But the instruction says "Do NOT repeat the job title as a heading (the page already shows it)". That's fine.
Now, schedule: The posting mentions "Steady Hours, Flexible Life" and "Flexible scheduling with full-time or part-time opportunities". That's schedule info. Could create a Schedule section. But the rule says never create Schedule section unless the posting actually states them. It does state scheduling info. So we can include a Schedule section.
But the "Why Join our Team" includes "Steady Hours, Flexible Life" which is about schedule. Could be part of Benefits or separate Schedule. Since there is a Schedule heading example, we can create a Schedule section.
Let's structure:
- Pay
- About the role
- Responsibilities
- Requirements
- Benefits
- Schedule
- About the Company (optional)
But we need to avoid thin sections. Schedule has only a couple lines. Might be okay.
Let's parse each part.
**Pay**: "Compensation Range $14.50 - $17.25 / Hour" -> Pay
Compensation Range: $14.50 - $17.25 per hour
**About the role**: The "Overview" paragraph. -> 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**: "What You'll Do" list. Each bullet is a duty. -> 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 exceptional service to ensure guest satisfaction
**Requirements**: "Your Background" list. -> Requirements
- Previous restaurant, hospitality, barista, or food service industry experience preferred
- Familiarity with beverage preparation and food handling, a plus
- Knowledge of food safety and sanitation practices
- Adaptable, patient, and able to thrive in a high volume environment
- Dependable, reliable, punctual, and dedicated with consistent work habits
- Team player with a passion for hospitality 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
**Benefits**: The "Why Join our Team" section has four subsections. We'll include all as bullet lists under Benefits. Could separate with bold labels. For semantic HTML, we can use ? But rule says use for section headings. It doesn't forbid for subsections. But to keep simple, we can use
Steady Hours, Flexible Life
... etc. That's acceptable.
Let's list each:
- 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)
- 50% off 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
We'll include all.
**Schedule**: The "Steady Hours, Flexible Life" includes scheduling info. But we already put that under Benefits. Could create a separate Schedule section with the scheduling bullet points. However, the rule says prefer a few substantive sections over many thin ones. Since scheduling is part of benefits, maybe keep under Benefits. But there is a Schedule heading example. The posting does mention scheduling explicitly. I'll create a Schedule section with the relevant bullets: "High-volume restaurant with consistent
. Probably we should keep it flat: one Benefits section with multiple bullet groups? But the rule says "Use - for any list of duties/requirements/benefits". So we can have a Benefits section with multiple
lists, each preceded by a bold label? But that might not be semantic. Alternatively, we could create separate sections for each category? But the example headings are limited. The user said "Prefer a few substantive sections over many thin ones." So maybe combine all benefits into one Benefits section with multiple lists.
But the posting has "Why Join our Team" with four subsections. Each has bullet points. We'll create a Benefits section and include all those bullet points as separate lists, maybe with a leading for the category name? Or we can use for category then . That's acceptable.
4. Responsibilities: "What You'll Do" is a list of duties. That's Responsibilities.
5. Requirements/Qualifications: "Your Background" lists requirements. Could be "Requirements" or "Qualifications". Use "Requirements".
6. Company info: "Who We Are" describes the company. Could be "About the Company" but not in the example headings. The example headings include "About the role". Might not need a separate section; but it's substantive. However, the rule says include a section ONLY when the posting has real, specific content for it. It does have content. But the example headings don't include "About the Company". Could we use "About the role"? That's different. Might be okay to include as a section with heading "About the Company"? But the instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning those are examples, not exhaustive. But we should stick to those typical headings. "Who We Are" is company description, maybe not needed. However, it's substantive and could be included as "About the Company". But the user might expect only those headings. I'll include it as a section with heading "About the Company" but that's not in the list. Safer to include as "About the role"? No, that's about the role. I think we can include a section "Company Overview" or similar. But the rule: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings. But to be safe, I'll include it as a section with heading "About the Company". However, the user might want only those headings. Let's see: The posting has "Who We Are" which is company info. It's not boilerplate; it's specific. I'll include it as a section with heading "About the Company". But the instruction says "Do NOT repeat the job title as a heading (the page already shows it)". That's fine.
Now, schedule: The posting mentions "Steady Hours, Flexible Life" and "Flexible scheduling with full-time or part-time opportunities". That's schedule info. Could create a Schedule section. But the rule says never create Schedule section unless the posting actually states them. It does state scheduling info. So we can include a Schedule section.
But the "Why Join our Team" includes "Steady Hours, Flexible Life" which is about schedule. Could be part of Benefits or separate Schedule. Since there is a Schedule heading example, we can create a Schedule section.
Let's structure:
- Pay
- About the role
- Responsibilities
- Requirements
- Benefits
- Schedule
- About the Company (optional)
But we need to avoid thin sections. Schedule has only a couple lines. Might be okay.
Let's parse each part.
**Pay**: "Compensation Range $14.50 - $17.25 / Hour" -> Pay
Compensation Range: $14.50 - $17.25 per hour
**About the role**: The "Overview" paragraph. -> 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**: "What You'll Do" list. Each bullet is a duty. -> 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 exceptional service to ensure guest satisfaction
**Requirements**: "Your Background" list. -> Requirements
- Previous restaurant, hospitality, barista, or food service industry experience preferred
- Familiarity with beverage preparation and food handling, a plus
- Knowledge of food safety and sanitation practices
- Adaptable, patient, and able to thrive in a high volume environment
- Dependable, reliable, punctual, and dedicated with consistent work habits
- Team player with a passion for hospitality 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
**Benefits**: The "Why Join our Team" section has four subsections. We'll include all as bullet lists under Benefits. Could separate with bold labels. For semantic HTML, we can use ? But rule says use for section headings. It doesn't forbid for subsections. But to keep simple, we can use
Steady Hours, Flexible Life
... etc. That's acceptable.
Let's list each:
- 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)
- 50% off 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
We'll include all.
**Schedule**: The "Steady Hours, Flexible Life" includes scheduling info. But we already put that under Benefits. Could create a separate Schedule section with the scheduling bullet points. However, the rule says prefer a few substantive sections over many thin ones. Since scheduling is part of benefits, maybe keep under Benefits. But there is a Schedule heading example. The posting does mention scheduling explicitly. I'll create a Schedule section with the relevant bullets: "High-volume restaurant with consistent
- lists, each preceded by a bold label? But that might not be semantic. Alternatively, we could create separate sections for each category? But the example headings are limited. The user said "Prefer a few substantive sections over many thin ones." So maybe combine all benefits into one Benefits section with multiple lists.
But the posting has "Why Join our Team" with four subsections. Each has bullet points. We'll create a Benefits section and include all those bullet points as separate lists, maybe with a leading
- 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 exceptional service to ensure guest satisfaction
- Previous restaurant, hospitality, barista, or food service industry experience preferred
- Familiarity with beverage preparation and food handling, a plus
- Knowledge of food safety and sanitation practices
- Adaptable, patient, and able to thrive in a high volume environment
- Dependable, reliable, punctual, and dedicated with consistent work habits
- Team player with a passion for hospitality 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
for the category name? Or we can use for category then Compensation Range: $14.50 - $17.25 per hour 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. Steady Hours, Flexible Life. That's acceptable.
4. Responsibilities: "What You'll Do" is a list of duties. That's Responsibilities.
5. Requirements/Qualifications: "Your Background" lists requirements. Could be "Requirements" or "Qualifications". Use "Requirements".
6. Company info: "Who We Are" describes the company. Could be "About the Company" but not in the example headings. The example headings include "About the role". Might not need a separate section; but it's substantive. However, the rule says include a section ONLY when the posting has real, specific content for it. It does have content. But the example headings don't include "About the Company". Could we use "About the role"? That's different. Might be okay to include as a section with heading "About the Company"? But the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning those are examples, not exhaustive. But we should stick to those typical headings. "Who We Are" is company description, maybe not needed. However, it's substantive and could be included as "About the Company". But the user might expect only those headings. I'll include it as a section with heading "About the Company" but that's not in the list. Safer to include as "About the role"? No, that's about the role. I think we can include a section "Company Overview" or similar. But the rule: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings. But to be safe, I'll include it as a section with heading "About the Company". However, the user might want only those headings. Let's see: The posting has "Who We Are" which is company info. It's not boilerplate; it's specific. I'll include it as a section with heading "About the Company". But the instruction says "Do NOT repeat the job title as a heading (the page already shows it)". That's fine.
Now, schedule: The posting mentions "Steady Hours, Flexible Life" and "Flexible scheduling with full-time or part-time opportunities". That's schedule info. Could create a Schedule section. But the rule says never create Schedule section unless the posting actually states them. It does state scheduling info. So we can include a Schedule section.
But the "Why Join our Team" includes "Steady Hours, Flexible Life" which is about schedule. Could be part of Benefits or separate Schedule. Since there is a Schedule heading example, we can create a Schedule section.
Let's structure:
- Pay
- About the role
- Responsibilities
- Requirements
- Benefits
- Schedule
- About the Company (optional)
But we need to avoid thin sections. Schedule has only a couple lines. Might be okay.
Let's parse each part.
**Pay**: "Compensation Range $14.50 - $17.25 / Hour" ->
Pay
About the role
Responsibilities
**Requirements**: "Your Background" list. -> Requirements
**Benefits**: The "Why Join our Team" section has four subsections. We'll include all as bullet lists under Benefits. Could separate with bold labels. For semantic HTML, we can use ? But rule says use
for section headings. It doesn't forbid
for subsections. But to keep simple, we can use
... etc. That's acceptable.
Let's list each:
- 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)
- 50% off 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
We'll include all.
**Schedule**: The "Steady Hours, Flexible Life" includes scheduling info. But we already put that under Benefits. Could create a separate Schedule section with the scheduling bullet points. However, the rule says prefer a few substantive sections over many thin ones. Since scheduling is part of benefits, maybe keep under Benefits. But there is a Schedule heading example. The posting does mention scheduling explicitly. I'll create a Schedule section with the relevant bullets: "High-volume restaurant with consistent