Travel Med Surg RN - $1,861 per week
Medical Solutions · Kirksville, MO · 1 mo ago
On-siteHealthcareInternship
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 need to parse the job posting.
Key details:
- Title: travel nurse RN Med Surg in Kirksville, Missouri.
- Specialty: Med Surg
- Discipline: RN
- Duration: 13 weeks
- Hours: 36 hours per week
- Shift: 12 hours, nights
- Employment Type: Travel
- Benefits listed: Day One Medical, Dental, 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; (plus later 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). Many duplicates.
- Pay: Estimated pay package based on bill rate; pay package based on 12 hour shifts and 36.0 hours per week with tax-free stipend amount to be determined. No exact numbers given. So we cannot create Pay section with specific numbers; but we can include Pay section if there is some info? The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does mention pay package based on bill rate, tax-free stipend to be determined. That's vague but still mentions pay. However we should avoid placeholder like "not specified". The posting does not give actual pay amount, but says "Estimated pay package based on bill rate at time job was posted." That's still not a specific number. The rule says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not create a Pay section if the content is just vague. However we could include a short paragraph describing that pay is based on bill rate and includes tax-free stipend, but that might be considered filler? It's not a specific number but it's still info. The rule says "never emit a heading followed by filler/placeholder text". The phrase "Estimated pay package based on bill rate at time job was posted." is not exactly placeholder like "not specified". It's a statement. I'd say we can include Pay section with that sentence.
- Schedule: we have shift: 12 hours, nights; 36 hours per week; duration 13 weeks. That's specific. So we can include Schedule section.
- Benefits: we have many specific benefits. So include Benefits section.
- About the role: we have description: "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!" plus maybe some description of role? Not much else. Could be considered About the role.
- Responsibilities: not explicitly listed. The posting does not list duties. So we should not create Responsibilities section.
- Requirements: not explicitly listed besides specialty Med Surg, discipline RN, maybe license? Not explicit. Could infer but not given. Better not to create Requirements if not explicit.
- Qualifications: similar.
- Skills: not listed.
Thus we will include sections: About the role, Benefits, Pay, Schedule. Possibly also a short meta paragraph for Job ID etc? The rule: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a
with Job ID and location etc at top before sections? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. We can include a
for location and job ID etc before sections. Not a heading. Thus structure:
Location: Kirksville, Missouri. Job ID: 1182350.
ThenAbout the role
with...
ThenBenefits
with- ...
Pay
with...
ThenSchedule
with- ...
or drop it. So we can include a short
with location and job ID. Then About the role can contain the descriptive sentences. Thus About the role
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!
Maybe also include the sentence about "We’re seeking talented healthcare professionals..." that's it. Now Pay section: we need to include the pay info: "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." 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." We should combine into a paragraph. Now Schedule section: we have Duration: 13 weeks; 36 hours per week; Shift: 12 hours, nights; Employment Type: Travel. So we can list bullets: Duration: 13 weeks; Hours per week: 36 hours; Shift: 12 hours, nights; Employment Type: Travel. Now we need to ensure we don't create sections with filler. All sections have real content. Now output HTML fragment. We'll start with afor location and job ID:
Location: Kirksville, Missouri. Job ID: 1182350.
ThenAbout the role
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!
ThenBenefits
- with each benefit as
- . We need to be careful not to miss any. Let's list them in a logical order, maybe as they appear. I'll compile list: - Day One Medical, Dental, and Vision with low premiums - Day One 4