Unit Manager

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 job title as heading. Do NOT put Job ID etc. Remove boilerplate: Equal Opportunity Employer etc. Also remove navigation/legal/EEO etc. Also remove duplicated lines. Preserve all substantive info. We have content: - Duties: list of duties: - Handle all supervisory duties for assigned unit - Help establish and implement employee policies and procedures - Mentor less experienced nurses, offering clinical & career advice - Maintain the standards of care for the unit - Review Resident records & quality of care - Monitor overall care & review individual Residents’ cases - Address questions or complaints brought forward by Residents or their families - Represent the unit's interests with the upper-level management - Requirements: - Must hold valid State RN License - 3 years Long Term Care Experience preferred - 2 years Charge Nurse experience preferred - Strong computer skills - Excellent communication skills - About Us: description of Steuben Center. - Benefits: "premium compensation, a comprehensive benefits package, professional growth & stability, innovative training programs, and more." This is benefits. - Pay: Not explicitly given. There's "premium compensation" but not a specific number. According to instructions: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits: they mention "comprehensive benefits package" and "premium compensation". That's somewhat vague but still mentions benefits. Should we include Benefits section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." They state "premium compensation, a comprehensive benefits package, professional growth & stability, innovative training programs, and more." That's a statement about benefits/compensation. So we can include Benefits section with that content. Pay: they didn't give a specific pay figure, just "premium compensation". That's vague; maybe we should not create Pay section because it's not a specific number. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It says "states them" meaning they actually state pay/schedule/benefits. They state benefits (comprehensive benefits package) and premium compensation (which is pay). But "premium compensation" is vague but still states compensation. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." I'd interpret that we should include Benefits because they mention benefits package. Pay maybe not needed because it's not a specific figure; but they said "premium compensation". Might be okay to include Pay with that phrase? But risk of being considered filler? The phrase "premium compensation" is substantive? It's a statement about pay being premium. Could be considered substantive. However they also said "Prefer a few substantive sections over many thin ones." Might combine Pay and Benefits into one Benefits section? But they want separate headings for Benefits, Pay, Schedule if present. Since we have benefits info, we can include Benefits section. Pay maybe we can omit because it's not a specific number; but they said "premium compensation" which is a statement about pay. I'd include Pay section with that phrase? However the instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." They do state "premium compensation". So we could include Pay section with that phrase. But we need to avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "premium compensation" is not filler; it's a statement. So we can include Pay. Schedule: Not mentioned. So no Schedule section. Now we need to output HTML fragment with headings

  for each section: About the role? Actually they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The posting has "Duties" and "Requirements" and "About Us". We could map Duties to Responsibilities heading. Requirements to Requirements heading. About Us to About the role? Actually About Us is about the company, not the role. But they said About the role as example; we could use About the role for description of role? But we have About Us describing the facility. Could we use About the role heading for that? Might be okay. However we could also create a section "About the facility" but not in list. The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those headings if applicable. So we should use those exact headings when we have content. For About Us, we could use About the role? But that's not exactly about the role. However we could treat About Us as About the role? Might be misaligned. But we could also not include a heading for About Us and just put it in a

  without heading? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must only use those headings, but they are examples. It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings for sections we have. For About Us, we could use About the role heading but maybe better to use About the role as heading for the description of the role? But we have no role description besides duties. The About Us is about the facility. Could we treat it as About the role? Not ideal but maybe acceptable. Alternatively we could not include a heading for About Us and just put it in a

  after a heading? But they'd want headings for sections. I'd include a heading "About the role" and put the About Us content there. However the About Us content is about the facility, not the role. But maybe it's okay. Alternatively we could create a heading "About the facility" but not in examples; but they didn't forbid other headings. They said use

  for section headings (e.g. ...). So we can use any heading, but they gave examples. I think it's safe to use About the role for the About Us paragraph. Thus sections: - Responsibilities (h3) with ul of duties. - Requirements (h3) with ul of requirements. - Benefits (h3) with ul? Benefits is a list: premium compensation, comprehensive benefits package, professional growth & stability, innovative training programs, and more. Could be ul. - Pay (h3) with p containing "premium compensation". But we already have premium compensation in Benefits; maybe we should not duplicate. Actually Benefits already includes premium compensation. So we could omit Pay section to avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So combine compensation into Benefits. So we will not create Pay section. Thus sections: Responsibilities, Requirements, Benefits. We also need to include location? The posting says "Steuben Center is hiring a Registered Nurse (RN) Unit Manager in Bath, NY." That's location info. Should we include that? It's substantive. Where to put? Could be in a

  after a heading? Maybe we can include a short paragraph under Responsibilities? Or we could create a heading "About the role" and include location there. But we already used About the role for About Us. Hmm. We could treat the first sentence as a brief intro: "Steuben Center is hiring a Registered Nurse (RN) Unit Manager in Bath, NY." This is location and job title. Since we cannot repeat job title as heading, we can put this as a

  before sections. That seems appropriate. Thus output:

  Steuben Center is hiring a Registered Nurse (RN) Unit Manager in Bath, NY.

  Then

  Responsibilities

  ...
  Then

  Requirements

  ...
  Then

  Benefits

  ...
  We need to preserve all substantive information: duties list, requirements list, about us description, benefits description. We must not include boilerplate: Equal Opportunity Employer etc. We must not include navigation/legal/EEO etc. We must not include duplicated lines. Check About Us content: "Steuben Center for Rehabilitation and Healthcare has been the provider of long-term care services in Steuben County since 1834. Formerly known as "The Infirmary" the facility is located in the county seat of Steuben County, nestled between Bath and Hammondsport. The focus of care is to provide quality health care with respect for the individual’s dignity in a homelike environment utilizing the collective talents of those who live, work, and visit the facility. At Steuben Center, we offer a friendly and warm working environment, premium compensation, a comprehensive benefits package, professional growth & stability, innovative training programs, and more. Steuben Center is a proud member of the Centers Health Care consortium." We need to preserve all that. We'll put that in a

  under About the role heading? Or we could make a heading "About the facility" but we don't have that in examples. However we could still use

  About the facility

  . The instruction didn't forbid other headings; they just gave examples. So we could use About the facility heading. That seems more accurate. Let's do that. Thus sections: - About the facility (h3) with the About Us paragraph. - Responsibilities (h3) with duties list. - Requirements (h3) with requirements list. - Benefits (h3) with benefits list (premium compensation, comprehensive benefits package, professional growth & stability, innovative training programs, and more). Note that premium compensation appears also in About Us; but we can still include it in Benefits. We need to avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep the premium compensation mention in About Us as well. It's okay to have it appear in both places if it's in the original text. However About Us already includes that phrase; Benefits also includes it. That's duplication but it's present in original? Actually the original About Us includes "premium compensation, a comprehensive benefits package, professional growth & stability, innovative training programs, and more." That's exactly the benefits list. So the Benefits section is essentially repeating that phrase. If we create a Benefits section, we would be duplicating the same text. But we could avoid duplication by not creating a separate Benefits section and just keep that sentence in About Us. However the instruction says to create Benefits section only if posting actually states them. It does state them, but they are already in About Us. We could still create a Benefits section with that same content; it's not inventing, it's just repeating. Might be okay but could be considered redundant. The instruction: "Prefer a few substantive sections over many thin ones." Having a Benefits section that just repeats the same sentence might be thin. Better to keep it in About Us and not create a separate Benefits section. However we still need to capture the benefits info; it's already in About Us. So we can omit a separate Benefits section. Thus sections: About the facility, Responsibilities, Requirements. We need to ensure we include all substantive info: The About Us paragraph includes the benefits info. So we are good. Thus final HTML:

  Steuben Center is hiring a Registered Nurse (RN) Unit Manager in Bath, NY.

  About the facility

  Steuben Center for Rehabilitation and Healthcare has been the provider of long-term care services in Steuben County since 1834. Formerly known as "The Infirm