Sous Chef Wabash College

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. We need to parse the posting. Content: - Location: Crawfordsville, IN - Pay Range: $59,000-$62,000 (note formatting: "$59.000-$62,000" but likely $59,000-$62,000) - Job Summary: Working as the Sous Chef, you will be responsible for the successful operation of the Culinary Department for a facility. You will assist in the supervision, preparation, and cooking of various food items, developing daily menu items and their preparation and garnishment. You may supervise hourly associates and you work with Executive Chef/Chef to develop new menus and assist with ordering. This is an exciting opportunity for an energetic, entrepreneurial Culinary professional. - Key Responsibilities: list bullet points: * Assists the Executive Chef with managing cost controls and control expenditures for the account * Assists the Executive Chef with planning and creating menus * Produces and execute catering events * Rolls out new culinary programs in conjunction with Company marketing and culinary team - Preferred Qualifications: list bullet points: * A.S. or equivalent experience * Some progressive culinary/kitchen management experience, depending upon formal degree or training * Catering experience a plus * High volume, complex foodservice operations experience - highly desirable * Institutional and batch cooking experiences helpful * Comprehensive knowledge of food and catering trends with a focus on quality, production, sanitation, food cost controls, and presentation * Must be experienced with computers; to include Microsoft Office (Word, Excel and Power Point), Outlook, E-mail and the Internet * Must be willing to participate in client satisfaction programs/activities * ServSafe certified - highly desirable - Benefits: "Associates at Bon Appétit are offered many fantastic benefits. Full-time and part-time positions offer the following benefits to associates: Retirement Plan, Associate Shopping Program, Health and Wellness Programs, Discount Marketplace, Identity Theft Protection, Pet Insurance, Voluntary Benefits, including Critical Illness Insurance, Accident Insurance, Hospital Indemnity Insurance, Legal Services, and Choice Auto and Home Program Full-time positions also offer the following benefits to associates: Medical, Dental, Vision, Life Insurance/AD, Disability Insurance, Commuter Benefits, Employee Assistance Program, Flexible Spending Accounts (FSAs) Associates may also be eligible for paid and/or unpaid time off benefits in accordance with applicable federal, state, and local laws." We can extract benefits list. - Pay: we have Pay Range. - Schedule: not mentioned. So we should not include Schedule section. - About the role: maybe we can use Job Summary as About the role. - Responsibilities: Key Responsibilities. - Requirements: maybe Preferred Qualifications? Could be Requirements. But we have both Requirements and Qualifications sections. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide mapping. We have content: Job Summary (About the role). Key Responsibilities (Responsibilities). Preferred Qualifications (Qualifications). Could also treat some as Requirements (maybe A.S. or equivalent experience etc). But we have both Requirements and Qualifications headings; we can split: Requirements could be mandatory items? The posting says "Preferred Qualifications:" which suggests they are preferred, not required. There's no explicit "Requirements" list. Could we treat "Preferred Qualifications" as Qualifications, and maybe we don't have a Requirements section. Or we could treat the list under Preferred Qualifications as Requirements (since they are qualifications). But we need to avoid empty sections. We also have Skills: maybe computer experience etc could be under Skills. But we could also put under Qualifications. Better to follow typical pattern: About the role (Job Summary), Responsibilities (Key Responsibilities), Requirements (maybe none), Qualifications (Preferred Qualifications), Skills (maybe computer skills), Benefits, Pay. But we must not create sections with filler like "not specified". So if we don't have content for a heading, we omit it. Thus we need to decide which headings have substantive content. - About the role: Yes (Job Summary). - Responsibilities: Yes (Key Responsibilities). - Requirements: Not explicitly listed; we could infer from Preferred Qualifications but those are preferred, not required. Might be better to omit Requirements. - Qualifications: Yes (Preferred Qualifications). - Skills: Could extract computer experience etc as skills. But we could also include under Qualifications. To avoid duplication, maybe we put computer experience under Skills. However the posting includes "Must be experienced with computers; to include Microsoft Office (Word, Excel and Power Point), Outlook, E-mail and the Internet". That's a skill. Also "Must be willing to participate in client satisfaction programs/activities" maybe a skill. But we could keep them under Qualifications. Given instruction to prefer a few substantive sections over many thin ones, we might combine Skills into Qualifications or Responsibilities. But we have separate headings allowed; we can include Skills if we have content. Let's see: we have computer experience, ServSafe certified, etc. Those are qualifications/skills. Could make a Skills section: "Proficient in Microsoft Office Suite, Outlook, email, internet; ServSafe certification; ability to participate in client satisfaction programs." But we also have other qualifications like A.S. degree, progressive experience, catering experience, high volume experience, institutional batch cooking, knowledge of trends, etc. Those are more qualifications/experience. Thus we could have: - About the role (Job Summary) - Responsibilities (Key Responsibilities) - Qualifications (Preferred Qualifications list) - Skills (Computer proficiency, ServSafe, client satisfaction) - Benefits - Pay We need to ensure we don't invent content. For Skills we must extract exactly what's stated: "Must be experienced with computers; to include Microsoft Office (Word, Excel and Power Point), Outlook, E-mail and the Internet" and "ServSafe certified - highly desirable" and "Must be willing to participate in client satisfaction programs/activities". Those are under Preferred Qualifications but we can treat them as skills. We must not add extra like "highly desirable" maybe we keep it as part of the bullet. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact phrasing? We can rephrase slightly but must keep meaning. Safer to keep the bullet points as they are. Thus for Skills we could list: - Must be experienced with computers; to include Microsoft Office (Word, Excel and Power Point), Outlook, E-mail and the Internet - ServSafe certified - highly desirable - Must be willing to participate in client satisfaction programs/activities But those are already in Preferred Qualifications list. If we put them also in Skills, we'd be duplicating content. The instruction says preserve ALL substantive information; does not forbid duplication? It says do NOT invent or summarize away detail. Duplication might be okay but could be considered redundant. Better to avoid duplication by not repeating same content in two sections. So we should decide where to place each piece. We could keep Preferred Qualifications as Qualifications section, and not have a separate Skills section. That avoids duplication. Then we have About the role, Responsibilities, Qualifications, Benefits, Pay. That's 5 sections, each substantive. Check if any content left out: Location? Not captured. Should we include location? Could be part of About the role or a separate section like "Location". But not in allowed headings. Could we put location in a paragraph under About the role? The About the role section currently is Job Summary; we could add location as a separate paragraph before or after. The instruction: Use

