Cook - Full Time
` for section headings (e.g., 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 (already shown)
- Do NOT put Job ID / requisition numbers as headings
- 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
- Prefer a few substantive sections over many thin ones
- Output ONLY the HTML fragment — no `/`, no markdown code fences
2. **Deconstruct the Job Posting:**
Let me extract the meaningful sections and content from the text. I need to identify:
- Job title (already mentioned: "Hermitage Richmond Prep Cook Full-time") - I should NOT repeat it as a heading
- Sections: About the role? Responsibilities? Requirements? Qualifications? Skills? Benefits? Pay? Schedule?
- The posting has specific content for many of these, but I need to map them carefully.
Let's parse the raw text:
- "Hermitage Richmond Prep Cook Full-time. 40 hours a week. 10:30A-7P shifts available Monday–Friday and every other weekend needed."
- "Job Description ..." (long list of duties)
- "Education, Experience, Certification And Licensure Requirements"
- "Job Duties" (actually overlapping with Job Description, but listed separately)
- "Qualifications"
- "Physical Requirements And Working Conditions"
- "INDK Benefits" (a block of benefits)
- "Company Description"
- "Vaccination Requirement"
Now, map to the requested heading format:
- Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule
- I need to decide which sections to include based on actual content, no placeholders.
Let's map:
- "About the role" - Not explicitly a separate section, but there's company description at the end. Could fold into a brief intro or "About the company" but the allowed headings are specific. The prompt says "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It doesn't say I must use all, only include when there's real content. I could use "About the role" if there's role-specific intro, or maybe skip and use company description elsewhere. Actually, the prompt says use
for section headings (e.g. About the role, Responsibilities, ...). It's giving examples of valid headings. I should use headings that match the content and are in that list. I need to be careful: "About the role" might not have dedicated content, but the company description could serve. However, the prompt says "include a section ONLY when the posting has real, specific content for it". I'll evaluate each.
Let's list content by requested heading categories:
**Responsibilities/Job Duties**:
The posting has "Job Description" and "Job Duties" sections. Both list many specific duties. I should combine them under "Responsibilities" or maybe "Job Duties". The heading options include "Responsibilities". I'll use `Responsibilities
` and list duties.
**Requirements**:
The posting has "Education, Experience, Certification And Licensure Requirements". That's clearly requirements. I'll use `Requirements
`.
**Qualifications**:
There's a "Qualifications" section. I'll use `Qualifications
`.
**Skills**:
The Qualifications section mentions: "Fundamental knowledge of general kitchen and ingredient offerings...", "Ability to learn Health Department Regulations...", "Strong ability to use and maintain kitchen equipment.", "Good communication skills." These could be skills. I could fold into Qualifications or make a separate Skills section. The prompt says "Prefer a few substantive sections over many thin ones." I need to check if Skills has enough distinct content. It does have specific skills listed. I'll consider merging or separating. Since the heading list includes "Skills", I could use it, but I need to ensure it's not filler. I'll likely include it as a subsection or merge into Qualifications. But the rule says include a section ONLY when the posting has real, specific content for it. The Qualifications section already has text; Skills could be derived but might be redundant. I'll see if I can map distinct content. The Qualifications section: "Fundamental knowledge of general kitchen and ingredient offerings to perform entry-level duties...", "Ability to learn Health Department Regulations related to food storage and preparation.", "Ability to learn Health Department Regulations related to food storage, preparation, and service.", "Strong ability to use and maintain kitchen equipment.", "Good communication skills." These are essentially qualifications/skills. I think I'll put them under Qualifications, or maybe create a Skills section if I can separate them cleanly. To be safe, I'll follow the pattern: use headings that have clear, specific content. I'll make Qualifications cover what's there, and maybe not add a separate Skills section unless it adds value without redundancy. But the prompt's example list includes "Skills" as a possible heading. I'll evaluate later.
**Benefits**:
There's a big "INDK Benefits" section with specific benefits: Double Time when working designated holidays, Holiday Pay, PTO with Cash Out, 8 Federal Holidays, One Paid Personal Day, Free parking, 6% Retirement Matching 403(b), PayActiv, Employee Assistance Program, Full Health/Dental/Vision insurance options, Zero cost term life insurance, Short-term Disability, Immunizations, Tuition Assistance, Team Member referral bonus, EVEN MORE BENEFITS AVAILABLE Depending on location. This is substantial. I'll use `Benefits
` and list them.
**Pay**:
The posting doesn't mention specific pay rates, salary, or hourly wage. It says "40 hours a week" but no pay. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Pay section should not be created if not present. So I will NOT include a Pay section.
**Schedule**:
The posting starts with "40 hours a week. 10:30A-7P shifts available Monday–Friday and every other weekend needed." That's schedule information. I could include a Schedule section with that info. The rule: include a section ONLY when the posting has real, specific content for it. Schedule content is specific: "40 hours a week. 10:30A-7P shifts available Monday–Friday and every other weekend needed." I'll include a Schedule section.
**About the role**:
The company description at the end: "A Top Richmond Workplace Winner for the 7th Year in a row! ... Our mission of Enriching Life’s Journey guides our team in delivering service that focus on autonomy and self-direction..." This is about the company/role context. I could use "About the role" or maybe fold into a brief intro. The heading list includes "About the role". I'll consider if it has enough specific role content beyond general company praise. It does describe the mission and values, which relates to the role. I'll include it as "About the role" or maybe "About the company" but the heading must be from the list. I'll use `About the role
` and put the company description/mission relevant to the role. But careful: the prompt says "do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid using "About the role" if there's content. I'll include it with the company/organization mission that contextualizes the role.
Now, let's systematically extract and structure.
**Identify and remove boilerplate/duplicated/irrelevant:**
- Remove: "Hermitage Richmond Prep Cook Full-time. 40 hours a week. 10:30A-7P shifts available Monday–Friday and every other weekend needed." - This is schedule/intro, I'll use schedule content.
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate: Not present in the pasted text, good.
- Remove duplicated lines: The "Job Description" and "Job Duties" have overlapping content. I'll combine unique duties.
- Remove application instructions: Not present, good.
- Remove Vaccination Requirement? It's substantive policy info. The rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Vaccination requirement is specific company policy, not boilerplate scam warning. I think I should include it or fold it. The rule says "Remove ... legal/EEO/equal-opportunity/scam-warning boilerplate". Vaccination requirement could be considered policy, but it's specific content. I'll decide: The prompt says "Remove ... legal/EEO/equal-opportunity/scam-warning boilerplate". The vaccination requirement is a policy statement, not necessarily boilerplate. However, it might be considered similar to EEO. But it's specific to the posting. I'll include it as part of Benefits or a separate note, but need to check if it fits a heading. The allowed headings don't include "Vaccination". I could fold into Benefits or a note. But the rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should preserve it, but how to format? Maybe include in a paragraph or fold into Benefits section. I'll see. The prompt says "Output ONLY the HTML fragment". I need to decide. I'll likely include the vaccination requirement in a `
` or fold into Benefits, but since there's no specific heading, I'll put it as prose maybe after Benefits or within. Actually, looking at the heading list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Vaccination requirement doesn't fit neatly. I'll include it as part of a `
` at the end or integrate. But the rule "include a section ONLY when the posting has real, specific content for it" - the content is there, but no heading. I'll fold it into a short paragraph maybe after Benefits, or I could create a "Vaccination Requirement" section but that's not in the allowed list. The allowed headings are examples, but the rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say I'm limited to exactly those, but the spirit is to use those. I'll be safe and include vaccination requirement as a `
` after the main sections, or fold into Benefits. Actually, re-read: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The vaccination requirement is not boilerplate; it's a specific condition. I'll include it as a `
` at the end, or maybe within Benefits. I think I'll put it as a separate `
` but not a heading, since no heading fits. But the rule says "Preserve ALL
` for prose - Do NOT repeat job title as heading (already shown) - Do NOT put Job ID / requisition numbers as headings - 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 - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Deconstruct the Job Posting:** Let me extract the meaningful sections and content from the text. I need to identify: - Job title (already mentioned: "Hermitage Richmond Prep Cook Full-time") - I should NOT repeat it as a heading - Sections: About the role? Responsibilities? Requirements? Qualifications? Skills? Benefits? Pay? Schedule? - The posting has specific content for many of these, but I need to map them carefully. Let's parse the raw text: - "Hermitage Richmond Prep Cook Full-time. 40 hours a week. 10:30A-7P shifts available Monday–Friday and every other weekend needed." - "Job Description ..." (long list of duties) - "Education, Experience, Certification And Licensure Requirements" - "Job Duties" (actually overlapping with Job Description, but listed separately) - "Qualifications" - "Physical Requirements And Working Conditions" - "INDK Benefits" (a block of benefits) - "Company Description" - "Vaccination Requirement" Now, map to the requested heading format: - Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule - I need to decide which sections to include based on actual content, no placeholders. Let's map: - "About the role" - Not explicitly a separate section, but there's company description at the end. Could fold into a brief intro or "About the company" but the allowed headings are specific. The prompt says "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It doesn't say I must use all, only include when there's real content. I could use "About the role" if there's role-specific intro, or maybe skip and use company description elsewhere. Actually, the prompt says use
for section headings (e.g. About the role, Responsibilities, ...). It's giving examples of valid headings. I should use headings that match the content and are in that list. I need to be careful: "About the role" might not have dedicated content, but the company description could serve. However, the prompt says "include a section ONLY when the posting has real, specific content for it". I'll evaluate each.
Let's list content by requested heading categories:
**Responsibilities/Job Duties**:
The posting has "Job Description" and "Job Duties" sections. Both list many specific duties. I should combine them under "Responsibilities" or maybe "Job Duties". The heading options include "Responsibilities". I'll use `Responsibilities
` and list duties.
**Requirements**:
The posting has "Education, Experience, Certification And Licensure Requirements". That's clearly requirements. I'll use `Requirements
`.
**Qualifications**:
There's a "Qualifications" section. I'll use `Qualifications
`.
**Skills**:
The Qualifications section mentions: "Fundamental knowledge of general kitchen and ingredient offerings...", "Ability to learn Health Department Regulations...", "Strong ability to use and maintain kitchen equipment.", "Good communication skills." These could be skills. I could fold into Qualifications or make a separate Skills section. The prompt says "Prefer a few substantive sections over many thin ones." I need to check if Skills has enough distinct content. It does have specific skills listed. I'll consider merging or separating. Since the heading list includes "Skills", I could use it, but I need to ensure it's not filler. I'll likely include it as a subsection or merge into Qualifications. But the rule says include a section ONLY when the posting has real, specific content for it. The Qualifications section already has text; Skills could be derived but might be redundant. I'll see if I can map distinct content. The Qualifications section: "Fundamental knowledge of general kitchen and ingredient offerings to perform entry-level duties...", "Ability to learn Health Department Regulations related to food storage and preparation.", "Ability to learn Health Department Regulations related to food storage, preparation, and service.", "Strong ability to use and maintain kitchen equipment.", "Good communication skills." These are essentially qualifications/skills. I think I'll put them under Qualifications, or maybe create a Skills section if I can separate them cleanly. To be safe, I'll follow the pattern: use headings that have clear, specific content. I'll make Qualifications cover what's there, and maybe not add a separate Skills section unless it adds value without redundancy. But the prompt's example list includes "Skills" as a possible heading. I'll evaluate later.
**Benefits**:
There's a big "INDK Benefits" section with specific benefits: Double Time when working designated holidays, Holiday Pay, PTO with Cash Out, 8 Federal Holidays, One Paid Personal Day, Free parking, 6% Retirement Matching 403(b), PayActiv, Employee Assistance Program, Full Health/Dental/Vision insurance options, Zero cost term life insurance, Short-term Disability, Immunizations, Tuition Assistance, Team Member referral bonus, EVEN MORE BENEFITS AVAILABLE Depending on location. This is substantial. I'll use `Benefits
` and list them.
**Pay**:
The posting doesn't mention specific pay rates, salary, or hourly wage. It says "40 hours a week" but no pay. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Pay section should not be created if not present. So I will NOT include a Pay section.
**Schedule**:
The posting starts with "40 hours a week. 10:30A-7P shifts available Monday–Friday and every other weekend needed." That's schedule information. I could include a Schedule section with that info. The rule: include a section ONLY when the posting has real, specific content for it. Schedule content is specific: "40 hours a week. 10:30A-7P shifts available Monday–Friday and every other weekend needed." I'll include a Schedule section.
**About the role**:
The company description at the end: "A Top Richmond Workplace Winner for the 7th Year in a row! ... Our mission of Enriching Life’s Journey guides our team in delivering service that focus on autonomy and self-direction..." This is about the company/role context. I could use "About the role" or maybe fold into a brief intro. The heading list includes "About the role". I'll consider if it has enough specific role content beyond general company praise. It does describe the mission and values, which relates to the role. I'll include it as "About the role" or maybe "About the company" but the heading must be from the list. I'll use `About the role
` and put the company description/mission relevant to the role. But careful: the prompt says "do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid using "About the role" if there's content. I'll include it with the company/organization mission that contextualizes the role.
Now, let's systematically extract and structure.
**Identify and remove boilerplate/duplicated/irrelevant:**
- Remove: "Hermitage Richmond Prep Cook Full-time. 40 hours a week. 10:30A-7P shifts available Monday–Friday and every other weekend needed." - This is schedule/intro, I'll use schedule content.
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate: Not present in the pasted text, good.
- Remove duplicated lines: The "Job Description" and "Job Duties" have overlapping content. I'll combine unique duties.
- Remove application instructions: Not present, good.
- Remove Vaccination Requirement? It's substantive policy info. The rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Vaccination requirement is specific company policy, not boilerplate scam warning. I think I should include it or fold it. The rule says "Remove ... legal/EEO/equal-opportunity/scam-warning boilerplate". Vaccination requirement could be considered policy, but it's specific content. I'll decide: The prompt says "Remove ... legal/EEO/equal-opportunity/scam-warning boilerplate". The vaccination requirement is a policy statement, not necessarily boilerplate. However, it might be considered similar to EEO. But it's specific to the posting. I'll include it as part of Benefits or a separate note, but need to check if it fits a heading. The allowed headings don't include "Vaccination". I could fold into Benefits or a note. But the rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should preserve it, but how to format? Maybe include in a paragraph or fold into Benefits section. I'll see. The prompt says "Output ONLY the HTML fragment". I need to decide. I'll likely include the vaccination requirement in a `
` or fold into Benefits, but since there's no specific heading, I'll put it as prose maybe after Benefits or within. Actually, looking at the heading list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Vaccination requirement doesn't fit neatly. I'll include it as part of a `
` at the end or integrate. But the rule "include a section ONLY when the posting has real, specific content for it" - the content is there, but no heading. I'll fold it into a short paragraph maybe after Benefits, or I could create a "Vaccination Requirement" section but that's not in the allowed list. The allowed headings are examples, but the rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say I'm limited to exactly those, but the spirit is to use those. I'll be safe and include vaccination requirement as a `
` after the main sections, or fold into Benefits. Actually, re-read: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The vaccination requirement is not boilerplate; it's a specific condition. I'll include it as a `
` at the end, or maybe within Benefits. I think I'll put it as a separate `
` but not a heading, since no heading fits. But the rule says "Preserve ALL