Cook - Full Time

Here's a thinking process: 1. **Analyze User Input:** - User wants me to reformat a job posting into clean, well-structured semantic HTML. - Rules: - Use `

` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use `

• ` for any list of duties/requirements/benefits - Use `

  ` for prose - Do NOT repeat the job title as a heading (page already shows it) - 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. **Examine the Provided Job Posting Text:** Role Overview The Cook prepares high-quality, nutritious meals according to standardized recipes and menus, ensuring food quality, taste, and presentation meet established standards. They follow dietary modifications and special meal requirements, record production quantities, food safety temperatures, and maintain compliance with food safety, sanitation, and OSHA guidelines. The role involves maintaining a clean, organized kitchen and storage areas, supporting dishwashing and dining services, and leading food production in the absence of the Dining Services Coordinator. Key Responsibilities Prepare and serve meals adhering to safety and quality standardsFollow dietary modifications and special meal requestsRecord food production and safety dataMaintain cleanliness and organization of kitchen and equipmentSupport dining services and dishwashing as neededLead food preparation when required Qualifications & Skills Experience in food preparation and kitchen safety protocolsAbility to follow recipes, dietary guidelines, and sanitation standardsStrong organizational skills and attention to detailTeam player with flexibility to support various dining functions Additional Information Competitive pay rateBenefits include health plans, retirement, paid time off, tuition reimbursement, and bonus opportunitiesSupportive, inclusive work environment focused on making a positive impact on residents’ lives Let me parse this into sections/parts: - "Role Overview" seems like a section title or just introductory text - "Key Responsibilities" is a clear section - Then there's a block of responsibilities text - "Qualifications & Skills" is a section title - Then qualifications/skills text - "Additional Information" - Then: "Competitive pay rate", "Benefits include health plans, retirement, paid time off, tuition reimbursement, and bonus opportunities", "Supportive, inclusive work environment focused on making a positive impact on residents’ lives" Wait, the user says: use `

  ` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But also: Do NOT repeat the job title as a heading (the page already shows it). The posting doesn't have a job title visible in the text, but I should not invent one or put it as a heading. Let's map the content to the allowed sections, following rules carefully: - Sections to consider: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule - Rule: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text - Rule: never create Pay/Schedule/Benefits sections unless the posting actually states them - The posting has "Competitive pay rate", "Benefits include health plans, retirement, paid time off, tuition reimbursement, and bonus opportunities", and "Supportive, inclusive work environment focused on making a positive impact on residents’ lives" Let's decide on section mapping: - "Role Overview" or "About the role": The first paragraph describes the cook's role. I can use `

  About the role

  ` or maybe just keep it as prose? The rules say use `

  ` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I can use those headings if there's content. The first paragraph is substantive: "The Cook prepares high-quality, nutritious meals according to standardized recipes and menus..." etc. I'll map it to "About the role" or maybe just keep it as a paragraph without a heading? But the rule says use `

  ` for section headings (e.g. About the role...). It doesn't say I must use all of them, only include when there's real content. The first paragraph is real content. I'll use `

  About the role

  ` followed by `

  ...

  `. - "Key Responsibilities" maps to "Responsibilities". There's a clear section with bulletable items: "Prepare and serve meals adhering to safety and quality standards", "Follow dietary modifications and special meal requests", "Record food production and safety data", "Maintain cleanliness and organization of kitchen and equipment", "Support dining services and dishwashing as needed", "Lead food preparation when required". I'll use `
  • ` for these. - "Qualifications & Skills" maps to "Qualifications" and/or "Skills". The text: "Experience in food preparation and kitchen safety protocols", "Ability to follow recipes, dietary guidelines, and sanitation standards", "Strong organizational skills and attention to detail", "Team player with flexibility to support various dining functions". I could split into Qualifications and Skills, or combine. The rules say prefer a few substantive sections over many thin ones. I'll likely use one `

    Qualifications

    ` or `

    Qualifications & Skills

    ` with `
    • `. But need to check if the heading "Qualifications & Skills" is allowed. Yes, it's in the example list. I'll use `

      Qualifications & Skills

      `. - "Additional Information" section has: "Competitive pay rate", "Benefits include health plans, retirement, paid time off, tuition reimbursement, and bonus opportunities", "Supportive, inclusive work environment focused on making a positive impact on residents’ lives". - Pay: "Competitive pay rate" - this is specific enough? The rule says never create Pay section unless the posting actually states them. It states "Competitive pay rate". I think that's substantive enough to include a Pay section with that text. But wait: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". "Competitive pay rate" is not filler, it's actual text. I'll include a `

      Pay

      ` with `

      Competitive pay rate

      ` or integrate it. - Benefits: "Benefits include health plans, retirement, paid time off, tuition reimbursement, and bonus opportunities" - this is clearly a Benefits section. I'll use `

      Benefits

      ` with `
      • ` or `

        `. - Schedule: Not mentioned. So no Schedule section. - The "Supportive, inclusive work environment focused on making a positive impact on residents’ lives" is prose, could go under Benefits or Additional Information, but since Benefits is already there, maybe I'll just include it as part of Benefits or as a separate `

        ` if it's substantive. But the rule says include a section ONLY when the posting has real, specific content for it. Benefits section will have the benefits list. The "supportive, inclusive work environment" could be part of Benefits or a separate culture note, but I'll keep it tight. Let's re-read the rules carefully: - "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)" - "Use

        • for any list of duties/requirements/benefits, and

          for prose." - "Do NOT repeat the job title as a heading (the page already shows it) and 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." Now, let's parse the posting text carefully and extract only real content, mapping to sections: Text breakdown: "Role Overview The Cook prepares high-quality, nutritious meals according to standardized recipes and menus, ensuring food quality, taste, and presentation meet established standards. They follow dietary modifications and special meal requirements, record production quantities, food safety temperatures, and maintain compliance with food safety, sanitation, and OSHA guidelines. The role involves maintaining a clean, organized kitchen and storage areas, supporting dishwashing and dining services, and leading food production in the absence of the Dining Services Coordinator." This is the "About the role" or general overview. I'll use `

          About the role

          ` and then `

          ` with that text. But wait: the rules say "use

          for section headings (e.g. About the role, Responsibilities, ...)". It's an example. I can use it. The first sentence says "Role Overview" which matches "About the role". I'll use `

          About the role

          `. "Key Responsibilities Prepare and serve meals adhering to safety and quality standardsFollow dietary modifications and special meal requestsRecord food production and safety dataMaintain cleanliness and organization of kitchen and equipmentSupport dining services and dishwashing as neededLead food preparation when required" This is clearly Responsibilities. I'll use `

          Responsibilities

          ` and `
          • ` for each bullet. Need to split by the listed items. The text has no punctuation separators between them except maybe spaces. I'll parse them as separate items: - Prepare and serve meals adhering to safety and quality standards - Follow dietary modifications and special meal requests - Record food production and safety data - Maintain cleanliness and organization of kitchen and equipment - Support dining services and dishwashing as needed - Lead food preparation when required "Qualifications & Skills Experience in food preparation and kitchen safety protocolsAbility to follow recipes, dietary guidelines, and sanitation standardsStrong organizational skills and attention to detailTeam player with flexibility to support various dining functions" This maps to Qualifications & Skills. I'll use `

            Qualifications & Skills

            ` and `
            • ` for each, or maybe `

              ` if they are prose-like. But they look like list items. I'll use `

              • `. "Additional Information Competitive pay rateBenefits include health plans, retirement, paid time off, tuition reimbursement, and bonus opportunitiesSupportive