Cook - Full-Time

Here's a thinking process: 1. **Analyze User Request:** - Input: A job posting text for a "Cook" role in senior living - Task: Reformat into clean, well-structured semantic HTML - Rules: - Use `

` for section headings (specific list provided: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use `

• ` for lists of duties/requirements/benefits - Use `

  ` for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID / requisition numbers as headings - fold minor metadata into 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") - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Analyze Input Text:** Input text: Role Overview The Cook is responsible for preparing high-quality, nutritious meals that promote residents' health and enjoyment in a senior living environment. Key duties include following standardized recipes and menus, ensuring food quality, taste, and presentation meet standards, and accommodating dietary modifications and special meal requirements. The role involves recording food production quantities and safety temperatures, stocking and rotating food per safety regulations, and maintaining cleanliness in the kitchen, storage, and equipment areas. The Cook also completes cleaning logs and equipment maintenance reports, adheres to all food safety, sanitation, and OSHA guidelines, and supports dishwashing and dining services as needed. In the absence of the Dining Services Coordinator, the Cook leads food production to ensure a positive dining experience while maintaining safety and compliance. Qualifications And Skills Experience in food preparation and kitchen safety protocolsAbility to follow recipes and dietary guidelines accuratelyStrong organizational and cleanliness habitsTeam-oriented with flexibility to support dining servicesKnowledge of food safety and sanitation standards Let me break it down: - There's a "Role Overview" section with description/duties - Then "Qualifications And Skills" section with a list of qualifications/skills - No explicit "About the role", "Responsibilities", "Requirements", "Benefits", "Pay", "Schedule" sections as such, but the content maps to these categories. - I need to map the content to the allowed headings, but only include sections that have real content. - Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule - I should NOT create sections with filler/placeholder text. - I need to preserve all substantive information. - Remove boilerplate (none present in this snippet, but rules mention removing it). - Output only HTML fragment, no html/body, no markdown fences. Let's map the content: - The first paragraph is essentially "About the role" or "Responsibilities". It describes the cook's duties. - The second part lists qualifications and skills. The heading says "Qualifications And Skills" but I need to check if I should use "Qualifications" and "Skills" as separate headings, or combine them. The rules say use `

  ` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It lists them as examples, but I think I can use them as separate sections if the content fits. However, the input combines "Qualifications And Skills" into one block. I could split them into two sections: "Qualifications" and "Skills", but only if there's distinct content. Looking at the text: "Experience in food preparation and kitchen safety protocols", "Ability to follow recipes and dietary guidelines accurately", "Strong organizational and cleanliness habits", "Team-oriented with flexibility to support dining services", "Knowledge of food safety and sanitation standards". These all seem like qualifications/skills mixed together. I could either make one "Qualifications And Skills" section, or split them. The rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say I must use all of them, only include when there's real content. I think I'll use "Qualifications" and "Skills" as separate headings where appropriate, but since the text blends them, maybe I'll just use one section "Qualifications And Skills" or map them appropriately. Let's see the exact wording: "Qualifications And Skills" is the heading in the input. I'll respect that but maybe format as "Qualifications" and "Skills" as separate `

  `s if I can distinguish them, but the rules say "Prefer a few substantive sections over many thin ones." So I'd rather keep it as one section if splitting would create thin/weak sections. However, the example headings list both "Qualifications" and "Skills" as separate items. I could do "Qualifications" then "Skills", but the content doesn't clearly separate. I'll check if I can split: "Experience in food preparation and kitchen safety protocols", "Ability to follow recipes and dietary guidelines accurately" could be qualifications. "Strong organizational and cleanliness habits", "Team-oriented with flexibility to support dining services", "Knowledge of food safety and sanitation standards" could be skills. But it's ambiguous. I'll probably just use one section "Qualifications And Skills" or maybe "Qualifications" since that's the heading given. Actually, re-reading: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". These are examples of valid headings. I don't have to use all of them. I'll include only those that have content. The input has two natural groupings: the duty/description part, and the qualifications/skills part. I'll map the first paragraph to "Responsibilities" or "About the role". The second to "Qualifications" or "Skills". Let's decide on section mapping: - "About the role" could encompass the description. But the first sentence says "Role Overview", so maybe "About the role" is appropriate. However, the content is mostly duties. I could use "Responsibilities" for the duties list, and "Qualifications" for the skills list. That seems clean. - The first paragraph: duties. → `

  Responsibilities

  ` - The second part: qualifications/skills. → I'll use `

  Qualifications

  ` and maybe `

  Skills

  ` but since it's blended, I'll just use one `

  Qualifications

  ` or `

  Qualifications And Skills

  `. But the rules say "include a section ONLY when the posting has real, specific content for it". The posting has content for qualifications/skills. I'll use `

  Qualifications

  ` and list the items. If I want to split hairs, I could, but I'll keep it as one section "Qualifications" since the heading in the input is "Qualifications And Skills". I'll just use "Qualifications". Wait, the rules give examples: "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It doesn't say I can't use multiple. But it also says "Prefer a few substantive sections over many thin ones." I'll use three sections: "Responsibilities", "Qualifications", and maybe "Skills" if I can distinctly map items. Let's look at the qualifications/skills text again: "Experience in food preparation and kitchen safety protocols" - qual. "Ability to follow recipes and dietary guidelines accurately" - qual/skill. "Strong organizational and cleanliness habits" - skill. "Team-oriented with flexibility to support dining services" - skill/qual. "Knowledge of food safety and sanitation standards" - qual/skill. It's really mixed. I'll just use one section "Qualifications" and list all five items under `
