Banquet Chef

We need to output HTML fragment with sections: About the role? Actually we have "About Us" but we shouldn't repeat job title. Use headings for sections: About the role, Responsibilities, Requirements (or Qualifications, Skills), Benefits, Pay, Schedule. We need to include only sections with real content. From posting: - About Us: description of Suser Restaurant Group. Could be "About the company" but heading "About the role"? Actually "About Us" is about company. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" heading for the description of the role? But we have "The Role" paragraph. Could use "About the role". Also we have "What We're Looking For" which is requirements/qualifications/skills. Could combine into Requirements or Skills. We have "We Offer: benefits, pay, flexible scheduling. So we have Pay, Benefits, Schedule. We need to preserve all substantive info. Remove boilerplate: no cookie/navigation/legal/EEO etc. There's none. We need to output only HTML fragment, no /, no markdown fences. Structure:

About the role

... (The Role paragraph)

Responsibilities

• ... each responsibility line

Requirements

• ... each requirement line from "What We're Looking For"

Benefits

• ... each benefit from "We Offer": Competitive hourly pay, Employee discounts, Flexible scheduling, Real opportunities for growth and advancement, A supportive team culture..., The opportunity to be part of a growing, multi-concept restaurant group...

We also have Pay and Schedule sections: "Competitive hourly pay" is pay; "Flexible scheduling" is schedule. Since we already have them in Benefits, but instruction says prefer few substantive sections over many thin ones. Could combine pay and schedule into Benefits? But they said include a section ONLY when posting has real specific content for it. We have pay and schedule content; we could make separate Pay and Schedule sections, but that would be thin. Better to keep them under Benefits? However they said use headings for Benefits, Pay, Schedule. If we put pay and schedule under Benefits, we are not following the heading list but it's not prohibited; they said use those headings for sections. It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we can use those headings if we have content. It doesn't forbid putting pay and schedule under Benefits, but better to follow the guidance: create Pay and Schedule sections if we have content. However they also say "Prefer a few substantive sections over many thin ones." So maybe combine Pay and Schedule into Benefits? But they'd be thin if separate. Let's think: Pay: "Competitive hourly pay". Schedule: "Flexible scheduling, including evenings, weekends, and holidays — as events frequently occur outside of traditional business hours." Actually flexible scheduling is mentioned under What We're Looking For? Wait it's under "What We're Looking For": "Flexible availability, including evenings, weekends, and holidays — as events frequently occur outside of traditional business hours." That's a requirement, not a benefit. The "We Offer" includes "Flexible scheduling". So we have both a requirement (flexible availability) and a benefit (flexible scheduling). Slight duplication but okay. Thus we have Pay: Competitive hourly pay. Schedule: Flexible scheduling. Benefits: Employee discounts, Real opportunities for growth and advancement, A supportive team culture..., The opportunity to be part of a growing, multi-concept restaurant group... We could make three sections: Pay, Schedule, Benefits. That's three thin sections but each has at least one substantive item. The instruction says prefer a few substantive sections over many thin ones. Having three thin sections might be okay if each has content. But we could also combine Pay and Schedule into Benefits? However they'd lose specificity. I'd follow the instruction to include sections only when posting has real specific content for it. We have real content for Pay, Schedule, Benefits. So we should include them. Thus sections: About the role, Responsibilities, Requirements (or Qualifications/Skills), Pay, Schedule, Benefits. We need to decide what to call the requirements section. Could be "Requirements". We'll list all items from "What We're Looking For". Also we might include "Skills" but we can just use Requirements. Now we need to extract content precisely. About the role: The paragraph under "The Role": "The Banquet Chef is a key culinary leader at Union 212 Banquet Hall, responsible for planning, preparing, and executing exceptional food programs for a wide variety of events — from intimate gatherings to large-scale celebrations. This role requires a highly organized, experienced culinary professional who thrives in a high-volume, event-driven environment and takes pride in delivering a consistently outstanding dining experience to every guest at every event. The ideal candidate combines strong technical culinary skills with exceptional planning ability, a keen eye for detail, and a genuine passion for hospitality." We'll put that in

