Cook

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections that have real specific content. We need to parse the posting. We have: Position Summary: description of role. Essential Duties and Responsibilities: list of duties. What You Bring: Required and Preferred. Work Environment and Physical Requirements: description. Compensation and Benefits: includes compensation statement and benefits list. About PAH: description of company. Equal Opportunity Employer: boilerplate to remove. We need to map to headings: - About the role: could be Position Summary. - Responsibilities: Essential Duties and Responsibilities. - Requirements: Required qualifications. - Qualifications: maybe Preferred? Or combine? Usually Requirements and Qualifications separate. We can put Required under Requirements, Preferred under Qualifications. - Skills: maybe not explicit; but we have abilities like communication, operate equipment, etc. Could be Skills. - Benefits: list. - Pay: compensation statement. - Schedule: work schedule info (flexible schedule, early mornings etc.) from Work Environment and Physical Requirements? Actually schedule info is in Work Environment and Physical Requirements: "Must be available to work a flexible schedule, including early mornings, evenings, weekends, holidays, and special events as business needs require." That's schedule. We also have physical requirements etc. Could be part of Work Environment but not a heading; we could include under Responsibilities? Not appropriate. Maybe we can include under Requirements? Not exactly. Could be omitted if not fitting headings. But we need to preserve all substantive information. We could include a section like "Work Environment" but not in allowed headings list. The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use h3 for section headings (e.g. ...). Likely we should only use those headings. So we need to fit all info into those categories. We have: - About the role: Position Summary. - Responsibilities: Essential Duties and Responsibilities. - Requirements: Required (basic knowledge, certification, ability to operate equipment, communication). - Qualifications: Preferred (previous experience, experience preparing breakfast etc.) - Skills: maybe combine abilities like communication, operate equipment, etc. But we already used those in Requirements. Could put communication etc under Skills. But we need to avoid duplication. Could split: Requirements = basic knowledge, certification; Skills = ability to operate equipment, communicate; Qualifications = preferred experience. However the instruction says prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one? But they ask to use headings as appropriate. We'll decide. We have also Pay: compensation statement. Benefits: list. Schedule: flexible schedule info. We also have Work Environment and Physical Requirements: physical demands, exposure etc. Where to put? Could be under Responsibilities? Not really. Could be under Requirements? Not exactly. Could be under Skills? Not. Could be under About the role? Not. We could create a section "Work Environment" but not allowed. However maybe we can include under Responsibilities as part of duties? Not accurate. Maybe we can treat physical requirements as part of "Requirements" (i.e., job requirements). That seems plausible: ability to stand, lift, etc. So Requirements can include both knowledge/certification and physical demands. Thus: - About the role: Position Summary. - Responsibilities: Essential Duties and Responsibilities. - Requirements: Required knowledge/certification + physical demands + ability to operate equipment + communication. - Qualifications: Preferred experience. - Skills: maybe not needed if we covered abilities in Requirements. Could omit Skills section if no specific content left. But we have communication etc already in Requirements. Could still have Skills for things like teamwork, etc. But we can skip if not needed. - Benefits: list. - Pay: compensation statement. - Schedule: flexible schedule. We must not include boilerplate like Equal Opportunity Employer. We must not include duplicated lines. We must preserve all substantive information. Let's extract details. Position Summary: "The Cook is responsible for preparing high-quality food for hotel guests in accordance with standardized recipes, food safety regulations, and brand standards. This role supports restaurant, breakfast, room service, banquet, and employee meal operations while maintaining a clean, safe, and organized kitchen environment." Essential Duties and Responsibilities bullet list: - Prepare, cook, and present menu items according to standardized recipes, portion guidelines, and brand quality standards. - Prepare food for hotel restaurants, breakfast service, room service, employee meals, banquets, and catered events as assigned. - Ensure all food is prepared in a timely manner while maintaining consistency, quality, and presentation standards. - Monitor food quality throughout preparation and service and promptly address any issues affecting guest satisfaction. - Prepare and replenish buffet items, ensuring food is fresh, properly displayed, and maintained at safe serving temperatures. - Set up and stock workstations with ingredients, supplies, and equipment before service. - Maintain organized food storage areas and ensure proper labeling, dating, and rotation of products using First In, First Out (FIFO) practices. - Assist with receiving, storing, and organizing food deliveries. - Minimize food waste while maintaining production efficiency and quality standards. - Follow all food safety, sanitation, and health department regulations, including proper food handling and temperature control procedures. - Maintain a clean and sanitary kitchen by following "Clean as You Go" practices throughout each shift. - Clean and sanitize kitchen equipment, utensils, workstations, storage areas, and food preparation surfaces. - Safely operate kitchen equipment and report equipment malfunctions or maintenance concerns to management. What You Bring: Required: - Basic knowledge of food preparation techniques and kitchen safety practices. - Must possess or obtain a Food Handler certification if required by state or local regulations. - Ability to safely operate commercial kitchen equipment. - Ability to communicate effectively with team members and supervisors. Preferred: - Previous experience in a restaurant, hotel, banquet, or commercial kitchen. - Experience preparing breakfast, buffet, banquet, or à la carte menu items. Work Environment and Physical Requirements: - This position is based on property in Charlotte, NC. - Must be available to work a flexible schedule, including early mornings, evenings, weekends, holidays, and special events as business needs require. - Ability to stand and walk for extended periods throughout the shift. - Frequently lift, carry, push, and pull items weighing up to 50 pounds. - Frequently bend, stoop, kneel, reach overhead, twist, and perform repetitive hand and wrist movements. - Ability to safely operate commercial kitchen equipment, including ovens, grills, fryers, slicers, mixers, and knives. - Regular exposure to hot surfaces, steam, sharp utensils, cleaning chemicals, refrigerated storage areas, and moderate to high noise levels. Compensation and Benefits: - Compensation: PAH Management offers a competitive base salary/pay commensurate with experience. - Benefits include: • Medical, Dental, and Vision Insurance • Short-Term and Long-Term Disability • 401(k) Retirement Plan • Term Life and AD&D Insurance • Employee Incentive Program • Voluntary Life Insurance (self, spouse, and child) • Hotel Stay Perks (Marriott and Hilton programs) • Accident, Critical Illness, and Hospital Indemnity Insurance • Educational Reimbursement • Paid Time Off • Manager in Training Program (where applicable) About PAH: - PAH Management is a Dallas-based hotel ownership and management company operating a portfolio of select-service properties across multiple states under Marriott and Hilton brands. - We are dedicated to developing a culture that places associates first while becoming America's preferred hotel management company. We need to exclude Equal Opportunity Employer. Now map to sections. About the role: Position Summary. Responsibilities: Essential Duties and Responsibilities. Requirements: Required + physical demands + ability to operate equipment (though that is also in Required). We'll combine. Qualifications: Preferred. Skills: maybe we can include communication etc but already in Requirements. Could omit Skills if no distinct content. But we have communication etc already in Requirements; we could still have Skills for communication and teamwork but duplication. Safer to omit Skills if not needed. Benefits: list. Pay: compensation statement. Schedule: flexible schedule info (from Work Environment). Also note location Charlotte, NC maybe not needed but could be part of About the role? Not required. Could include location in About the role? Not specified. We could include location in About the role? It's not part of Position Summary. Could add a short paragraph under About the role? But we must not invent. Could add a separate section? Not allowed. Could include location in About the role as extra sentence? That would be adding info not originally in that section but it's still substantive info from posting. It's okay to include it under About the role as it's still about the role. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we can include location in About the role as it's still about the role. However the Position Summary didn't mention location; but we can add it as part of About the role because it's still about the role. It's not inventing; it's taking from posting. So we can add "This position is based on property in Charlotte, NC." to About the role. Similarly, we might include ability to safely operate commercial kitchen equipment (already in Requirements). Also physical demands. Now schedule: "Must be available to work a flexible schedule, including early mornings, evenings, weekends, holidays, and special events as business needs require." Now Benefits: list as given. Pay: "Compensation: PAH Management offers a competitive base salary/pay commensurate with experience." Now we need to output HTML fragment with h3 headings and appropriate

