Bussers/Food Runners

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting. Posting content: - Title: NOW HIRING: BUSSERS! At Creole Cuisine Restaurant Concepts... - Intro: "We know that a smooth dining experience starts with a strong support team — and our Bussers are essential to keeping service running like clockwork. We’re looking for dependable, energetic team players who take pride in keeping our dining rooms clean, organized, and guest-ready." - Then "Why Join the Creole Cuisine Family?" bullet list: Medical, Dental, & Vision insurance available; Flexible Scheduling; Weekly Pay; Meal Discounts; Opportunity for Career Advancement (30+ locations - We love to promote from within!) - Then "What We’re Looking For": bullet list: A team-first attitude and strong attention to detail; Ability to stay on your feet and move quickly in a fast-paced environment; Reliable, professional, and ready to pitch in wherever needed; Flexible schedule with availability for nights, weekends, and holidays; Previous experience is a plus, but not required — we’ll train the right person! - Then "Be part of something bigger than just a job — join a team that values your effort and energy. Apply today to become a Busser with Creole Cuisine Restaurant Concepts!" (application instruction, we should remove) - Then "Company Introduction": paragraph about Royal House building history. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. Remove application instructions: "Apply today to become a Busser..." Remove "Be part of something bigger..." maybe keep as prose? It's motivational but not a list; could be part of About the role? Might be considered fluff but it's substantive? It's not a list; we can keep as paragraph under About the role. We need sections: About the role (intro description), Responsibilities (maybe duties), Requirements/Qualifications/Skills (maybe combine), Benefits (list), Pay (if mentioned), Schedule (if mentioned). The posting mentions Weekly Pay under Benefits? Actually "Weekly Pay" is listed under Why Join... So that is a benefit. Pay section: we have mention of Weekly Pay but not specific amount. The rule: do NOT create Pay/Schedule/Benefits sections unless the posting actually states them. It states Weekly Pay (but not amount). Is that enough to create a Pay section? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It states Weekly Pay (a benefit). So we could include Pay section with that info. However they also said "Prefer a few substantive sections over many thin ones." Might combine Pay into Benefits? But they have separate headings for Benefits, Pay, Schedule. We could put Weekly Pay under Benefits, but they said include a section ONLY when posting has real, specific content for it. If we put Weekly Pay under Benefits, we still need a Benefits section. That's fine. Pay section would be redundant if we already have Benefits. Better to not create a separate Pay section if we don't have specific pay amount; we can treat Weekly Pay as a benefit. So we will have Benefits section containing: Medical, Dental, & Vision insurance available; Flexible Scheduling; Weekly Pay; Meal Discounts; Opportunity for Career Advancement (30+ locations - We love to promote from within!). Schedule: The posting mentions Flexible schedule with availability for nights, weekends, and hours? Actually "Flexible schedule with availability for nights, weekends, and holidays" is under What We’re Looking For (requirements). That's a schedule requirement. So we could have a Schedule section with that detail. However the rule: include a section ONLY when posting has real, specific content for it. It does mention flexible schedule and availability for nights, weekends, holidays. That's specific enough. So we can create a Schedule section with that bullet. Responsibilities: The posting mentions duties: keeping dining rooms clean, organized, guest-ready; moving quickly; staying on feet; etc. Could be under Responsibilities. Requirements/Qualifications/Skills: The bullet list under What We’re Looking For includes team-first attitude, attention to detail, ability to stay on feet, reliable, professional, flexible schedule, previous experience plus. Those could be Requirements or Skills. We could combine into Requirements section. We need to avoid duplication. Let's decide sections: - About the role: intro paragraph about role importance and what we're looking for? Actually we have intro: "We know that a smooth dining experience starts with a strong support team — and our Bussers are essential to keeping service running like clockwork. We’re looking for dependable, energetic team players who take pride in keeping our dining rooms clean, organized, and guest-ready." That's about the role. - Responsibilities: maybe list duties: Keep dining rooms clean, organized, guest-ready; Ensure smooth service; etc. But the posting doesn't have explicit list of duties beyond that. Could combine with About the role. - Requirements: list of desired attributes: team-first attitude, attention to detail, ability to stay on feet and move quickly, reliable, professional, ready to pitch in, flexible schedule with availability for nights, weekends, holidays, previous experience a plus. - Benefits: list as above. - Company Introduction: maybe not a standard heading but we could include as About the company? Not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Company Introduction is not allowed; we could drop it or incorporate into About the role? The rule: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should use those headings for sections. It didn't forbid other headings, but likely they expect only those. Safer to stick to those. So we can omit Company Introduction or maybe treat as About the role? But it's about company history, not role. Could drop as not required? The rule: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep company intro info. If we cannot use a heading not in list, we could just put it as a

without heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot have other headings, but they gave examples. Probably they expect only those headings. However we need to preserve company intro. Could we put it under About the role as a paragraph? That would mix role description with company history, but still preserve info. Might be acceptable. Alternatively we could add a heading like "About the Company" but not in list; risk being considered not following instruction. Safer to embed as paragraph under About the role. Thus final HTML:

About the role

We know that a smooth dining experience starts with a strong support team — and our Bussers are essential to keeping service running like clockwork. We’re looking for dependable, energetic team players who take pride in keeping our dining rooms clean, organized, and guest-ready. The Royal House building has been a French Quarter icon for over 100 years. It was originally built as a family home, but the first floor was soon converted into a thriving restaurant, Tortorici’s. At a time when few Italian restaurants in New Orleans served anything more interesting than spaghetti, Tortorici’s stood out with its dishes of scampi, veal, and fish. It became one of the longest running restaurants in the city, alongside its fellow French Quarter icons— Galatoire’s, Arnaud’s, Antoine’s, and Broussard’s—until its ultimate closure after Hurricane Katrina. In 2008, the Ammari brothers bought the restaurant, restored it, and reopened it as Royal House. Over a decade later, we’re still serving up delicious Cajun and Creole cuisine to locals and tourists alike.

Responsibilities

• Keep dining rooms clean, organized, and guest‑ready.
• Maintain a smooth flow of service by clearing tables and resetting them promptly.
• Support servers and staff as needed to ensure a positive guest experience.

But we need to ensure we don't invent details not in posting. The posting didn't explicitly mention "Maintain a smooth flow of service by clearing tables and resetting them promptly." It said Bussers essential to keeping service running like clockwork, keep dining rooms clean, organized, guest-ready. That's it. We should not add extra duties not stated. So we should only list what is explicitly mentioned: keeping dining rooms clean, organized, guest-ready. Maybe also "take pride in keeping our dining rooms clean, organized, and guest-ready." That's the only duty. Could also include "support service running like clockwork" but that's vague. Better to keep just that one bullet. Thus Responsibilities:

• Keep dining rooms clean, organized, and guest‑ready.

But that seems thin. However we must not invent. Could combine About the role and Responsibilities? Maybe better to have only About the role and Requirements and Benefits and Schedule. Let's see. Requirements: list of attributes from What We’re Looking For. - A team-first attitude and strong attention to detail - Ability to stay on your feet and move quickly in a fast-paced environment - Reliable, professional, and ready to pitch in wherever needed - Flexible schedule with availability for nights, weekends, and holidays - Previous experience is a plus, but not required — we’ll train the right person! We could put schedule item under Requirements or Schedule section. Since we have Schedule section, we could move that bullet there. Thus Requirements: team-first attitude, attention to detail, ability to stay on feet and move quickly, reliable/professional/ready to pitch in, previous experience a plus. Schedule: Flexible schedule with availability for nights, weekends, and holidays. Benefits: as listed. Now About the role: include intro and company history. Check for any mention of Pay: Weekly Pay is a benefit; we already have Benefits section includes Weekly Pay. So no separate Pay section. Now ensure we don't include boilerplate like "Apply today..." removed. Now produce HTML fragment. We need to use

for each section heading. Use

• for lists. Use

  for prose. Let's craft:

  About the role

  We know that a smooth dining experience starts with a strong support team — and our Bussers are essential to keeping service running like clockwork. We’re looking for dependable, energetic team players who take pride in keeping our dining rooms clean, organized, and guest-ready. The Royal House building has been a French Quarter icon for over 100 years. It was originally built as a family home, but the first floor was soon converted into a thriving restaurant, Tortorici’s. At a time when few Italian restaurants in New Orleans served anything more interesting than spaghetti, Tortorici’s stood out with its dishes of scampi, veal, and fish. It became one of the longest running restaurants in the city, alongside its fellow French Quarter icons— Galatoire’s, Arnaud’s, Antoine’s, and Broussard’s—until its ultimate closure after Hurricane Katrina. In 2008, the Ammari brothers bought the restaurant, restored it, and reopened it as Royal House. Over a decade later, we’re still serving up delicious Cajun and Creole cuisine to locals and tourists alike.

  Responsibilities

  • Keep dining rooms clean, organized, and guest‑ready.

  Requirements

  • A team‑first attitude and strong attention to detail
  • Ability to stay on your