Server

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must preserve all substantive info, no invented details. Remove boilerplate: cookie/navigation/legal/EEO etc. The posting includes location, schedule, etc. We need to decide sections. We have: - About the role: description of role, mission, etc. Could be a paragraph. - Responsibilities: list of duties (What You'll Do). Use

• . - Requirements: maybe "What We're Looking For" includes ideal candidate traits. Could be Requirements. - Qualifications: Education & Experience. - Skills: maybe combine with Requirements? But we need to decide. - Benefits: "Why Hillcrest?" and "What Hillcrest Offers" includes benefits: competitive compensation, schedule, supportive leadership, professional development, Dayforce Wallet, gym membership reimbursement, partner discounts, leadership experience, growth opportunities. - Pay: Not explicitly given; only "Competitive compensation." That's vague; we should not create Pay section unless posting actually states them. It says "Competitive compensation." That's not a specific number or range; but it's still mention of compensation. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive compensation." That's a statement about pay, albeit vague. Should we include Pay? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive compensation." That is a statement about pay, so we could include Pay section with that sentence. However they also say: prefer a few substantive sections over many thin ones. Could combine Pay into Benefits? But Benefits section already includes many items; we could include Pay as part of Benefits. However they said to use headings for Benefits, Pay, Schedule separately if content exists. Since we have schedule info explicitly: "Part-Time | Approximately 2–3 Shifts per Week | Some Weekends | Primarily 4:00 p.m. – 8:00 p.m." Also repeated in What Hillcrest Offers. So we should have Schedule section. Pay: we have "Competitive compensation." That's specific enough? It's not a number but it's a statement. I'd include Pay section with that sentence. Benefits: we have many bullet-ish items: supportive leadership, professional development, Dayforce Wallet, gym membership reimbursement, partner discounts, leadership experience, growth opportunities. Also "Competitive compensation" maybe duplicate. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment. Structure:

  About the role

  ... paragraph ...

  Responsibilities

  • ...
  ...

  Requirements

  maybe list of ideal candidate traits? Could be bullet list. But we also have Qualifications (Education & Experience). Could separate. We need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role, Responsibilities, Requirements (what we're looking for), Qualifications (Education & Experience), Skills (maybe we can extract skills from requirements), Benefits, Pay, Schedule. We must not repeat job title as heading. We must not include Job ID etc. We must preserve all substantive info. Let's extract paragraphs. About the role: The paragraph after location and schedule: "Hillcrest Health & Living is looking for a friendly, dependable, and service-focused Culinary Service Lead (CSL) to join our dining team at Hillcrest Millard in Omaha, NE. Hillcrest Millard provides post-acute rehabilitation and long-term care in a modern, welcoming environment. Our team works together to create a comfortable experience where guests and residents feel known, valued, and supported. At Hillcrest, our mission is simple: Inspiring people to live their best lives. As a Culinary Service Lead, you will help bring that mission to life by supporting smooth meal-service operations, assisting and guiding the dining team, and creating positive dining experiences for guests and residents." That's good. Responsibilities: The "What You’ll Do" section bullet list (though not bullet in text). We'll convert each sentence to
  • . List: - Help lead and coordinate dining-room service during assigned shifts. - Provide direction and support to Servers to help keep meal service organized and running smoothly. - Serve as a resource for team members when questions or service needs arise. - Greet guests and residents warmly and provide friendly, attentive service. - Take and communicate meal and beverage orders accurately as needed. - Serve meals and beverages according to individual preferences and established dining procedures. - Follow prescribed diets, food textures, allergies, and other individualized dining needs as directed. - Assist guests and residents with meal selections and special dining requests. - Help coordinate room trays and other meal-service needs. - Ensure dining areas are prepared and ready before meal service. - Help monitor dining-room cleanliness, organization, and presentation throughout the shift. - Support table setup, clearing, cleaning, and resetting as needed. - Assist with dishes, dishwashing, and other kitchen or dining responsibilities when needed. - Monitor supply levels and help ensure dining areas remain stocked. - Support completion of required food-temperature and safety documentation. - Ensure food items are properly dated, labeled, stored, and rotated according to established procedures. - Communicate guest and resident preferences, concerns, or changes to the appropriate team member. - Help address service concerns promptly and professionally. - Support new or developing dining team members with day-to-day questions and expectations. - Build positive relationships with guests and residents through friendly conversation and dependable service. - Work collaboratively with the culinary team to keep meal service moving efficiently. - Assist with special meals, celebrations, events, and additional dining needs as assigned. That's many items. Requirements: "What We’re Looking For" paragraph: "We are looking for someone who enjoys working with people, naturally steps in to help, and can provide a little extra leadership during meal service. The right candidate will be friendly and approachable while also being comfortable helping keep the team organized and focused. You should be someone who notices what needs to be done, communicates clearly, and is willing to jump in wherever needed." Then "Ideal Candidates Will Have" list bullet-ish sentences: - A friendly, welcoming, and service-focused personality. - Previous restaurant, senior living, hospitality, food service, or customer-service experience preferred. - Previous lead, shift-lead, or informal leadership experience helpful. - A genuine interest in working with aging adults. - Strong communication and interpersonal skills. - Ability to provide courteous and professional service to guests, residents, families, and visitors. - Confidence providing direction and support to other dining team members. - Strong attention to detail with dining preferences and dietary needs. - Dependability and consistent follow-through. - Ability to stay organized and manage multiple priorities during busy meal periods. - A positive and flexible approach when guest or resident needs change. - Strong teamwork and a willingness to jump in and help. - Ability to recognize a service issue and take appropriate action. - Ability to follow food-safety, sanitation, and infection-control procedures. - Comfort working in a fast-paced dining environment while maintaining excellent service. We can put these as
    • under Requirements. Qualifications: "Education & Experience" section: - High school diploma or equivalent preferred. - Previous dining, food service, restaurant, hospitality, senior living, or customer-service experience preferred. - Previous lead or supervisory experience helpful but not required. - Experience working with aging adults is helpful but not required. We can list as
      . Skills: Could be derived from Requirements but maybe we can combine? However we have a separate Skills heading possible. We could list skills like: communication, interpersonal, leadership, organization, attention to detail, teamwork, flexibility, food safety, etc. But we must not invent details; we can extract from the Ideal Candidates list. But that might be redundant with Requirements. However the instruction: Prefer a few substantive sections over many thin ones. Could we omit Skills and just have Requirements and Qualifications? But we need to follow headings list only if we have content. We could decide to not include Skills if we think it's thin. However we have content for skills; but we could merge into Requirements. The instruction: "Prefer a few substantive sections over many thin ones." So better to have fewer sections. We could combine Requirements and Qualifications into one? But they have distinct headings. We could keep Requirements and Qualifications separate, and omit Skills. That seems reasonable. Benefits: "Why Hillcrest?" paragraph plus "What Hillcrest Offers" list. Why Hillcrest? paragraph: "Dining is an important part of everyday life at Hillcrest Millard. Meals provide more than nutrition—they are an opportunity for guests and residents to connect with others, enjoy familiar routines, and take a break from the clinical side of their day. As a Culinary Service Lead, you will have the opportunity to get to know the people you serve while also helping the dining team deliver a consistent and enjoyable experience. This is a great opportunity for someone who enjoys working with people, likes being the person others can turn to, and is looking for a part-time schedule of approximately 2–3 shifts per week, primarily from 4:00 p.m. to 8:00 p.m., with some weekend availability." What Hillcrest Offers list: - Competitive compensation. - Approximately 2–3 shifts per week. - Primarily 4:00 p.m. – 8:00 p.m. shifts. - Some weekend shifts required. - Supportive leadership and a collaborative culinary team. - Professional development and career-growth opportunities. - Dayforce Wallet, allowing you to choose when you get paid. - Gym membership reimbursement and partner discounts. - Opportunity to build leadership experience within the culinary team. - Opportunities to grow within a mission-driven senior care organization. We can combine these into Benefits section as
      • . Note that some items overlap with schedule and pay; but we will also have separate Pay and Schedule sections. To avoid duplication, we could keep schedule and pay separate and benefits only the other items. However the instruction: "Prefer a few substantive sections over many thin ones." Having separate Pay, Schedule, Benefits may be thin if each only has few items. But we have multiple benefit items. We could put schedule and pay within Benefits as well, but then we would not have separate Pay/Schedule headings. The rule says: "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings if we have content. It does not forbid having overlapping content across sections, but we should avoid duplication? Not explicitly forbidden, but we should preserve all substantive information; duplication is okay if it's in original. However we should not invent. The original repeats schedule and compensation in both "What Hillcrest Offers" and earlier schedule line. It's okay to duplicate. We could create: - Pay:

        Competitive compensation.

        - Schedule:

        Part-Time | Approximately 2–3 Shifts per Week | Some Weekends | Primarily 4:00 p.m. – 8:00 p.m.

        (or list items) - Benefits:

        with the rest: supportive leadership, professional development, Dayforce Wallet, gym membership reimbursement and partner discounts, opportunity to build leadership experience, opportunities to grow within mission-driven senior care organization. We could also include "Competitive compensation" in Pay only, not duplicate in Benefits. Now we need to ensure we don't include boilerplate like "EEO", "scam-warning". Not present. Now produce HTML fragment. We'll need to escape any HTML special characters? Not needed. Let's craft.

        About the role