PM Lead Cook

We need to output HTML fragment with sections: About Us, The role, Why our kitchen, What You'll Lead, Where you can go, What You Bring, What we offer. Use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. No Job ID. Remove boilerplate like "Search blurb:" and "Powered by JazzHR". Also remove any navigation/legal etc. The posting includes some bullet-like sentences; we need to format them as lists where appropriate. Let's parse content: - About Us: paragraph(s). "The Perlant is a private, wine-focused membership club. Our members come to us for exceptional wine, food and hospitality, and they come back because every visit feels considered. We cook with care, pair with intention and hold every plate to the same standard." - The role: paragraph(s). "The Lead Line Cook is the backbone of our PM line. You'll work a station at full speed while keeping the whole line moving, supporting and developing our cooks, and being the sous chef's right hand during service. This role is built for an experienced cook who's ready to lead and who sees Sous Chef as the next step." - Why our kitchen: bullet list of statements: "One team, every ticket. We work together to get through every ticket that comes in, and nobody gets left behind", "Old-school technique, new ingredients. You'll learn classic techniques and apply them to new, exciting products", "We eat together. There's always time to take a break and share a meal as a team if you want to", "One voice, real autonomy. We move as one kitchen, and you're trusted to make decisions that make service better", "Total focus in service. Once service starts, outside distractions stay outside. We execute call after call with one mind", "Respect in every conversation. When it's time for a 'chat in the walk-in,' we bring everything forward with respect and understanding". These are separate bullet points. - What You'll Lead: multiple sub-sections: Setting up the line, Running service, Developing the team, Closing strong. Each has bullet points. We could treat each as a list under a heading? But we only have headings for sections; we can embed lists inside paragraphs? The instruction: Use

  • for any list of duties/requirements/benefits. So we need to convert each bullet list to
    • . For "What You'll Lead", we have multiple categories each with bullet points. Could either make a single list combining all bullet points, or separate lists per subheading. Since we cannot add extra headings beyond the allowed ones (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can still use

      for section headings; we are not limited to those exact words? The instruction says: use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can use other headings? It says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect we use those standard headings if applicable. But we can also use other headings as long as they are

      . However they said "Prefer a few substantive sections over many thin ones." So we may combine. We have content that maps to sections: About Us -> About the role? Actually "About Us" could be "About the role"? But they said do NOT repeat the job title as a heading. "About Us" is okay as a heading. Could map to "About the role"? Might be better to use "About the role" as heading for the description of the role and company. But we have separate "The role" paragraph. Could combine About Us and The role under "About the role". However we need to preserve all info; we can just have a section "About the role" containing both About Us and The role paragraphs. Why our kitchen could be "Skills" or "Responsibilities"? It's more about culture; maybe "Skills"? But it's not a skill list; it's cultural attributes. Could be "Responsibilities"? Not exactly. Could be "Qualifications"? Not. Could be "Benefits"? No. Could be "About the role"? Already used. Could be "What You'll Lead" corresponds to "Responsibilities". That seems appropriate: responsibilities of the role. So we can make a section "Responsibilities" containing the bullet points under What You'll Lead (setting up line, running service, developing team, closing strong). Also maybe include the "Why our kitchen" as part of responsibilities? But it's more about culture; maybe we can put under "Skills" or "Qualifications"? Actually "Why our kitchen" describes the kitchen culture; could be part of "About the role" or "Skills". But we can treat it as a separate section "Skills" listing those cultural expectations as skills/attributes. However they are not skills per se but values. Could be "Qualifications"? Not. Better: Use sections: About the role (includes About Us and The role), Responsibilities (What You'll Lead), Qualifications (What You Bring), Benefits (What we offer). Also maybe include Pay as part of Benefits? They said include Pay section only if posting actually states them. The posting states "$24–$25/hr" under What we offer. So we could have a Pay section with that info, or include it in Benefits. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Pay and Benefits into one Benefits section that includes pay and benefits. But they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state pay and benefits, so we could have separate Pay and Benefits sections, but that would be thin. Better to combine into Benefits section that includes pay and benefits. However they said "Prefer a few substantive sections over many thin ones." So combine. Thus sections: About the role, Responsibilities, Qualifications, Benefits. Now we need to format content. About the role: combine About Us paragraph and The role paragraph. Responsibilities: list bullet points from What You'll Lead (Setting up the line, Running service, Developing the team, Closing strong). Each bullet point is a sentence or multiple sentences. We'll make each bullet as

      . Qualifications: list bullet points from What You Bring (3+ years..., Mastery..., A calm head..., A drive..., ServSafe..., Availability..., Ability...). Also maybe include "Where you can go" as part of Qualifications? That's about career path; could be included in Qualifications or Benefits. It's about growth opportunity. Could be part of Benefits (clear path to Sous Chef). Actually "Where you can go" is about career progression; could be part of Benefits (clear, supported path to Sous Chef). We'll incorporate that into Benefits. Benefits: include pay ($24–$25/hr), benefits list (health, PTO, staff meals, dining/wine discounts), clear path to Sous Chef, professional respectful kitchen culture with real ownership. Also maybe mention "What we offer" includes those. Now we need to ensure we don't include boilerplate like "Search blurb:" and "Powered by JazzHR". Remove. Now produce HTML:

      About the role

      The Perlant is a private, wine-focused membership club. Our members come to us for exceptional wine, food and hospitality, and they come back because every visit feels considered. We cook with care, pair with intention and hold every plate to the same standard.

      The Lead Line Cook is the backbone of our PM line. You'll work a station at full speed while keeping the whole line moving, supporting and developing our cooks, and being the sous chef's right hand during service. This role is built for an experienced cook who's ready to lead and who sees Sous Chef as the next step.

      Responsibilities

      • Setting up the line: Make sure every station is fully prepped, stocked and ready before the first ticket, with fresh herbs picked and chopped and the line wiped down; take the AM-to-PM pass-off and make sure high-priority prep is covered; confirm that steaks and chicken are tempered and proteins are counted before service.
      • Running service: Work your own station while watching the whole line, and jump in wherever someone is falling behind; keep communication flowing between the line, the sous chef, the porters and the runners; track protein counts across the line and flag low items to the chef early; protect the standard: sauces are tasted before plating, and no plate goes out unless it's right; make real-time calls that keep service moving, and escalate to the sous chef when needed.
      • Developing the team: Train new cooks on stations, standards and systems; coach in the moment, correct with respect, and model the culture we want; help the chef and sous chef spot cooks who are ready for more responsibility.
      • Closing strong: Lead the scrub-down, inventory and the team's prep-list writing; check out with the chef and pass off the next day's priorities; help with ordering, waste tracking and keeping the walk-in organized.

      Qualifications

      • 3+ years of line experience in a quality-focused kitchen, including 1+ year in a lead, senior or trainer role.
      • Mastery of every hot-line station; grill or live-fire experience is a plus.
      • A calm head, clear communication and a team-first attitude under pressure.
      • A drive to teach, lead by example and grow into kitchen management.
      • ServSafe Food Handler or Manager certification, or willingness to get one.
      • Availability for evenings, weekends and holidays.
      • Ability to stand for a full shift and lift heavy items, such as a full stock pot, with a teammate's help.

      Benefits

      • $24–$25/hr
      • Health insurance, PTO, staff meals, dining and wine discounts
      • A clear, supported path to Sous Chef
      • A professional, respectful kitchen culture with real ownership

      Check that we didn't repeat job title as heading. We used About the role, Responsibilities, Qualifications, Benefits. Good. We omitted "Where you can go" content but incorporated into Benefits as path to Sous Chef. Also we omitted "Why our kitchen" content; we didn't include that. Did we lose substantive info? The "Why our kitchen" bullet points describe culture; we included "professional, respectful kitchen culture with real ownership" in Benefits but we missed the specific bullet points: One team every ticket, Old-school technique..., We eat together..., One voice real autonomy..., Total focus in service..., Respect in every conversation. Those are substantive. Should we include them? They are cultural aspects; could be placed under Benefits or maybe under Qualifications as soft skills. Since we have Benefits section, we could add those as list items under Benefits. However Benefits already has list; we can add more items. But we need to avoid making Benefits too thin? It's okay. We should incorporate those bullet points into Benefits or maybe a separate section "Skills"? But we want few sections. Let's add them to Benefits as additional items. Thus Benefits list: - $24–$25/hr - Health insurance, PTO, staff meals, dining and wine discounts - A clear, supported path to Sous Chef - A professional, respectful kitchen culture with real ownership - One team, every ticket: work together to get through every ticket that comes in, nobody gets left behind - Old-school technique, new ingredients: learn classic techniques and apply them to new, exciting products - We eat together: always time to take a break and share a meal as a team