Beverage Server (Part Time)
` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule).
- Use `- ` for lists of duties/requirements/benefits.
- Use `
` for prose.
- Do NOT repeat the job title as a heading (already shown).
- 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. **Identify the Sections & Content from the Posting:**
- Title: Beverage Server (Part Time) - already at top, not to be repeated as heading.
- Requisition ID#: 5011 - metadata, fold into short `
` or drop. Rule: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." I'll fold it into a short `
` at the top or bottom, but not as a heading.
- Location: Dumfries, VA, US, 22026 - also metadata.
- Property: The Rose Gaming Resort - description.
- Pay Range: Hourly Rate: $9.00 + Tips - substantive, should be a section or part of Pay.
- Job Summary - substantive.
- Essential Duties And Responsibilities - substantive, will be `
- `.
- Required Skills And Abilities - substantive, but overlaps with duties; rule says "Required Skills And Abilities" is a heading option. I need to check if it's distinct enough. The posting has "Required Skills And Abilities" section with compliance, training, licenses, etc. I'll include it as a section or fold into duties? Rule: "include a section ONLY when the posting has real, specific content for it". It has content. I'll use it.
- Education And Experience - substantive.
- Certificates, Licenses, and Registrations - substantive.
- Physical Requirements & Working Conditions - substantive.
- "Work With Us" / EEO statement - rule says remove EEO/equal-opportunity boilerplate. So I'll drop the EEO paragraph.
- "Already Work Here? Here's a Link To Apply Internally Employee Login" - remove as application instructions.
- "Nearest Major Market: Washington DC" - metadata, fold into short `
`.
- Pay Range given: "$9.00 + Tips" - create a Pay section with this exact info.
- Schedule: Not explicitly given beyond "Part Time". Rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Schedule not stated, so no Schedule section. Benefits not stated, no Benefits section.
- Other boilerplate: "All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, or disability." - remove as EEO boilerplate.
Let's map the sections that have real, specific content:
- Pay: "$9.00 + Tips" -> yes.
- About the role / Property description: The Rose Gaming Resort description is substantive. I could put it under "About the role" or similar. The headings allowed: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I need to choose which headings to use, and only when there's content.
- Responsibilities: "Essential Duties And Responsibilities" -> yes.
- Requirements: "Education And Experience", "Certificates, Licenses, and Registrations", plus age, physical requirements. I'll structure under "Requirements" or separate? The headings list includes "Requirements" and "Qualifications". I'll use "Requirements" for education/experience/licenses, and maybe "Skills" for abilities. But rule: "Prefer a few substantive sections over many thin ones." I should consolidate intelligently.
- Skills: "Required Skills And Abilities" -> yes, but overlaps with requirements. I'll decide based on content.
- Benefits: Not stated -> omit.
- Schedule: Not stated -> omit.
- Pay: stated -> include.
Let's re-read the heading examples: "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". These are suggestions, not a strict mandate to use all. I need to pick the ones that have real content.
Let's list the substantive content groups:
- Property/Description: "The Rose Gaming Resort is a $480 million gaming and entertainment complex destination..." -> This is "About the role" or I could call it "About the Property". I'll use `
About the role
` and put the property description there, or maybe a short intro. The rule says "use for section headings (e.g. About the role, Responsibilities, ...)". I'll use "About the role" for the property spiel.
- Responsibilities: "Essential Duties And Responsibilities" -> `Responsibilities
` with `- `.
- Requirements: "Education And Experience", "Certificates, Licenses, and Registrations", age, physical requirements. I could use `
Requirements
` and list them, or `Qualifications
`. The heading list has both "Requirements" and "Qualifications". I'll pick one or split if meaningful. To avoid thin sections, I'll combine education/licenses/physical under one `Requirements
` or maybe `Qualifications
`. Let's see the content: "Education And Experience High School Diploma or GED equivalent required. Casino or hospitality experience preferred. Must be at least eighteen (21) years of age. Must be able to stand for longer than 8 hours. The ability to lift, push and pull up to 20 pounds." Then "Certificates, Licenses, and Registrations: Virginia Racing Commission License Valid Driver’s License with a minimum of three (3) years driving experience." Then "Physical Requirements & Working Conditions" with a long list. I think I'll use `Requirements
` for education/age/experience/licenses, and maybe fold physical into a `` or separate section? But "Physical Requirements & Working Conditions" is a distinct section in the posting. I could use `
Physical Requirements & Working Conditions
` but the allowed headings don't include that exact phrase. The allowed are examples. I think I can use closer headings, but rule: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g.", so I can use other reasonable headings? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I think I should stick to those or very close, and only use when content exists. But "Physical Requirements & Working Conditions" has content, so I need to map it. Maybe I'll use `Requirements
` and include education/licenses/physical as lists within it, or use `Qualifications
` for education/age/experience and `
` for physical? Let's re-read carefully: "Preserve ALL substantive information; do NOT invent or summarize away detail." So I must include the physical requirements text. I could put it under a `
` that makes sense. The examples are just examples; I can use other `` phrases if needed, but to be safe, I'll use the ones listed and fold physical into an appropriate one, or use `Working Conditions
`? Actually, the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings, but says "Prefer a few substantive sections over many thin ones." I'll interpret that I should use the listed headings where content fits, and if a section like "Physical Requirements & Working Conditions" doesn't fit neatly, I might integrate it. But it's substantial content. Let's look at the posting structure: It has "Education And Experience", "Certificates, Licenses, and Registrations", "Physical Requirements & Working Conditions". These are three distinct sections. I could map them to "Requirements" (education/exp), "Qualifications" (licenses?), and maybe "Skills" or another heading for physical? That might create thin sections. Better to combine all three under one `Requirements
` or `Qualifications
`, but then I'd have to merge content, which is okay as long as I preserve all substantive info. The rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." Merging into a heading with lists should preserve detail.
Let's plan the HTML structure:
Top metadata: Job title already given at top of output? The rule: "Do NOT repeat the job title as a heading (the page already shows it)". So I shouldn't have a `` or `` for job title. I can have a short `
` with metadata (requisition ID, location, pay) but folded. I'll start with a `
` containing location and pay range, or just the pay range in a Pay section. Actually, "Pay Range: Hourly Rate: $9.00 + Tips" should be a `
Pay
` section with that text.
Let's outline sections with content:
1. About the role / property description. (I'll use `About the role
`)
2. Responsibilities. (`Responsibilities
`)
3. Requirements / Qualifications. I'll use `Requirements
` to cover education, experience, licenses, age, physical. Or maybe `Qualifications
`. I'll check the heading list: "Requirements, Qualifications". I'll use `Requirements
` and put education/experience/licenses/physical there, or split into two. To keep it few and substantive, I'll use `Requirements
` and list all relevant items.
4. Skills. The posting has "Required Skills And Abilities". I'll use `Skills
` for that content.
5. Pay. `Pay
` with "$9.00 + Tips".
6. Maybe Schedule? Not stated, omit.
7. Benefits? Not stated, omit.
Now, let's extract exact content for each, preserving all substantive info, no placeholders.
**About the role / Property:**
` for prose. - Do NOT repeat the job title as a heading (already shown). - 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. **Identify the Sections & Content from the Posting:** - Title: Beverage Server (Part Time) - already at top, not to be repeated as heading. - Requisition ID#: 5011 - metadata, fold into short `
` or drop. Rule: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." I'll fold it into a short `
` at the top or bottom, but not as a heading. - Location: Dumfries, VA, US, 22026 - also metadata. - Property: The Rose Gaming Resort - description. - Pay Range: Hourly Rate: $9.00 + Tips - substantive, should be a section or part of Pay. - Job Summary - substantive. - Essential Duties And Responsibilities - substantive, will be `
- `.
- Required Skills And Abilities - substantive, but overlaps with duties; rule says "Required Skills And Abilities" is a heading option. I need to check if it's distinct enough. The posting has "Required Skills And Abilities" section with compliance, training, licenses, etc. I'll include it as a section or fold into duties? Rule: "include a section ONLY when the posting has real, specific content for it". It has content. I'll use it.
- Education And Experience - substantive.
- Certificates, Licenses, and Registrations - substantive.
- Physical Requirements & Working Conditions - substantive.
- "Work With Us" / EEO statement - rule says remove EEO/equal-opportunity boilerplate. So I'll drop the EEO paragraph.
- "Already Work Here? Here's a Link To Apply Internally Employee Login" - remove as application instructions.
- "Nearest Major Market: Washington DC" - metadata, fold into short `
`. - Pay Range given: "$9.00 + Tips" - create a Pay section with this exact info. - Schedule: Not explicitly given beyond "Part Time". Rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Schedule not stated, so no Schedule section. Benefits not stated, no Benefits section. - Other boilerplate: "All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, or disability." - remove as EEO boilerplate. Let's map the sections that have real, specific content: - Pay: "$9.00 + Tips" -> yes. - About the role / Property description: The Rose Gaming Resort description is substantive. I could put it under "About the role" or similar. The headings allowed: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I need to choose which headings to use, and only when there's content. - Responsibilities: "Essential Duties And Responsibilities" -> yes. - Requirements: "Education And Experience", "Certificates, Licenses, and Registrations", plus age, physical requirements. I'll structure under "Requirements" or separate? The headings list includes "Requirements" and "Qualifications". I'll use "Requirements" for education/experience/licenses, and maybe "Skills" for abilities. But rule: "Prefer a few substantive sections over many thin ones." I should consolidate intelligently. - Skills: "Required Skills And Abilities" -> yes, but overlaps with requirements. I'll decide based on content. - Benefits: Not stated -> omit. - Schedule: Not stated -> omit. - Pay: stated -> include. Let's re-read the heading examples: "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". These are suggestions, not a strict mandate to use all. I need to pick the ones that have real content. Let's list the substantive content groups: - Property/Description: "The Rose Gaming Resort is a $480 million gaming and entertainment complex destination..." -> This is "About the role" or I could call it "About the Property". I'll use `
About the role
` and put the property description there, or maybe a short intro. The rule says "usefor section headings (e.g. About the role, Responsibilities, ...)". I'll use "About the role" for the property spiel. - Responsibilities: "Essential Duties And Responsibilities" -> `
Responsibilities
` with `- `.
- Requirements: "Education And Experience", "Certificates, Licenses, and Registrations", age, physical requirements. I could use `
Requirements
` and list them, or `Qualifications
`. The heading list has both "Requirements" and "Qualifications". I'll pick one or split if meaningful. To avoid thin sections, I'll combine education/licenses/physical under one `Requirements
` or maybe `Qualifications
`. Let's see the content: "Education And Experience High School Diploma or GED equivalent required. Casino or hospitality experience preferred. Must be at least eighteen (21) years of age. Must be able to stand for longer than 8 hours. The ability to lift, push and pull up to 20 pounds." Then "Certificates, Licenses, and Registrations: Virginia Racing Commission License Valid Driver’s License with a minimum of three (3) years driving experience." Then "Physical Requirements & Working Conditions" with a long list. I think I'll use `Requirements
` for education/age/experience/licenses, and maybe fold physical into a `` or separate section? But "Physical Requirements & Working Conditions" is a distinct section in the posting. I could use `
Physical Requirements & Working Conditions
` but the allowed headings don't include that exact phrase. The allowed are examples. I think I can use closer headings, but rule: "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g.", so I can use other reasonable headings? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I think I should stick to those or very close, and only use when content exists. But "Physical Requirements & Working Conditions" has content, so I need to map it. Maybe I'll use `
Requirements
` and include education/licenses/physical as lists within it, or use `Qualifications
` for education/age/experience and `` for physical? Let's re-read carefully: "Preserve ALL substantive information; do NOT invent or summarize away detail." So I must include the physical requirements text. I could put it under a `
` that makes sense. The examples are just examples; I can use other `
` phrases if needed, but to be safe, I'll use the ones listed and fold physical into an appropriate one, or use `
Working Conditions
`? Actually, the rule says "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings, but says "Prefer a few substantive sections over many thin ones." I'll interpret that I should use the listed headings where content fits, and if a section like "Physical Requirements & Working Conditions" doesn't fit neatly, I might integrate it. But it's substantial content. Let's look at the posting structure: It has "Education And Experience", "Certificates, Licenses, and Registrations", "Physical Requirements & Working Conditions". These are three distinct sections. I could map them to "Requirements" (education/exp), "Qualifications" (licenses?), and maybe "Skills" or another heading for physical? That might create thin sections. Better to combine all three under one `
Requirements
` or `Qualifications
`, but then I'd have to merge content, which is okay as long as I preserve all substantive info. The rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." Merging into a heading with lists should preserve detail. Let's plan the HTML structure: Top metadata: Job title already given at top of output? The rule: "Do NOT repeat the job title as a heading (the page already shows it)". So I shouldn't have a `` or `` for job title. I can have a short `` with metadata (requisition ID, location, pay) but folded. I'll start with a `
` containing location and pay range, or just the pay range in a Pay section. Actually, "Pay Range: Hourly Rate: $9.00 + Tips" should be a `
Pay
` section with that text. Let's outline sections with content: 1. About the role / property description. (I'll use `About the role
`) 2. Responsibilities. (`Responsibilities
`) 3. Requirements / Qualifications. I'll use `Requirements
` to cover education, experience, licenses, age, physical. Or maybe `Qualifications
`. I'll check the heading list: "Requirements, Qualifications". I'll use `Requirements
` and put education/experience/licenses/physical there, or split into two. To keep it few and substantive, I'll use `Requirements
` and list all relevant items. 4. Skills. The posting has "Required Skills And Abilities". I'll use `Skills
` for that content. 5. Pay. `Pay
` with "$9.00 + Tips". 6. Maybe Schedule? Not stated, omit. 7. Benefits? Not stated, omit. Now, let's extract exact content for each, preserving all substantive info, no placeholders. **About the role / Property:**
- `.
- Requirements: "Education And Experience", "Certificates, Licenses, and Registrations", age, physical requirements. I could use `