Hospitality Manager

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: 1. "Living Our Values" - this seems like company culture/values, but it's generic boilerplate. The rules say to remove boilerplate. However, "Why Join Us" and "Total Rewards" seem more specific to the role/company. I should include sections that have real, specific content. 2. "Why Join Us" - has three bullet points: Career Growth, Culture of Excellence, Competitive Benefits. This is specific content. 3. "Total Rewards" - describes compensation structure and benefits package. This is specific. 4. "A Day In The Life" - describes the role. This is the "About the role" section. 5. "As a Mgr, Hospitality You Will" - list of responsibilities. This is "Responsibilities". 6. "What We Need From You" - requirements/qualifications. This includes education, experience, skills, physical requirements, travel. This could be split into "Requirements" and "Qualifications" or "Skills". The rules mention headings like Requirements, Qualifications, Skills. I'll combine into "Requirements" and maybe "Qualifications" for the skills list. 7. Physical and Environmental Requirements - specific details. 8. Travel Requirements - specific. 9. "Join Us" - EEO, accommodations, diversity, sponsorship. This is boilerplate per rules: remove EEO/equal-opportunity boilerplate. So I should drop this. Also, the job title is "Hospitality Manager" (from "As a Mgr, Hospitality"). The page already shows it, so don't repeat as heading. Job ID/requisition numbers: there's "DL NUMBER - Driver License, Valid and in State" - that's a requirement, not a job ID. No requisition number visible. Now, structure: - About the role (from "A Day In The Life") - Responsibilities (from "As a Mgr, Hospitality You Will") - Requirements (from "What We Need From You" - education, experience) - Qualifications/Skills (the bullet points under "Required") - Physical Requirements (separate section) - Travel Requirements (maybe combine with Physical or separate) - Benefits (from "Why Join Us" and "Total Rewards") - but "Why Join Us" includes Competitive Benefits, and "Total Rewards" details benefits. Could create a "Benefits" section. - Pay/Compensation: "Total Rewards" mentions compensation structure but not specific numbers. It says "competitive and fair compensation structure that includes base pay and performance-based rewards. Compensation is based on skill set, experience, qualifications, and job-related requirements." That's generic, but it's specific to the posting. The rules: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation structure and benefits. So include Benefits and maybe Pay? But Pay section would be thin. The rules: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here it says "competitive and fair compensation structure..." but no numbers. That might be considered filler? However, it's actual content from the posting. I think include a "Compensation" or "Pay" section with that description. But the rules say "Prefer a few substantive sections over many thin ones." Could combine into "Total Rewards" section. Also "Schedule flexibility is required for early mornings, evenings, weekends, holidays, and high-volume event periods." That's schedule info. Could create a "Schedule" section. Let's decide sections: 1. About the role (from A Day In The Life) 2. Responsibilities (from As a Mgr, Hospitality You Will) 3. Requirements (education, experience) 4. Qualifications (skills list) 5. Physical Requirements 6. Travel Requirements 7. Benefits (from Why Join Us and Total Rewards) 8. Compensation (from Total Rewards) 9. Schedule (from the line in responsibilities) But maybe combine Physical and Travel into "Requirements" or separate. The rules: include a section ONLY when the posting has real, specific content. Physical and Travel are specific. Also "Why Join Us" is like a benefits/culture section. Could be "Why Join Us" heading? The rules say use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So "Why Join Us" is not in the example list, but we can use it if it's a heading in the posting. However, the rules say "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but prefer those. I'll map "Why Join Us" to "Benefits" or keep as "Why Join Us"? The content is about career growth, culture, benefits. Could be "Benefits" but also includes culture. Might create a "Why Join Us" section. But the rules: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can use other headings. I'll structure as: - About the Role - Responsibilities - Requirements - Qualifications - Physical Requirements - Travel Requirements - Benefits - Compensation - Schedule But that's many sections. Some are thin. Let's see content. "About the Role": from "A Day In The Life" - a paragraph describing the role. Good. "Responsibilities": list of 13 bullet points. Good. "Requirements": education and experience. Two bullet points: Bachelor's degree, 6-8 years experience. Good. "Qualifications": the list of required skills (Strong people leadership, Extensive knowledge, Exceptional discretion, etc.) - 7 bullet points. Good. "Physical Requirements": paragraph with details. Good. "Travel Requirements": paragraph. Good. "Benefits": from "Why Join Us" bullet points and "Total Rewards" benefits description. Could combine. "Compensation": from "Total Rewards" compensation description. One paragraph. "Schedule": one sentence from responsibilities: "Primarily campus, office, meeting, and event environments with frequent onsite activity. Schedule flexibility is required for early mornings, evenings, weekends, holidays, and high-volume event periods." That's specific. Now, the "Living Our Values" paragraph is generic boilerplate. Remove. "Join Us" EEO boilerplate. Remove. Also "DL NUMBER - Driver License, Valid and in State" - that's a requirement. Should be included in Requirements or Qualifications. It's a specific requirement. I'll add as a bullet in Requirements. Now, write HTML. Use

