Restaurant Server PT

We need to output HTML fragment with sections: About the role (but we already have "About the Role:" heading). Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. Do NOT repeat job title as heading (the page already shows it). Do NOT put Job ID / requisition numbers as headings — none present. Remove boilerplate etc. Preserve all substantive info. We need to include sections only when posting has real specific content. We have: About Lakefront Anchorage (intro). About the Role: Server (role description). Then "Your Impact" maybe part of role. Then "What You'll Be Doing" with subcategories: Operations & Execution, Guest Experience, Team Collaboration, Compliance & Standards. Those are lists of duties. Then "Requirements" with bullet points. Then "Technical / Role-Specific Requirements". Then "Education (Optional / Adjustable)". Then "Benefits". Then "Why Join Us". Also "At Millennium, we are guided by our core values:" maybe part of intro. Also "About Lakefront Anchorage" paragraph. We need to decide which sections to output as headings: Possibly "About Lakefront Anchorage", "About the Role", "Responsibilities" (or "What You'll Be Doing"), "Requirements", "Benefits", "Why Join Us". Also maybe "Core Values". But we need to avoid thin sections. Let's see content. We have a paragraph about Lakefront Anchorage location and description. That's substantive. Then "At Millennium, we are guided by our core values:" with list of values. That could be a section "Core Values". It's substantive. Then "About the Role: Server" with description. Could be heading "About the Role". Then "Your Impact" maybe part of role description. Then "What You'll Be Doing" with subheadings. Could be heading "Responsibilities". Under that we have bullet lists for each subcategory. Could combine into one list or separate sublists. Then "Requirements" heading with bullet list. Then "Technical / Role-Specific Requirements" maybe part of Requirements; could be merged. Then "Education (Optional / Adjustable)" maybe part of Requirements; could be included. Then "Benefits" heading with bullet list. Then "Why Join Us" heading with paragraph. We must not include sections with filler like "Salary Range: Not Required by AK" - we should drop that line. Also "Hotel Name: Lakefront Anchorage Location: Onsite - Anchorage, AK" maybe we can include location in a short paragraph? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we could include a short paragraph with hotel name and location. But we already have "About Lakefront Anchorage" which includes location. The hotel name and location line is redundant; we can drop it. We must not include cookie/navigation/legal/EEO etc. Not present. We must not invent or summarize away detail. Preserve all substantive information. So we need to keep all details from the posting, but we can reformat. Let's extract substantive content: - Hotel Name: Lakefront Anchorage (maybe not needed) - Location: Onsite - Anchorage, AK (maybe included in About Lakefront Anchorage) - About Lakefront Anchorage paragraph: "Located on the shores of Lake Hood, Lakefront Anchorage offers a one-of-a-kind setting where guests can take in breathtaking views of floatplanes, mountains, and Alaska's natural landscape. As one of Anchorage's most distinctive hotels, the property serves as a gateway for travelers seeking both adventure and comfort. With easy access to downtown Anchorage and nearby attractions, Lakefront Anchorage blends scenic surroundings with a relaxed, inviting atmosphere—creating an experience that is uniquely Alaskan. As part of Millennium Hotels & Resorts, a global hospitality leader with over 145 hotels across key destinations worldwide, our hotel is backed by a legacy of quality, consistency, and service excellence—driven by a passion for hospitality, an entrepreneurial spirit, innovation, and a progressive, solutions-oriented approach." - Core values list: Passion for Hospitality - Delivering meaningful and memorable guest experiences; Entrepreneurial - Taking ownership and acting with agility; Innovation & Progressive - Continuously improving how we operate and serve; Solutions & Results Oriented - Staying adaptable and focused on results. - About the Role: Server paragraph: "As our Server you will play an integral role in delivering an exceptional guest experience while contributing to a collaborative and high-performing team environment. This role is ideal for someone who brings a passion for hospitality, takes ownership, and is committed to continuous improvement and results." - Your Impact: "You will support day-to-day operations, support team performance, and ensure service standards are consistently delivered. You'll act as a bridge between leadership and frontline teams—driving accountability, engagement, and results." - What You'll Be Doing: subheadings with bullet points. Operations & Execution: - Ensure smooth, efficient operations aligned with brand standards - Identify opportunities for innovation and continuous improvement - Deliver consistent, high-quality results in a fast-paced environment Guest Experience: - Deliver exceptional service rooted in passion for hospitality - Anticipate needs and respond with a solutions-first mindset - Create memorable, personalized experiences for every guest Team Collaboration: - Work collaboratively across teams to achieve shared goals - Communicate effectively and contribute to a positive work environment - Support a culture of respect, energy, and accountability Compliance & Standards: - Follow all company policies, safety standards, and procedures - Maintain accuracy in processes, reporting, and documentation - Uphold a culture of accountability and operational excellence - Check station before, during and after shift for proper set-up and cleanliness - Greet the guests in a friendly, courteous manner within 30 seconds of being seated and explain any specials and/or restaurant promotions for guest awareness - Record the details of the order from the guests, repeating the order to the guest to check for accuracy - Input the order into the Point of Sale computer to inform the kitchen of the particulars in the order being placed - Present the check to guest promptly and collect payment - Replenish beverages as necessary and check with guests for overall satisfaction - Be knowledgeable about all Food & Beverage products served. Requirements: - Passion for hospitality and delivering exceptional service - Strong communication and interpersonal skills - Ability to work in a fast-paced, dynamic environment - Solutions-oriented mindset with attention to detail - Flexibility to work varied schedules, including evenings, weekends, and holidays Technical / Role-Specific Requirements: - Must have basic knowledge of food and beverage preparation, service standards, guest relations and etiquette. - Must have knowledge of the appropriate table settings, service-ware and menu items. - Requires lifting and carrying of objects weighing up to 50 pounds. - Prior hospitality experience preferred. - Ability to obtain TIPS certification is required. - Guest attentiveness and a neat appearance - Exceptional customer service skills - Be professional in all interactions with guests and associates. Education (Optional / Adjustable): - High school diploma or equivalent required Benefits: - Hotel Room Discounts across our global portfolio - Employee Assistance Program (EAP) - Benefits eligibility and offerings are subject to plan terms and company policy. Why Join Us: - At Millennium Hotels & Resorts, you're not just taking a job—you're joining a team passionate about hospitality, growth, and creating memorable experiences. Whether you're behind the scenes or on the front line, your work makes an impact. If you're ready to learn, grow, and be part of something meaningful, we'd love to meet you. We also have "At Millennium, we are guided by our core values:" preceding the list. We need to output HTML fragment with headings

  . Use

  • for any list of duties/requirements/benefits. Use

    for prose. We need to decide which sections to include. Likely:

    About Lakefront Anchorage

    ...

    Core Values

    • ...
    ...

    About the Role

    ...

    maybe also include Your Impact as part of same

    or separate

    . Then

    Responsibilities

    with all duty items (maybe grouped under subheadings? But we cannot have headings inside
    ? We could have

    but only

    allowed for section headings. Could we include subheadings as or just plain text? 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 says use

    for section headings. Could we still use

    for subheadings? Might be okay but safer to avoid extra headings; we can just list all duties in one

    with maybe a brief intro sentence before each group using

    or . But we need to preserve all substantive information; we can keep the subheadings as plain text (maybe ) inside

    • or preceding

      . Let's think. We could output:

      Responsibilities

      Operations & Execution:

      • Ensure smooth, efficient operations aligned with brand standards
      ...

      Guest Experience:

      ...
      ... That seems acceptable; still using

      for main section, and using

      with for subheadings. Similarly for Requirements: could split into General Requirements and Technical / Role-Specific Requirements and Education. We'll do:

      Requirements

      General Requirements:

      ...

      Technical / Role-Specific Requirements:

      ...

      Education:

      ...
      Benefits:

      Benefits

      ... Why Join Us:

      Why Join Us

      ... We must not include sections with filler like "Salary Range: Not Required by AK". We'll drop that. We also need to include the hotel name and location? Already in About Lakefront Anchorage paragraph includes location (Lake Hood, Anchorage). The hotel name is mentioned there? Not explicitly; but we could add a short paragraph:

      Lakefront Anchorage, located onsite in Anchorage, AK.

      but maybe redundant. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it. So we could include a short paragraph with hotel name and location before the About Lakefront Anchorage section. But we already have About Lakefront Anchorage which includes location; we could just keep that. Let's craft HTML. We need to ensure we don't include any markdown code fences. Just raw HTML. Let's write:

      About Lakefront Anchorage

      Located on the shores of Lake Hood, Lakefront Anchorage offers a one-of-a-kind setting where guests can take in breathtaking views of floatplanes, mountains, and Alaska's natural landscape. As one of Anchorage's most distinctive hotels, the property serves as a gateway for travelers seeking both adventure and comfort. With easy access to downtown Anchorage and nearby attractions, Lakefront Anchorage blends scenic surroundings with a relaxed, inviting atmosphere—creating an experience that is uniquely Alaskan. As part of Millennium Hotels & Resorts, a global hospitality leader with over 145 hotels across key destinations worldwide, our hotel is backed by a legacy of quality,