Registered Nurse / RN - Med Surg Neuro

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include only sections with real specific content. We need to parse the posting. Posting content: "Our client is looking to add a Registered Nurse to their team. Job Details: Location: St. Louis, MissouriDuration: 13 WeeksStart Date: 07/06/2026Shift: 3x12 NightsEstimated Gross Weekly Pay: $1,886 Qualifications: Current Missouri license Excellent interpersonal skills including patience, empathy, and compassion Effective communication skills, including active listening, writing, speaking and reading comprehension Fast and adaptive problem-solving abilities Ability to stand for long periods of time If you meet the required qualifications and are interested in this role, please apply today. Why Work with Us The success of Solomon Page is defined by our people. Offering a comprehensive benefits package, travel nurses have immediate access to medical coverage and ReviveHealth virtual care. Additionally, you are offered access to dental and vision coverage, commuter benefits, a 401(k) plan, flexible spending, referral bonuses, ongoing training, and more. As an ESOP company, Solomon Page offers an employee stock ownership plan to all consultants. As a member of our traveler community, you will join a nurturing culture that fosters your career goals. Solomon Page can connect you with your next opportunity – whether it is in your hometown, or you are looking to travel to a new destination. About Solomon Page Healthcare & Medical Staffing Accredited by the Joint Commission with the Gold Seal of Approval, Solomon Page prides ourselves in developing long-term relationships with healthcare providers based on trust and respect. Our experienced Healthcare and Medical Staffing experts are committed to providing safe and quality patient care through our wide network of travel nurses, locum tenens, and allied resources. For more information and additional healthcare opportunities, visit: solomonpage.com and connect with Solomon Page on Instagram, Facebook, Twitter, LinkedIn, and TikTok. 452009" We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The line "If you meet the required qualifications and are interested in this role, please apply today." is application instruction, should be removed. Also "Why Work with Us" is a heading but we need to map to appropriate sections: Benefits maybe. "About Solomon Page Healthcare & Medical Staffing" is about the company, could be "About the role"? Actually "About the role" is for role description. The posting includes location, duration, start date, shift, pay. Those could be in a "Job Details" but we need to map to sections: maybe "About the role" includes location, duration, start date, shift? Or we could have separate sections: "Pay" and "Schedule". The rules: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create sections that match content. We have: - Qualifications: list of qualifications (Current Missouri license, interpersonal skills, communication skills, problem-solving, ability to stand). That's a list. - Benefits: described in "Why Work with Us": comprehensive benefits package, medical coverage, ReviveHealth virtual care, dental and vision coverage, commuter benefits, 401(k) plan, flexible spending, referral bonuses, ongoing training, ESOP employee stock ownership plan, nurturing culture, career goals, connecting to next opportunity. That's benefits. - Pay: Estimated Gross Weekly Pay: $1,886. - Schedule: Shift: 3x12 Nights. - Location, Duration, Start Date: Could be part of "About the role" maybe. Or we could create a section "About the role" containing location, duration, start date. - Responsibilities: Not explicitly given. The posting does not list responsibilities. So we should not create a Responsibilities section if no specific content. - Requirements: Might overlap with qualifications. But we have qualifications already. Could also have "Requirements" but we already have qualifications. The rule: prefer a few substantive sections over many thin ones. So we can combine qualifications and requirements into one "Qualifications" section. Or we could have "Requirements" separate but we don't have distinct requirements beyond qualifications. So we will have Qualifications. - Skills: Could be part of qualifications (interpersonal, communication, problem-solving). But we could also have a Skills section. However we already have qualifications covering skills. To avoid thin sections, we can keep Qualifications only. Thus sections: About the role (location, duration, start date), Qualifications, Benefits, Pay, Schedule. We must not include headings with filler like "commensurate with experience". Not applicable. We need to output only HTML fragment, no /, no markdown fences. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract details: About the role: Location: St. Louis, Missouri; Duration: 13 Weeks; Start Date: 07/06/2026. Possibly also shift? But shift goes to Schedule. We could phrase as prose: "Location: St. Louis, Missouri. Duration: 13 Weeks. Start Date: July 6, 2026." Keep as is. Qualifications: list: - Current Missouri license - Excellent interpersonal skills including patience, empathy, and compassion - Effective communication skills, including active listening, writing, speaking and reading comprehension - Fast and adaptive problem-solving abilities - Ability to stand for long periods of time We need to keep exact phrasing? Preserve all substantive information; do not invent or summarize away detail. So we should keep the phrases as they appear. Could be list items. Benefits: from "Why Work with Us": Offering a comprehensive benefits package, travel nurses have immediate access to medical coverage and ReviveHealth virtual care. Additionally, you are offered access to dental and vision coverage, commuter benefits, a 401(k) plan, flexible spending, referral bonuses, ongoing training, and more. As an ESOP company, Solomon Page offers an employee stock ownership plan to all consultants. As a member of our traveler community, you will join a nurturing culture that fosters your career goals. Solomon Page can connect you with your next opportunity – whether it is in your hometown, or you are looking to travel to a new destination. We need to keep all that. Could be a list? It's prose with enumerated items. Could convert to list for clarity but must preserve info. The rule: Use

  • for any list of duties/requirements/benefits. So we should turn benefits into a list. Let's extract each benefit item: - Immediate access to medical coverage - ReviveHealth virtual care - Dental and vision coverage - Commuter benefits - 401(k) plan - Flexible spending - Referral bonuses - Ongoing training - Employee stock ownership plan (ESOP) for all consultants - Nurturing culture that fosters career goals - Connection to next opportunity (in hometown or new destination) Also "comprehensive benefits package" is a general statement; we could keep as intro sentence. We need to preserve all substantive information; we can keep an introductory

    then a

    . Pay: Estimated Gross Weekly Pay: $1,886. Could be

    Estimated Gross Weekly Pay: $1,886.

    Schedule: Shift: 3x12 Nights. Could be

    Shift: 3x12 Nights.

    We must not include application instruction line. Also need to remove duplicated lines and boilerplate like "452009" at end (maybe a job ID). Remove that. Also remove "Why Work with Us" heading as we will use Benefits heading. Also remove "About Solomon Page Healthcare & Medical Staffing" etc. That's company info; could be considered boilerplate? It's not required but might be considered "About the company". The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description may not be boilerplate but could be considered extra. However we need to preserve ALL substantive information. Is company description substantive? It might be considered not essential to the job but still part of posting. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it unless it's considered boilerplate. The company description is likely not boilerplate; it's about the company. However we have no specific section for "About the company". We could include it under "About the role"? But that's about role not company. Could create a section "About the company" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not create a heading outside those. So we need to decide: either incorporate company info into existing sections (maybe as part of Benefits? Not appropriate). Or we could drop it if it's considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Company description is not those. But we cannot create a heading for it because only allowed headings are those. However we could put it in a

    without a heading? The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid having

    without heading. It says use those headings for section headings. It doesn't say we cannot have other headings, but we should follow the pattern. Probably we should only include those headings if we have content. If we have extra content that doesn't fit, we could still include as

    without heading? The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies that if we need a heading, we should use those. It doesn't forbid other headings but suggests to use those for sections. Safer to stick to those headings and put any other prose as

    without heading? But then we would have stray

    not under a heading, which might be okay. However the instruction: "Prefer a few substantive sections over many thin ones." So we could combine company info into Benefits or About the role? Not ideal. Maybe we can treat company info as part of "About the role" as a description of the employer. The heading "About the role" could include both role details and company overview. That seems acceptable. Thus About the role section will contain location, duration, start date, and also company description. Let's extract company description: "Accredited by the Joint Commission with the Gold Seal of Approval, Solomon Page prides ourselves in developing long-term relationships with healthcare providers based on trust and respect. Our experienced Healthcare and Medical Staffing experts are committed to providing safe and quality patient care through our wide network of travel nurses, locum tenens, and allied resources. For more information and additional healthcare opportunities, visit: solomonpage.com and connect with Solomon Page on Instagram, Facebook, Twitter, LinkedIn, and TikTok." We need to preserve that exactly. Thus About the role

    About the role

    then a

    containing location, duration, start date, and company description. Could be multiple

    but we can combine. We must not repeat job title as heading. Now ensure we don't include any filler like "commensurate with experience". Not present. Now produce HTML:

    About the role