. Responsibilities: list each bullet after "Responsibilities". Let's extract: - Plan, prepare, and execute all food production for banquet events at Union 212 Banquet Hall, ensuring the highest standards of quality, consistency, and presentation for every event - Collaborate with event coordinators, sales staff, and clients to develop customized banquet menus that meet the vision, dietary needs, and budget of each event - Oversee all aspects of banquet kitchen operations, from prep through service and breakdown, ensuring smooth and efficient execution at every stage - Lead, coach, and develop the banquet kitchen team, fostering a culture of excellence, accountability, and continuous growth - Create detailed production schedules, prep lists, and timelines for each event to ensure all food is prepared and ready for service on time - Conduct pre-event walkthroughs and tastings to ensure all menu items meet established standards before service begins - Manage food costs, portion control, and waste reduction across all banquet events, ensuring profitability without compromising quality - Oversee ordering, receiving, and inventory management for all banquet events, ensuring the freshest ingredients are always on hand - Ensure strict compliance with all health codes, food safety regulations, sanitation standards, and company policies at all times - Coordinate closely with front of house banquet staff and event coordinators to ensure seamless communication and flawless event execution - Manage kitchen scheduling for banquet events, ensuring adequate staffing while maintaining labor cost targets - Monitor and maintain all banquet kitchen equipment, reporting any issues promptly and ensuring proper preventative maintenance is performed - Assist the Executive Chef with menu development, special events, and catering initiatives as needed - Represent Suser Restaurant Group with professionalism and passion at all events, serving as a culinary ambassador for the Union 212 Banquet Hall brand We'll put each as

. Requirements: from "What We're Looking For". Let's list: - 3+ years of culinary experience in a banquet, catering, hotel, or high-volume event environment, with at least 1-2 years in a supervisory or lead culinary role - Strong technical culinary skills with a thorough knowledge of cooking methods, techniques, ingredients, and large-scale food production - Proven ability to plan, organize, and execute high-volume banquet events with precision and consistency - Experience developing and executing customized banquet menus for a wide variety of events and dietary needs - Solid understanding of food and labor cost management, inventory control, and ordering - Strong leadership and team development skills, with the ability to motivate and lead a kitchen team in a fast-paced, event-driven environment - Exceptional organizational and time management skills, with the ability to manage multiple events and deadlines simultaneously - ServSafe certification preferred - Excellent communication and interpersonal skills, with the ability to work closely with clients, event coordinators, and front of house staff - Flexible availability, including evenings, weekends, and holidays — as events frequently occur outside of traditional business hours - Ability to stand for extended periods and lift up to 50 pounds regularly - A genuine passion for food, hospitality, and creating memorable experiences for every guest We'll put each as

. Pay: "Competitive hourly pay". We'll put

Competitive hourly pay

under

Pay

. Schedule: "Flexible scheduling". Actually the benefit says "Flexible scheduling". We'll put

Flexible scheduling

under

Schedule

. However we also have flexible availability as a requirement; but that's separate. Benefits: list from "We Offer": Competitive hourly pay (already used), Employee discounts, Flexible scheduling (already used), Real opportunities for growth and advancement, A supportive team culture built on respect, accountability, and collaboration, The opportunity to be part of a growing, multi-concept restaurant group with a strong presence in Oakland County. We should avoid duplicating Competitive hourly pay and Flexible scheduling if we already have separate sections. To avoid duplication, we can omit them from Benefits list, or we can keep them but note duplication. Better to avoid duplication: Benefits section will include Employee discounts, Real opportunities for growth and advancement, A supportive team culture..., The opportunity to be part of a growing, multi-concept restaurant group... Thus Benefits

with those four items. Now ensure we don't include any boilerplate like "This Is More Than a Job..." etc. That's promotional but still substantive? It's more like marketing fluff. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That paragraph is substantive? It's more like a motivational statement. It might be considered substantive but could be considered boilerplate? It's not cookie/navigation/legal/EEO etc. It's part of the posting. Should we include? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This paragraph is not those. It's a motivational closing. I'd include it maybe under About the role? Or as a separate section? There's no heading for it. Could add a

after About the role? But we already used About the role for the role description. We could add another

after that paragraph to include the motivational statement. However the instruction says prefer a few substantive sections over many thin ones. Adding a separate paragraph might be okay. But we already have About the role section with the role description. We could append the motivational statement as another

within same section. That would preserve info. Thus About the role

About the role

The Banquet Chef ...

This Is More Than a Job. It's an opportunity to be the culinary force behind some of the most memorable moments in people's lives — weddings, celebrations, corporate events, and everything in between. At Union 212 Banquet Hall, every event is a chance to showcase your craft, lead your team, and deliver an experience that guests will talk about long after the night is over. If you're a skilled culinary professional who thrives in an event-driven environment and is ready to take ownership of a world-class banquet program, we want to hear from you. Join our team at Suser Restaurant Group — apply today!

But note the last sentence includes "apply today!" which is application instruction. We should remove application instructions. So we need to cut that sentence. The instruction: remove application instructions. So we should not include "Join our team at Suser Restaurant Group — apply today!" That's an application instruction. So we should exclude that sentence. Also maybe "If you're a skilled culinary professional..." is not an instruction, it's encouragement. That's okay. We'll keep up to "we want to hear from you." That's not an instruction to apply, it's an invitation. Might be okay. But safer