Kitchen Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings.
We have About the role (intro). Responsibilities: likely the duties: "Oversee 1–2 kitchen departments including dish, prep, and/or line; Maintain a professional image and uphold Cooper’s Hawk culinary and safety standards; Use tools like POS systems, scheduling software, ordering/inventory systems, and Microsoft Office to stay organized; Help execute new menu roll-outs, kitchen initiatives, and private events, including monthly Wine Club dinners; Help hire, train, and develop hourly kitchen Team Members on kitchen standards; Ensure adherence to food safety, sanitation, and kitchen policies; Be accountable for prep and line knowledge to drive financial and operational results; Assist with weekly inventory and labor management; Foster strong collaboration between kitchen and front-of-house teams; Lead department meetings and coach Team Members; Partner with the Executive Kitchen Manager and General Manager to achieve restaurant goals; Assist in executing private events, including monthly themed Wine Club dinners; Represent Cooper’s Hawk values and create a respectful, inclusive kitchen culture; Support your team with the tools and training they need to succeed; Ensure every dish meets our high standards and enhances the guest experience; Empower your team to take pride in their work and deliver exceptional food; Celebrate wins, big and small, with your team; Contribute to a kitchen environment that inspires excellence."
Also "Show Up Ready: Come prepared, stay sharp and start strong." etc could be responsibilities.
We need to decide what goes where.
Requirements: maybe "1-2 years of supervisory experience in high volume kitchen in a full-service restaurant environment. Scratch kitchen experience preferred. Minimum age requirement of 21 years. Ability to read, understand and communicate in English. Demonstrates financial acumen. Proficient in Microsoft Office Suite. Preferred certifications include ServSafe and state/local licensing requirements. Must be able to lift and carry up to 50 lbs. Must be able to stand for at least 10 hours per shift. Must have the ability to work 50-60 hours per week. Must be able to work flexible shifts and schedules, inclusive of weekends and some holidays."
Qualifications: maybe overlapping with Requirements. Could treat Requirements as qualifications? But we need both sections if content distinct. Could put Requirements as the hard requirements (experience, age, language, physical). Qualifications could be preferred certifications, financial acumen, etc. But we can combine if not distinct. However instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one? But they ask to use those headings if content exists. We could have Requirements (experience, age, language, physical) and Qualifications (certifications, financial acumen, Microsoft Office). Skills: maybe communication skills, etc.
Let's extract:
- Experience: 1-2 years supervisory experience in high volume kitchen in full-service restaurant environment. Scratch kitchen experience preferred.
- Minimum age requirement of 21 years.
- Ability to read, understand and communicate in English.
- Demonstrates financial acumen.
- Proficient in Microsoft Office Suite.
- Preferred certifications include ServSafe and state/local licensing requirements.
- Must be able to lift and carry up to 50 lbs.
- Must be able to stand for at least 10 hours per shift.
- Must have the ability to work 50-60 hours per week.
- Must be able to work flexible shifts and schedules, inclusive of weekends and some holidays.
- Excellent verbal and written communication skills (listed under "What You Will Bring").
Thus we have communication skills as skill.
Thus we can have:
Requirements: experience, age, language, physical (lift, stand, hours, schedule). Qualifications: certifications, financial acumen, Microsoft Office. Skills: communication skills.
But we could also put communication skills under Skills.
Now Benefits: we have list.
Pay: compensation range + bonus potential.
Schedule: maybe mention work 50-60 hours per week, flexible shifts, weekends, holidays. That's schedule.
Thus we can have Schedule section.
Now About the role: intro paragraph.
Responsibilities: the bullet list of duties.
Now we need to output HTML fragment with headings and - for lists,
for prose.
We must not include any boilerplate like EEO, legal, etc. Must not repeat job title. Must not include navigation etc.
We must preserve all substantive information. Ensure we don't miss any.
Let's list all substantive info from posting:
Intro: "As Kitchen Manager, you will help lead the way in our fast-paced, high-volume, scratch kitchen, driving the culinary execution of our uniquely inspired menu with items thoughtfully paired with our Cooper’s Hawk wines. You will partner closely with the Executive Kitchen Manager to deliver uncompromising hospitality, while coaching and inspiring our Team Members to ensure high food quality and a memorable guest experience."
Compensation: "KM Compensation range is $55,000-$65,000/year + 10% bonus potential. The final offered salary will be based on several factors, including but not limited to the candidate's depth of experience, skill set, qualifications, and internal pay equity."
Benefits list: as above.
How You Will Succeed (success factors) - we can treat as responsibilities or maybe as separate but we can incorporate into Responsibilities.
What You Will Bring (requirements/qualifications/skills): list.
About Us: description of company (maybe not needed? It's substantive but could be considered "About the company". Not in allowed headings. Could be omitted? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include About Us info somewhere. But allowed headings are limited to those. Could we put it under About the role? That's about the role, not company. Could we add a generic
without heading? The instruction 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 use those for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we could still use other headings if needed, but better to stick to those. However we need to include About Us info. Could we incorporate it into About the role as a brief description? Might be okay to add a paragraph about company under About the role heading? But that might misrepresent. However we could add a separate
without heading after the sections? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't say we cannot have untagged paragraphs. But they said use
for section headings (e.g. ...). It didn't forbid other elements. So we could add a
for About Us without heading. But better to include it under a heading like "About the company" but not in list. Might be okay to add a heading not in list? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we could add another heading like "About the company". However to be safe, we could incorporate About Us into a
after the sections without a heading. The instruction: "Prefer a few substantive sections over many thin ones." Adding a stray paragraph might be okay.
But we need to preserve all substantive information, including About Us. Let's include it as a
after the sections, maybe preceded by a
About the Company. I think it's acceptable.
Let's decide to add a heading "About the Company". It's not in the examples but seems reasonable.
Now let's structure:
About the role
As Kitchen Manager, you will help lead the way in our fast-paced, high-volume, scratch kitchen, driving the culinary execution of our uniquely inspired menu with items thoughtfully paired with our Cooper’s Hawk wines. You will partner closely with the Executive Kitchen Manager to deliver uncompromising hospitality, while coaching and inspiring our Team Members to ensure high food quality and a memorable guest experience.
Responsibilities
- Oversee 1–2 kitchen departments including dish, prep, and/or line
- Maintain a professional image and uphold Cooper’s Hawk culinary and safety standards
- Use tools like POS systems, scheduling software, ordering/inventory systems, and Microsoft Office to stay organized
- Help execute new menu roll-outs, kitchen initiatives, and private events, including monthly Wine Club dinners
- Help hire, train, and develop hourly kitchen Team Members on kitchen standards
- Ensure adherence to food safety, sanitation, and kitchen policies
- Be accountable for prep and line knowledge to drive financial and operational results
- Assist with weekly inventory and labor management
- Foster strong collaboration between kitchen and front-of-house teams
- Lead department meetings and coach Team Members
- Partner with the Executive Kitchen Manager and General Manager to achieve restaurant goals
- Assist in executing private events, including monthly themed Wine Club dinners
- Represent Cooper’s Hawk values and create a respectful, inclusive kitchen culture
- Support your team with the tools and training they need to succeed
- for lists,
for prose. We must not include any boilerplate like EEO, legal, etc. Must not repeat job title. Must not include navigation etc. We must preserve all substantive information. Ensure we don't miss any. Let's list all substantive info from posting: Intro: "As Kitchen Manager, you will help lead the way in our fast-paced, high-volume, scratch kitchen, driving the culinary execution of our uniquely inspired menu with items thoughtfully paired with our Cooper’s Hawk wines. You will partner closely with the Executive Kitchen Manager to deliver uncompromising hospitality, while coaching and inspiring our Team Members to ensure high food quality and a memorable guest experience." Compensation: "KM Compensation range is $55,000-$65,000/year + 10% bonus potential. The final offered salary will be based on several factors, including but not limited to the candidate's depth of experience, skill set, qualifications, and internal pay equity." Benefits list: as above. How You Will Succeed (success factors) - we can treat as responsibilities or maybe as separate but we can incorporate into Responsibilities. What You Will Bring (requirements/qualifications/skills): list. About Us: description of company (maybe not needed? It's substantive but could be considered "About the company". Not in allowed headings. Could be omitted? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include About Us info somewhere. But allowed headings are limited to those. Could we put it under About the role? That's about the role, not company. Could we add a generic
without heading? The instruction 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 use those for section headings. It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we could still use other headings if needed, but better to stick to those. However we need to include About Us info. Could we incorporate it into About the role as a brief description? Might be okay to add a paragraph about company under About the role heading? But that might misrepresent. However we could add a separate
without heading after the sections? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't say we cannot have untagged paragraphs. But they said use
for section headings (e.g. ...). It didn't forbid other elements. So we could add a
for About Us without heading. But better to include it under a heading like "About the company" but not in list. Might be okay to add a heading not in list? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we could add another heading like "About the company". However to be safe, we could incorporate About Us into a
after the sections without a heading. The instruction: "Prefer a few substantive sections over many thin ones." Adding a stray paragraph might be okay. But we need to preserve all substantive information, including About Us. Let's include it as a
after the sections, maybe preceded by a
About the Company. I think it's acceptable. Let's decide to add a heading "About the Company". It's not in the examples but seems reasonable. Now let's structure:
About the role
As Kitchen Manager, you will help lead the way in our fast-paced, high-volume, scratch kitchen, driving the culinary execution of our uniquely inspired menu with items thoughtfully paired with our Cooper’s Hawk wines. You will partner closely with the Executive Kitchen Manager to deliver uncompromising hospitality, while coaching and inspiring our Team Members to ensure high food quality and a memorable guest experience.
Responsibilities
- Oversee 1–2 kitchen departments including dish, prep, and/or line
- Maintain a professional image and uphold Cooper’s Hawk culinary and safety standards
- Use tools like POS systems, scheduling software, ordering/inventory systems, and Microsoft Office to stay organized
- Help execute new menu roll-outs, kitchen initiatives, and private events, including monthly Wine Club dinners
- Help hire, train, and develop hourly kitchen Team Members on kitchen standards
- Ensure adherence to food safety, sanitation, and kitchen policies
- Be accountable for prep and line knowledge to drive financial and operational results
- Assist with weekly inventory and labor management
- Foster strong collaboration between kitchen and front-of-house teams
- Lead department meetings and coach Team Members
- Partner with the Executive Kitchen Manager and General Manager to achieve restaurant goals
- Assist in executing private events, including monthly themed Wine Club dinners
- Represent Cooper’s Hawk values and create a respectful, inclusive kitchen culture
- Support your team with the tools and training they need to succeed