Line Cook

We need to output HTML fragment with sections: headings

for sections present: About the role? The posting includes "Job Description" and "Position Summary", "Essential Responsibilities", "Qualifications", "Why Join Lions Gate CCRC?" (benefits?), "Benefits". Also schedule and pay are given: Pay: $19.00 - $20.00 per Hour, Schedule Full-TimeEvery other weekend requiredAdditional weekday shifts based on department schedule. So we need sections for Pay and Schedule if they have real content. They do: Pay and Schedule are present. Benefits also present (list). So we will have sections: About the role? Could use "About the role" heading for the introductory paragraph after job description? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content accordingly. We need to avoid repeating job title as heading. No Job ID. We need to remove boilerplate: EEO, etc. Also remove "Company Description" maybe? It's not required but could be considered "About the role"? Actually "Company Description" is extra but we can include as part of About the role? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep company description but maybe under "About the role" or separate? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put company description under About the role. The job description includes "Join Our Culinary Team!" etc. That's about the role. So we can put that under About the role. Responsibilities: Essential Responsibilities list. Requirements: Could be Qualifications? Actually Qualifications is separate heading. Requirements maybe same as Qualifications? But we have both Qualifications and Requirements headings allowed. The posting has "Qualifications" section. We could treat that as Requirements. Or we could have both Qualifications and Requirements with same content? Better to use Qualifications heading for the qualifications list. Requirements maybe not needed if not distinct. But we can include Requirements heading with same content? Might be duplicate. Better to follow: Use Qualifications for the list of qualifications. Use Requirements maybe for any specific requirements like ServSafe certification? But it's already in qualifications. I'd just use Qualifications. Skills: Not explicitly listed; we could omit if no specific skills section. Benefits: list. Pay: $19.00 - $20.00 per Hour. Schedule: Full-TimeEvery other weekend requiredAdditional weekday shifts based on department schedule. We need to format schedule as prose maybe

. Could also be list? It's a single sentence. We need to output only HTML fragment, no /. Use

headings,

