Local Contract Progressive Care Unit RN - $39-46 per hour
Medical Solutions · Goldsboro, NC · 1 mo ago
On-siteHealthcareContract
We need to output HTML fragment with sections: About the role? The posting includes description: "Medical Solutions is seeking a local contract nurse RN PCU - Progressive Care Unit for a local contract nursing job in Goldsboro, North Carolina." Then description includes specialty, discipline, duration, hours, shift, employment type. Then a paragraph about seeking talented healthcare professionals... Then list of benefits (Day One Medical... etc). Then "Equal Employment Opportunity And More!" (should be removed as boilerplate). Then "Estimated pay package based on bill rate..." (pay info but vague). Then "Medical Solutions Job ID #1181727L. Posted job title: Stepdown." (Job ID and posted job title - we should fold minor metadata into short p or drop it). Then "About Medical Solutions" paragraph (company description). Then "Benefits" list (Weekly pay, Holiday Pay, etc). There's duplication of benefits; we need to preserve all substantive info but not duplicate lines. We need to combine benefits sections? The posting includes two benefit lists: first list after "Some of the industry-leading benefits enjoyed..." and second list under "Benefits". We need to include a Benefits section only if posting has real specific content. Both lists contain benefits; we should combine them into one Benefits section, removing duplicates and boilerplate like EEO. Also remove "Equal Employment Opportunity And More!" and "And More!" etc.
We need headings: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content.
We have: About the role? Could be description of role: specialty, discipline, duration, hours, shift, employment type. Could be placed under About the role.
Responsibilities? Not explicitly listed; maybe not.
Requirements? Could be RN license, PCU experience? Not explicit. The posting says "RN PCU - Progressive Care Unit". Could infer requirement: RN license, PCU experience. But we should not invent. Only include if explicitly stated. The posting does not list explicit requirements besides being an RN and PCU specialty. Might be considered implicit but not explicit. Safer to not create Requirements section if not explicit.
Qualifications? Not explicit.
Skills? Not explicit.
Pay: The posting includes "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." That's vague but mentions pay package. It's not a specific number. According to rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). This is vague but says "Exact pay package may vary". That's somewhat placeholder. Might be considered not specific enough. Should we include Pay section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state estimated pay package based on bill rate, but not actual numbers. Is that considered stating them? It's stating that there is an estimated pay package, but not giving specifics. Might be considered stating Pay section exists (they mention pay). However the rule says avoid filler like "varies". This says "Exact pay package may vary". That's similar to "varies". Might be considered filler. Safer to omit Pay section.
Schedule: The posting includes shift: 12 hours, nights; 36 hours per week; duration 13 weeks. That's schedule info. So we can create Schedule section with those details.
Benefits: We have specific benefits listed; we should include Benefits section.
About the role: we can include role details.
We need to output only HTML fragment, no html/body tags.
Structure:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content.
We have: About the role? Could be description of role: specialty, discipline, duration, hours, shift, employment type. Could be placed under About the role.
Responsibilities? Not explicitly listed; maybe not.
Requirements? Could be RN license, PCU experience? Not explicit. The posting says "RN PCU - Progressive Care Unit". Could infer requirement: RN license, PCU experience. But we should not invent. Only include if explicitly stated. The posting does not list explicit requirements besides being an RN and PCU specialty. Might be considered implicit but not explicit. Safer to not create Requirements section if not explicit.
Qualifications? Not explicit.
Skills? Not explicit.
Pay: The posting includes "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." That's vague but mentions pay package. It's not a specific number. According to rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). This is vague but says "Exact pay package may vary". That's somewhat placeholder. Might be considered not specific enough. Should we include Pay section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state estimated pay package based on bill rate, but not actual numbers. Is that considered stating them? It's stating that there is an estimated pay package, but not giving specifics. Might be considered stating Pay section exists (they mention pay). However the rule says avoid filler like "varies". This says "Exact pay package may vary". That's similar to "varies". Might be considered filler. Safer to omit Pay section.
Schedule: The posting includes shift: 12 hours, nights; 36 hours per week; duration 13 weeks. That's schedule info. So we can create Schedule section with those details.
Benefits: We have specific benefits listed; we should include Benefits section.
About the role: we can include role details.
We need to output only HTML fragment, no html/body tags.
Structure:
About the role
Medical Solutions is seeking a local contract nurse RN PCU - Progressive Care Unit for a local contract nursing job in Goldsboro, North Carolina. Specialty: PCU - Progressive Care Unit. Discipline: RN. Duration: 13 weeks. 36 hours per week. Shift: 12 hours, nights. Employment Type: Local Contract.
Maybe also include the enthusiastic sentence: "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!" That's prose about role; could be included in About the role paragraph. Then Benefits section:Benefits
- 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
- 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