Jobs · Healthcare · California

Local Contract Nurse RN - CVICU - $67-71 per hour

Host Healthcare, Inc. · Sacramento, CA · 1 mo ago
On-siteHealthcareContract
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Let's parse the posting. Content: - Host Healthcare is seeking a local contract nurse RN CVICU for a local contract nursing job in Sacramento, California. - Job Description & Requirements - Specialty: CVICU - Discipline: RN - Start Date: 10/13/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, nights - Employment Type: Local Contract - Host Healthcare Job ID #La1fVX0000045ZUHYA2. - 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 - CVICU - About Host Healthcare: description. - Benefits list: many items. We need to avoid repeating job title as heading. No Job ID as heading; can fold into short p. We need sections: About the role (maybe description of role), Responsibilities (none given), Requirements (maybe specialty, discipline, start date, duration, hours, shift, employment type), Qualifications (maybe none), Skills (none), Benefits (list), Pay (mention pay package based on 12 hour shifts and 36 hours per week with tax-free stipend amount to be determined - but that's vague; "tax-free stipend amount to be determined" is not specific; maybe we should not include Pay section because it's not specific? The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here "tax-free stipend amount to be determined" is placeholder; also "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation)" is somewhat specific but still not a concrete amount. Might be considered not specific enough. Safer to omit Pay section. Schedule: we have shift: 12 hours, nights; 36 hours per week. That's specific. So we can include Schedule section. Benefits: we have a list of benefits; we can include Benefits section. About the role: we have description of role: local contract nurse RN CVICU in Sacramento, California. Could be considered About the role. Responsibilities: none given. Requirements: we have specialty, discipline, start date, duration, hours, shift, employment type. Those could be Requirements. Qualifications: none given. Skills: none given. Thus sections: About the role, Requirements, Benefits, Schedule. We need to use

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

    for prose. We must not repeat job title as heading. Not include Job ID as heading; we can fold into short p. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details: location Sacramento, California; specialty CVICU; discipline RN; start date 10/13/2026; duration 13 weeks; 36 hours per week; shift 12 hours nights; employment type Local Contract; Host Healthcare description; benefits list; pay package note (maybe we can include in About the role or Requirements? It's about pay; but we decided to omit Pay section due to vagueness. However we must preserve all substantive information; the pay package note is substantive albeit vague. We could include it in a

    under About the role or Requirements as a note. The rule says we should not create Pay section unless posting actually states them. It does state "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 is a statement about pay, albeit not specific. Should we include it? The instruction: "Prefer a few substantive sections over many thin ones." And "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The phrase "tax-free stipend amount to be determined" is placeholder; but the rest is somewhat specific: based on 12 hour shifts and 36 hours per week. Might be considered not specific enough for a Pay section. Safer to not create Pay section, but we must preserve the info somewhere else. Could embed in a paragraph under About the role or Requirements. That would preserve it without a dedicated heading. Similarly, schedule: we have shift and hours; we can put in Schedule section. Now craft HTML. Structure:

    About the role

    Host Healthcare is seeking a local contract nurse RN CVICU for a local contract nursing job in Sacramento, California. Specialty: CVICU; Discipline: RN; Start Date: 10/13/2026; Duration: 13 weeks; 36 hours per week; Shift: 12 hours, nights; Employment Type: Local Contract. 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.

    Requirements

    • Specialty: CVICU
    • Discipline: RN
    • Start Date: 10/13/2026
    • Duration: 13 weeks
    • 36 hours per week
    • Shift: 12 hours, nights
    • Employment Type: Local Contract
    But note we already included those details in About the role; we might duplicate. The rule: preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay? It might be considered redundant but not violating. However we could avoid duplication by moving details to Requirements only, and About the role just a brief description. But we need to keep all info; we can put details in Requirements and keep About the role short. Let's do that. About the role: brief description: Host Healthcare is seeking a local contract nurse RN CVICU for a local contract nursing job in Sacramento, California. Then Requirements list includes specialty, discipline, start date, duration, hours, shift, employment type, pay package note. Benefits: list. Schedule: shift and hours. But schedule duplicates hours/shift from Requirements. Might be okay but could be considered thin. However we have schedule specifics; we could keep schedule separate and not duplicate in Requirements. But we need to preserve all info; we can put hours/shift in Schedule only, and not duplicate in Requirements. However Requirements also need to include shift/hours? The posting includes them under Job Description & Requirements; they are part of requirements. It's okay to have them in both sections? Might be considered duplication but not prohibited. The instruction: "Prefer a few substantive sections over many thin ones." Having duplicate info may make sections thin. Better to assign each piece to one section. Let's allocate: - About the role: brief description of role and location. - Requirements: specialty, discipline, start date, duration, employment type. - Schedule: shift (12 hours, nights) and hours per week (36). - Benefits: list. - Pay note: maybe include in Requirements as a line? Or in About the role? Since it's about pay, we could add a line in Requirements: "Pay package: based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." Even though it's vague, it's still part of requirements. But we said we shouldn't create Pay section; we can include it as a line in Requirements. Thus Requirements will have multiple items. Now Benefits: list all benefits. Now we need to ensure we don't include boilerplate like EEO etc. The posting includes a benefits list; we keep that. Now produce HTML. Check for any stray text: "Posted job title: RN - CVICU" - we should not repeat job title as heading; we can include that as a line maybe in About the role? But it's basically same as role; we can ignore as it's redundant. Now produce final HTML. Let's craft:

    About the role

    Host Healthcare is seeking a local contract nurse RN CVICU for a local contract nursing job in Sacramento, California.

    Requirements

    • Specialty: CVICU
    • Discipline: RN
    • Start Date: 10/13/2026
    • Duration: 13 weeks
    • Employment Type: Local Contract
    • Pay package: based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined

    Schedule

    • Shift: 12 hours, nights
    • Hours per week: 36

    Benefits

    • Referral bonus
    • School loan reimbursement
    • Vision benefits
    • Wellness and fitness programs
    • Company provided housing options
    • License and certification reimbursement
    • Life insurance
    • Medical benefits
    • Mileage reimbursement
    • Pet insurance
    • Discount program
    • Employee assistance programs
    • Guaranteed Hours
    • Health savings account
    • Holiday Pay
    • 401k retirement plan
    • Continuing Education
    • Dental benefits
    Check: we omitted "Travel reimbursements", "dedicated housing support", "24/7 support", "access to on-staff clinicians", "Day 1 medical that continues up to 30 days between assignments", "401K matching". Those are mentioned in the About Host Healthcare paragraph. We need to preserve all substantive information. The About Host Healthcare paragraph includes many benefits details that are not in the bullet list. We need to include them somewhere. We could incorporate them into Benefits list as well, or add a paragraph under About Host Healthcare. Since we have no section for About Host Healthcare, we could add a paragraph under About the role or maybe a separate section "About Host Healthcare". But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't list "About Host Healthcare". However we can include that info in About the role section as prose. The About the role currently only has brief line; we can expand it to include the Host Healthcare description. That would preserve all info. Thus About the role paragraph should include the description: "At Host Healthcare, we provide a truly comfortable experience as you explore your travel nursing, therapy, or allied career. We make your travel healthcare journey easy by taking care of all the details, so you don’t have to. We are on a mission to help others live better and we do this by helping the healers of the world be as comfortable as possible. With access to tens of thousands of travel nursing, therapy, and allied jobs in all 50 states, our responsive and friendly recruiters find your dream position based on what’s important to you. During your assignment, get access to premium benefits, including Day 1 medical that continues up to 30 days between assignments, 401K matching, travel reimbursements, dedicated housing support, and more. We also offer 2

Similar jobs