• `. That's substantive and not thin. What about "Requirements"? The text doesn't explicitly separate requirements, but duties often imply requirements. I'll stick to what's there. Let's structure: - `

  Responsibilities

  ` with list of duties from first paragraph. - `

  Qualifications

  ` with list of qualifications/skills from second paragraph. But wait: the rules say "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might expect me to use exactly those phrasings or similar. I'll use "Responsibilities" and "Qualifications". Also, "Do NOT repeat the job title as a heading (the page already shows it)" - I won't add a heading for "Cook". "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." - No job ID in input. "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." - None present. "Preserve ALL substantive information; do NOT invent or summarize away detail." - I'll keep all details. "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." - I won't create Pay/Schedule/Benefits since not present. "Output ONLY the HTML fragment — no /, no markdown code fences." Now, let's map the text precisely: First paragraph content: "The Cook is responsible for preparing high-quality, nutritious meals that promote residents' health and enjoyment in a senior living environment. Key duties include following standardized recipes and menus, ensuring food quality, taste, and presentation meet standards, and accommodating dietary modifications and special meal requirements. The role involves recording food production quantities and safety temperatures, stocking and rotating food per safety regulations, and maintaining cleanliness in the kitchen, storage, and equipment areas. The Cook also completes cleaning logs and equipment maintenance reports, adheres to all food safety, sanitation, and OSHA guidelines, and supports dishwashing and dining services as needed. In the absence of the Dining Services Coordinator, the Cook leads food production to ensure a positive dining experience while maintaining safety and compliance." This is all substantive. I'll put under "Responsibilities" as a `

  • ` list? Or `

    `? The rules: "Use

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

      for prose." The first paragraph is prose describing duties, but it also contains list-like items. I could either make a `

      • ` for each duty, or keep as `

        `. The rules say "Use

        • for any list of duties/requirements/benefits". I think I should extract the duties into a list, as they are clearly duties. Let's parse each duty sentence: - preparing high-quality, nutritious meals that promote residents' health and enjoyment - following standardized recipes and menus - ensuring food quality, taste, and presentation meet standards - accommodating dietary modifications and special meal requirements - recording food production quantities and safety temperatures