Travel ER RN - $2,008 per week

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to parse the posting. Content: - Job: travel nurse RN ED - Emergency Department in Breckenridge, Minnesota. - Specialty: ED - Emergency Department - Discipline: RN - Start Date: 09/28/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, days, nights - Employment Type: Travel - Pay Rate: $1958.00 - $2058.00 (presumably weekly? It says Pay Rate: $1958.00 - $2058.00) - Required Qualifications: - Registered Nurse, ER Experience: 2 years - Licenses: RN-MN (Copy needed) - Certifications: ACLS-AHA (Copy Needed); BLS-AHA (Copy Needed); CERT-NIH Stroke Scale (Copy Needed); CERT-TNCC (Copy Needed) - SSN Required - DOB Required - References: 1 Reference in entire work history - Job Benefits: - Competitive pay rates - Free, quality, private housing - Medical, Dental, Vision - 401(k) and Flex Spending - Life Insurance - Accident and Short-term Disability Coverage - Free Continuing Education - Refer a friend and earn extra cash! - About the Company: description (maybe not needed as a section? Could be About the role? The instruction: use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. We have: - About the role: could include description of unit, team, environment. The posting says: "This outstanding unit is looking for the right RN to join their team of compassionate and driven health care professionals. Join this highly motivated team of caregivers and enjoy a challenging and welcoming environment based on optimal patient care." That's about the role. - Responsibilities: Not explicitly listed. Could infer from ED RN duties but we must not invent. So we should not include Responsibilities if no specific content. - Requirements: maybe includes start date, duration, hours, shift, employment type, location? Those are job details. Could be considered Requirements? But we have Qualifications separate. The instruction: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide what goes where. Typically: - About the role: description of role/unit. - Responsibilities: list of duties (not present). - Requirements: maybe mandatory items like license, certifications, experience, SSN, DOB, references. - Qualifications: maybe education, experience? But we have overlapping. Could treat Requirements as mandatory items (license, certifications, experience) and Qualifications as preferred? But we have no preferred. Better: Use Requirements for the mandatory qualifications (experience, licenses, certifications, SSN, DOB, references). Use Qualifications for maybe education? Not given. Could skip Qualifications if no distinct content. Skills: maybe list of skills like ACLS, BLS, NIH Stroke Scale, TNCC. Those are certifications, but could be considered skills. Could put under Skills. Pay: we have pay rate. Schedule: we have shift details: 12 hour shifts, days/nights, 36 hours per week. Benefits: we have list. Thus sections: - About the role: description paragraph. - Requirements: list of mandatory qualifications (experience 2 years, RN-MN license, certifications ACLS, BLS, NIH Stroke Scale, TNCC, SSN, DOB, 1 reference). - Skills: maybe list of certifications as skills? But we already listed them under Requirements. Could avoid duplication. Perhaps we put certifications under Skills, and experience/license under Requirements. Let's see. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must include all info: experience, license, certifications, SSN, DOB, reference, pay, benefits, schedule, start date, duration, location, shift, employment type. We need to decide where each piece goes without duplication. Potential mapping: About the role: location (Breckenridge, Minnesota), unit description, team, environment. Requirements: start date, duration, hours per week, shift, employment type? Those are job details, not necessarily requirements but could be considered requirements for the assignment. However the instruction says "Requirements" heading for any list of duties/requirements/benefits. Actually they said: Use

• for any list of duties/requirements/benefits. So Requirements heading could contain list of requirements (like experience, license, certifications, SSN, DOB, reference). Also could contain start date, duration, etc? Those are not requirements but job details. Might be better to put them under About the role? But About the role is for description of role, not logistics. Maybe we can create a section "Details" but not allowed headings. Only allowed headings are those listed. So we must fit all info into those headings. We could put start date, duration, hours, shift, employment type under About the role as part of description? Could be okay. But we need to avoid filler headings. So we must only include sections that have real specific content. Thus we will include: - About the role: includes location, start date, duration, hours/week, shift, employment type, description of unit/team. - Requirements: includes experience, license, certifications, SSN, DOB, reference. - Skills: maybe not needed if we already put certifications under Requirements. Could omit Skills. - Benefits: list. - Pay: pay rate. - Schedule: maybe we already included shift/hours in About the role; but we could also put schedule details there. However we need to avoid duplication. Could put schedule under Schedule heading: 12 hour shifts, days/nights, 36 hours per week. Thus we need to decide what goes where without duplication. Let's list all data points: - Location: Breckenridge, Minnesota - Specialty: ED - Emergency Department - Discipline: RN - Start Date: 09/28/2026 - Duration: 13 weeks - Hours per week: 36 hours - Shift: 12 hours, days, nights - Employment Type: Travel - Pay Rate: $1958.00 - $2058.00 (likely weekly) - Required Qualifications: - Registered Nurse, ER Experience: 2 years - Licenses: RN-MN (Copy needed) - Certifications: ACLS-AHA (Copy Needed); BLS-AHA (Copy Needed); CERT-NIH Stroke Scale (Copy Needed); CERT-TNCC (Copy Needed) - SSN Required - DOB Required - References: 1 Reference in entire work history - Benefits: - Competitive pay rates - Free, quality, private housing - Medical, Dental, Vision - 401(k) and Flex Spending - Life Insurance - Accident and Short-term Disability Coverage - Free Continuing Education - Refer a friend and earn extra cash! - About the Company description (maybe not needed) - Additional note: Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined. (This is extra about pay, but we already have pay rate; we could note that stipend TBD but we should not include filler like "TBD". The instruction: 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. So we should not include the tax-free stipend amount to be determined because it's TBD. We can omit that sentence. - Posted job title etc not needed. Thus we have concrete data for: About the role: location, specialty, discipline, start date, duration, hours/week, shift, employment type, unit description. Requirements: experience, license, certifications, SSN, DOB, reference. Benefits: list. Pay: pay rate. Schedule: maybe we already included shift/hours in About the role; but we could still have Schedule heading with shift details (12 hour shifts, days/nights, 36 hours per week). However that would duplicate info from About the role. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but could be considered redundant. It's okay to repeat? Might be better to avoid duplication but not required. However we need to ensure we don't miss any info. If we put shift/hours only under About the role, we still have them. If we also put under Schedule, it's duplicate but still preserving. Might be okay but could be seen as unnecessary. I'd prefer to put schedule details under Schedule heading and keep About the role focused on description (location, specialty, start date, duration, employment type, unit description). Then we avoid duplication. Thus: About the role: location (Breckenridge, Minnesota), specialty (ED - Emergency Department), discipline (RN), start date (09/28/2026), duration (13 weeks), employment type (Travel), unit description paragraph. Schedule: shift (12 hours, days, nights), hours per week (36 hours). Pay: pay rate ($1958.00 - $2058.00). Requirements: experience (2 years ER), license (RN-MN), certifications (ACLS-AHA, BLS-AHA, NIH Stroke Scale, TNCC), SSN required, DOB required, references (1 reference in entire work history). Benefits: list as given. We should not include Skills section unless we have specific skills beyond certifications. Could omit. Now we need to output HTML fragment with headings

  for each section, and

  • for lists,

    for prose. We must not include or tags. We must not include markdown code fences. We must ensure we only include sections with real content. Let's craft:

    About the role

    Located in Breckenridge, Minnesota, this Emergency Department (ED) Registered Nurse (RN) travel position starts on 09/28/2026 for a duration of 13 weeks. Employment type is travel. The unit seeks a compassionate and driven RN to join a team of caregivers, offering a challenging and welcoming environment focused on optimal patient care.

    Schedule

    • 12‑hour shifts, days and nights
    • 36 hours per week

    Pay

    $1958.00 – $2058.00 (weekly)

    Requirements

    • Registered Nurse with 2 years of ER experience
    • Current RN license in Minnesota (RN‑MN)
    • ACLS certification (AHA)
    • BLS certification (AHA)
    • NIH Stroke Scale certification
    • TNCC certification
    • Social Security Number required
    • Date of Birth required
    • One professional reference from entire work history

    Ben