• for lists,

  for prose. We must not include filler like "commensurate with experience". Not present. We need to preserve all substantive information: include the introductory paragraphs, position summary, etc. Let's extract content: Intro: "Voorhees, NJ 08043 Posted: 08/28/2026 Employment: Full-time Pay: $19.00 - $20.00 per Hour Department: Dining Experience: Intermediate Job Description Join Our Culinary Team! Lions Gate CCRC is looking for a dependable, motivated, and experienced Line Cook to join our Dining Services team. If you enjoy preparing high-quality meals in a fast-paced, team-oriented kitchen while making a difference in the lives of older adults, we'd love to meet you! Our culinary team takes pride in providing restaurant-quality dining experiences for our residents every day." We can combine location/posted etc into a short

  maybe under About the role? Or we could put metadata in a short

  before sections. The instruction: fold minor metadata into a short

  or drop it. So we can have a

  with location, posted date, employment type, department, experience. Then About the role heading with the paragraph about joining culinary team. Then Responsibilities heading with list of essential responsibilities. Then Qualifications heading with list. Then Benefits heading with list. Then Pay heading with

  containing pay. Then Schedule heading with

  containing schedule. We should not include "Position Summary" as separate heading; we could incorporate into About the role or Responsibilities? The position summary is a paragraph describing responsibilities. Could be part of About the role or Responsibilities. To preserve all info, we could include it under About the role as well. But we already have About the role intro; we could add position summary as another

  under About the role. Alternatively, we could have a separate heading "About the role" and include both intro and position summary. Let's craft:

  Voorhees, NJ 08043 • Posted: 08/28/2026 • Employment: Full-time • Department: Dining • Experience: Intermediate

  About the role

  Join Our Culinary Team! Lions Gate CCRC is looking for a dependable, motivated, and experienced Line Cook to join our Dining Services team. If you enjoy preparing high-quality meals in a fast-paced, team-oriented kitchen while making a difference in the lives of older adults, we'd love to meet you! Our culinary team takes pride in providing restaurant-quality dining experiences for our residents every day.

  The Line Cook is responsible for preparing and cooking meals according to standardized recipes while maintaining the highest standards of food quality, safety, sanitation, and customer service. This position works closely with the culinary team to ensure meals are prepared efficiently and served in a timely manner.

  Responsibilities

  • Prepare breakfast, lunch, and dinner items according to standardized recipes and production schedules.
  • Set up and stock the cook line with ingredients, supplies, and utensils before each meal service.
  • Prepare food in accordance with established portion sizes and presentation standards.
  • Follow production screens and meal counts to ensure accurate meal preparation.
  • Maintain quality, consistency, and food safety throughout meal service.
  • Work efficiently during busy meal periods while maintaining attention to detail.
  • Communicate effectively with servers and other kitchen staff to ensure excellent resident service.
  • Assist with food preparation, cooking, and plating as needed.
  • Follow all sanitation, food handling, and infection control procedures.
  • Maintain a clean and organized workstation using a "clean as you go" approach.
  • Complete daily cleaning assignments and assist with kitchen closing duties.
  • Properly label, store, rotate, and date food items following food safety guidelines.
  • Help minimize food waste while maintaining quality standards.
  • Maintain and follow the dietary laws required to support our Kosher community.
  • Perform other duties as assigned by the Dining Services leadership team.

  Qualifications

  • High school diploma or GED preferred.
  • One to three years of experience as a line cook, prep cook, or cook in a restaurant, healthcare, senior living, hotel, or similar food service environment.
  • ServSafe Certification is preferred (or willingness to obtain).
  • Knowledge of safe food handling and sanitation practices.
  • Ability to work efficiently in a fast-paced kitchen.
  • Strong teamwork and communication skills.
  • Dependable with excellent attendance.
  • Ability to stand for extended periods and safely lift up to 50 pounds.

  Benefits

  • 403(b) Retirement
  • Medical Insurance
  • Dental Insurance
  • Vision Plan
  • Paid Holidays
  • Paid Time Off (PTO)
  • Health Insurance Waiver
  • Life Insurance
  • MetLaw

  Pay

  $19.00 - $20.00 per Hour

  Schedule

  Full-Time • Every other weekend required • Additional weekday shifts based on department schedule

  Check: we omitted "Company Description". That's substantive but not covered by headings. Could we include it under About the role as another paragraph? The company description is about Lions Gate CCRC. It's substantive. We should preserve it. We can add another

  under About the role after the position summary, or maybe a separate heading "About the company"? Not allowed headings list but we could still include as a paragraph under About the role? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to add other headings but better to stick to allowed. We can incorporate company description into About the role as a paragraph. Add after position summary: another

  with company description. Let's extract company description: "Lions Gate is a not-for-profit continuing care retirement community rooted in Jewish traditions and values. A home to seniors who share a passion for the things that matter – lifestyle, care, community, and tradition – to those who share a passion for life and all its possibilities. Here at Lions Gate, we have created a high standard of living for all of our residents. We are committed to honoring the programs and traditions of the Jewish faith in our community. Our employees reflect this commitment through their warm and loving nature in providing care and services to all those that reside at Lions Gate. By becoming part of the Lions Gate community and committing yourself to the care and comfort of each and every resident we serve, we assure you that your life will also be enriched in many ways." Add as

  . Now check for any other substantive info: "Why Join Lions Gate CCRC?" section includes bullet points: Competitive pay, Full-time, stable schedule, Supportive team environment, Opportunity to make a meaningful impact..., Beautiful senior living community, Opportunities for growth and advancement. This is essentially benefits/attributes. We already have Benefits section (list of specific benefits). The "Why Join" could be considered part of Benefits or maybe a separate section like "Why Join". But we already have Benefits list; we could incorporate those points into Benefits as additional list items. However the instruction: Prefer a few substantive sections over many thin ones. We could merge them into Benefits. But we already have Benefits list of specific offerings; we could add those as list items as well. However the "Why Join" includes Competitive pay (already covered in Pay), Full-time stable schedule (Schedule), Supportive team environment, Opportunity to make a meaningful impact..., Beautiful senior living community, Opportunities for growth and advancement. Some are overlapping with existing sections. To preserve all info, we could add them as list items under Benefits, but we risk duplication. Better to add a separate section "Why Join Lions Gate CCRC?" but heading not in list; but we could still use

  for it? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings. We could incorporate the "Why Join" points into Benefits as additional items, but we should avoid duplication. We could add items like "Supportive team environment", "Opportunity to make a meaningful impact in the lives of our residents", "Beautiful senior living community", "Opportunities for growth and advancement". Those are not already in Benefits list. So we can add them. Thus Benefits list will include: 403(b) Retirement, Medical Insurance, Dental Insurance, Vision Plan, Paid Holidays, Pa