Management Development Program - Culinary
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We need to extract substantive info. From posting: Company Description: Auberge Collection description. Job Description: description of MDP program: 12-month on property paid training, 80% work experience 20% professional development, two phases, focus areas Food & Beverage, Culinary, Rooms. Candidates select path and location. Upon completion placed into management role (based on availability and willingness to relocate). Note: exclusively for students or graduates from accredited hospitality school within US. Program Benefits: list: Fast-track management development, Promotion to management level upon program completion, Support role rotations throughout the property, guided by learning objectives for each department, Ongoing career growth with a rapidly expanding luxury hotel company, Monthly MDP Meetups with fellow MDPs across the collection, Mentorship opportunities with home office leaders, Discounted rates through the Team Member Stay Program, Task force opportunities and assignments abroad, Housing available at participating locations, Relocation stipend for approved expenses, Health insurance, 401(k) match, Paid holidays and time off, Overtime pay eligibility, Referral bonus. Qualifications: The Management Development Program is specifically tailored for students or graduates from accredited hospitality schools within the United States. While prior experience in hospitality is preferred, the following qualities are essential: A demonstrated passion for the hospitality industry and a commitment to delivering exceptional guest experiences. Strong communication and interpersonal skills. A proven willingness to learn, coupled with curiosity, resilience, and self-motivation. The ability to excel in a fast-paced environment. A keen interest in leadership and career advancement. Offer letters to be issued within 2-4 weeks of completing the interview process. Additional Information: About Auberge Collection (duplicate of company description). About Friedkin (irrelevant? Might be considered boilerplate? It's not EEO but it's extra company info; but we should keep substantive info? It's about Friedkin parent company. Might be considered not boilerplate but could be kept? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Friedkin section is not boilerplate but is extra info about parent company. It might be considered relevant? Probably we can keep as part of "About the company" but we already have Company Description. It's somewhat duplicated? Not exactly duplicate but similar. Might be considered extra but not required. The instruction: Prefer a few substantive sections over many thin ones. We could combine company description into a section like "About the role"? Actually "About the role" is for role description. Could use "About the role" for job description. "Qualifications" for qualifications. "Benefits" for benefits. "Responsibilities" maybe not present; we have program description includes responsibilities? Could treat as responsibilities. "Requirements" maybe same as qualifications. We need to decide which headings to use based on content. We have: - Job Description: description of program (could be "About the role" or "Responsibilities"). - Program Benefits: list -> Benefits section. - Qualifications: list -> Qualifications section (or Requirements). Also includes "Offer letters to be issued within 2-4 weeks..." maybe part of qualifications or additional info. - Company Description: could be "About the role"? Actually "About the role" is about the job, not company. Could use "About the role" for job description, and maybe "About the company" not a prescribed heading; we only allowed those headings. So we might omit company description or fold into a short
under maybe "About the role"? But we shouldn't invent headings not allowed. We could include a
without heading? 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 those for section headings. Likely we should only use those headings when we have content. We can also have
without heading? Probably yes, but better to structure with headings. We could treat company description as part of "About the role"? Not ideal. Maybe we can omit company description as it's not required? But we must preserve ALL substantive information; cannot omit. So we need to include it somewhere. Could put it under a heading like "About the role"? But that heading is for role description, not company. However we could still put company description there; it's still substantive. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive list. So we could also use other headings if needed, but better to stick to given ones. Could we use "About the role" to include both role and company? Might be okay. Alternatively, we could create a heading "About the company" but not in list; risk being considered not following instruction. Safer to use given headings only. Thus we need to map content: - About the role: could include job description (MDP program details). Also maybe include company description? Might be okay. - Responsibilities: maybe not distinct; we could treat program phases as responsibilities. - Requirements: maybe qualifications. - Qualifications: maybe same as requirements; but we need to avoid duplication. We could have sections: About the role (program overview), Responsibilities (phases and focus areas), Qualifications (essential qualities), Benefits (list). Possibly also Skills (communication etc) but that's covered in qualifications. We must not create Pay or Schedule sections because not specified. We must not repeat job title. We must not include boilerplate like EEO etc. We must remove duplicated lines: there is duplicate company description later (About Auberge Collection) and also About Friedkin. The Friedkin section is not duplicate but maybe considered extra; we could keep it? It's substantive about parent company. Might be okay to keep under About the role? But it's not about role. Could we include a short
without heading for that? Probably okay. But instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine everything into few sections: About the role (includes program description, company description, Friedkin info), Responsibilities (phases and focus areas), Qualifications (essential qualities + offer letter timeline), Benefits (list). That seems reasonable. Now we need to output HTML fragment only, no /, no markdown fences. We'll produce:
About the role
... content ...
Then maybeResponsibilities
- ...
Qualifications
- ...
Benefits
- ...
and then
or
- .
For About the role, we may have multiple paragraphs; we can combine into one
with sentences. But we need to preserve all info; we can use multiple
under same heading? The instruction: Use
for prose. It's okay to have multiple
under a heading. We'll do:
About the role
Auberge Collection is a portfolio of extraordinary hotels, resorts, safaris, residences, and private clubs. While each property is unique, all share a crafted approach to luxury and bring the soul of the locale to life through captivating design, exceptional cuisine, innovative wellbeing, and gracious yet unobtrusive service. With 39 one-of-a-kind hotels, resorts, safaris, and residences, Auberge invites guests to create