Travel Stepdown / MedSurg RN - $2,349 per week
AMN Healthcare Allied · Morgantown, WV · Today
On-siteFull-time
We need to output HTML fragment with sections: headings using 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.
Content:
- Title: travel nurse RN Med Surg / Telemetry in Morgantown, West Virginia.
- Job Description & Requirements:
Specialty: Med Surg / Telemetry
Discipline: RN
Start Date: ASAP
Duration: 13 weeks
36 hours per week
Shift: 12 hours
Employment Type: Travel
**All positions require at least two proven years experience**
Aequor Healthcare Job ID #1821308. (metadata)
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: Registered Nurse (RN) - PCU/Stepdown
- About Aequor Healthcare: description.
- Benefits: list: Weekly pay, Holiday Pay, 401k retirement plan, Referral bonus, Medical benefits, Dental benefits, Vision benefits.
We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We need to not repeat job title as heading. So we will not include heading for job title.
We need to include sections only when there is real specific content.
Potential sections:
- About the role: Could include description of role: specialty, discipline, start date, duration, hours, shift, employment type, experience requirement. That's substantive.
- Responsibilities: Not explicitly listed. The posting does not list duties/responsibilities. So we should not create Responsibilities section.
- Requirements: Could include experience requirement (2 years proven). Also maybe specialty, discipline. But we already have those in About the role. Might be better to separate: About the role (overview) and Requirements (experience). However we need to avoid thin sections. Could combine.
- Qualifications: Not specified beyond experience.
- Skills: Not listed.
- Benefits: we have list.
- Pay: we have mention: Pay package based on 12 hour shifts and 36 hours per week, tax-free stipend amount to be determined. This is somewhat vague but still specific: mentions basis and that stipend TBD. It says "subject to confirmation". It's not a specific number, but it's still some info. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state pay package based on 12 hour shifts and 36 hours per week, tax-free stipend amount to be determined. That's stating something about pay, albeit not a number. Should we include? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay, so we can include Pay section with that info. However we must avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". The phrase "tax-free stipend amount to be determined" is TBD. That's like TBD. Might be considered filler. The rule says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we include Pay section, we must ensure we have substantive content not just TBD. The posting says "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 includes specifics: based on 12 hour shifts and 36 hours per week. That's substantive. The stipend amount TBD is placeholder but we still have other info. So we can include Pay section with that sentence.
- Schedule: we have shift: 12 hours, 36 hours per week. That's schedule info. So we can include Schedule section.
- Benefits: we have list.
Thus sections: About the role (maybe combine description), Requirements (experience), Benefits, Pay, Schedule.
We need to use
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.
Content:
- Title: travel nurse RN Med Surg / Telemetry in Morgantown, West Virginia.
- Job Description & Requirements:
Specialty: Med Surg / Telemetry
Discipline: RN
Start Date: ASAP
Duration: 13 weeks
36 hours per week
Shift: 12 hours
Employment Type: Travel
**All positions require at least two proven years experience**
Aequor Healthcare Job ID #1821308. (metadata)
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: Registered Nurse (RN) - PCU/Stepdown
- About Aequor Healthcare: description.
- Benefits: list: Weekly pay, Holiday Pay, 401k retirement plan, Referral bonus, Medical benefits, Dental benefits, Vision benefits.
We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We need to not repeat job title as heading. So we will not include heading for job title.
We need to include sections only when there is real specific content.
Potential sections:
- About the role: Could include description of role: specialty, discipline, start date, duration, hours, shift, employment type, experience requirement. That's substantive.
- Responsibilities: Not explicitly listed. The posting does not list duties/responsibilities. So we should not create Responsibilities section.
- Requirements: Could include experience requirement (2 years proven). Also maybe specialty, discipline. But we already have those in About the role. Might be better to separate: About the role (overview) and Requirements (experience). However we need to avoid thin sections. Could combine.
- Qualifications: Not specified beyond experience.
- Skills: Not listed.
- Benefits: we have list.
- Pay: we have mention: Pay package based on 12 hour shifts and 36 hours per week, tax-free stipend amount to be determined. This is somewhat vague but still specific: mentions basis and that stipend TBD. It says "subject to confirmation". It's not a specific number, but it's still some info. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state pay package based on 12 hour shifts and 36 hours per week, tax-free stipend amount to be determined. That's stating something about pay, albeit not a number. Should we include? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay, so we can include Pay section with that info. However we must avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". The phrase "tax-free stipend amount to be determined" is TBD. That's like TBD. Might be considered filler. The rule says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we include Pay section, we must ensure we have substantive content not just TBD. The posting says "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 includes specifics: based on 12 hour shifts and 36 hours per week. That's substantive. The stipend amount TBD is placeholder but we still have other info. So we can include Pay section with that sentence.
- Schedule: we have shift: 12 hours, 36 hours per week. That's schedule info. So we can include Schedule section.
- Benefits: we have list.
Thus sections: About the role (maybe combine description), Requirements (experience), Benefits, Pay, Schedule.
We need to use for each section heading.
Inside sections, use
for prose,
- for lists.
We must preserve all substantive information; do not invent or summarize away detail.
Let's extract details:
About the role:
- Specialty: Med Surg / Telemetry
- Discipline: RN
- Start Date: ASAP
- Duration: 13 weeks
- Hours: 36 hours per week
- Shift: 12 hours
- Employment Type: Travel
- Experience: at least two proven years experience
- Job ID: #1821308 (metadata, maybe drop or put in short p)
- Posted job title: Registered Nurse (RN) - PCU/Stepdown (maybe note but not repeat title as heading)
- Location: Morgantown, West Virginia (mentioned at start)
We should include location somewhere.
We need to not repeat job title as heading, but we can mention it in prose.
We should drop Job ID/requisition numbers as headings; fold minor metadata into short p or drop it. So we can include Job ID in a short p maybe.
We need to avoid duplication.
Let's craft About the role section:
About the role
Location: Morgantown, West Virginia. Specialty: Med Surg / Telemetry. Discipline: RN. Start date: ASAP. Duration: 13 weeks. Schedule: 36 hours per week, 12‑hour shifts. Employment type: Travel. Requires at least two proven years of experience. Posted job title: Registered Nurse (RN) - PCU/Stepdown. Aequor Healthcare Job ID #1821308.
That's a paragraph. Now Requirements section: maybe just experience? But we already included experience in About the role. Could we avoid duplication? The rule: Prefer a few substantive sections over many thin ones. So maybe we combine experience into About the role and not have separate Requirements. However we need to capture "All positions require at least two proven years experience". Already included. So we could skip Requirements. But we might still want a Requirements section to highlight experience. However that would be thin if only that. Better to incorporate. Thus we have About the role covering all. Benefits section: list.Benefits
- Weekly pay
- Holiday Pay
- 401k retirement plan
- Referral bonus
- Medical benefits
- Dental benefits
- Vision benefits
Pay
Pay package is based on 12‑hour shifts and 36.0 hours per week (subject to confirmation) with a tax‑free stipend amount to be determined.
Schedule section:Schedule
12‑hour shifts, 36 hours per week.
We should ensure we don't repeat same info. Schedule repeats hours; but it's okay. Check for any other info: Aequor Healthcare description: "Aequor Travel Nursing is a premiere healthcare staffing agency..." That's about the company, not the role. Should we include a section like "About the company"? Not in allowed headings list; we have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". So we should omit that description as it's not requested heading. The instruction: "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we can use those headings; we shouldn't add other headings. So we should not include a section about Aequor Healthcare description. However we might incorporate that into About the role? But it's about the company, not the role. The rule says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit the company description, we lose substantive info. But we cannot create a heading not in the list? The list is examples; maybe we can use other headings if needed? The instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create any heading we think appropriate, but they gave examples. Probably we should stick to those examples to be safe. However we need to preserve all substantive information; the company description is substantive. If we cannot add a heading not in examples, maybe we can incorporate it into About the role as a brief note? But that would be mixing role and company. Might be okay. Alternatively we could add a section "About the company" using
. Since it's not prohibited, and the examples are just examples, it's likely acceptable. The instruction didn't forbid other headings. It said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use any heading, but they gave examples. So we can add "About the company". Let's do that. Thus sections: - About the role (role specifics) - About the company (description of Aequor) - Benefits - Pay - Schedule We must avoid duplication. Now craft About the company paragraph: "Aequor Travel Nursing is a premiere healthcare staffing agency that specializes in placing healthcare travelers in short term contracts throughout the US. Whether you’re a seasoned healthcare professional looking for your next great adventure or just starting out and looking for your first big opportunity, Aequor has the inside track on the top jobs available in today’s healthcare and clinical markets. At Aequor, our top priority is to be the best resource to help you connect with the perfect career opportunity and take the best care of you from the moment we first connect until your last shift is worked. We pride ourselves on always offering top industry competitive pay. We have positions for nationwide covering every single state and ranging from 4 weeks – 26 weeks." We need to preserve all info; no summarizing away. That's fine. Now ensure we didn't include boilerplate like EEO etc. Not present. Now output HTML fragment only. Let's assemble:
About the role
Location: Morgantown, West Virginia. Specialty: Med Surg / Telemetry. Discipline: RN. Start date: ASAP. Duration: 13 weeks. Schedule: 36 hours per week, 12‑hour shifts. Employment type: Travel. Requires at least two proven years of experience. Posted job title: Registered Nurse (RN) - PCU/Stepdown. Aequor Healthcare Job ID #1821308.
About the company
Aequor Travel Nursing is a premiere healthcare staffing agency that specializes in placing healthcare travelers in short term contracts throughout the US. Whether you’re a seasoned healthcare professional looking for your next great adventure or just starting out and looking for your first big opportunity, Aequor has the inside track on the top jobs available in today’s healthcare and clinical markets. At Aequor, our top priority is to be the best resource to help you connect with the perfect career opportunity and take the best care of you from the moment we first connect until your last shift is worked. We pride ourselves on always offering top industry competitive pay. We have positions for nationwide covering every single state and ranging from 4 weeks – 26 weeks.
Benefits
- Weekly pay
- Holiday Pay