for section headings (e.g. 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 (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Thus we can include location as a short

  maybe before sections. It's minor metadata; we can fold into a short

  . Similarly Pay Range we need a Pay section. Thus structure:

  Location: Crawfordsville, IN

  Then

  About the role

  Job Summary text...

  Then

  Responsibilities

  • ...
  Then

  Qualifications

  • ...
  Then

  Benefits

  • ...
  (need to list benefits as items) Then

  Pay

  Pay Range: $59,000-$62,000

  We must not include Schedule. Check Benefits list: we need to extract all benefits mentioned. From text: "Full-time and part-time positions offer the following benefits to associates: Retirement Plan, Associate Shopping Program, Health and Wellness Programs, Discount Marketplace, Identity Theft Protection, Pet Insurance, Voluntary Benefits, including Critical Illness Insurance, Accident Insurance, Hospital Indemnity Insurance, Legal Services, and Choice Auto and Home Program Full-time positions also offer the following benefits to associates: Medical, Dental, Vision, Life Insurance/AD, Disability Insurance, Commuter Benefits, Employee Assistance Program, Flexible Spending Accounts (FSAs) Associates may also be eligible for paid and/or unpaid time off benefits in accordance with applicable federal, state, and local laws." We need to list each benefit as a list item. Could combine similar ones. We should preserve all substantive information; we can list each distinct benefit. Let's parse: Full-time and part-time: - Retirement Plan - Associate Shopping Program - Health and Wellness Programs - Discount Marketplace - Identity Theft Protection - Pet Insurance - Voluntary Benefits, including Critical Illness Insurance, Accident Insurance, Hospital Indemnity Insurance, Legal Services, and Choice Auto and Home Program Thus Voluntary Benefits is a category with sub-items. We could list Voluntary Benefits (including Critical Illness Insurance, Accident Insurance, Hospital Indemnity Insurance, Legal Services, Choice Auto and Home Program) as one item, or break them out. To preserve detail, we could list each. Full-time only: - Medical - Dental - Vision - Life Insurance/AD - Disability Insurance - Commuter Benefits - Employee Assistance Program - Flexible Spending Accounts (FSAs) Also paid/unpaid time off benefits per law. Thus we can create list items for each. We must not invent; we must keep exact phrasing? We can keep as given. Thus Benefits
  with many
  • . Now ensure we don't include boilerplate like EEO etc. We removed. Now produce HTML fragment. Check for any other content: "About Compass Group: Achieving leadership in the foodservice industry ..." That's boilerplate about Compass Group; we should remove as it's not specific to the role? It's about the company but could be considered boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Compass Group" paragraph might be considered boilerplate but it's not EEO etc. However it's generic company description; could be considered not substantive to the role. Safer to remove. Also "Learn more about careers with Bon Appétit: http://www.bamco.com/careers/" is a link; could be considered minor metadata; we could fold into a short p or drop. Probably drop. Also "For positions