Food Services Tier 1 Cook (full-time)

We need to output HTML fragment with sections: headings

for sections like 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. 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. We need to parse the posting. Given: POSITION: FOOD SERVICE COOK LOCATION: Nashua High School North WORK YEAR: 2026-2027 School Year (7 hours per day) SALARY RANGE: Depending on experience and/or SNA Certification, Minimum starting salary $18.94 per hour with Benefits per Union Contract Qualifications Prior experience in quantity cookery and/or child nutrition programs required. Must be physically capable of performing duties which include the ability to walk, bend and stand for long periods of time, and lift and carry objects weighing a minimum of 50 pounds. Knowledge of local, state and federal statutes pertaining to school meal requirements; operation and care of kitchen equipment; state and local regulations as they relate to health and food safety issues; computer literacy desirable. Good verbal and written communications skills are desired. Summary Of Responsibilities Assures implementation of current safety and health practices, reports discrepancies to site coordinator, proficiency in use, operation and cleaning of all kitchen equipment, directs efforts of food service assistants on a daily basis, overseas each work station set up and service, supervises daily clean up of food service areas and equipment, assists the site coordinator with required records, and reports and work schedules, responsible for the operation decisions in the absence of the site coordinator, orients and trains all new food service assistants, advises site coordinator on staffing needs when regular employees are absent, assists the site coordinator to insure compliance with USDA standards and reporting requirements, monitors food and supply inventories and provides order information to the site coordinator as needed, assists the site coordinator with menu development and selection of food items offered, assists the site coordinator with catering needs for special functions utilizing the Food Service area, performs other duties pertaining to food service as necessary. This posting should not be construed to imply that this is the exclusive list of job functions or expectations associated with this position. Application Procedure Interested Applicants should apply online at www.nashua.edu. Then EEO boilerplate. We need to remove application instructions and EEO boilerplate. We need to preserve all substantive info: position, location, work year, salary range, qualifications, responsibilities. We need to decide sections: maybe "About the role" (could include position, location, work year). "Responsibilities" (list). "Qualifications" (list). "Pay" (salary range). "Schedule" (work year/hours). "Benefits" (mentioned: with Benefits per Union Contract). Actually "Benefits per Union Contract" is mentioned in salary range line. So we can include Benefits section. We must not create sections with filler. So we need actual content. We need to use

  for each section heading. We need to use

  • for any list of duties/requirements/benefits. For prose use

    . We need to avoid repeating job title as heading. So we will not have a heading "FOOD SERVICE COOK". We'll embed that info maybe in About the role. We need to preserve all substantive info: location, work year, salary range, qualifications, responsibilities, benefits. We need to decide what goes where. Potential sections: - About the role: could contain position title, location, work year (maybe as a paragraph). Could also include brief summary? But we must not invent. We can put:

    Position: Food Service Cook at Nashua High School North. Work year: 2026-2027 School Year (7 hours per day).

    - Responsibilities: list each duty from Summary Of Responsibilities. We need to split into list items. The responsibilities are a long sentence separated by commas. We can break at each comma? Better to keep as list items each duty. We'll parse: "Assures implementation of current safety and health practices", "reports discrepancies to site coordinator", "proficiency in use, operation and cleaning of all kitchen equipment", "directs efforts of food service assistants on a daily basis", "oversees each work station set up and service", "supervises daily clean up of food service areas and equipment", "assists the site coordinator with required records, and reports and work schedules", "responsible for the operation decisions in the absence of the site coordinator", "orients and trains all new food service assistants", "advises site coordinator on staffing needs when regular employees are absent", "assists the site coordinator to insure compliance with USDA standards and reporting requirements", "monitors food and supply inventories and provides order information to the site coordinator as needed", "assists the site coordinator with menu development and selection of food items offered", "assists the site coordinator with catering needs for special functions utilizing the Food Service area", "performs other duties pertaining to food service as necessary". Also note "overseas" is typo for "oversees". We'll keep as is? Probably keep original text but correct? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should not correct typos? It's ambiguous. Usually we keep as is. But "overseas" is likely a mistake; but we should preserve as given. We'll keep "overseas". However it's weird. We'll keep exactly as in text: "overseas each work station set up and service". We'll keep. We need to ensure we don't lose any content. - Qualifications: list each qualification. We have bullet-like sentences. We'll make list items: 1. Prior experience in quantity cookery and/or child nutrition programs required. 2. Must be physically capable of performing duties which include the ability to walk, bend and stand for long periods of time, and lift and carry objects weighing a minimum of 50 pounds. 3. Knowledge of local, state and federal statutes pertaining to school meal requirements; operation and care of kitchen equipment; state and local regulations as they relate to health and food safety issues; computer literacy desirable. 4. Good verbal and written communications skills are desired. We could also combine some but keep as list. - Pay: Salary range: "Depending on experience and/or SNA Certification, Minimum starting salary $18.94 per hour with Benefits per Union Contract". That's the pay info. We'll put in

    . - Benefits: The phrase "with Benefits per Union Contract" indicates benefits exist per union contract. Could we create a Benefits section? The posting mentions benefits but not details. It says "with Benefits per Union Contract". That's substantive: indicates benefits are provided per union contract. We could create a Benefits section with that statement. However we must not create a Benefits section unless posting actually states them. It does state "with Benefits per Union Contract". So we can include Benefits section with that sentence. - Schedule: Work year: "2026-2027 School Year (7 hours per day)". That's schedule info. We'll create Schedule section. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown. We'll structure:

    About the role

    Position: Food Service Cook at Nashua High School North. Work year: 2026-2027 School Year (7 hours per day).

    But we already have schedule separate; maybe we shouldn't duplicate work year in About the role if we have Schedule section. However About the role could include position and location only. Let's think: The instruction: Prefer a few substantive sections over many thin ones. So we could combine About the role (position, location) and maybe schedule? But schedule is separate info; we could include schedule in About the role to reduce sections. However we need to include schedule info somewhere; we could put it in About the role. But we also have Benefits and Pay separate. Let's see. We could have sections: About the role (position, location, work year), Responsibilities, Qualifications, Pay, Benefits. That's 5 sections. Could we combine Pay and Benefits? Possibly but they are distinct. The instruction: prefer a few substantive sections over many thin ones. 5 is okay. Alternatively we could have About the role (position, location), Responsibilities, Qualifications, Pay & Benefits (combined), Schedule. But schedule is separate. We need to ensure we don't create sections with filler. All sections will have real content. Let's decide: - About the role: position and location. - Responsibilities: list. - Qualifications: list. - Pay: salary range. - Benefits: union contract benefits. - Schedule: work year and hours. That's 6 sections. Might be okay but maybe we can combine Pay and Benefits? The posting says "Minimum starting salary $18.94 per hour with Benefits per Union Contract". That's both pay and benefits together. Could we make a single section "Compensation" (but we only allowed headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We cannot use "Compensation". We could use Pay and Benefits separate but they are both in same sentence. Could we put Pay section with that sentence and Benefits section maybe empty? Not allowed. Better to combine them into Pay section and omit Benefits section because benefits are mentioned as part of pay line. However the instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (with Benefits per Union Contract). So we could create Benefits section with that phrase. But then Pay section would have salary range only. That's okay. But we might be creating thin sections: Pay: "$18.94 per hour" (short). Benefits: "with Benefits per Union Contract" (short). That's thin but still substantive. The instruction says prefer a few substantive sections over many thin ones. Could we combine Pay and Benefits into one section labeled "Pay"? But we cannot rename heading; we must use allowed headings. We could use Pay heading and include both salary and benefits info in that section. That would be one Pay section with both. Then we wouldn't need Benefits section. That seems better: we avoid thin Benefits section. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't forbid combining them into Pay. So we can have Pay section containing both salary and benefits. That's substantive enough. Similarly, Schedule: we have work year and hours. That's substantive. Thus sections: About the role, Responsibilities, Qualifications, Pay, Schedule. Now we need to ensure we include all info. About the role: position and location. Could also include brief summary? Not needed. Responsibilities: list. Qualifications: list. Pay: "Depending on experience and/or SNA Certification, Minimum starting salary $18.94 per hour with Benefits per Union Contract." Schedule: "2026-2027 School Year (7 hours per day)." We must not repeat job title as heading; we are not. We must not put Job ID/requisition numbers as headings; none. We must remove application instructions and EEO boilerplate. Now format. We need to use

    for each section heading.