• for lists,

  for prose. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must not include boilerplate. We must not create sections with filler like "commensurate with experience" for Pay? Actually Pay section has that phrase; it's actual content from posting, so it's okay. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Wait they say never emit a heading followed by filler/placeholder text like "commensurate with experience". That suggests we should not create a Pay section if the only content is "commensurate with experience" (i.e., vague). But the posting actually says "Compensation: PAH Management offers a competitive base salary/pay commensurate with experience." That's still vague but it's the actual statement. The instruction says never emit a heading followed by filler/placeholder text. So if we create a Pay section, we would have heading Pay and then content "commensurate with experience" which is considered filler. So we should avoid creating a Pay section unless the posting actually states specific pay (like a number or range). Since it's only vague, we should omit Pay section. Similarly for Benefits we have actual list, so okay. Schedule we have specific flexible schedule details, okay. Thus we will omit Pay section. Now we need to decide about Skills section: we might have some skills like communication, teamwork, etc. But we already put communication in Requirements. Could we move communication to Skills and keep Requirements for knowledge/certification and physical demands? That would give Skills substantive content. Let's do that. Thus: - About the role: Position Summary + location. - Responsibilities: Essential Duties and Responsibilities. - Requirements: Required knowledge/certification + physical demands + ability to safely operate commercial kitchen equipment (maybe also ability to operate equipment). Actually ability to operate equipment is a skill; but we can keep it in Requirements as it's a requirement. We'll decide. - Skills: Ability to communicate effectively with team members and supervisors. Also maybe teamwork? Not listed. We'll just put communication. - Qual