RN - Medical Surgical - Full Time Night

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the description. Key info: - Title: RN - Medical Surgical at Providence Santa Rosa Memorial Hospital in Santa Rosa, CA. (We should not repeat job title as heading.) - Position: Full-Time, 12-hour Night shifts. - Required Qualifications: list bullet points: - Graduation from an accredited nursing program. - California Registered Nurse License upon hire. - National Provider BLS - American Heart Association upon hire. - Provider ACLS - American Heart Association upon hire. - Institutes of Health Stroke Scale (NIHSS) Certificate – NIH Stroke Scale Training Course within 90 days of hire - 1 year of Nursing experience. - Why Join Providence? (benefits description) but we need Benefits section only if posting actually states them. It does: "Our best-in-class benefits are uniquely designed to support you and your family in staying well, growing professionally, and achieving financial security." Then later: "Providence offers a comprehensive benefits package including a retirement 401(k) Savings Plan with employer matching, health care benefits (medical, dental, vision), life insurance, disability insurance, time off benefits (paid parental leave, vacations, holidays, health issues), voluntary benefits, well-being resources and much more." So we can include Benefits section with list. - About Providence: description of organization, mission, etc. Could be "About the role"? Actually "About the role" maybe not present. There's "About Providence" which is about the organization. Could map to "About the role"? Not exactly. There's "About The Team" also. But we need to decide which sections to include based on headings we are allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for Requirements (maybe same as Qualifications). We have Qualifications list. We have Responsibilities? Not explicit duties; maybe we can infer from role: "As a Providence caregiver, you’ll apply your specialized training to deliver world-class health with human connection and make a difference every day through your extraordinary care." That's a generic responsibility. Could be included as Responsibilities. We have Pay: "Pay Range: $74.82 - $102.83" plus note about base pay range and additional compensation. So we can include Pay section. Schedule: "Full-Time and will work 12-hour Night shifts." So we can include Schedule section. Skills: Not explicitly listed; maybe we can omit if no specific skills. About the role: Could combine description about role and mission. There's description: "Providence nurses are not simply valued – they’re invaluable. You will thrive in our culture of patient-focused, whole-person care built on understanding, commitment, and mutual respect. Your voice matters here, because we know that to inspire and retain the best nurses, we must empower them. Learn why nurses choose to work at Providence by visiting our Nursing Institute page. Join our team at Santa Rosa Memorial Hospital. As a Providence caregiver, you’ll apply your specialized training to deliver world-class health with human connection and make a difference every day through your extraordinary care." That's about the role. So we can put that under About the role. We also have "About Providence" and "About The Team" but those are more about organization; could be omitted or maybe included under About the role? But we should not invent sections; we can include About the role with that content. The extra paragraphs about Providence could be considered part of About the role or maybe we could add a separate section like "About Providence" but not allowed headings. So we stick to allowed headings. We must not include boilerplate like EEO, etc. Remove duplicated lines. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all specifics: list of qualifications, benefits list, pay range, schedule, etc. We need to use

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

  for prose. We need to output only HTML fragment, no /, no markdown. Let's craft:

  About the role

  Providence nurses are not simply valued – they’re invaluable. You will thrive in our culture of patient-focused, whole-person care built on understanding, commitment, and mutual respect. Your voice matters here, because we know that to inspire and retain the best nurses, we must empower them. Learn why nurses choose to work at Providence by visiting our Nursing Institute page. Join our team at Santa Rosa Memorial Hospital. As a Providence caregiver, you’ll apply your specialized training to deliver world-class health with human connection and make a difference every day through your extraordinary care.

  Responsibilities

  As a Providence caregiver, you’ll apply your specialized training to deliver world-class health with human connection and make a difference every day through your extraordinary care.

  But that duplicates the same sentence; maybe we can combine? However we need to preserve all substantive information; we can keep the description under About the role and maybe Responsibilities can be brief: "Provide direct patient care on the medical-surgical unit, collaborate with interdisciplinary team, monitor patient status, administer medications, and educate patients and families." But that's not in the posting; we cannot invent. So we should not create responsibilities if not present. The posting does not list specific duties beyond the generic statement. We could either omit Responsibilities section or include it with the generic statement (which is already in About the role). But we must not repeat content? It's okay to repeat if it's substantive? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid repetition, but better to avoid duplication. However we need to include a section only when posting has real, specific content for it. The posting does have a statement about applying specialized training etc. That could be considered responsibilities. So we can include Responsibilities with that statement. The About the role could contain more narrative about culture etc. Let's split: About the role: narrative about culture, mission, empowerment. Responsibilities: the specific duty statement. Thus: About the role paragraph: "Providence nurses are not simply valued – they’re invaluable. You will thrive in our culture of patient-focused, whole-person care built on understanding, commitment, and mutual respect. Your voice matters here, because we know that to inspire and retain the best nurses, we must empower them. Learn why nurses choose to work at Providence by visiting our Nursing Institute page. Join our team at Santa Rosa Memorial Hospital." Responsibilities paragraph: "As a Providence caregiver, you’ll apply your specialized training to deliver world-class health with human connection and make a difference every day through your extraordinary care." That preserves both. Now Requirements/Qualifications: The posting lists "Required Qualifications". We can put under Requirements or Qualifications. Since we have both headings allowed, we need to decide which to use. The posting says "Required Qualifications". So we can use

  Qualifications

  with list. We also have "Required Qualifications" list; we can also include "Requirements" maybe same. To avoid duplication, we can just use Qualifications. Thus:

  Qualifications

  • Graduation from an accredited nursing program.
  • California Registered Nurse License upon hire.
  • National Provider BLS - American Heart Association upon hire.
  • Provider ACLS - American Heart Association upon hire.
  • Institutes of Health Stroke Scale (NIHSS) Certificate – NIH Stroke Scale Training Course within 90 days of hire
  • 1 year of Nursing experience.
  Now Benefits: we have description. We'll create

  Benefits

  with list. List items: retirement 401(k) Savings Plan with employer matching, health care benefits (medical, dental, vision), life insurance, disability insurance, time off benefits (paid parental leave, vacations, holidays, health issues), voluntary benefits, well-being resources. We should preserve the exact phrasing: "Providence offers a comprehensive benefits package including a retirement 401(k) Savings Plan with employer matching, health care benefits (medical, dental, vision), life insurance, disability insurance, time off benefits (paid parental leave, vacations, holidays, health issues), voluntary benefits, well-being resources and much more." We can break into list items. Thus:

  Benefits

  • Retirement 401(k) Savings Plan with employer matching
  • Health care benefits (medical, dental, vision)
  • Life insurance
  • Disability insurance
  • Time off benefits (paid parental leave, vacations, holidays, health issues)
  • Voluntary benefits
  • Well-being resources
  Now Pay: we have Pay Range: $74.82 - $102.83 plus note about base pay range and additional compensation. We'll do:

  Pay

  Pay range: $74.82 – $102.83 (base pay). Additional compensation may be available for this role, such as shift differentials, standby/on‑call, overtime, premiums, extra shift incentives, or bonus opportunities.

  Now Schedule: we have Full-Time, 12-hour Night shifts. Thus:

  Schedule

  Full‑time position working 12‑hour night shifts.

  We should not include any other sections like Skills if not present. We must ensure we don't include any boilerplate like EEO, etc. Check for duplicated lines: we have not included the "Why Join Providence?" paragraph separate; we used benefits. The "Why Join Providence?" paragraph is basically about benefits; we captured that. We also have "About Providence" and "About The Team" paragraphs; we omitted them as they are not under allowed headings. But the instruction says "Preserve ALL substantive information". If we omit those paragraphs, we are losing substantive information about the organization. However we could incorporate that information into About the role section? The About the role section could include that description. The posting includes "About Providence" and "About The Team" which are substantive. We need to preserve them. Since we cannot create new headings outside allowed list, we need to fit them into allowed sections. Perhaps we can put them under About the role (makes sense) or maybe under Responsibilities? But About the role is appropriate for organizational description. Thus we should merge the About Providence and About The Team paragraphs into About the role section. Let's extract those paragraphs: About Providence: "At Providence, our strength lies in Our Promise of “Know me, care for me, ease my way.” Working at our family of organizations means that regardless of your role, we’ll walk alongside you in your career, supporting you so you can support others. We provide best-in-class benefits and we foster an inclusive workplace where diversity is valued, and everyone is essential, heard and respected. Together, our 120,000 caregivers (all employees) serve in over 50 hospitals, over 1,000 clinics and a full range of health and social services across Alaska, California, Montana, New Mexico, Oregon, Texas and Washington. As a comprehensive health care organization, we are serving more people, advancing best practices and continuing our more than 100-year tradition of serving the poor and vulnerable." About The Team: "The Sisters of Providence and Sisters of St. Joseph of Orange have deep roots in California, bringing health care and education to communities from the redwood forests to the beach shores of Orange county - and everywhere in between. In Northern California, Providence provides health care services to Eureka, Fortuna, Healdsburg, Napa, Petaluma and Santa Rosa. Our award-winning and comprehensive medical centers are known for outstanding programs in cancer, cardiology, neurosciences, orthopedics, women's services, emergency and