Banquet & Catering Server
` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use `- ` for any list of duties/requirements/benefits
- Use `
` for prose
- Do NOT repeat the job title as a heading (page already shows it)
- Do NOT put Job ID / requisition numbers as headings - fold minor metadata into a short `
` or drop it
- Preserve ALL substantive information; do NOT invent or summarize away detail
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
- IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them
- Prefer a few substantive sections over many thin ones
- Output ONLY the HTML fragment — no `/`, no markdown code fences
2. **Analyze the Input Job Posting:**
Let me extract the content from the provided text. It's a job posting for "Banquet & Catering Server Hampton Roads, VA Part-Time | Flexible Event Schedule $15.00- $17.00 an hour | Weekly Pay Givens Talent is hiring Banquet & Catering Servers..."
Let me parse it carefully:
- Title/Role: Banquet & Catering Server (but I shouldn't output this as a heading)
- Location: Hampton Roads, VA
- Pay: $15.00- $17.00 an hour (also says "Starting pay of $16.00 per hour Weekly pay")
- Job Type: Part-Time / Event-Based
- Schedule: Flexible part-time scheduling, evening and weekend events
- About the role/company: Givens Talent is hiring for upcoming weddings, private parties, corporate events, banquets, and other special events throughout Hampton Roads. If you enjoy working in a busy event environment, meeting new people, and having a schedule that can vary from week to week, this is a great opportunity to pick up part-time event work. Events are held at a variety of venues throughout the area, so no two shifts are exactly the same.
- Responsibilities (What You'll Be Doing):
* Assist with setting up tables, dining areas, buffets, and beverage stations before events
* Greet guests and provide friendly, professional service
* Serve plated meals, buffet service, hors d'oeuvres, and beverages depending on the event
* Keep tables and guest areas clean and organized throughout service
* Clear plates, glassware, and other items during and after events
* Restock beverages, utensils, napkins, and other event supplies
* Assist catering and event staff as needed throughout the shift
* Help with breakdown and cleanup at the end of events
* Follow food safety, sanitation, and venue guidelines
* Work as part of a team to keep events running smoothly
- Requirements/Qualifications (What We're Looking For):
* Previous banquet, catering, restaurant, hospitality, or customer service experience is preferred, but not required
* Friendly and professional when interacting with guests
* Reliable and able to arrive on time for scheduled events
* Comfortable working in a fast-paced environment
* Able to take direction and work well with different teams
* Available for evening and weekend events
* Professional appearance appropriate for banquet and catered events
- Physical Requirements:
* This is an active position that requires standing and walking for most of the shift. Servers must be able to bend, reach, carry trays and event supplies, and lift up to 30 pounds.
- Why Work Events with Givens Talent? (Benefits):
* Starting pay of $16.00 per hour
* Weekly pay
* Flexible part-time scheduling
* Pick up event shifts based on availability
* Work at a variety of venues and special events
* Opportunities for additional event assignments
* Great opportunity for someone looking to earn extra income around another job, school, or other commitments
- Job Type: Part-Time / Event-Based
Now, I need to map this to the requested structure using `
` for section headings. The allowed headings examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Let's decide on sections that have real, specific content:
- About the role (or "About the Role" / "About the Position") - has content
- Responsibilities - has content (What You'll Be Doing)
- Requirements - has content (What We're Looking For) - but note: there's also "Physical Requirements" which could be part of Requirements or a separate section. I'll combine or handle carefully.
- Benefits - has content (Why Work Events with Givens Talent?) - but pay is also stated separately. The rules say: never create Pay/Schedule/Benefits sections unless the posting actually states them. They are stated. But I need to be careful not to create thin sections. I'll combine Benefits and Pay maybe, or handle Pay as a separate `
` within Benefits or separate. Let's see.
- Schedule - has content (Flexible part-time scheduling, evening and weekend events)
- Qualifications - could be merged with Requirements. The examples list "Requirements, Qualifications" as possible headings. I'll probably use one or the other, or combine. Let's read carefully: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists them as examples. I should use what fits. I'll likely use: About the role, Responsibilities, Requirements, Benefits, Schedule. Or maybe Skills? There's no explicit "Skills" section, but requirements could be considered skills. I'll stick to what's substantively present.
Let's re-read the IMPORTANT rule: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones."
So I should only include sections that have real content. Pay is stated: "$15.00- $17.00 an hour" and "Starting pay of $16.00 per hour Weekly pay". Schedule is stated: "Flexible part-time scheduling", "evening and weekend events". Benefits are stated: "Starting pay of $16.00 per hour Weekly pay Flexible part-time scheduling Pick up event shifts based on availability Work at a variety of venues and special events Opportunities for additional event assignments Great opportunity for someone looking to earn extra income around another job, school, or other commitments". But some of these overlap with Pay and Schedule. I need to decide how to structure without duplicating or creating thin sections.
Let me map out a structure that makes sense semantically and follows the rules:
Possible sections:
- About the role (or "About the Position")
- Responsibilities (What You'll Be Doing)
- Requirements (What We're Looking For + Physical Requirements) - but I'll keep Physical Requirements as part of Requirements or separate if it has specific content. It does have specific content.
- Benefits - but careful: the "Why Work Events with Givens Talent?" section lists benefits, but some are pay/schedule related. I could make a Benefits section with the non-pay/non-schedule benefits, or include them all and have Pay/Schedule as separate sections. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." They are stated. But I need to avoid thin sections. I'll probably combine Pay and Benefits into one section maybe, or do Benefits with the specific benefit descriptions, and Pay as a concise statement. Let's see.
Actually, re-reading: "Prefer a few substantive sections over many thin ones." So I should merge where sensible.
Let me list what content is present and group logically:
1. About the role/company: "Givens Talent is hiring Banquet & Catering Servers for upcoming weddings, private parties, corporate events, banquets, and other special events throughout Hampton Roads. If you enjoy working in a busy event environment, meeting new people, and having a schedule that can vary from week to week, this is a great opportunity to pick up part-time event work. Events are held at a variety of venues throughout the area, so no two shifts are exactly the same."
2. Responsibilities: "What You'll Be Doing" list of 10 items.
3. Requirements/Qualifications: "What We're Looking For" list of 7 items, plus "Physical Requirements" with specific details.
4. Pay: "$15.00- $17.00 an hour" and "Starting pay of $16.00 per hour Weekly pay"
5. Schedule: "Flexible part-time scheduling", "evening and weekend events", "schedule that can vary from week to week"
6. Benefits/Why Work Here: "Why Work Events with Givens Talent?" list of 6 items, but some overlap with Pay/Schedule. I could either merge Benefits into a general section, or omit a separate Benefits section if it's thin. But there are genuine benefits listed beyond pay/schedule: "Work at a variety of venues and special events", "Opportunities for additional event assignments", "Great opportunity for someone looking to earn extra income around another job, school, or other commitments". These are substantive.
Let me think about the heading names allowed: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I can use any of these as ``. I need to pick a set that fits the content and avoids empty sections.
Proposed structure:
- `About the role
` + paragraph
- `Responsibilities
` + `- ` list
- `
Requirements
` + `- ` list (combining "What We're Looking For" and "Physical Requirements" into one requirements section, or I could keep Physical Requirements as a sub-list or separate paragraph within Requirements. Since the rules say use `
- ` for any list of duties/requirements/benefits, and `
` for prose, I'll make the physical requirements a `
` or include in the list. Let's see: "Physical Requirements This is an active position that requires standing and walking for most of the shift. Servers must be able to bend, reach, carry trays and event supplies, and lift up to 30 pounds." This is prose with specific details, so `
` is fine. I'll include it as a `
` after the requirements list, or merge the list items and add the physical prose separately.)
- `
Pay
` + `` with pay info. But rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. I'll include Pay as a section with the specific hourly range and weekly pay.
- `
Schedule
` + `` with schedule flexibility, evening/weekend
` for prose - Do NOT repeat the job title as a heading (page already shows it) - Do NOT put Job ID / requisition numbers as headings - fold minor metadata into a short `
` or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Analyze the Input Job Posting:** Let me extract the content from the provided text. It's a job posting for "Banquet & Catering Server Hampton Roads, VA Part-Time | Flexible Event Schedule $15.00- $17.00 an hour | Weekly Pay Givens Talent is hiring Banquet & Catering Servers..." Let me parse it carefully: - Title/Role: Banquet & Catering Server (but I shouldn't output this as a heading) - Location: Hampton Roads, VA - Pay: $15.00- $17.00 an hour (also says "Starting pay of $16.00 per hour Weekly pay") - Job Type: Part-Time / Event-Based - Schedule: Flexible part-time scheduling, evening and weekend events - About the role/company: Givens Talent is hiring for upcoming weddings, private parties, corporate events, banquets, and other special events throughout Hampton Roads. If you enjoy working in a busy event environment, meeting new people, and having a schedule that can vary from week to week, this is a great opportunity to pick up part-time event work. Events are held at a variety of venues throughout the area, so no two shifts are exactly the same. - Responsibilities (What You'll Be Doing): * Assist with setting up tables, dining areas, buffets, and beverage stations before events * Greet guests and provide friendly, professional service * Serve plated meals, buffet service, hors d'oeuvres, and beverages depending on the event * Keep tables and guest areas clean and organized throughout service * Clear plates, glassware, and other items during and after events * Restock beverages, utensils, napkins, and other event supplies * Assist catering and event staff as needed throughout the shift * Help with breakdown and cleanup at the end of events * Follow food safety, sanitation, and venue guidelines * Work as part of a team to keep events running smoothly - Requirements/Qualifications (What We're Looking For): * Previous banquet, catering, restaurant, hospitality, or customer service experience is preferred, but not required * Friendly and professional when interacting with guests * Reliable and able to arrive on time for scheduled events * Comfortable working in a fast-paced environment * Able to take direction and work well with different teams * Available for evening and weekend events * Professional appearance appropriate for banquet and catered events - Physical Requirements: * This is an active position that requires standing and walking for most of the shift. Servers must be able to bend, reach, carry trays and event supplies, and lift up to 30 pounds. - Why Work Events with Givens Talent? (Benefits): * Starting pay of $16.00 per hour * Weekly pay * Flexible part-time scheduling * Pick up event shifts based on availability * Work at a variety of venues and special events * Opportunities for additional event assignments * Great opportunity for someone looking to earn extra income around another job, school, or other commitments - Job Type: Part-Time / Event-Based Now, I need to map this to the requested structure using `
` for section headings. The allowed headings examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Let's decide on sections that have real, specific content: - About the role (or "About the Role" / "About the Position") - has content - Responsibilities - has content (What You'll Be Doing) - Requirements - has content (What We're Looking For) - but note: there's also "Physical Requirements" which could be part of Requirements or a separate section. I'll combine or handle carefully. - Benefits - has content (Why Work Events with Givens Talent?) - but pay is also stated separately. The rules say: never create Pay/Schedule/Benefits sections unless the posting actually states them. They are stated. But I need to be careful not to create thin sections. I'll combine Benefits and Pay maybe, or handle Pay as a separate `
` within Benefits or separate. Let's see. - Schedule - has content (Flexible part-time scheduling, evening and weekend events) - Qualifications - could be merged with Requirements. The examples list "Requirements, Qualifications" as possible headings. I'll probably use one or the other, or combine. Let's read carefully: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists them as examples. I should use what fits. I'll likely use: About the role, Responsibilities, Requirements, Benefits, Schedule. Or maybe Skills? There's no explicit "Skills" section, but requirements could be considered skills. I'll stick to what's substantively present.
Let's re-read the IMPORTANT rule: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones."
So I should only include sections that have real content. Pay is stated: "$15.00- $17.00 an hour" and "Starting pay of $16.00 per hour Weekly pay". Schedule is stated: "Flexible part-time scheduling", "evening and weekend events". Benefits are stated: "Starting pay of $16.00 per hour Weekly pay Flexible part-time scheduling Pick up event shifts based on availability Work at a variety of venues and special events Opportunities for additional event assignments Great opportunity for someone looking to earn extra income around another job, school, or other commitments". But some of these overlap with Pay and Schedule. I need to decide how to structure without duplicating or creating thin sections.
Let me map out a structure that makes sense semantically and follows the rules:
Possible sections:
- About the role (or "About the Position")
- Responsibilities (What You'll Be Doing)
- Requirements (What We're Looking For + Physical Requirements) - but I'll keep Physical Requirements as part of Requirements or separate if it has specific content. It does have specific content.
- Benefits - but careful: the "Why Work Events with Givens Talent?" section lists benefits, but some are pay/schedule related. I could make a Benefits section with the non-pay/non-schedule benefits, or include them all and have Pay/Schedule as separate sections. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." They are stated. But I need to avoid thin sections. I'll probably combine Pay and Benefits into one section maybe, or do Benefits with the specific benefit descriptions, and Pay as a concise statement. Let's see.
Actually, re-reading: "Prefer a few substantive sections over many thin ones." So I should merge where sensible.
Let me list what content is present and group logically:
1. About the role/company: "Givens Talent is hiring Banquet & Catering Servers for upcoming weddings, private parties, corporate events, banquets, and other special events throughout Hampton Roads. If you enjoy working in a busy event environment, meeting new people, and having a schedule that can vary from week to week, this is a great opportunity to pick up part-time event work. Events are held at a variety of venues throughout the area, so no two shifts are exactly the same."
2. Responsibilities: "What You'll Be Doing" list of 10 items.
3. Requirements/Qualifications: "What We're Looking For" list of 7 items, plus "Physical Requirements" with specific details.
4. Pay: "$15.00- $17.00 an hour" and "Starting pay of $16.00 per hour Weekly pay"
5. Schedule: "Flexible part-time scheduling", "evening and weekend events", "schedule that can vary from week to week"
6. Benefits/Why Work Here: "Why Work Events with Givens Talent?" list of 6 items, but some overlap with Pay/Schedule. I could either merge Benefits into a general section, or omit a separate Benefits section if it's thin. But there are genuine benefits listed beyond pay/schedule: "Work at a variety of venues and special events", "Opportunities for additional event assignments", "Great opportunity for someone looking to earn extra income around another job, school, or other commitments". These are substantive.
Let me think about the heading names allowed: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I can use any of these as ``. I need to pick a set that fits the content and avoids empty sections.
Proposed structure:
- `About the role
` + paragraph
- `Responsibilities
` + `- ` list
- `
Requirements
` + `- ` list (combining "What We're Looking For" and "Physical Requirements" into one requirements section, or I could keep Physical Requirements as a sub-list or separate paragraph within Requirements. Since the rules say use `
- ` for any list of duties/requirements/benefits, and `
` for prose, I'll make the physical requirements a `
` or include in the list. Let's see: "Physical Requirements This is an active position that requires standing and walking for most of the shift. Servers must be able to bend, reach, carry trays and event supplies, and lift up to 30 pounds." This is prose with specific details, so `
` is fine. I'll include it as a `
` after the requirements list, or merge the list items and add the physical prose separately.)
- `
Pay
` + `` with pay info. But rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. I'll include Pay as a section with the specific hourly range and weekly pay.
- `
Schedule
` + `` with schedule flexibility, evening/weekend
About the role
` + paragraph - `Responsibilities
` + `- ` list
- `
Requirements
` + `- ` list (combining "What We're Looking For" and "Physical Requirements" into one requirements section, or I could keep Physical Requirements as a sub-list or separate paragraph within Requirements. Since the rules say use `
- ` for any list of duties/requirements/benefits, and `
` for prose, I'll make the physical requirements a `
` or include in the list. Let's see: "Physical Requirements This is an active position that requires standing and walking for most of the shift. Servers must be able to bend, reach, carry trays and event supplies, and lift up to 30 pounds." This is prose with specific details, so `
` is fine. I'll include it as a `
` after the requirements list, or merge the list items and add the physical prose separately.) - `
Pay
` + `` with pay info. But rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. I'll include Pay as a section with the specific hourly range and weekly pay. - `
Schedule
` + `` with schedule flexibility, evening/weekend
- ` for any list of duties/requirements/benefits, and `
- ` list (combining "What We're Looking For" and "Physical Requirements" into one requirements section, or I could keep Physical Requirements as a sub-list or separate paragraph within Requirements. Since the rules say use `