Travel Med Surg RN - $1,518 per week

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to parse the posting. Given text: "Aequor Healthcare is seeking a travel nurse RN Med Surg for a travel nursing job in Henderson, North Carolina. Job Description & Requirements Specialty: Med Surg Discipline: RN Start Date: 10/12/2026 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 #1810747. 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) - Med Surg About Aequor Healthcare 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 401k retirement plan Referral bonus Medical benefits Dental benefits Vision benefits" We need to remove boilerplate: cookie/navigation/legal/EEO etc none present. Also remove duplicated lines, application instructions (none). Keep substantive info. We need sections: maybe "About the role" (description), "Requirements" (experience, specialty, discipline, start date, duration, hours, shift, employment type), "Benefits" (list), "Pay" (mention pay package based on 12 hour shifts and 36 hours per week, tax-free stipend amount to be determined). However note: we should not create Pay section unless posting actually states them. It does mention 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's some pay info, albeit vague. The rule: "never create Pay/Schedule/Benefits sections unless the 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 still stating something about pay, albeit not specific amount. Should we include? It 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's some info about pay structure. It's not a specific amount, but it's still stating something. The rule says: "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/TBD. So that might be considered filler. Also "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation)" is somewhat generic but still mentions basis. Might be okay? However we need to avoid filler. The phrase "subject to confirmation" is vague. Might be considered placeholder. Safer to omit Pay section because the only pay info is vague and includes TBD. The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay, but it's not a concrete amount; still it's stating something. However the rule about filler text says never emit a heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". The phrase "tax-free stipend amount to be determined" is TBD-like. So including Pay section would have filler. Better to omit Pay section. Schedule: we have shift: 12 hours, 36 hours per week. That's schedule info. Could we create a Schedule section? The posting states shift and hours per week. That's specific. Not filler. So we can include Schedule section. Benefits: we have list: Weekly pay, Holiday Pay, 401k retirement plan, Referral bonus, Medical benefits, Dental benefits, Vision benefits. That's specific. So Benefits section. About the role: we have description about Aequor Healthcare (company description). Could be "About the role" or "About Aequor Healthcare". The rule says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "About the role" for the company description and job overview. Or we could use "About Aequor Healthcare" but that's not in allowed list. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, but we should stick to those headings? Likely we should use those exact headings when appropriate. So we can use "About the role" for the company overview. Then "Requirements" for specialty, discipline, start date, duration, hours, shift, employment type, experience requirement. Could also include "Responsibilities" but none given. So we skip. We need to preserve all substantive information. Let's extract: - Location: Henderson, North Carolina. - Specialty: Med Surg - Discipline: RN - Start Date: 10/12/2026 - Duration: 13 weeks - Hours per week: 36 hours - Shift: 12 hours - Employment Type: Travel - Experience: at least two proven years experience - Job ID: #1810747 (but we should drop Job ID as per instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include it in a short paragraph maybe, but better to drop? It says fold minor metadata into a short

or drop it. So we can include a short p with Job ID maybe. But it's minor metadata; we could drop it. Safer to drop it? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a short p containing Job ID. Let's include a short p: "

Job ID: #1810747

" maybe at top. - Pay package: based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. This is vague; we might include in Pay section? But we decided to omit Pay due to filler. Could we include it in Schedule? Not appropriate. Could we include in a short p under About the role? Might be considered minor metadata. But it's about pay. The rule says never create Pay section unless posting actually states them. It does state something, but it's vague. Might be better to include a short p about pay? However the instruction about Pay section: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay, so we could create Pay section but must avoid filler. The content includes "subject to confirmation" and "tax-free stipend amount to be determined" which is filler. If we include that, we would be emitting filler text. The rule says never emit a heading followed by filler/placeholder text. So if we create Pay section, we must not have filler. We could rephrase to only include the concrete part: "Pay package is based on 12 hour shifts and 36.0 hours per week." That's concrete. The rest is filler; we could omit that part. But we must preserve ALL substantive information; we cannot invent or summarize away detail. Omitting the stipend detail might be summarizing away detail? It's detail but it's placeholder. The rule says do not invent or summarize away detail. Summarizing away detail might be considered omitting detail. However the detail is placeholder/TBD; maybe it's okay to omit because it's not substantive? The rule says preserve ALL substantive information. The stipend amount to be determined is not substantive (it's unknown). So we could omit that detail. The "subject to confirmation" is also not substantive. So we could keep only the concrete part: "Pay package is based on 12 hour shifts and 36.0 hours per week." That is substantive. So we can include Pay section with that sentence. Similarly Schedule: we have shift: 12 hours, 36 hours per week. That's schedule. Could also be in Schedule section. Benefits: list. Now we need to avoid duplicate lines. Ensure we don't repeat. Let's craft HTML:

About the role

Aequor Healthcare is seeking a travel nurse RN Med Surg for a travel nursing job in Henderson, North Carolina. 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.

Requirements

• Specialty: Med Surg
• Discipline: RN
• Start Date: 10/12/2026
• Duration: 13 weeks
• 36 hours per week
• Shift: 12 hours
• Employment Type: Travel
• At least two proven years of experience

Maybe also include Job ID in a short p before sections? Could add

Job ID: #1810747

after About the role? But it's minor metadata; we can include as a short p.

Schedule

• 12‑hour shifts
• 36 hours per week

Pay

Pay package is based on 12 hour shifts and 36.0 hours per week.

Benefits

• Weekly pay
• Holiday Pay
• 401k retirement plan
• Referral bonus
• Medical benefits
• Dental benefits
• Vision benefits

Check for any duplicated content: we have "36 hours per week" appears in Requirements and Schedule; that's okay as it's substantive in both contexts. Could we avoid duplication? The rule says remove duplicated lines. It might consider duplicate lines as same exact line appearing multiple times. We have "36 hours per week" appears in Requirements list and Schedule list. That's duplicated line. We should avoid duplication.