Travel IMU RN - $2,299 per week

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. First, there is some confusion: The posting starts with "VyTalent Solutions is seeking a travel nurse RN Intermediate Care for a travel nursing job in Lynchburg, Virginia." Then "Job Description & Requirements Specialty: Intermediate Care Discipline: RN Start Date: 10/12/2026 Duration: 13 weeks 36 hours per week Shift: 12 hours Employment Type: Travel". Then "The right role can make all the difference..." then "At VyTalent Solutions, we support..." then "We’re currently looking for a Stepdown Neuro Registered Nurse for a Hospital contract. Job Details: Job Title: Stepdown Neuro Registered Nurse Location: Lynchburg, VA Setting: Hospital Pay Range: 2080.20 - 2184.21 Schedule: 18:45 - 07:15 Contract Length: 13 weeks Candidate Type: Traveler Requirements: BLS, ACLS, NIHSS; Minimum 2 years of experience, pref in neuro; Will consider candidates with pending certifications; biweekly orientation on Mondays; floating responsibilities; NICOTINE FREE CAMPUS; Will consider candidates with pending certifications. Responsibilities: Provide specialized neuro step-down care to patients in a hospital setting. Float to different units as needed, supporting various patient care needs. Follow biweekly orientation schedule to ensure compliance and updated training. Maintain certification requirements including BLS, ACLS, and NIHSS. Adhere to unit-specific policies, including NICOTINE FREE CAMPUS regulations. Why Choose VyTalent Solutions? At VyTalent Solutions, support starts with benefits that work for you, an uncapped referral program, and a recruiter who’s with you every step of the assignment. Equal Opportunity Employer ... VyTalent Solutions Job ID #110074. Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. Posted job title: RN - Registered Nurse Stepdown/IMC/PCU About VyTalent Solutions ... Benefits ..." We need to remove boilerplate: EEO, legal, navigation, cookie, application instructions, duplicated lines. Also remove Job ID etc. We need to preserve substantive info: specialty, discipline, start date, duration, hours per week, shift, employment type, location, setting, pay range, schedule (time), contract length, candidate type, requirements (certifications, experience, pending certifications, biweekly orientation, floating responsibilities, nicotine free campus), responsibilities (provide neuro step-down care, float, follow orientation, maintain certifications, adhere to policies), benefits (list: medical, dental, vision, life insurance, 401(k) with company match, Employee Assistance Program, wellness program, BetterHelp partnership, Scrubin uniform discounts, Hotel Engine travel discounts, Working Advantage employee discount program, Referral Program: $500 referral). Also maybe "Why Choose VyTalent Solutions?" could be considered as a section? Not required but could be "About the role" or "Why Choose". The instructions say use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. We have: - About the role: could include description of role, setting, specialty, discipline, start date, duration, hours per week, shift, employment type, location, setting, contract length, candidate type. Possibly also "Why Choose VyTalent Solutions?" but that's more about company. - Responsibilities: list bullet points. - Requirements: list bullet points (certifications, experience, pending certifications, biweekly orientation, floating responsibilities, nicotine free campus). Also maybe "Minimum 2 years of experience, pref in neuro". Also "Will consider candidates with pending certifications" appears twice; we can deduplicate. - Qualifications: maybe same as Requirements? But we can combine. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have Requirements content. We might not have separate Qualifications or Skills distinct from Requirements; we could omit those if no specific content. Pay: we have Pay Range: 2080.20 - 2184.21 (likely hourly? maybe weekly?). Also "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's vague; we have a pay range, so we can include Pay section with that range. Schedule: we have Shift: 12 hours, Schedule: 18:45 - 07:15 (night shift), also 36 hours per week, 12 hour shifts. So we can include Schedule section with shift details and hours. Benefits: we have a list. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. We should not include Qualifications or Skills if no distinct content. Now we need to format:

About the role

then

prose summarizing role details? Or we could use