for headings. Use

• for lists. Use

  for prose. No markdown code fences. Just HTML fragment. Let's craft. First, About the Role:

  About the Role

  The Hospitality Manager leads hospitality and guest-service operations for associates, executives, visitors, and affiliated Friedkin companies. Reporting to the Director, Signature Experiences, this role establishes and delivers consistent white-glove hospitality standards across executive meetings, campus events, internal programs, VIP visits, and corporate events. The Manager leads the Hospitality team, managing the team's service calendar and resources, and partners across the enterprise to ensure every interaction is thoughtful, efficient, welcoming, and aligned with the Signature Experiences vision.

  Responsibilities:

  Responsibilities

  • Lead, coach, schedule, and develop the Hospitality team; establish service standards, operating procedures, coverage expectations, and performance goals.
  • Own hospitality operations for executive meetings, VIP visits, internal meetings, campus events, corporate events, and other high-touch guest experiences.
  • Establish consistent white-glove service standards for reception, greeting, credentialing, catering, meeting-room readiness, signage, amenities, gifting, guest communications, and issue resolution.
  • Manage the master hospitality and campus event calendar, resource allocation, staffing plans, event priorities, and escalation protocols.
  • Partner with the Director and Experiences team to integrate hospitality into signature events and ensure a seamless attendee journey across all touchpoints.
  • Serve as a trusted partner to executives and internal stakeholders, translating requests into clear service plans while anticipating needs and recommending solutions.
  • Oversee catering, facilities coordination, internal event setup, décor, signage, vendors, supplies, and service partners; negotiate and manage vendor relationships and contracts within delegated authority.
  • Oversee purchasing, department budgets, forecasts, invoices, expense reporting, vendor setup, and cost controls for hospitality operations.
  • Coordinate closely with Facilities, Security, IT, Mail Services, Risk, Compliance, Finance, Procurement, Communications, and other internal partners.
  • Lead service recovery and resolution of guest concerns; maintain composure and discretion with executives, VIPs, customers, and confidential matters.
  • Establish KPIs and feedback mechanisms, review service performance, and implement process improvements that increase consistency, efficiency, and guest satisfaction.
  • Serve as onsite hospitality lead for major campus or executive programs and provide operational leadership during high-volume periods.
  • Primarily campus, office, meeting, and event environments with frequent onsite activity. Schedule flexibility is required for early mornings, evenings, weekends, holidays, and high-volume event periods.
  Note: The last bullet includes schedule info. Could separate schedule. But it's part of responsibilities. I'll keep as is, but also create a Schedule section? The rules: include a section ONLY when the posting has real, specific content. The schedule info is one sentence. Could be a Schedule section. But it's already in responsibilities. Might duplicate. I'll create a separate Schedule section with that sentence. But the last bullet is part of the "As a Mgr, Hospitality You Will" list. It's a responsibility about environment and schedule. I'll keep it in responsibilities and also create a Schedule section? That would duplicate. Better to move that sentence to Schedule section and remove from responsibilities. However, the rule: preserve ALL substantive information; do NOT invent or summarize away detail. So I must include it. I can include it in both? No, duplication not good. I'll include it in responsibilities as a bullet, and also create a Schedule section with that same info? That's duplication. I'll create a Schedule section and not include that bullet in responsibilities? But the bullet is part of the list. The list includes it as a duty. I'll keep it in responsibilities and not create a separate Schedule section, because it's already covered. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states schedule flexibility requirement. That's a schedule detail. Could be a Schedule section. But it's minor. I'll create a Schedule section with that sentence. Let's see: The responsibilities list has 13 bullets. The last bullet is about environment and schedule. I'll keep it in responsibilities, and also add a Schedule section? That would be duplicate. I'll remove that bullet from responsibilities and put in Schedule section. But the bullet is part of the "You Will" list. It's a responsibility. I think it's fine to have a Schedule section with that info, and keep the bullet but maybe rephrase. However, the rule: preserve ALL substantive information. So I must include that sentence. I'll include it in Schedule section and also keep in responsibilities? That's duplicate. I'll include it only in Schedule section and remove from responsibilities list. But the responsibilities list is from the posting; removing a bullet might be considered summarizing away detail. The bullet is a responsibility: "Prim