Travel Med/Surg RN - $2,302 per week

We need to produce HTML fragment with sections only if real specific content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must not include Job ID etc as headings; fold minor metadata into short

or drop it. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Preserve all substantive info. We need to parse the job posting. Key info: - Focus Staff seeking travel nurse RN Med Surg for travel nursing job in Urbana, Illinois. - Specialty: Med Surg - Discipline: RN - Start Date: 10/12/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel - Contract Length: 13 Weeks - Start Date: 10/12/2026 - Shift: 3x12 Nights - Benefits: weekly direct deposits, 401(k) matching, generous bonuses, day one medical, dental, vision, life insurance (no waiting period), licensure reimbursement, relocation support, exclusive discounts, dedicated recruiter 24/7 support, flexible scheduling options, pet-friendly housing. - Requirements: Minimum of 1-2 years experience, Valid IL RN License, Current BLS and ACLS certification, Must be eligible to work in the United States. - About Focus Staff: description. - Pay: "Estimated pay package based on bill rate at time job was posted. Bill rates can change frequently and without notice. Exact pay package may vary based on several factors, including, but not limited to, guaranteed hours, travel distance, demand, experience, etc." Also "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." So pay info is vague; we should not create Pay section unless posting actually states them. It says "Estimated pay package..." but not actual numbers. It's not specific; we should avoid Pay section because no concrete pay figure. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". So we should not create Pay section. - Schedule: we have shift details: 3x12 Nights, 36 hours per week, 12 hour shifts nights. That's specific. So we can create a Schedule section. - Benefits: we have specific benefits listed. So Benefits section. - Responsibilities: The posting includes description: "Your daily work will directly contribute to optimal patient outcomes by providing meticulous care and compassionate support to individuals on their path to wellness." That's a prose description of responsibilities. Could be under Responsibilities. - About the role: maybe we can have About the role section summarizing role. But we must not repeat job title as heading. Could have About the role with description of role. - Qualifications/Skills: Requirements list could be under Requirements or Qualifications. We need to decide which headings to use. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which are appropriate. We have responsibilities, requirements, benefits, schedule. Could also have About the role. We'll avoid thin sections. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details: start date, duration, hours per week, shift, location, contract length, benefits details, requirements, about Focus Staff description. We must not include boilerplate like EEO, legal, duplicated lines, application instructions (like "Interested in becoming a traveler with Focus Staff? Discover why travelers choose us, apply today!"). We also need to drop minor metadata like Job ID, posting date, etc. Could fold into a short p if needed, but better to drop as per instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we could include a short p with location and dates maybe. But we already have location in About the role? We'll include location in About the role or maybe a separate p. We must not repeat job title as heading. So we will not have

Travel Med/Surg Nurse RN

. Instead we can have About the role with description. Let's craft HTML:

About the role

Focus Staff is seeking a travel nurse RN Med Surg for a travel nursing assignment in Urbana, Illinois. The role is a 13‑week contract starting October 12, 2026, with 36 hours per week (3×12‑hour night shifts).

Responsibilities

Provide meticulous care and compassionate support to medical‑surgical patients, contributing to optimal patient outcomes and supporting individuals on their path to wellness.

Requirements

• Minimum of 1‑2 years of recent Med/Surg nursing experience
• Valid Illinois RN license
• Current Basic Life Support (BLS) certification
• Current Advanced Cardiac Life Support (ACLS) certification
• Eligibility to work in the United States

Benefits

• Weekly direct deposit pay
• 401(k) matching
• Generous bonuses
• Day‑one medical, dental, vision, and life insurance (no waiting period)
• Licensure reimbursement
• Relocation support
• Exclusive discounts on travel and services
• Dedicated recruiter available 24/7
• Flexible scheduling options
• Pet‑friendly housing assistance

Schedule

• Shift pattern: 3×12‑hour night shifts per week
• Total hours: 36 hours per week
• Contract length: 13 weeks
• Start date: October 12, 2026

We might also include About Focus Staff description as a section maybe "About Focus Staff". But the instruction list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not About Focus Staff. However we could incorporate that into About the role or maybe a separate section like "About the company". But not in list; better to keep to allowed headings. Could put Focus Staff description under About the role or maybe a separate

after benefits. 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, not exclusive. But we should prefer a few substantive sections over many thin ones. Adding About Focus Staff might be okay but could be considered thin? It's substantive. However we already have About the role; we could incorporate Focus Staff description there. But the description is about the company, not the role. Might be better to have a separate section "About Focus Staff". But the instruction didn't forbid other headings; just gave examples. It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use other headings if needed, but better to stick to those to avoid many thin sections. The Focus Staff description is substantive; we could put it under About the role or maybe a separate paragraph without heading. The instruction: "Use

for prose." So we can just add a

after the sections describing Focus Staff. That would preserve info without extra heading. Thus final HTML will have sections: About the role, Responsibilities, Requirements, Benefits, Schedule. No Pay section. No Qualifications/Skills separate (we used Requirements). Could also add Qualifications but we already have Requirements; we can keep Requirements. Make sure not to include any boilerplate like EEO, duplicated lines, application instructions, etc. Check for any repeated content: We have start date, duration, shift in About the role and Schedule; that's okay but not duplicate? It's okay to mention in both but we should avoid duplication if possible. However we need to preserve all substantive info; it's fine to mention in both places but maybe we can keep start date and duration in About the role, and schedule details in Schedule. That's fine. Now produce HTML fragment only. Let's craft:

About the role

Focus Staff is seeking a travel nurse RN Med Surg for a travel nursing assignment in Urbana, Illinois. The role is a 13‑week contract starting October 12, 2026, with 36 hours per week (3×12‑hour night shifts).

Responsibilities

Provide meticulous care and compassionate support to medical‑surgical patients, contributing to optimal patient outcomes and supporting individuals on their path to wellness.

Requirements

• Minimum of 1‑2 years of recent Med/Surg nursing experience
• Valid Illinois RN license
• Current Basic Life Support (BLS) certification
• Current Advanced Cardiac Life Support (ACLS) certification
• Eligibility to work in the United States

Benefits

• Weekly direct deposit pay
• 401(k) matching
• Generous bonuses
• Day‑one medical, dental, vision, and life insurance (no waiting period)
• Licensure reimbursement
• Relocation support
• Exclusive discounts on travel and services
• Dedicated recruiter available 24/7
• Flexible scheduling options
• Pet‑friendly housing assistance

Schedule

• Shift pattern: 3×12‑hour night shifts per week
• Total hours: 36 hours per week
• Contract length: 13 weeks
• Start date: October 12, 2026

Check for any prohibited content: No mention of pay, no job ID, no EEO, no application instructions. All substantive info preserved: location, start date, duration, hours, shift, responsibilities, requirements, benefits, schedule. Also includes Focus Staff description? We included a brief line about Focus Staff seeking... but not the longer description about Focus Staff mission etc. The longer description about Focus Staff is considered boilerplate? It's descriptive of the company but maybe considered substantive. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The Focus Staff mission paragraph is not exactly boilerplate; it's promotional but could be considered part of the posting. However we might need to preserve all substantive information; does that include the "About Focus Staff" paragraph? It says "About Focus Staff: Focus Staff is a traveler-first healthcare staffing agency..." That is substantive about the company. Should we preserve it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that description. However we already have a brief line about Focus Staff seeking... but we omitted the longer description. We could incorporate that into About the role or add a separate paragraph without heading. Since we already have About the role section, we could add a