Lead Bellperson

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. We need to extract from posting. Let's parse the posting: Company Description: description of Goldener Hirsch, Auberge Collection. Job Description: "Take charge of hospitality as a Lead Bell , where your leadership will set the tone for exceptional guest service. Leading a team of bellmen, you'll orchestrate seamless arrivals and departures, ensuring each guest's journey begins and ends with a touch of warmth and efficiency. Supervise and lead the bell staff, providing guidance, training, and support to ensure efficient and courteous service.Assist guests with luggage, transportation, and other needs, ensuring a seamless and welcoming arrival and departure experience.Collaborate with other hotel departments to coordinate services for guests, including transportation, room assignments, and special requests.Conduct training sessions for bell staff, ensuring they are well-versed in customer service standards, safety procedures, and hotel policies.Handle guest concerns or issues related to bell services, finding effective solutions and ensuring a positive experience for guests." Qualifications: "A minimum of one-year experience as a Bellperson, preferably in a luxury environmentAbility to work a flexible schedule, including weekends and holidays, according to department needsValid License to operate a motor vehicle" Additional Information About Auberge Collection: description of Auberge Collection. About Friedkin: description. EEO boilerplate. We need to produce sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: Could be the Job Description paragraph that describes the role. So we can put that under About the role. - Responsibilities: Could be list of duties from the job description: supervising, assisting guests, collaborating, conducting training, handling concerns. Those are responsibilities. - Requirements: Could be qualifications? Actually qualifications are separate. Requirements might be things like experience, license, flexible schedule. But we have Qualifications section separate. The instructions say we can have both Requirements and Qualifications sections if content exists. We need to decide what goes where. Typically Requirements are mandatory items; Qualifications could be preferred. But we can split: Requirements: minimum one-year experience as a Bellperson, valid license, ability to work flexible schedule. Qualifications: preferably in a luxury environment (maybe that's a qualification). However the posting lumps them together. We could put all under Qualifications and leave Requirements empty (but we must not create empty sections). So we need to decide which sections have real content. We have content for About the role (job description overview). Responsibilities (list of duties). Qualifications (experience, license, flexible schedule, luxury environment). Skills? Not explicitly listed. Could infer skills like customer service, leadership, communication, but not explicitly stated. We should not invent. So we omit Skills. Benefits, Pay, Schedule: Not mentioned. The posting does not mention benefits, pay, or schedule specifics beyond flexible schedule mentioned under qualifications. But schedule is mentioned as "Ability to work a flexible schedule, including weekends and holidays, according to department needs". That's schedule info but it's a requirement/qualification. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedule flexibility, but that's a requirement, not a benefit. However we could still create a Schedule section if there is specific content about schedule. The posting mentions ability to work flexible schedule. That is schedule-related. Should we create a Schedule section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule flexibility, so we could include a Schedule section with that content. However we also have that content under Qualifications/Requirements. To avoid duplication, we need to preserve ALL substantive information; we can place it in Schedule section and not duplicate elsewhere. But we also need to keep other qualifications like experience and license. Those could go under Requirements or Qualifications. We need to decide a clean structure: About the role (overview), Responsibilities (list), Requirements (experience, license), Qualifications (luxury environment preference), Schedule (flexible schedule). Benefits, Pay omitted. But we must not create sections with filler like "commensurate with experience". We have real content. Let's extract exact sentences. About the role: Could be first sentence: "Take charge of hospitality as a Lead Bell , where your leadership will set the tone for exceptional guest service. Leading a team of bellmen, you'll orchestrate seamless arrivals and departures, ensuring each guest's journey begins and ends with a touch of warmth and efficiency." But that's also part of responsibilities. However we can treat that as overview. Responsibilities: list items: - Supervise and lead the bell staff, providing guidance, training, and support to ensure efficient and courteous service. - Assist guests with luggage, transportation, and other needs, ensuring a seamless and welcoming arrival and departure experience. - Collaborate with other hotel departments to coordinate services for guests, including transportation, room assignments, and special requests. - Conduct training sessions for bell staff, ensuring they are well-versed in customer service standards, safety procedures, and hotel policies. - Handle guest concerns or issues related to bell services, finding effective solutions and ensuring a positive experience for guests. We need to put each as

inside

. Requirements: maybe "A minimum of one-year experience as a Bellperson" and "Valid License to operate a motor vehicle". Also maybe "Ability to work a flexible schedule, including weekends and holidays, according to department needs" but that's schedule. Qualifications: "preferably in a luxury environment". That's a preference. Schedule: "Ability to work a flexible schedule, including weekends and holidays, according to department needs". We must not repeat content. So we assign each piece to one section. Let's craft:

