Dietary Aide

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse job description. Content: - Job title: Dietary Aide (not to be repeated as heading) - Position Summary: The Dietary Aide performs a variety of patient food service, cafeteria food service and dish room duties, as well as catered tasks and other related tasks. The Dietary Aide is expected to provide exceptional customer service. - Work Schedule: Casual/On-call, variable start times, days, evenings, some weekend and rotated holidays. - Preferred Qualifications: High school education or equivalent preferred, but is not required, food service experience preferred. Must be able to communicate effective via the written and spoken word. Must be able to perform simple cash transactions. Demonstrates knowledge of age-related growth and development principles necessary to provide appropriate service and assure safety of patients. Servsafe certification a plus (which will be offered after the employee is hired). - About Us: description of HealthPartners. - Benefits Designed To Support Your Total Health: description of benefits. - EEO boilerplate: remove. We need sections: About the role (maybe position summary?), Responsibilities (list duties), Requirements (maybe qualifications?), Qualifications (maybe preferred qualifications?), Skills (maybe communication, cash transactions, knowledge), Benefits (benefits description), Pay (none), Schedule (work schedule). We must only include sections if posting has real specific content. We have content for: - About the role: Could be the Position Summary? Or "About Us"? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content. "About the role" could be the Position Summary (what the role does). We'll put that as prose

