Local Contract IMC RN - $36-42 per hour

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. We must not repeat job title as heading. Must not include Job ID as heading. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. We need to parse the posting. Content: - Medical Solutions is seeking a local contract nurse RN PCU - Progressive Care Unit for a local contract nursing job in Charlotte, North Carolina. - Job Description & Requirements Specialty: PCU - Progressive Care Unit Discipline: RN Duration: 13 weeks 48 hours per week Shift: 12 hours, nights Employment Type: Local Contract - "We’re seeking talented healthcare professionals whose adventure game is as strong as their clinical game. Those that want flexibility and high pay, we have the positions for you!" This is prose. - Benefits list: Day One Medical, Dental, and Vision with low premiums; Day One 401(k) with Company Contribution; Personalized Compensation Packages; Paid, Private, Fully Furnished, Pet-Friendly Housing; Dedicated Recruiter and 24/7 Customer Care Line; Per Diem Allowance and Paid Travel; Licensure and Certification Reimbursement; Free Liability Coverage; Voluntary Benefits: Critical Illness, Hospital Indemnity, Accident, and Pet Insurance; Equal Employment Opportunity (boilerplate, remove); And More! - Estimated pay package based on bill rate at time job was posted. Bill rates can change frequently and without notice. Exact pay package may vary based on guaranteed hours, distance being traveled, and customizations available for travelers. - Medical Solutions Job ID #1190116L. Posted job title: Stepdown (we drop ID and job title heading) - About Medical Solutions paragraph (company description) - we can include as "About the role"? Actually "About the role" is for role description; but we have company description. Could put under "About the role" maybe? But guidelines: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only if posting has real specific content for it. We have: - About the role: Could include the description of the role: specialty, discipline, duration, hours, shift, employment type, location, maybe the "We’re seeking talented..." prose. That seems appropriate. - Responsibilities: Not explicitly listed. The posting does not list duties/responsibilities. So we should not create a Responsibilities section. - Requirements: Could include specialty, discipline, maybe license/certification? Not explicit. The posting mentions "Licensure and Certification Reimbursement" as benefit, not requirement. No explicit requirements like "must have active RN license". Not given. So we should not create Requirements. - Qualifications: Not given. - Skills: Not given. - Benefits: We have a list of benefits. Should include Benefits section. - Pay: We have info about estimated pay package based on bill rate, can change, exact may vary. That's specific enough? It mentions pay but not actual numbers. It says "Estimated pay package based on bill rate at time job was posted. Bill rates can change frequently and without notice. Exact pay package may vary based on guaranteed hours, distance being traveled, and customizations available for travelers." This is substantive but not a specific number. The instruction: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". This is somewhat similar to "varies". It says exact pay package may vary. That's vague. Might be considered filler. However we have some info: "Estimated pay package based on bill rate at time job was posted." That's still vague. The instruction says do not create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay, albeit vague. Should we include Pay section? The instruction: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The phrase "Exact pay package may vary based on guaranteed hours, distance being traveled, and customizations available for travelers." includes "varies". That's similar to placeholder. Might be considered filler. Safer to omit Pay section if it's just vague. However we could include Pay section with the statement about estimated pay package based on bill rate, but that is still vague. The instruction says do not create Pay section unless posting actually states them. It does state something about pay (estimated pay package). I'd lean to include Pay section with that sentence, but ensure not just filler. It's not a specific number but it's a statement. Might be acceptable. - Schedule: We have shift: 12 hours, nights; 48 hours per week; duration 13 weeks. That's schedule info. So we can include Schedule section. Thus sections: About the role, Benefits, Pay?, Schedule. We need to use

