Ale Haus Cook - Omaha
- for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Preserve ALL substantive information; do NOT invent or summarize away detail. Include a section ONLY when 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 posting actually states them. We have Pay Rate: $18.00/hour. Schedule: Open availability required. Must be able to work all shifts, including evenings, weekends, and holidays as needed. Thus we have Pay and Schedule sections. We have Position Summary (could be About the role). We have Essential Duties & Responsibilities (Responsibilities). We have Qualifications (Required and Preferred). We have Benefits (list). We have Core Competencies (maybe Skills). We have Physical Requirements (maybe Skills? but could be part of Requirements? Might be separate but we have no heading for Physical Requirements; we could include under Requirements or Skills? The instruction says use headings from list; we can decide to put Physical Requirements under Requirements or Skills? Probably under Requirements (since they are job requirements). But we also have Licensing & Certifications (must obtain Nebraska Gaming License, ServSafe preferred). That could be part of Qualifications. We also have Physical Requirements Assessment Rating Scale etc. That's a lot of detail; we need to preserve all substantive information. We could include that under a section maybe "Physical Requirements" but not in allowed headings list. The allowed headings are limited to those eight. We cannot create new headings. So we must fit that info into existing headings. Perhaps we can put Physical Requirements under Requirements (since they are job requirements). Or under Skills? Probably Requirements. We also have Core Competencies list; could be Skills. We have Benefits list. We have Pay and Schedule. We have About the role (Position Summary). We have Responsibilities (Essential Duties & Responsibilities). We have Qualifications (Required and Preferred). Also Licensing & Certifications. Thus we will produce sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide if we need Requirements separate from Qualifications? The list includes Requirements as a possible heading. But we have Qualifications heading already. Could we use both Requirements and Qualifications? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all; we can choose. We have both Qualifications and maybe Requirements (like age, education, experience). Could split: Requirements for mandatory items (age, diploma, experience, etc.) and Qualifications for preferred? But the posting lumps Required and Preferred under Qualifications. Safer to use Qualifications heading for both required and preferred. We could also add Requirements heading for age, diploma, experience? Might be redundant. Better to follow the posting: Use Qualifications for required and preferred. We'll not create a separate Requirements heading unless we have content that fits that heading but not covered elsewhere. We have Licensing & Certifications which could be under Qualifications. We have Core Competencies (Skills). So Skills section. We have Physical Requirements details; we could embed them under Qualifications or Skills? Probably under Qualifications as they are job requirements. But we already have a lot there. Could also put under Skills? Might be okay. We need to preserve all substantive information. So we need to include the physical requirements details (list of abilities). Also the Physical Requirements Assessment Rating Scale table? That's a lot of detail; we need to preserve it. We could represent as a
- list of each item with its rating? The posting includes a table with categories and ratings. We need to preserve all substantive information; we cannot invent or summarize away detail. So we need to include that table content. How to represent in HTML? We could use
- for each line? But the instruction says use
- for any list of duties/requirements/benefits. The physical requirements rating scale is a list of items with ratings; we could treat as a list. Use
- each item: e.g., "Work Environment: 2", etc. That preserves the info.
Similarly, we have Physical Effort, Mental Effort, Communication, Sensory Abilities sections each with items and ratings. We'll need to include all.
We also have Licensing & Certifications: Must be able to obtain and maintain a Nebraska Gaming License. ServSafe Certification preferred.
We have Benefits list: Medical, Dental, Vision Insurance; Federal Employee Medical Coverage; 401(k) with Company Match and Immediate Vesting; Quarterly Incentive Program; Paid Vacation; Paid Holidays; Paid Sick Leave.
We have Pay Rate: $18.00/hour.
Schedule: Open availability required. Must be able to work all shifts, including evenings, weekends, and holidays as needed.
Also earlier: Schedule Requirements: Due to the nature... team members must be available to work flexible schedules, including: Days, Nights, Weekends, Holidays, Overtime as business needs require.
We need to preserve that too.
Thus Schedule section will include both statements.
Now About the role: Position Summary paragraph.
Responsibilities: list of duties.
Qualifications: Required and Preferred bullet list.
Skills: Core Competencies list.
We also have Physical Requirements details; we could put under Qualifications as a subsection? But we need to use
- for any list. We could embed a
- list under Qualifications for physical requirements. However Qualifications already has a list; we could combine? Better to separate: maybe Qualifications heading for education/experience/licensing, and Skills heading for core competencies, and we could add another heading? Not allowed. Could put physical requirements under Skills? But they are not skills. Could put under Qualifications as another list after the required/preferred list. That's okay: we can have multiple
- under same heading? The instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid multiple lists under same heading. So we can have under Qualifications: first a
describing required and preferred? Actually we need to preserve the Required and Preferred bullet list. We'll do
- for each required item, then maybe a note "Preferred:" then another
- for preferred items. Then after that, we can add another
- for physical requirements? Might be confusing but okay.
Alternatively, we could create a separate section "Requirements" for the physical requirements and licensing etc. But we already have Qualifications; we could use Requirements heading for mandatory items (age, diploma, experience, ability to obtain license, etc.) and Qualifications for preferred? But the posting lumps required and preferred under Qualifications. However we can split: Requirements heading for required items (age, diploma, experience, ability to obtain license, etc.) and Qualifications heading for preferred items (ServSafe, hospitality experience). That would follow the headings list. Let's do that: Requirements: required items. Qualifications: preferred items. Then Skills: core competencies. Then we can add Physical Requirements under Requirements? Might be too much.
Better: Use Requirements heading for all mandatory requirements (age, diploma, experience, knowledge, ability to follow recipes, communication skills, ability to work fast-paced, must possess tools, must obtain Nebraska Gaming License). Use Qualifications heading for preferred items (ServSafe Certification, experience in hospitality/gaming/restaurant). Use Skills heading for Core Competencies. Use Benefits, Pay, Schedule as given. Use About the role for Position Summary. Use Responsibilities for duties.
Physical Requirements details: we could put under Requirements as a list (since they are requirements). Or under Skills? I'd put under Requirements as they are job requirements.
Thus we will have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Qualifications we might omit if we split preferred into Skills? But we have preferred items: ServSafe Certification, Experience in hospitality, gaming, or restaurant environments. Those could go under Skills? Or we could keep Qualifications for preferred. But we already have Skills for core competencies; we could put preferred under Qualifications. Let's keep Qualifications for preferred items (ServSafe, hospitality experience). Then Requirements for mandatory items (age, diploma, experience, knowledge, ability to follow recipes, communication, teamwork, tools, license). Physical requirements also under Requirements.
Thus we have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Now we need to ensure we don't create empty sections. All have content.
Now we need to format.
We'll output HTML fragment:
About the role
Position Summary WarHorse Gaming is seeking a dedicated and dependable Cook to join our Food & Beverage team. In this role, you will prepare high-quality food according to established recipes and standards while maintaining a clean, safe, and guest-focused work environment. Successful candidates are team-oriented, thrive in a fast-paced setting, and are committed to delivering exceptional service.
But note the original text: "Position Summary WarHorse Gaming is seeking..." It's a single sentence; we can keep as paragraph. Now Responsibilities:Responsibilities
- ... each duty.
Requirements
- Must be at least 19 years of age.
- High School Diploma, GED, or equivalent work experience.
- One to five years of cooking experience in a high-volume food service environment.
- Knowledge of kitchen sanitation, food safety, and food preparation techniques.
- Ability to follow recipes, measurements, and production specifications.
- Strong communication and guest service skills.
- Ability to work efficiently in a fast-paced environment.
- Ability to take direction and work as part of a team.
- Must possess and maintain personal culinary tools, including knives.
- Must be able to obtain and maintain a Nebraska Gaming License. Then physical requirements list: we need to include all those items from the Physical Requirements section and the assessment rating scale. We need to preserve all substantive information: the list of abilities (Ability to stand and walk for extended periods, Ability to lift and carry up to 50 pounds, Frequent use of hands and fingers for food preparation, Ability to work in a fast-paced kitchen environment, Ability to taste, smell, see,
- for physical requirements? Might be confusing but okay.
Alternatively, we could create a separate section "Requirements" for the physical requirements and licensing etc. But we already have Qualifications; we could use Requirements heading for mandatory items (age, diploma, experience, ability to obtain license, etc.) and Qualifications for preferred? But the posting lumps required and preferred under Qualifications. However we can split: Requirements heading for required items (age, diploma, experience, ability to obtain license, etc.) and Qualifications heading for preferred items (ServSafe, hospitality experience). That would follow the headings list. Let's do that: Requirements: required items. Qualifications: preferred items. Then Skills: core competencies. Then we can add Physical Requirements under Requirements? Might be too much.
Better: Use Requirements heading for all mandatory requirements (age, diploma, experience, knowledge, ability to follow recipes, communication skills, ability to work fast-paced, must possess tools, must obtain Nebraska Gaming License). Use Qualifications heading for preferred items (ServSafe Certification, experience in hospitality/gaming/restaurant). Use Skills heading for Core Competencies. Use Benefits, Pay, Schedule as given. Use About the role for Position Summary. Use Responsibilities for duties.
Physical Requirements details: we could put under Requirements as a list (since they are requirements). Or under Skills? I'd put under Requirements as they are job requirements.
Thus we will have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Qualifications we might omit if we split preferred into Skills? But we have preferred items: ServSafe Certification, Experience in hospitality, gaming, or restaurant environments. Those could go under Skills? Or we could keep Qualifications for preferred. But we already have Skills for core competencies; we could put preferred under Qualifications. Let's keep Qualifications for preferred items (ServSafe, hospitality experience). Then Requirements for mandatory items (age, diploma, experience, knowledge, ability to follow recipes, communication, teamwork, tools, license). Physical requirements also under Requirements.
Thus we have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Now we need to ensure we don't create empty sections. All have content.
Now we need to format.
We'll output HTML fragment:
- for preferred items. Then after that, we can add another
- for each required item, then maybe a note "Preferred:" then another
- for any list of duties/requirements/benefits. It doesn't forbid multiple lists under same heading. So we can have under Qualifications: first a
- under same heading? The instruction: Use
- list under Qualifications for physical requirements. However Qualifications already has a list; we could combine? Better to separate: maybe Qualifications heading for education/experience/licensing, and Skills heading for core competencies, and we could add another heading? Not allowed. Could put physical requirements under Skills? But they are not skills. Could put under Qualifications as another list after the required/preferred list. That's okay: we can have multiple
- for any list. We could embed a
- each item: e.g., "Work Environment: 2", etc. That preserves the info.
Similarly, we have Physical Effort, Mental Effort, Communication, Sensory Abilities sections each with items and ratings. We'll need to include all.
We also have Licensing & Certifications: Must be able to obtain and maintain a Nebraska Gaming License. ServSafe Certification preferred.
We have Benefits list: Medical, Dental, Vision Insurance; Federal Employee Medical Coverage; 401(k) with Company Match and Immediate Vesting; Quarterly Incentive Program; Paid Vacation; Paid Holidays; Paid Sick Leave.
We have Pay Rate: $18.00/hour.
Schedule: Open availability required. Must be able to work all shifts, including evenings, weekends, and holidays as needed.
Also earlier: Schedule Requirements: Due to the nature... team members must be available to work flexible schedules, including: Days, Nights, Weekends, Holidays, Overtime as business needs require.
We need to preserve that too.
Thus Schedule section will include both statements.
Now About the role: Position Summary paragraph.
Responsibilities: list of duties.
Qualifications: Required and Preferred bullet list.
Skills: Core Competencies list.
We also have Physical Requirements details; we could put under Qualifications as a subsection? But we need to use
- for any list of duties/requirements/benefits. The physical requirements rating scale is a list of items with ratings; we could treat as a list. Use
- for each line? But the instruction says use
- list of each item with its rating? The posting includes a table with categories and ratings. We need to preserve all substantive information; we cannot invent or summarize away detail. So we need to include that table content. How to represent in HTML? We could use