Assistant Cook

We need to output HTML fragment with sections: About the role? Actually we have company description and job description. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. We have: - Company Description: could be "About the role"? Actually "Company Description" is about Harvard University Central Administration. Could map to "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have job description details: responsibilities (list of duties). We have qualifications (basic qualifications, additional qualifications). We have skills (maybe part of qualifications). We have benefits described. We have pay (Compensation Range/Rate). We have schedule (Standard Hours/Schedule). Also physical requirements maybe part of qualifications? Could be under Requirements? But we have separate "Requirements" heading maybe for qualifications? We'll decide. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, etc. Also remove navigation, legal, etc. Remove duplicated lines. Also remove "Work Format Details", "Salary Grade and Ranges", "Visa Sponsorship Information", "Pre-Employment Screening", etc? Those are maybe minor metadata; we can fold into short p or drop. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a short p for things like visa sponsorship, pre-employment screening, work format, etc. But we should not create sections for them unless they have real specific content. Probably better to drop them or include in a short p under maybe "Additional Information". But we are limited to headings list; we could add a

after sections for misc. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all duties, qualifications, benefits, pay, schedule, physical requirements, etc. We need to use

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

  for prose. Thus: - Section About the role: maybe a

  summarizing company description? But we must not invent or summarize away detail. We could keep the company description as prose in a

  under About the role. That is okay. - Responsibilities: list of duties from "Prepares and cooks menu items..." etc. That's a long list; we can put each sentence as

• . - Requirements: maybe physical requirements? Or "Basic Qualifications"? Actually "Qualifications" heading is separate. The instruction includes both Requirements and Qualifications as possible headings. We need to decide what goes where. Usually Requirements are things like education, experience, certifications. Qualifications could be skills. But we have both Basic Qualifications and Additional Qualifications and Skills. We could treat "Requirements" as the basic qualifications (education, experience, etc.) and "Qualifications" as additional qualifications and skills. Or we could combine. But we must not create empty sections. We have content for both. Let's map: - Requirements: Basic Qualifications (High School Diploma, English proficiency, three years experience, culinary ability, basic math skills, proficiency with kitchen tools, knife skills, follow directions, neat appearance, work independently/team, multi-tasking, communication, cooperative, fast-paced, customer service). Also maybe physical requirements? Could be under Requirements as well. - Qualifications/Skills: Additional Qualifications and Skills: ServSafe certification within first year, previous university experience preferred. Also maybe skills like "knowledge of HACCP", "clean as you go", etc. But those are in responsibilities. We'll keep Additional Qualifications and Skills as a list. - Skills: maybe we could separate but we have limited headings; we could put skills under Qualifications. But we have both Qualifications and Skills headings available; we could put Additional Qualifications under Qualifications, and maybe specific skills like "knife skills", "multi-tasking", etc under Skills. However we already have those in Basic Qualifications. Might be redundant. Better to follow typical pattern: Requirements = education, experience, certifications; Skills = abilities like communication, teamwork, etc. But we have many overlapping. Given the instruction: "Prefer a few substantive sections over many thin ones." So we should not create many sections with little content. We have enough content for About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. That's 7 sections. Skills maybe thin; we could omit Skills section and put skills under Qualifications or Requirements. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Now we need to ensure we don't include headings with filler like "commensurate with experience". We have specific content. Now we need to format. Let's extract content precisely. Company Description paragraph: "By working at Harvard University, you join a vibrant community that advances Harvard's world-changing mission in meaningful ways, inspires innovation and collaboration, and builds skills and expertise. We are dedicated to creating a diverse and welcoming environment where everyone can thrive. Why join Harvard University Central Administration? Harvard University's Central Administration (CADM) is a 5,000+ employee organization that supports the university's overall excellence by understanding and serving the needs of its schools, students, faculty, staff, alumni, and surrounding communities. Through dynamic and collaborative partnerships, CADM provides high-quality and efficient services to the schools to help them achieve their goals." We'll put that as a

  under About the role. Responsibilities: list each duty sentence from "Prepares and cooks menu items according to proper preparation methods in small batches and/or as required by business needs." through "Performs other duties as assigned." Let's copy them: - Prepares and cooks menu items according to proper preparation methods in small batches and/or as required by business needs. - Tastes and evaluates all food before service to ensure food quality standards are met, consults manager with any concerns. - Reads and follows standardized recipes. - Fries, grills, sautés, roasts, bakes, braises and steams food products as needed. - Heats soups, sauces and prepared products ensuring product has reached appropriate temperature before serving. - Carves or slices meat for service both in back-of-house setting and at carving stations in front-of- house setting when necessary. - Assists in the preparation and presentation of catered functions. - Cools, refrigerates, labels and properly stores food according to HACCP procedures. - Knowledgeable in use of all standard kitchen equipment. - Demonstrates a “Clean as you go” philosophy maintaining sanitary and organized work space and equipment. - Leaves work station clean and re-stocked. - Accurately records portion amount of food used during meals on service records. - Accurately measures food temperatures. - Recycles products per policy and procedure. - Accurately fills out sanitation and temperature logs and food service records as required. - Informs person in charge when corrective action is needed. - Follows sanitation standards in compliance with all regulatory agencies including Harvard Environmental Health and Safety regulations. - Complies with State of Massachusetts and Dining Services’ “Food Employee Illness Policy”. - Communicates effectively and works cooperatively and respectfully with a diverse set of staff, management team and guests - Represents HUDS to students, faculty, staff and guests in a positive and professional manner. - Works to meet the mission and core values of Harvard University Dining Services with enthusiasm and a spirit of cooperation. - Attends trainings as assigned. - Maintains current certifications as required. - Performs other duties as assigned. Note: Some lines have line breaks; we will treat each as

