Travel OR RN - $2,116 per week
` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use `- ` for any list of duties/requirements/benefits
- Use `
` for prose
- Do NOT repeat the job title as a heading (page already shows it)
- 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
- Output ONLY the HTML fragment — no `/`, no markdown code fences
2. **Analyze the Input Text:**
Let me parse the job posting content. It's from ARMStaffing, travel nurse RN OR - Operating Room in McKinney, Texas.
Key sections I can identify:
- Job Title/Position: travel nurse RN OR - Operating Room (but I shouldn't repeat it as a heading)
- Job ID: #38108861 (should be folded into a short
or dropped, but the rule says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." I'll fold it into a
at the end or beginning, but carefully.)
- Specialty: OR - Operating Room
- Discipline: RN
- Start Date: ASAP
- Duration: 13 weeks
- Hours: 36 hours per week
- Shift: 12 hours, nights
- Employment Type: Travel
- Location: McKinney, TX
- Assignment Duration: 13-week contract position
- Schedule: 7 PM - 7 AM, Thursday, Friday, Saturday. Call requirement of one day a week and one weekend a month.
- Job Description: seeking skilled Travel RN specializing in Operating Room duties. Ideal candidate will possess essential general/trauma OR skills and significant experience in the operating room, particularly in neuro and ortho/spine procedures. This role requires a team player with a positive attitude.
- Responsibilities: Assist in various surgical procedures including ortho, neuro, robotics, general, trauma, and urology. Collaborate with surgical teams to ensure patient safety and quality care. Monitor patient vital signs and conditions during surgery.
- Required Experience / Certifications / Licensure: Must have at least 1 year of experience in the Operating Room. Must possess current BLS certification. Experience in neuro and ortho/spine required. Trauma center experience is preferred.
- Why ARMStaffing? / Benefits: Health Benefits: Medical, Dental, Vision, Life, and more. Onboarding Made Easy: We handle physicals, titers, and more so you can focus on care. Clinical Support: In-house clinical team available to assist and advocate. 401k Retirement Plan: Eligible after waiting period; 4% match with 5% contribution. Recruiter Matching: Get paired with a recruiter based on your location and specialty. Extras: Travel reimbursement, housing allowance, meals, referral bonuses, and more.
- Additional praise/boilerplate about ARMStaffing: SIA's Top-50 Fastest Growing Healthcare Staffing Firms – 2019, SIA's Largest Healthcare Staffing Agencies in the U.S. – 2023, Top Workplace in the Lehigh Valley – 2022, 2023, Perfect scores for 'Name, Not a Number' and 'Recruiters' Personalities' on Highway Hypodermics, The Joint Commission’s Gold Seal of Approval for healthcare staffing, 15 years strong and counting!, Contract & local rates may vary based on location and applicant residency. Ask your ARMStaffing recruiter for details!
- Pay package: 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:OR,19:00:00-07:00:00
- About ARMStaffing: description of the company.
Now, I need to follow the strict rules:
- Use `
` for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But only include them if the posting has real, specific content. Never emit a heading followed by filler/placeholder text.
- Do NOT repeat the job title as a heading.
- 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.
- Never create Pay/Schedule/Benefits sections unless the posting actually states them.
- Never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD").
- Prefer a few substantive sections over many thin ones.
- Output ONLY the HTML fragment — no /, no markdown code fences.
Let me decide which sections to include based on actual content:
- "About the role": The posting has job description, responsibilities, requirements. I could use "About the role" or maybe just start with Responsibilities/Requirements. The rule says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I need to map the content to these headings appropriately, but only if there's real content.
- Let's map:
* "About the role" could cover the general description, specialty, discipline, start date, duration, hours, employment type, location, schedule. But the rule says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". I need to be careful not to create thin sections.
* "Responsibilities": clearly present - list of duties.
* "Requirements": clearly present - certifications, licensure, experience.
* "Qualifications": might overlap with Requirements. The example list includes "Qualifications" but the rule says use those headings if applicable. I'll see if there's distinct "Qualifications" content. The posting has "Required Experience / Certifications / Licensure" which is essentially qualifications. I might combine or use one.
* "Skills": maybe neuro and ortho/spine skills, robotics, etc. Could be part of Requirements or a separate section.
* "Benefits": clearly present - health benefits, 401k, onboarding, clinical support, extras.
* "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." It also says "Contract & local rates may vary based on location and applicant residency. Ask your ARMStaffing recruiter for details!" And "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." There's also "Posted job title: RN:OR,19:00:00-07:00:00". The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay-related info, but it also has "tax-free stipend amount to be determined" and "subject to confirmation". The rule also says "never emit a heading followed by filler/placeholder text (e.g. ... "TBD")". So I should NOT create a Pay section if it contains "amount to be determined" or "TBD". Let's read carefully: "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." This contains "amount to be determined" which is a placeholder. The rule says never emit a heading followed by filler/placeholder text. So I should either omit the Pay section, or include the substantive part without the placeholder. But the rule is strict: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". So if I create a Pay , I'd need to put content after it. If the content includes "amount to be determined", that's a placeholder. I think I should either fold pay info into a
without creating a Pay heading, or omit the Pay section entirely. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, but with placeholders. I'll interpret "actually states them" as having concrete, specific information without placeholders that would violate the "no filler" rule. I'll include pay-related info in a
perhaps, or fold it into metadata. But the rule says use
for section headings (e.g. ... Pay, Schedule). I need to decide.
* "Schedule": the posting has "Shift: 12 hours, nights" and "Schedule Shift: 7 PM - 7 AM, Thursday, Friday, Saturday. Call requirement of one day a week and one weekend a month." So Schedule has specific content. I can create a Schedule section with that info.
* Benefits: has concrete info: Health Benefits: Medical, Dental, Vision, Life, and more. Onboarding Made Easy: We handle physicals, titers, and more so you can focus on care. Clinical Support: In-house clinical team available to assist and advocate. 401k Retirement Plan: Eligible after waiting period; 4% match with 5% contribution. Extras: Travel reimbursement, housing allowance, meals, referral bonuses, and more. That's substantive, no placeholders. So Benefits section is good.
* Qualifications: The posting has "Required Experience / Certifications / Licensure". I could use "Requirements" for that, or "Qualifications". The example headings include both. I'll use "Requirements" since that's what the posting calls it, or maybe "Qualifications". I'll check the rule: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists both Requirements and Qualifications. I might use one or the other, or combine. I'll use "Requirements" for the cert/experience part, and maybe "Skills" for the procedure-specific skills. But I need to be careful not to create thin sections.
Let me re-read the posting carefully and extract only substantive, non-placeholders info.
Structure planning:
- I'll start with a
for minor metadata like Job ID, start date, duration, hours, employment type, location, maybe schedule summary. But the rule says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." I'll
` for prose - Do NOT repeat the job title as a heading (page already shows it) - 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 - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Analyze the Input Text:** Let me parse the job posting content. It's from ARMStaffing, travel nurse RN OR - Operating Room in McKinney, Texas. Key sections I can identify: - Job Title/Position: travel nurse RN OR - Operating Room (but I shouldn't repeat it as a heading) - Job ID: #38108861 (should be folded into a short
or dropped, but the rule says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." I'll fold it into a
at the end or beginning, but carefully.) - Specialty: OR - Operating Room - Discipline: RN - Start Date: ASAP - Duration: 13 weeks - Hours: 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel - Location: McKinney, TX - Assignment Duration: 13-week contract position - Schedule: 7 PM - 7 AM, Thursday, Friday, Saturday. Call requirement of one day a week and one weekend a month. - Job Description: seeking skilled Travel RN specializing in Operating Room duties. Ideal candidate will possess essential general/trauma OR skills and significant experience in the operating room, particularly in neuro and ortho/spine procedures. This role requires a team player with a positive attitude. - Responsibilities: Assist in various surgical procedures including ortho, neuro, robotics, general, trauma, and urology. Collaborate with surgical teams to ensure patient safety and quality care. Monitor patient vital signs and conditions during surgery. - Required Experience / Certifications / Licensure: Must have at least 1 year of experience in the Operating Room. Must possess current BLS certification. Experience in neuro and ortho/spine required. Trauma center experience is preferred. - Why ARMStaffing? / Benefits: Health Benefits: Medical, Dental, Vision, Life, and more. Onboarding Made Easy: We handle physicals, titers, and more so you can focus on care. Clinical Support: In-house clinical team available to assist and advocate. 401k Retirement Plan: Eligible after waiting period; 4% match with 5% contribution. Recruiter Matching: Get paired with a recruiter based on your location and specialty. Extras: Travel reimbursement, housing allowance, meals, referral bonuses, and more. - Additional praise/boilerplate about ARMStaffing: SIA's Top-50 Fastest Growing Healthcare Staffing Firms – 2019, SIA's Largest Healthcare Staffing Agencies in the U.S. – 2023, Top Workplace in the Lehigh Valley – 2022, 2023, Perfect scores for 'Name, Not a Number' and 'Recruiters' Personalities' on Highway Hypodermics, The Joint Commission’s Gold Seal of Approval for healthcare staffing, 15 years strong and counting!, Contract & local rates may vary based on location and applicant residency. Ask your ARMStaffing recruiter for details! - Pay package: 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:OR,19:00:00-07:00:00 - About ARMStaffing: description of the company. Now, I need to follow the strict rules: - Use `
` for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But only include them if the posting has real, specific content. Never emit a heading followed by filler/placeholder text. - Do NOT repeat the job title as a heading. - 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. - Never create Pay/Schedule/Benefits sections unless the posting actually states them. - Never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). - Prefer a few substantive sections over many thin ones. - Output ONLY the HTML fragment — no /, no markdown code fences. Let me decide which sections to include based on actual content: - "About the role": The posting has job description, responsibilities, requirements. I could use "About the role" or maybe just start with Responsibilities/Requirements. The rule says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I need to map the content to these headings appropriately, but only if there's real content.
- Let's map:
* "About the role" could cover the general description, specialty, discipline, start date, duration, hours, employment type, location, schedule. But the rule says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". I need to be careful not to create thin sections.
* "Responsibilities": clearly present - list of duties.
* "Requirements": clearly present - certifications, licensure, experience.
* "Qualifications": might overlap with Requirements. The example list includes "Qualifications" but the rule says use those headings if applicable. I'll see if there's distinct "Qualifications" content. The posting has "Required Experience / Certifications / Licensure" which is essentially qualifications. I might combine or use one.
* "Skills": maybe neuro and ortho/spine skills, robotics, etc. Could be part of Requirements or a separate section.
* "Benefits": clearly present - health benefits, 401k, onboarding, clinical support, extras.
* "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." It also says "Contract & local rates may vary based on location and applicant residency. Ask your ARMStaffing recruiter for details!" And "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." There's also "Posted job title: RN:OR,19:00:00-07:00:00". The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay-related info, but it also has "tax-free stipend amount to be determined" and "subject to confirmation". The rule also says "never emit a heading followed by filler/placeholder text (e.g. ... "TBD")". So I should NOT create a Pay section if it contains "amount to be determined" or "TBD". Let's read carefully: "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." This contains "amount to be determined" which is a placeholder. The rule says never emit a heading followed by filler/placeholder text. So I should either omit the Pay section, or include the substantive part without the placeholder. But the rule is strict: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". So if I create a Pay , I'd need to put content after it. If the content includes "amount to be determined", that's a placeholder. I think I should either fold pay info into a
without creating a Pay heading, or omit the Pay section entirely. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, but with placeholders. I'll interpret "actually states them" as having concrete, specific information without placeholders that would violate the "no filler" rule. I'll include pay-related info in a
perhaps, or fold it into metadata. But the rule says use
for section headings (e.g. ... Pay, Schedule). I need to decide.
* "Schedule": the posting has "Shift: 12 hours, nights" and "Schedule Shift: 7 PM - 7 AM, Thursday, Friday, Saturday. Call requirement of one day a week and one weekend a month." So Schedule has specific content. I can create a Schedule section with that info.
* Benefits: has concrete info: Health Benefits: Medical, Dental, Vision, Life, and more. Onboarding Made Easy: We handle physicals, titers, and more so you can focus on care. Clinical Support: In-house clinical team available to assist and advocate. 401k Retirement Plan: Eligible after waiting period; 4% match with 5% contribution. Extras: Travel reimbursement, housing allowance, meals, referral bonuses, and more. That's substantive, no placeholders. So Benefits section is good.
* Qualifications: The posting has "Required Experience / Certifications / Licensure". I could use "Requirements" for that, or "Qualifications". The example headings include both. I'll use "Requirements" since that's what the posting calls it, or maybe "Qualifications". I'll check the rule: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists both Requirements and Qualifications. I might use one or the other, or combine. I'll use "Requirements" for the cert/experience part, and maybe "Skills" for the procedure-specific skills. But I need to be careful not to create thin sections.
Let me re-read the posting carefully and extract only substantive, non-placeholders info.
Structure planning:
- I'll start with a
for minor metadata like Job ID, start date, duration, hours, employment type, location, maybe schedule summary. But the rule says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." I'll