Travel Cardiac Telemetry RN - $1,780 per week

We need to output HTML fragment with sections: About the role? Actually we need headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to extract substantive content from the posting. Given text: "Aequor Healthcare is seeking a travel nurse RN Telemetry for a travel nursing job in Stockbridge, Georgia. Job Description & Requirements Specialty: Telemetry Discipline: RN Start Date: 09/28/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 #1821941. 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) - Telemetry 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 produce sections: maybe About the role (description), Requirements (experience, specialty, discipline), Benefits (list), Pay (maybe mention pay package based on 12 hour shifts and 36 hours per week, tax-free stipend amount to be determined - but that is vague; we should not create Pay section unless posting actually states them. It does state "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 is somewhat vague but it's still stating pay package based on shifts and hours. However the instruction says: 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, but the amount is TBD. Is that considered filler? It says "tax-free stipend amount to be determined." That's vague. The instruction: 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 would have to include something like "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 "subject to confirmation" and "tax-free stipend amount to be determined." That's somewhat placeholder. Might be considered filler. Safer to omit Pay section unless we have concrete numbers. Since we don't have actual pay amount, we should not create Pay section. Schedule: we have shift: 12 hours, 36 hours per week, duration 13 weeks. That's schedule info. Should we create Schedule section? The posting states shift and hours per week and duration. That is specific. So we can include Schedule section with those details. Benefits: we have a 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: "Aequor Healthcare is seeking a travel nurse RN Telemetry for a travel nursing job in Stockbridge, Georgia." plus maybe "Job Description & Requirements" but we need to separate responsibilities? There's no explicit responsibilities list. Could treat the description as About the role. Could also include Requirements: specialty Telemetry, discipline RN, start date, duration, 36 hours per week, shift 12 hours, employment type travel, at least two years experience. Also maybe include "All positions require at least two proven years experience". That's a requirement. We need to avoid repeating job title as heading. So we will not have a heading for "Registered Nurse (RN) - Telemetry". We'll just have sections. We need to use

  for section headings. Use

  • for any list of duties/requirements/benefits, and

    for prose. We need to preserve all substantive information. So include location, start date, duration, hours per week, shift, employment type, experience requirement, specialty, discipline, benefits list, about Aequor Healthcare description. We need to decide sections: Perhaps "About the role" (prose about job location and role), "Requirements" (list of requirements: specialty, discipline, start date, duration, hours, shift, employment type, experience), "Benefits" (list), "Schedule" (maybe include shift, hours per week, duration). But schedule may overlap with requirements. Could combine schedule into requirements? But we need to avoid thin sections. Perhaps we can have "About the role", "Requirements", "Benefits". Schedule info could be part of Requirements (since it's about shift/hours). But the instruction says prefer a few substantive sections over many thin ones. So we could combine schedule into Requirements. Thus sections: About the role (prose), Requirements (list), Benefits (list). Possibly also "About Aequor Healthcare" could be part of About the role? Actually About Aequor Healthcare is about the agency, not the role. Could be a separate section "About the agency". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the agency". However we could put that info in About the role? Might be okay to include as prose under About the role? But it's not about the role; it's about the agency. However we could treat it as part of About the role? Might be misrepresenting. But we could also omit that info? The instruction says preserve ALL substantive information. So we need to include that info somewhere. Could we put it under "About the role" as a paragraph? It's not exactly about the role but it's still substantive. Could we create a section "About Aequor Healthcare"? Not in allowed headings list, but the instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings when appropriate, but we could also use other headings? The instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they want us to use those specific headings for sections. It doesn't forbid other headings, but likely they expect only those. Safer to stick to those headings. So we need to fit the agency description into one of those headings. Perhaps "About the role" could include both role and agency info? Might be okay. Alternatively, we could put agency info under "Requirements"? No. Better: we could treat "About Aequor Healthcare" as part of "About the role" because it's describing the employer, which is relevant to the role. So we can include that prose. Thus sections: - About the role: prose containing location, job title (maybe not repeat title?), description of role, agency description. But we must not repeat the job title as a heading; we can still mention it in prose. - Requirements: list of specialty, discipline, start date, duration, hours per week, shift, employment type, experience requirement. - Benefits: list of benefits. We need to ensure we don't create Pay or Schedule sections. Now format:

    About the role

    ... prose ...

    Requirements

    • Specialty: Telemetry
    • Discipline: RN
    • Start Date: September 28, 2026
    • Duration: 13 weeks
    • Hours per week: 36 hours
    • Shift: 12 hours
    • Employment Type: Travel
    • Minimum experience: at least two proven years

    Benefits

    • Weekly pay
    • Holiday Pay
    • 401k retirement plan
    • Referral bonus
    • Medical benefits
    • Dental benefits
    • Vision benefits
    We need to preserve all substantive information: also 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." Since we omitted Pay section, we might lose that info. But it's somewhat vague; maybe we can include it in Requirements as a note about pay? But it's not a requirement. Could we include it in About the role as prose? It's about pay, not role. But we could add a sentence about pay package being based on 12 hour shifts and 36 hours per week, with tax-free stipend TBD. That is substantive (though vague). The instruction says never emit a heading followed by filler/placeholder text, but we can include that info in prose under About the role or Requirements? It's not a requirement but could be considered part of role details. However the instruction says "Prefer a few substantive sections over many thin ones." Adding a Pay section would be thin because it's vague. So better to incorporate that info into About the role or Requirements as a note. But the instruction also says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package based on shifts and hours, but amount TBD. That is still stating something about pay. However the instruction also says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". So if we made a Pay section, we would have to include that TBD info, which is placeholder. So we should avoid Pay section. Instead we can mention the pay basis in About the role or Requirements as a note, but not as a separate heading. Similarly, schedule info: we have shift, hours per