for each section heading. Use

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

    for prose. For Schedule, we can use

    or maybe

    • if list. We'll use

      . We must not include boilerplate like EEO, duplicated lines, navigation, legal, application instructions. Remove duplicated Benefits list (there is a Benefits section later with weekly pay etc). We need to preserve all substantive information. There's a Benefits section later with items: Weekly pay, Holiday Pay, Guaranteed Hours, Continuing Education, 401k retirement plan, Pet insurance, Company provided housing options, Cancelation protection, Wellness and fitness programs, Mileage reimbursement, Referral bonus, Employee assistance programs, Medical benefits, Dental benefits, Vision benefits, Benefits start day 1, License and certification reimbursement, Life insurance, Discount program. This is another list of benefits (maybe duplicates). We need to combine? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we need to merge the two benefit lists, removing duplicates. First benefit list from earlier: Day One Medical, Dental, and Vision with low premiums; Day One 401(k) with Company Contribution; Personalized Compensation Packages; Paid, Private, Fully Furnished, Pet-Friendly Housing; Dedicated Recruiter and 24/7 Customer Care Line; Per Diem Allowance and Paid Travel; Licensure and Certification Reimbursement; Free Liability Coverage; Voluntary Benefits: Critical Illness, Hospital Indemnity, Accident, and Pet Insurance. Second benefits list: Weekly pay, Holiday Pay, Guaranteed Hours, Continuing Education, 401k retirement plan, Pet insurance, Company provided housing options, Cancelation protection, Wellness and fitness programs, Mileage reimbursement, Referral bonus, Employee assistance programs, Medical benefits, Dental benefits, Vision benefits, Benefits start day 1, License and certification reimbursement, Life insurance, Discount program. We need to combine and deduplicate. Let's list unique items: - Day One Medical, Dental, and Vision with low premiums (covers Medical, Dental, Vision benefits) - Day One 401(k) with Company Contribution (401k retirement plan) - Personalized Compensation Packages - Paid, Private, Fully Furnished, Pet-Friendly Housing (Company provided housing options, Pet insurance? Actually housing includes pet-friendly; pet insurance separate) - Dedicated Recruiter and 24/7 Customer Care Line - Per Diem Allowance and Paid Travel - Licensure and Certification Reimbursement (also appears as License and certification reimbursement) - Free Liability Coverage - Voluntary Benefits: Critical Illness, Hospital Indemnity, Accident, and Pet Insurance (Pet insurance appears also) - Weekly pay - Holiday Pay - Guaranteed Hours - Continuing Education - Pet insurance (already in voluntary benefits) - Company provided housing options (same as Paid, Private, Fully Furnished, Pet-Friendly Housing) - Cancelation protection - Wellness and fitness programs - Mileage reimbursement - Referral bonus - Employee assistance programs - Medical benefits (covered in Day One Medical) - Dental benefits (covered) - Vision benefits (covered) - Benefits start day 1 (implicit in Day One) - Life insurance - Discount program We need to avoid duplication. So we can create a unified list: - Day One Medical, Dental, and Vision with low premiums - Day One 401(k) with Company Contribution - Personalized Compensation Packages - Paid, Private, Fully Furnished, Pet-Friendly Housing - Dedicated Recruiter and 24/7 Customer Care Line - Per Diem Allowance and Paid Travel - Licensure and Certification Reimbursement - Free Liability Coverage - Voluntary Benefits: Critical Illness, Hospital Indemnity, Accident, and Pet Insurance - Weekly pay - Holiday Pay - Guaranteed Hours - Continuing Education - Cancelation protection - Wellness and fitness programs - Mileage reimbursement - Referral bonus - Employee assistance programs - Life insurance - Discount program Check duplicates: Pet insurance appears in voluntary benefits; we keep that. Housing: we have Paid, Private, Fully Furnished, Pet-Friendly Housing (includes pet-friendly). Good. Now About the role content: location Charlotte, North Carolina; specialty PCU; discipline RN; duration 13 weeks; 48 hours per week; shift 12 hours nights; employment type Local Contract; plus the prose "We’re seeking talented healthcare professionals whose adventure game is as strong as their clinical game. Those that want flexibility and high pay, we have the positions for you!" Also maybe mention job title Stepdown? Actually posted job title: Stepdown (but we should not repeat job title as heading). Could include that as part of About the role? The posting says "Posted job title: Stepdown". That's a detail about the job. Should we preserve? It's substantive. We can include in About the role paragraph: "Posted job title: Stepdown." But we must not repeat the job title as a heading; we can include it in prose. Also we have "Medical Solutions Job ID #1190116L." We should drop ID per instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it. So we could drop it entirely or fold into a short p. Since it's minor metadata, we can drop it. The instruction says "fold minor metadata into a short

      or drop it." So we could include a short p with the ID? But better to drop it as it's not needed. We'll drop. Now Pay section: we have "Estimated pay package based on bill rate at time job was posted. Bill rates can change frequently and without notice. Exact pay package may vary based on guaranteed hours, distance being traveled, and customizations available for travelers." This is somewhat vague but it's the only pay info. According to instruction, we should not create Pay section if it's just filler like "varies". However it's not exactly "varies" but mentions variation. Might be considered filler. Safer to omit Pay section. But we need to preserve ALL substantive information. This is substantive about pay, albeit vague. If we omit, we lose that info. The instruction says "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The phrase "Exact pay package may vary based on..." includes "varies". That's similar to