Travel PCU/Stepdown Registered Nurse - $2,096 per week

We need to output HTML fragment with sections: About the role? Actually we have job description and requirements. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. Let's parse the posting. Content: - Aequor Healthcare is seeking a travel nurse RN PCU - Progressive Care Unit for a travel nursing job in Baltimore, Maryland. - Job Description & Requirements - Specialty: PCU - Progressive Care Unit - 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 #1813005. - 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: 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. Remove duplicated lines, application instructions none. We need to not repeat job title as heading. So no heading for job title. We need to include sections only if real specific content. Let's decide sections: - About the role: Could include description of role: travel nurse RN PCU, location Baltimore, specialty, discipline, start date, duration, hours, shift, employment type, experience requirement. That's substantive. - Responsibilities: Not given explicitly. The posting doesn't list responsibilities. So we should not create Responsibilities section. - Requirements: Could include "All positions require at least two proven years experience". Also maybe specialty, discipline, etc. But those are more about role. Could put requirements section with experience requirement. - Qualifications: Not given beyond experience. Could combine with requirements. - Skills: Not given. - Benefits: We have list: Weekly pay, Holiday Pay, 401k retirement plan, Referral bonus, Medical benefits, Dental benefits, Vision benefits. That's specific. - Pay: 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's vague but includes some info: based on 12 hour shifts, 36 hours per week, tax-free stipend amount TBD. It says subject to confirmation. This is somewhat vague but still some content. However rule: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The pay section includes "tax-free stipend amount to be determined" which is TBD. Also "subject to confirmation". This might be considered placeholder. The rule says do NOT 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, with tax-free stipend amount to be determined. That's stating something, albeit partially TBD. Is that allowed? The rule says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "tax-free stipend amount to be determined" is essentially TBD. That might be considered filler. However we also have concrete: based on 12 hour shifts and 36 hours per week. That's specific. Could we include Pay section with that detail, omitting the TBD part? We must preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include the pay info as given, but we could phrase it as a

that includes the exact sentence. That's not filler; it's the actual text. The rule about filler refers to headings with placeholder text like "Pay: TBD". If we include the heading Pay and then a paragraph with the actual sentence, that's okay because it's not just placeholder. So we can include Pay section. - Schedule: We have shift: 12 hours, 36 hours per week. That's schedule info. So we can include Schedule section. Now we need to format. We should not include Job ID as heading; fold minor metadata into a short

or drop it. So we can include Job ID in a paragraph maybe under About the role or separate metadata paragraph. We need to remove duplicated lines. Let's craft HTML:

About the role

Aequor Healthcare is seeking a travel nurse RN for a Progressive Care Unit (PCU) position in Baltimore, Maryland. Specialty: PCU - Progressive Care Unit. Discipline: RN. Start date: October 12, 2026. Duration: 13 weeks. Schedule: 36 hours per week, 12‑hour shifts. Employment type: Travel. All positions require at least two proven years of experience.

Maybe also include Job ID:

Job ID: #1813005.

but we said fold minor metadata into a short

or drop it. Could add a small paragraph after About the role. Then Benefits:

Benefits

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

Pay:

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:

Schedule

36 hours per week, 12‑hour shifts.

We should not include Responsibilities, Requirements, Qualifications, Skills if no specific content. We have experience requirement which could be under Requirements. But we already included experience in About the role. Could we create a Requirements section with that? The rule: prefer a few substantive sections over many thin ones. So maybe keep experience in About the role and not create separate Requirements. That's fine. Check for any other specifics: Posted job title: Registered Nurse (RN) - PCU/Stepdown. We should not repeat job title as heading, but we could include that info in About the role paragraph. Already we said travel nurse RN PCU. Could add that the posted job title is Registered Nurse (RN) - PCU/Stepdown. Let's incorporate. Also About Aequor Healthcare description: we could include that as part of About the role? Or maybe a separate section About the company? Not in allowed headings list. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should incorporate company description into About the role maybe as a brief note. But the rule: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should only use those headings. So we should not add a heading like "About Aequor Healthcare". Instead we can fold that content into About the role paragraph. Thus About the role paragraph can include: Aequor Travel Nursing is a premiere healthcare staffing agency... etc. Let's incorporate that. Now ensure we preserve all substantive information: location, specialty, discipline, start date, duration, hours, shift, employment type, experience requirement, job ID, pay package description, benefits list, posted job title, company description. Let's craft final HTML. We need to output only HTML fragment, no /, no markdown. Let's produce:

About the role

Aequor Healthcare is seeking a travel nurse RN for a Progressive Care Unit (PCU) position in Baltimore, Maryland. Specialty: PCU - Progressive Care Unit. Discipline: RN. Start date: October 12, 2026. Duration: 13 weeks. Schedule: 36 hours per week, 12‑hour shifts. Employment type: Travel. All positions require at least two proven years of experience. Posted job title: Registered Nurse (RN) - PCU/Stepdown. Aequor Travel Nursing is a premiere healthcare staffing agency that specializes in placing healthcare travelers in short‑term contracts throughout the US, offering top industry‑competitive pay and assignments ranging from 4 to 26 weeks nationwide.

Job ID: #1813005.

Benefits

• Weekly pay
• Holiday pay
• 401(k) 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

36 hours per week, 12‑hour shifts.

Check for any duplicated lines: we have schedule mentioned twice (in About the role and Schedule section). That's okay because we need to preserve all info; but we might be duplicating. The rule says remove duplicated lines. However schedule info appears in both About the role and Schedule section. Could we avoid duplication by not including schedule in About the role? But About the role needs to include schedule info as part of role description. However we could keep schedule only in Schedule section and mention in About the role generically? The rule: Preserve ALL substantive information; do NOT invent or summarize away detail. If we remove schedule from About the role, we would lose that detail unless we keep it elsewhere. We have Schedule section with that detail, so we could keep schedule only there and not duplicate in About the role. However About the role currently includes schedule; we could remove it from there to avoid duplication. But we need to ensure we still convey that it's a travel nurse PCU role etc. The schedule is substantive; we have it in Schedule section, so it's preserved. So we can drop schedule from About the role to avoid duplication. Similarly, we might have duration and hours etc. Let's see: About the role currently includes start date, duration, schedule, employment type, experience, job ID, company description, posted job title. We could keep start date, duration, employment type, experience, job ID, company description, posted job title. Schedule moved to its own section. That seems fine. Now check for any other duplicated lines: Benefits list is unique. Pay section unique. Now ensure we didn't include any boilerplate like EEO etc. Not present. Now ensure we didn't include any placeholder text like "TBD". The Pay section includes "tax‑free stipend amount to be determined." That's still placeholder but it's the exact wording from posting. The rule says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "to be determined" is similar to TBD. However it's not just a heading with placeholder; it's a full sentence. The rule might be interpreted as: don't create a section where the only content is placeholder like "Pay: TBD". Since we have actual info about based on