• for list of duties/requirements/benefits. For About the role, we can use

  with sentences. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include each piece of info exactly as given, but we can rephrase? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we should not omit details, but we can rephrase? Safer to keep the exact phrasing where possible, but we can combine into sentences. We need to avoid duplication. Let's extract details: From first part: - Specialty: Intermediate Care - Discipline: RN - Start Date: 10/12/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours - Employment Type: Travel Later: - Job Title: Stepdown Neuro Registered Nurse - Location: Lynchburg, VA - Setting: Hospital - Pay Range: 2080.20 - 2184.21 (likely per week? but we keep as given) - Schedule: 18:45 - 07:15 - Contract Length: 13 weeks - Candidate Type: Traveler Requirements: - BLS, ACLS, NIHSS - Minimum 2 years of experience, pref in neuro - Will consider candidates with pending certifications (mentioned twice) - biweekly orientation on Mondays - floating responsibilities - NICOTINE FREE CAMPUS Responsibilities: - Provide specialized neuro step-down care to patients in a hospital setting. - Float to different units as needed, supporting various patient care needs. - Follow biweekly orientation schedule to ensure compliance and updated training. - Maintain certification requirements including BLS, ACLS, and NIHSS. - Adhere to unit-specific policies, including NICOTINE FREE CAMPUS regulations. Why Choose VyTalent Solutions? (maybe we can include as part of About the role or separate but not required). It says: "At VyTalent Solutions, support starts with benefits that work for you, an uncapped referral program, and a recruiter who’s with you every step of the assignment." That's substantive but could be part of About the role or Benefits? It mentions benefits and referral program. However we already have Benefits section listing specific benefits; the referral program is mentioned there as "Referral Program: Earn $500 when you refer a friend, and they'll earn $500, too." So we can incorporate that into Benefits. About VyTalent Solutions description: generic company description; could be considered boilerplate? It's not EEO/legal but it's generic marketing. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This company description might be considered boilerplate? It's not explicitly listed but could be considered fluff. However it's substantive about the company. The instruction says "Prefer a few substantive sections over many thin ones." Might be okay to include as About the role? But the heading "About the role" is for role description, not company. Could we add a section "About the company"? Not in allowed headings. So maybe we omit that generic description to avoid thin sections. The instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The company description is somewhat generic but still specific to VyTalent Solutions. However it's not about the role. Since we don't have a heading for company, we could incorporate relevant parts into About the role or Benefits? The part about support starts with benefits that work for you, an uncapped referral program, and a recruiter who’s with you every step of the assignment. That's about benefits and support; we could mention in Benefits or About the role. But we already have Benefits section with list; we could add a sentence about recruiter support and referral program (though referral program already in Benefits). We'll keep Benefits as list; we can add a sentence about recruiter support in Benefits paragraph? But Benefits must be

  • for any list of duties/requirements/benefits. So we need to keep benefits as list; we can add a

    before list for prose? The instruction: Use

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

      for prose. So we can have a

      describing benefits generally, then a

      • for the list. That's acceptable. Similarly for Responsibilities and Requirements we use
        • . Now About the role: we can use

          with prose containing all role details. Now Pay: we have Pay Range: 2080.20 - 2184.21. Also note "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's somewhat vague but we can include the range and note that it's based on 12 hour shifts and 36 hours per week, stipend TBD. However we must not include placeholder text like "TBD" or "not specified". The phrase "tax-free stipend amount to be determined" is placeholder; we should avoid including that if it's placeholder. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It says we should not include filler/placeholder text. So we should omit the stipend part if it's placeholder. But we can include the pay range and note that it's based on 12 hour shifts and 36 hours per week (that's not placeholder). So we can say: Pay range: $2080.20 - $2184.21 (based on 12‑hour shifts, 36 hours per week). That's fine. Schedule: we have Shift: 12 hours, Schedule: 18:45 - 07:15, 36 hours per week. Also maybe mention shift pattern (night). We'll include that. Now we need to ensure we don't include duplicated lines. For requirements, "Will consider candidates with pending certifications" appears twice; we'll include once. Now we need to remove Job ID, EEO, etc. Now produce HTML fragment. Structure:

          About the role

          ...