• . Now Requirements: Basic Qualifications list: - High School Diploma or equivalent - Must have proficiency with the English language (speaking, reading and writing). - Minimum three years of relevant food preparation experience in hospitality industry. - Must have culinary ability to execute recipes with the technical understanding of all cooking methods. - Must have basic math skills and ability to analyze digital and analog thermometers, scales, and other measuring devices. - Must have proficiency with kitchen tools and equipment without restrictions - Must have relevant knife skills. - Must be able to follow directions. - Must be neat in appearance and comply with proper dress code as designated by HUDS. - Must be able to work independently and as part of a team. - Must have strong multi-tasking skills. - Must have excellent communication skills. - Must be able to work cooperatively and respectfully with a diverse set of staff, management and guests. - Must be able to work in a fast-paced diverse environment. - Must be customer service oriented. Also Physical Requirements: Could be under Requirements as well. Let's include them as part of Requirements maybe as a sublist? But we need to use
  • for any list. We could have a separate
    for physical requirements under Requirements heading. Or we could add a

    describing physical requirements. But we have list items: "Must be able to routinely lift 50 lbs. without restrictions", "Continuous: standing, manual dexterity, reaching, walking, lifting, handling", "Frequent: push/pull, bending", "Occasional: climbing, squatting, sitting". We'll treat each as

    • . Thus Requirements section will have two lists? Could combine into one list with all items. That's fine. Now Qualifications: Additional Qualifications and Skills: - ServSafe certification within first year of employment. - Previous experience in a University environment preferred. We could also include any other skills like "knowledge of HACCP" but that's in responsibilities. We'll keep this as Qualifications. Now Benefits: list from "Generous paid time off including parental leave" etc. Benefits list: - Generous paid time off including parental leave - Medical, dental, and vision health insurance coverage starting on day one - Retirement plans with university contributions - Wellbeing and mental health resources - Support for families and caregivers - Professional development opportunities including tuition assistance and reimbursement - Commuter benefits, discounts and campus perks We'll put as
      • . Pay: Compensation Range/Rate: "28.09 - 29.83" (presumably per hour). Also note "including Shift Differential if applicable". We'll include that as

        maybe. Schedule: Standard Hours/Schedule: "40 hours per week Sunday, Monday, Tuesday, Wednesday & Saturday 10:45am - 7:45pm". We'll put as

        . Now we need to exclude boilerplate: EEO, etc. Also remove "Work Format Details", "Salary Grade and Ranges", "Visa Sponsorship Information", "Pre-Employment Screening", etc. However we might want to keep visa sponsorship info as a short p? The instruction: fold minor metadata into a short

        or drop it. Visa sponsorship is minor metadata; we could include a short p under maybe after Schedule? But we should not create a heading for it. We could add a

        after the sections: "Harvard University is unable to provide visa sponsorship for this position." Similarly "Pre-Employment Screening: Identity, Criminal, Drug Test, and References." and "Work Format Details: This position has been determined by school or unit leaders that all duties and responsibilities must be performed at a Harvard or Harvard-designated location. Certain visa types may limit work location. Individuals must meet work location sponsorship requirements prior to employment." That's a bit longer but still metadata. We could drop them to keep concise. The instruction says preserve ALL substantive information; is visa sponsorship substantive? It's about eligibility; maybe considered substantive. But it's minor metadata; we could fold into a short p. Let's include a short p after the sections: maybe under a generic "Additional Information" but we don't have heading for that. We could just add a

        after the last section without a heading. That's allowed? The instruction says output ONLY the HTML fragment; we can