Jobs · Healthcare · New Mexico

Travel ER RN - $1,650 per week

Host Healthcare, Inc. · Albuquerque, NM · 1 mo ago
On-siteHealthcareInternship
We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Let's parse the posting: - Host Healthcare is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Albuquerque, New Mexico. - Job Description & Requirements Specialty: ED - Emergency Department Discipline: RN Start Date: 10/12/2026 Duration: 13 weeks 36 hours per week Shift: 12 hours, nights Employment Type: Travel Host Healthcare Job ID #a1fVX0000042uztYAA. 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: RN - Emergency Room - About Host Healthcare: description paragraph. - Benefits: list of benefits. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to not repeat job title as heading. So no heading for RN - Emergency Room. We need to include sections only if real specific content. Potential sections: - About the role: could include description of role: travel nurse RN ED, location, start date, duration, hours, shift, employment type. That's substantive. - Responsibilities: not explicitly listed. The posting does not list duties. So we should not create Responsibilities section. - Requirements: maybe specialty, discipline, etc. Could be considered requirements. But we need to see if there are specific requirements listed: Specialty: ED - Emergency Department, Discipline: RN. That's it. Could be considered requirements. But we need to decide if we should create a Requirements section. The posting includes "Job Description & Requirements" heading but only lists specialty and discipline. Might be considered requirements. However we need to avoid thin sections. Could combine About the role and Requirements? But we must follow instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include About the role and Benefits and Pay and Schedule if we have content. 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, not specific amount. It says "subject to confirmation" and "tax-free stipend amount to be determined." This is not a concrete pay figure. According to instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here we have "subject to confirmation" and "tax-free stipend amount to be determined." That's placeholder-ish. So we should not create a Pay section because it's not specific. Schedule: we have shift: 12 hours, nights; 36 hours per week. That's specific schedule info. So we can include Schedule section. Benefits: we have a list of benefits. So include Benefits section. About the role: we can include description: travel nurse RN ED in Albuquerque, New Mexico; start date 10/12/2026; duration 13 weeks; 36 hours per week; shift 12 hours nights; employment type travel. That's substantive. We could also include Requirements: maybe specialty and discipline. But we might combine into About the role. However we need to decide if we should create a Requirements section. The posting includes "Job Description & Requirements" but only gives specialty and discipline. That's thin. Might be better to not create a separate Requirements section to avoid thin section. Instead incorporate those details into About the role. Qualifications: not listed. Skills: not listed. Thus sections: About the role, Benefits, Schedule. We need to use

for section headings. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We need to preserve all substantive information; do not invent or summarize away detail. Let's craft About the role paragraph: include location, specialty, discipline, start date, duration, hours, shift, employment type, job ID maybe? The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. So we can include Job ID in a short paragraph maybe within About the role or separate minor metadata paragraph. But we should not create a heading for it. We can include it in About the role paragraph as a sentence. We need to remove duplicated lines. Not seeing duplicates. Benefits list: we need to output as

    • each benefit. List from posting: - Referral bonus - School loan reimbursement - Vision benefits - Wellness and fitness programs - Company provided housing options - License and certification reimbursement - Life insurance - Medical benefits - Mileage reimbursement - Pet insurance - Discount program - Employee assistance programs - Guaranteed Hours - Health savings account - Holiday Pay - 401k retirement plan - Continuing Education - Dental benefits We need to preserve exactly as given. Ensure correct capitalization? Keep as is. Schedule: we have shift: 12 hours, nights; 36 hours per week. Could phrase as "Shift: 12 hours, nights; 36 hours per week." Use

      . Now output HTML fragment:

      About the role

      Host Healthcare is seeking a travel nurse RN specializing in the Emergency Department (ED) for a position in Albuquerque, New Mexico. The role is for an RN (Registered Nurse) with a start date of October 12, 2026, a duration of 13 weeks, 36 hours per week, 12‑hour night shifts, and is a travel employment type. Job ID: a1fVX0000042uztYAA.

      Benefits

      • Referral bonus
      • School loan reimbursement
      • Vision benefits
      • Wellness and fitness programs
      • Company provided housing options
      • License and certification reimbursement
      • Life insurance
      • Medical benefits
      • Mileage reimbursement
      • Pet insurance
      • Discount program
      • Employee assistance programs
      • Guaranteed Hours
      • Health savings account
      • Holiday Pay
      • 401k retirement plan
      • Continuing Education
      • Dental benefits

      Schedule

      Shift: 12 hours, nights; 36 hours per week.

      Check if any other info: Posted job title: RN - Emergency Room. We should not repeat job title as heading, but we could include it in About the role maybe. Already we said RN specializing in ED. Could add "Posted job title: RN - Emergency Room." but that's redundant. Might be okay to include as minor metadata. But we already have RN. Might be okay to include. We need to preserve ALL substantive information. The posted job title is substantive. So we should include it somewhere. Let's add a sentence: "Posted job title: RN - Emergency Room." Thus About the role paragraph: include that. Now ensure no extra sections like Pay. Check for any other specifics: "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 decided not to include Pay section because it's placeholder. But we could include that info in About the role? It's about pay but it's vague. The instruction says never emit a heading followed by filler/placeholder text. It doesn't forbid including vague pay info in a paragraph if not under a Pay heading. However we should avoid inventing or summarizing away detail. We could include a short sentence about pay being based on 12 hour shifts and 36 hours per week with tax-free stipend TBD. That is substantive? It's somewhat vague but it's actual info from posting. It's not a specific number but it's a statement. It's not placeholder like "commensurate with experience"? It says "subject to confirmation" and "tax-free stipend amount to be determined." That is somewhat placeholder but it's still info. The instruction says 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. It doesn't say we cannot include that info in a paragraph under another heading. However it's about pay, and we are not creating a Pay section. So we could include a sentence about pay in About the role or maybe a separate short paragraph without heading. But we must avoid creating a Pay heading. So we could add a sentence: "The pay package is based on 12‑hour shifts and 36 hours per week (subject to confirmation) with a tax‑free stipend amount to be determined." That preserves the info. Similarly, we might include "Duration: 13 weeks" etc already. Thus About the role paragraph can include start date, duration, hours, shift, employment type, job ID, posted job title, pay package note. Let's craft:

      Host Healthcare is seeking a travel nurse RN specializing in the Emergency Department (ED) for a position in Albuquerque, New Mexico. The posted job title is RN - Emergency Room. The role offers a start date of October 12, 2026, a duration of 13 weeks, 36 hours per week, 12‑hour night shifts, and is a travel employment type. The 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. Job ID: a1fVX0000042uztYAA.

      That covers all. Now Benefits list as above. Schedule section: we already have shift and hours. Could also mention "Shift: 12 hours, nights; 36 hours per week." That's fine. Now ensure we didn't include any boilerplate. The Host Healthcare description paragraph about mission etc is considered boilerplate? It's generic marketing but maybe considered substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Host Healthcare mission paragraph is not explicitly listed as boilerplate to remove, but it's generic marketing. However it's part of the posting. The instruction says "Preserve ALL substantive information". Is that substantive? It's about the company. Might be considered substantive. But we already have About the role section; we could include a brief About Host Healthcare paragraph if we want. However we already used About the role heading for role details. We could add another section like "About Host Healthcare" but headings list only includes specific headings; we could still use

      for About Host Healthcare? The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive; we could use other headings? It says "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should limit to those headings. So we should not create a heading like "About Host Healthcare". So we should not include that paragraph unless we fold it into About the role? But that would be mixing

Similar jobs