About the role

Take charge of hospitality as a Lead Bell, where your leadership will set the tone for exceptional guest service. Leading a team of bellmen, you'll orchestrate seamless arrivals and departures, ensuring each guest's journey begins and ends with a touch of warmth and efficiency.

Responsibilities

• Supervise and lead the bell staff, providing guidance, training, and support to ensure efficient and courteous service.
• Assist guests with luggage, transportation, and other needs, ensuring a seamless and welcoming arrival and departure experience.
• Collaborate with other hotel departments to coordinate services for guests, including transportation, room assignments, and special requests.
• Conduct training sessions for bell staff, ensuring they are well-versed in customer service standards, safety procedures, and hotel policies.
• Handle guest concerns or issues related to bell services, finding effective solutions and ensuring a positive experience for guests.

Requirements

• A minimum of one-year experience as a Bellperson.
• Valid license to operate a motor vehicle.

Qualifications

• Preferably experience in a luxury environment.

Schedule

• Ability to work a flexible schedule, including weekends and holidays, according to department needs.
We should not include Benefits, Pay sections. Check for any other content: The company description etc is not part of job posting content we need to include? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The substantive information includes company description? The job posting includes company description at top. Should we include that? The sections we can use are limited to the headings list. There's no heading for Company Description. But we could incorporate that into About the role? However About the role is supposed to be about the role, not company. The instruction says we must not repeat the job title as a heading, and we must not put Job ID etc. It didn't say we must exclude company description. But we have limited headings; we could put company description under About the role? That might be misleading but maybe acceptable. However the instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exhaustive; we could add other headings? It says use

for section headings (e.g. About the role, ...). It implies we should use those headings for sections. It doesn't forbid other headings, but to follow the pattern we likely should only use those headings. The company description is substantive; we need to preserve it. Where to put? Could be a paragraph before the headings, not inside a heading. The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid having a

before headings. So we could include a

with company description before the sections. That would preserve all info. Thus we output:

Company Description Goldener Hirsch, Auberge Collection is an iconic luxury inn located in legendary Deer Valley, Utah. Designed in the spirit of an Austrian ski chalet, the intimate resort’s mid-mountain location offers direct access to over 200 perfectly groomed ski runs and 4,300 skiable acres as well as warm-weather outdoor pursuits. The 18 newly redesigned rooms and suites, including a Signature Suite that occupies the entire fourth floor, offer old-world charm with wood-burning fireplaces, vaulted ceilings and arched doorways; and, 40 residences, set in two new modern buildings designed by acclaimed architect Tom Kundig, are outfitted with full-service kitchens, contemporary living spaces and private balconies. Resort amenities include a luxurious lobby, adjacent Terrasse, exclusive private dining room, unique venues for private events and post-adventure wellness amenities such as customized massages in spa suites, breathtaking rooftop pool, infinity-edge hot tub and state-of-the-art fitness center. An award-winning restaurant skillfully marries Bavarian specialties with farm-fresh regional fare sourced from local Park City pastures, while the Antler Lounge, a chic gathering spot, comes alive in the evenings with après cocktails and live entertainment. Founded in 1992, the inn is owned by the philanthropic Eccles family who have been a part of the development of Utah’s ski region since the late 1800s. For more information: auberge.com/goldener-hirsch Follow Goldener Hirsch on Instagram @goldenerhirschauberge

Then the sections. We also have Additional Information About Auberge Collection and About Friedkin and EEO. Those are also substantive but maybe considered boilerplate? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The Additional Information About Auberge Collection and About Friedkin might be considered boilerplate? They are not EEO but they are extra company info. The instruction says remove legal/EEO boilerplate, but not necessarily remove all extra company description. However the company description we already included. The Additional Information about Auberge Collection and About Friedkin could be considered extra but not required. The instruction says preserve ALL substantive information. Are those substantive? They describe the parent companies. Might be considered substantive but maybe not needed for the job. However they are not boilerplate like EEO. But they are somewhat generic. The instruction didn't explicitly say to remove them. However they are not about the role. The sections we have are limited; we could add another

for that info. But we must not create sections with filler. We could just add a

after the sections containing that info. However that might be considered extra but okay. But the instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The Additional Information About Auberge Collection and About Friedkin are not EEO or