Host
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
- 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 $15.92 - $18.00 / Hour" - this is specific pay info, so include Pay section.
2. Overview: "Our Hosts know that first impressions are everything..." - this is prose about the role. Could be "About the role" or just part of overview. Since there's a "What You'll Do" section for responsibilities, maybe "About the role" for the overview paragraph.
3. Why Join our Team: This contains multiple subsections: "Steady Hours, Flexible Life", "Benefits That Have Your Back", "Grow With Us", "Perks, Recognition & Community". These are benefits and perks. Should I combine into a Benefits section? The rules say use headings like Benefits, Pay, Schedule. The posting has specific benefits listed. I'll create a Benefits section with sub-lists.
4. What You'll Do: list of responsibilities - use Responsibilities heading.
5. Your Background: list of requirements - use Requirements heading.
6. Who We Are: company description - could be "About the company" but not in the suggested headings. The suggested headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Who We Are" is company info, maybe not needed as a separate heading? But it's substantive. Could include as a paragraph under "About the role" or separate. Since the rules say prefer few substantive sections, maybe include as a paragraph at the end or under a heading? The rules don't have "About the company" heading. I could include it as a paragraph after the main sections, but the instruction says use
for section headings like those listed. I think I'll include it as a paragraph under a heading "About the company" but that's not in the list. However, the list is not exhaustive; it says "e.g." So I can use other headings if needed. But the rule: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., so other headings are allowed. But to keep it simple, maybe include "Who We Are" as a heading? However, the posting includes EEO statement at the end which is boilerplate. The "Who We Are" paragraph includes company info and EEO. The EEO part is boilerplate. I should remove the EEO boilerplate. The company description is substantive. I'll include a section "About the company" with the descriptive paragraph, but not the EEO part.
Also, there's a line "To notify of a non-compliant job posting..." that's boilerplate, remove.
Now, let's structure:
- Pay section: with the compensation range.
- About the role: overview paragraph.
- Responsibilities: list from "What You'll Do".
- Requirements: list from "Your Background".
- Benefits: combine all benefits/perks from "Why Join our Team". This includes multiple categories: Steady Hours, Flexible Life (scheduling, pay access, discounts), Benefits That Have Your Back (vacation, medical, etc.), Grow With Us (training, advancement, education), Perks, Recognition & Community (discounts, recognition, HELP Fund, community events, awards). I'll create a Benefits section with sub-lists or a single list? The rules say use - for any list of duties/requirements/benefits. I can make a list of benefit items. But there are many. Could group them under subheadings? But the rule says use
for section headings, not subheadings. I could use but not specified. Better to keep flat list or use multiple with maybe for categories? But the instruction says use - for any list. I think I'll create a Benefits section with a list of all benefit items, each as a li. But there are many. Could separate into multiple lists? The rule doesn't forbid multiple lists. I'll create a single
with all benefit items, but that might be long. Alternatively, I can create sub-sections using but not required. I'll keep it as a single list with each benefit as a li, maybe grouping by category using bold text within li. But the rule says use - for any list. I'll do a list.
- Schedule: The posting mentions "Flexible scheduling with full-time or part-time opportunities" and "Steady Hours". That's schedule info. Should I create a Schedule section? The rules say never create Schedule section unless posting actually states them. It does state scheduling info. So include Schedule section.
- About the company: "Who We Are" paragraph (without EEO). Could be a section.
Now, check for boilerplate: The EEO paragraph: "We are an equal opportunity employer... We welcome applicants... The Cheesecake Factory offers reasonable accommodations..." This is boilerplate, remove. Also the line "To notify of a non-compliant job posting..." remove.
Also, the "Why Join our Team" heading is not needed as a separate heading; we'll incorporate its content into Benefits and Schedule.
Now, let's write HTML.
First, Pay section:
Pay
Compensation Range: $15.92 - $18.00 per hour
But the original says "Compensation Range $15.92 - $18.00 / Hour". I'll keep as is.
About the role:
About the role
Our Hosts know that first impressions are everything. As a Host, your warm, friendly, welcoming personality will shine while greeting and seating guests, managing the waitlist, and accommodating reservations. When we’re on a wait, you’ll quote accurate times, engage guests in casual conversation, and encourage them to explore our iconic menu or beautiful bakery case, answering questions along the way. With pride and a passion for hospitality, you’ll help ensure every guest feels welcomed and cared for from start to finish.
Responsibilities:
Responsibilities
- Warmly greet guests creating a positive first impression
- Use a floor plan and follow a seating rotation to assign tables promoting guest satisfaction
- Provide accurately quoted wait times while managing reservations to support smooth guest flow
- Play an important role in front of house operations, supporting teamwork to enhance the overall guest experience
- Answer phones with a sense of urgency, helping guests with general questions
- Follow instructions with attention to detail and consistency
- Demonstrate ownership of sidework and closing tasks
- Multitask and work well under pressure while maintaining cleanliness and organization
- Work with speed and efficiency in a fast paced, full-service restaurant
Requirements:
Requirements
- Previous restaurant, hospitality, customer service, or food service industry experience preferred
- Strong communication and interpersonal skills with a focus on guest service
- Dependable, dedicated, reliable, and punctual with a strong work ethic
- Adaptable and patient, taking pride in providing excellent guest relations
- Team player with a positive, patient attitude
- Ability to lift up to 35 pounds, stand for extended periods, continuously bend, reach and twist
- Must be at least 18 years old
Benefits:
Benefits
- Steady hours with flexible scheduling (full-time or part-time opportunities)
- Faster Pay – access up to 50% of earned wages the next day (exclusions apply)
- 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 designed to support 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) for moments that matter
- Opportunities to give back through community and charity events
- Award-winning company recognition: Fortune 100 Best Companies to Work For® (since 2014), PEOPLE® Companies That Care (since 2021), Great Place to Work® Certified
Schedule:
Schedule
Flexible scheduling with full-time or part-time opportunities; steady hours in a high-volume restaurant.
About the company:
About the company
Named to FORTUNE Magazine’s “100 Best Companies to Work For®” list every year since 2014, The Cheesecake Factory Incorporated is a leader in experiential dining. We are culinary-forward and relentlessly focused on hospitality. Delicious, memorable experiences created by passionate people—this defines who we are and where we are going. We currently own and operate over 370 restaurants throughout the United States and Canada under brands including The Cheesecake Factory®, North Italia®, Flower Child® and a collection of other FRC brands. Internationally, 35 The Cheesecake Factory® restaurants operate under licensing agreements. Our bakery division operates two facilities that produce quality cheesecakes and other baked products for our restaurants, international licensees and third-party bakery customers.
Now, check if any section has filler: Pay has specific numbers. Benefits has specific items. Schedule has specific info. All good.
Now, ensure no duplicate info. The "Why Join our Team" had "Steady Hours, Flexible Life" which includes scheduling and pay access. I've included scheduling in Schedule and pay access in Benefits. That's fine.
Now, output only the HTML fragment. No markdown fences. Just the HTML.
Let's write
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 - 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 $15.92 - $18.00 / Hour" - this is specific pay info, so include Pay section. 2. Overview: "Our Hosts know that first impressions are everything..." - this is prose about the role. Could be "About the role" or just part of overview. Since there's a "What You'll Do" section for responsibilities, maybe "About the role" for the overview paragraph. 3. Why Join our Team: This contains multiple subsections: "Steady Hours, Flexible Life", "Benefits That Have Your Back", "Grow With Us", "Perks, Recognition & Community". These are benefits and perks. Should I combine into a Benefits section? The rules say use headings like Benefits, Pay, Schedule. The posting has specific benefits listed. I'll create a Benefits section with sub-lists. 4. What You'll Do: list of responsibilities - use Responsibilities heading. 5. Your Background: list of requirements - use Requirements heading. 6. Who We Are: company description - could be "About the company" but not in the suggested headings. The suggested headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Who We Are" is company info, maybe not needed as a separate heading? But it's substantive. Could include as a paragraph under "About the role" or separate. Since the rules say prefer few substantive sections, maybe include as a paragraph at the end or under a heading? The rules don't have "About the company" heading. I could include it as a paragraph after the main sections, but the instruction says use
for section headings like those listed. I think I'll include it as a paragraph under a heading "About the company" but that's not in the list. However, the list is not exhaustive; it says "e.g." So I can use other headings if needed. But the rule: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., so other headings are allowed. But to keep it simple, maybe include "Who We Are" as a heading? However, the posting includes EEO statement at the end which is boilerplate. The "Who We Are" paragraph includes company info and EEO. The EEO part is boilerplate. I should remove the EEO boilerplate. The company description is substantive. I'll include a section "About the company" with the descriptive paragraph, but not the EEO part.
Also, there's a line "To notify of a non-compliant job posting..." that's boilerplate, remove.
Now, let's structure:
- Pay section: with the compensation range.
- About the role: overview paragraph.
- Responsibilities: list from "What You'll Do".
- Requirements: list from "Your Background".
- Benefits: combine all benefits/perks from "Why Join our Team". This includes multiple categories: Steady Hours, Flexible Life (scheduling, pay access, discounts), Benefits That Have Your Back (vacation, medical, etc.), Grow With Us (training, advancement, education), Perks, Recognition & Community (discounts, recognition, HELP Fund, community events, awards). I'll create a Benefits section with sub-lists or a single list? The rules say use - for any list of duties/requirements/benefits. I can make a list of benefit items. But there are many. Could group them under subheadings? But the rule says use
for section headings, not subheadings. I could use but not specified. Better to keep flat list or use multiple with maybe for categories? But the instruction says use - for any list. I think I'll create a Benefits section with a list of all benefit items, each as a li. But there are many. Could separate into multiple lists? The rule doesn't forbid multiple lists. I'll create a single
with all benefit items, but that might be long. Alternatively, I can create sub-sections using but not required. I'll keep it as a single list with each benefit as a li, maybe grouping by category using bold text within li. But the rule says use - for any list. I'll do a list.
- Schedule: The posting mentions "Flexible scheduling with full-time or part-time opportunities" and "Steady Hours". That's schedule info. Should I create a Schedule section? The rules say never create Schedule section unless posting actually states them. It does state scheduling info. So include Schedule section.
- About the company: "Who We Are" paragraph (without EEO). Could be a section.
Now, check for boilerplate: The EEO paragraph: "We are an equal opportunity employer... We welcome applicants... The Cheesecake Factory offers reasonable accommodations..." This is boilerplate, remove. Also the line "To notify of a non-compliant job posting..." remove.
Also, the "Why Join our Team" heading is not needed as a separate heading; we'll incorporate its content into Benefits and Schedule.
Now, let's write HTML.
First, Pay section:
Pay
Compensation Range: $15.92 - $18.00 per hour
But the original says "Compensation Range $15.92 - $18.00 / Hour". I'll keep as is.
About the role:
About the role
Our Hosts know that first impressions are everything. As a Host, your warm, friendly, welcoming personality will shine while greeting and seating guests, managing the waitlist, and accommodating reservations. When we’re on a wait, you’ll quote accurate times, engage guests in casual conversation, and encourage them to explore our iconic menu or beautiful bakery case, answering questions along the way. With pride and a passion for hospitality, you’ll help ensure every guest feels welcomed and cared for from start to finish.
Responsibilities:
Responsibilities
- Warmly greet guests creating a positive first impression
- Use a floor plan and follow a seating rotation to assign tables promoting guest satisfaction
- Provide accurately quoted wait times while managing reservations to support smooth guest flow
- Play an important role in front of house operations, supporting teamwork to enhance the overall guest experience
- Answer phones with a sense of urgency, helping guests with general questions
- Follow instructions with attention to detail and consistency
- Demonstrate ownership of sidework and closing tasks
- Multitask and work well under pressure while maintaining cleanliness and organization
- Work with speed and efficiency in a fast paced, full-service restaurant
Requirements:
Requirements
- Previous restaurant, hospitality, customer service, or food service industry experience preferred
- Strong communication and interpersonal skills with a focus on guest service
- Dependable, dedicated, reliable, and punctual with a strong work ethic
- Adaptable and patient, taking pride in providing excellent guest relations
- Team player with a positive, patient attitude
- Ability to lift up to 35 pounds, stand for extended periods, continuously bend, reach and twist
- Must be at least 18 years old
Benefits:
Benefits
- Steady hours with flexible scheduling (full-time or part-time opportunities)
- Faster Pay – access up to 50% of earned wages the next day (exclusions apply)
- 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 designed to support 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) for moments that matter
- Opportunities to give back through community and charity events
- Award-winning company recognition: Fortune 100 Best Companies to Work For® (since 2014), PEOPLE® Companies That Care (since 2021), Great Place to Work® Certified
Schedule:
Schedule
Flexible scheduling with full-time or part-time opportunities; steady hours in a high-volume restaurant.
About the company:
About the company
Named to FORTUNE Magazine’s “100 Best Companies to Work For®” list every year since 2014, The Cheesecake Factory Incorporated is a leader in experiential dining. We are culinary-forward and relentlessly focused on hospitality. Delicious, memorable experiences created by passionate people—this defines who we are and where we are going. We currently own and operate over 370 restaurants throughout the United States and Canada under brands including The Cheesecake Factory®, North Italia®, Flower Child® and a collection of other FRC brands. Internationally, 35 The Cheesecake Factory® restaurants operate under licensing agreements. Our bakery division operates two facilities that produce quality cheesecakes and other baked products for our restaurants, international licensees and third-party bakery customers.
Now, check if any section has filler: Pay has specific numbers. Benefits has specific items. Schedule has specific info. All good.
Now, ensure no duplicate info. The "Why Join our Team" had "Steady Hours, Flexible Life" which includes scheduling and pay access. I've included scheduling in Schedule and pay access in Benefits. That's fine.
Now, output only the HTML fragment. No markdown fences. Just the HTML.
Let's write
- for any list of duties/requirements/benefits. I can make a list of benefit items. But there are many. Could group them under subheadings? But the rule says use
for section headings, not subheadings. I could use
but not specified. Better to keep flat list or use multiple
- with maybe for categories? But the instruction says use
- for any list. I think I'll create a Benefits section with a list of all benefit items, each as a li. But there are many. Could separate into multiple lists? The rule doesn't forbid multiple lists. I'll create a single
- with all benefit items, but that might be long. Alternatively, I can create sub-sections using
- for any list. I'll do a list.
- Schedule: The posting mentions "Flexible scheduling with full-time or part-time opportunities" and "Steady Hours". That's schedule info. Should I create a Schedule section? The rules say never create Schedule section unless posting actually states them. It does state scheduling info. So include Schedule section.
- About the company: "Who We Are" paragraph (without EEO). Could be a section.
Now, check for boilerplate: The EEO paragraph: "We are an equal opportunity employer... We welcome applicants... The Cheesecake Factory offers reasonable accommodations..." This is boilerplate, remove. Also the line "To notify of a non-compliant job posting..." remove.
Also, the "Why Join our Team" heading is not needed as a separate heading; we'll incorporate its content into Benefits and Schedule.
Now, let's write HTML.
First, Pay section:
Pay
Compensation Range: $15.92 - $18.00 per hour
But the original says "Compensation Range $15.92 - $18.00 / Hour". I'll keep as is. About the role:About the role
Our Hosts know that first impressions are everything. As a Host, your warm, friendly, welcoming personality will shine while greeting and seating guests, managing the waitlist, and accommodating reservations. When we’re on a wait, you’ll quote accurate times, engage guests in casual conversation, and encourage them to explore our iconic menu or beautiful bakery case, answering questions along the way. With pride and a passion for hospitality, you’ll help ensure every guest feels welcomed and cared for from start to finish.
Responsibilities:Responsibilities
- Warmly greet guests creating a positive first impression
- Use a floor plan and follow a seating rotation to assign tables promoting guest satisfaction
- Provide accurately quoted wait times while managing reservations to support smooth guest flow
- Play an important role in front of house operations, supporting teamwork to enhance the overall guest experience
- Answer phones with a sense of urgency, helping guests with general questions
- Follow instructions with attention to detail and consistency
- Demonstrate ownership of sidework and closing tasks
- Multitask and work well under pressure while maintaining cleanliness and organization
- Work with speed and efficiency in a fast paced, full-service restaurant
Requirements
- Previous restaurant, hospitality, customer service, or food service industry experience preferred
- Strong communication and interpersonal skills with a focus on guest service
- Dependable, dedicated, reliable, and punctual with a strong work ethic
- Adaptable and patient, taking pride in providing excellent guest relations
- Team player with a positive, patient attitude
- Ability to lift up to 35 pounds, stand for extended periods, continuously bend, reach and twist
- Must be at least 18 years old
Benefits
- Steady hours with flexible scheduling (full-time or part-time opportunities)
- Faster Pay – access up to 50% of earned wages the next day (exclusions apply)
- 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 designed to support 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) for moments that matter
- Opportunities to give back through community and charity events
- Award-winning company recognition: Fortune 100 Best Companies to Work For® (since 2014), PEOPLE® Companies That Care (since 2021), Great Place to Work® Certified
Schedule
Flexible scheduling with full-time or part-time opportunities; steady hours in a high-volume restaurant.
About the company:About the company
Named to FORTUNE Magazine’s “100 Best Companies to Work For®” list every year since 2014, The Cheesecake Factory Incorporated is a leader in experiential dining. We are culinary-forward and relentlessly focused on hospitality. Delicious, memorable experiences created by passionate people—this defines who we are and where we are going. We currently own and operate over 370 restaurants throughout the United States and Canada under brands including The Cheesecake Factory®, North Italia®, Flower Child® and a collection of other FRC brands. Internationally, 35 The Cheesecake Factory® restaurants operate under licensing agreements. Our bakery division operates two facilities that produce quality cheesecakes and other baked products for our restaurants, international licensees and third-party bakery customers.
Now, check if any section has filler: Pay has specific numbers. Benefits has specific items. Schedule has specific info. All good. Now, ensure no duplicate info. The "Why Join our Team" had "Steady Hours, Flexible Life" which includes scheduling and pay access. I've included scheduling in Schedule and pay access in Benefits. That's fine. Now, output only the HTML fragment. No markdown fences. Just the HTML. Let's write
but not required. I'll keep it as a single list with each benefit as a li, maybe grouping by category using bold text within li. But the rule says use
- for any list. I'll do a list.
- Schedule: The posting mentions "Flexible scheduling with full-time or part-time opportunities" and "Steady Hours". That's schedule info. Should I create a Schedule section? The rules say never create Schedule section unless posting actually states them. It does state scheduling info. So include Schedule section.
- About the company: "Who We Are" paragraph (without EEO). Could be a section.
Now, check for boilerplate: The EEO paragraph: "We are an equal opportunity employer... We welcome applicants... The Cheesecake Factory offers reasonable accommodations..." This is boilerplate, remove. Also the line "To notify of a non-compliant job posting..." remove.
Also, the "Why Join our Team" heading is not needed as a separate heading; we'll incorporate its content into Benefits and Schedule.
Now, let's write HTML.
First, Pay section:
- for any list. I think I'll create a Benefits section with a list of all benefit items, each as a li. But there are many. Could separate into multiple lists? The rule doesn't forbid multiple lists. I'll create a single