. "Responsibilities": list of duties: patient food service, cafeteria food service, dish room duties, catered tasks, other related tasks, provide exceptional customer service. Could be bullet list. "Requirements": maybe mandatory requirements? The posting says "Preferred Qualifications: High school education or equivalent preferred, but is not required, food service experience preferred. Must be able to communicate effective via the written and spoken word. Must be able to perform simple cash transactions. Demonstrates knowledge of age-related growth and development principles necessary to provide appropriate service and assure safety of patients. Servsafe certification a plus (which will be offered after the employee is hired)." Some are "preferred" not required. There's no explicit required qualifications besides maybe none. But we can still put Requirements as maybe none? But we should not create a section with filler. If there is no explicit required qualifications, maybe we skip Requirements. However we have "Preferred Qualifications" which could go under Qualifications section. The instruction: Use headings like Qualifications. So we can put the preferred qualifications under Qualifications. Skills: maybe communication, cash transactions, knowledge of age-related growth, Servsafe (plus). Could be list. Benefits: we have description. Schedule: we have Work Schedule. Pay: none -> omit. Thus sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Schedule. We need to ensure we don't repeat job title as heading. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: EEO, etc. We need to use

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

  for prose. Thus:

  About the role

  The Dietary Aide performs a variety of patient food service, cafeteria food service and dish room duties, as well as catered tasks and other related tasks. The Dietary Aide is expected to provide exceptional customer service.

  Responsibilities

  • Patient food service
  • Cafeteria food service
  • Dish room duties
  • Catered tasks
  • Other related tasks
  • Provide exceptional customer service

  Qualifications

  High school education or equivalent preferred (but not required); food service experience preferred.

  But also we have other qualifications like communication, cash transactions, knowledge, Servsafe. Those could be under Skills. Thus Qualifications maybe just education/experience. Alternatively we could combine all under Qualifications but better to separate. Let's put Qualifications as education/experience.

  Skills

  • Effective written and spoken communication
  • Ability to perform simple cash transactions
  • Knowledge of age-related growth and development principles to provide appropriate service and assure patient safety
  • ServSafe certification (a plus; offered after hire)

  Benefits

  As a HealthPartners colleague, we’re committed to nurturing your diverse talents, valuing your dedication, and supporting your work-life balance. We offer a comprehensive range of benefits to support every aspect of your life, including health, time off, retirement planning, and continuous learning opportunities. Our goal is to help you thrive physically, mentally, emotionally, and financially, so you can continue delivering exceptional care.

  Schedule

  Casual/On-call, variable start times, days, evenings, some weekend and rotated holidays.

  We need to ensure we didn't include any boilerplate like "About Us" description of HealthPartners. That is substantive but not covered by headings; maybe we could include under About the role? But About the role already used for position summary. The "About Us" paragraph is about the organization; could be considered part of "About the role"? Not exactly. The instruction says use headings for sections like About the role, Responsibilities, etc. It didn't forbid adding extra prose not under headings? It says 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. It doesn't say we cannot have other headings, but we should follow the given headings. The "About Us" could be considered part of "About the role"? Might be okay to include as prose under About the role? But we already used About the role for position summary. Could we expand About the role to include both position summary and about the organization? The instruction: "About the role" likely refers to description of the role. The "About Us" is about the company, not the role. However we could still include it as a separate section? Not in the list. But we could omit it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the About Us description. Where to put it? Could we create a heading like "About HealthPartners"? Not allowed per instruction? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not an exhaustive list; we could use other headings if needed, but better to stick to those. However we could incorporate the About Us description into a

    under maybe "About the role" as additional prose, but that would mix role description with company description. Might be acceptable as preserving info. Alternatively we could add a section "About the company" but not in list; risk of violating instruction? 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

    for section headings (e.g. ...). It implies we should use those headings for sections. It's safer to use only those headings. So we need to fit About Us somewhere. We could put About Us as a

    after the role summary but before Responsibilities, without a heading? The instruction says use

    for section headings, but doesn't forbid having prose without heading. It says use

    for prose. So we can have a

    without heading. That would preserve the About Us info. Thus structure:

    About the role

    Position summary...

    About Us paragraph...

    But that would have two

    under same heading; okay. Alternatively we could put About Us as its own

    before any heading. Let's do:

    About Us paragraph...

    About the role

    Position summary...

    ... But the About Us paragraph is not a heading; it's just prose. That's fine. We must ensure we don't repeat job title as heading. Now check for any other substantive info: "We are an Equal Opportunity Employer..." boilerplate to remove. Thus final HTML fragment:

    At HealthPartners we believe in the power of good – good deeds and good people working together. As part of our team, you’ll find an inclusive environment that encourages new ways of thinking, celebrates differences, and recognizes hard work. We’re a nonprofit, integrated health care organization, providing health insurance in six states and high-quality care at more than 90 locations, including hospitals and clinics in Minnesota and Wisconsin. We bring together research and education through HealthPartners Institute, training medical professionals across the region and conducting innovative research that improve lives around the world. At HealthPartners, everyone is welcome, included and valued. We’re working together to increase diversity and inclusion in our workplace, advance health equity in care and coverage, and partner with the community as advocates for change.

    About the role

    The Dietary Aide performs a variety of patient food service, cafeteria food service and dish room duties, as well as catered tasks and other related tasks. The Dietary Aide is expected to provide exceptional customer service.

    Responsibilities

    • Patient food service
    • Cafeteria food service
    • Dish room duties
    • Catered tasks
    • Other related tasks
    • Provide exceptional customer service

    Qualifications

    High school education or equivalent preferred (but not required); food service experience preferred.

    Skills

    • Effective written and spoken communication
    • Ability to perform simple cash transactions
    • Knowledge of age-related growth and development principles to provide appropriate service and assure patient safety
    • ServSafe certification (a plus; offered after hire)

    Benefits

    As a HealthPartners colleague, we’re committed to nurturing your diverse talents, valuing your dedication, and supporting your work-life balance. We offer a comprehensive range of benefits to support every aspect of your life, including health, time off, retirement planning, and continuous learning opportunities. Our goal is to help you thrive physically, mentally, emotionally, and financially, so you can continue delivering exceptional care.

    Schedule

    Casual/On-call, variable start times, days, evenings, some weekend and rotated holidays.

    Check we didn't include Pay section (omit). Good. Check we didn't include any boilerplate like EEO. Good. Check we preserved all substantive info: position summary, about us, responsibilities, qualifications (education/experience), skills (communication, cash, knowledge, Servsafe), benefits, schedule. Did we miss "Must be able to communicate effective via the written and spoken word." (we have effective written and spoken communication). "Must be able to perform simple cash transactions." (we have). "Demonstrates knowledge of age-related growth and development principles necessary to