Travel PCU Registered Nurse - Make $1,854 to $2,084/week
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists,
for prose
- Do NOT repeat job title as heading (page already shows it)
- Do NOT put Job ID / requisition numbers as headings — fold minor metadata into 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
- Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer a few substantive sections over many thin ones
- Output ONLY HTML fragment — no /, no markdown code fences
Now, let's map the content to appropriate sections.
The job title is "PCU Registered Nurse in Roanoke, VA" — we should not repeat as heading.
We have pay information: "$1854 to $2084 weekly" — that's specific, so we can have a Pay section.
Schedule: "Days", "3, 12-Hour 06:45 - 19:15" — specific, so Schedule section.
Assignment length: 13 weeks — could be part of Job Details or Schedule.
Openings: 2 — minor metadata, maybe fold into a short p.
Start date: 11/09/2026 — specific.
Charting system: Epic — requirement.
Experience: 1 Year — requirement.
Licensure: VA License or Compact License — requirement.
Previous Charge Nurse Experience: Preferred — requirement.
Facility & Unit Information: multiple details — could be a section "Facility & Unit Information" or "About the Facility". The rules mention headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We can use custom headings as long as they are semantic. The rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says e.g., so we can use other relevant headings.
We have "Aya Delivers" which is essentially benefits and perks. That's a Benefits section.
We also have "Aya is an Equal Employment Opportunity..." — that's boilerplate, remove.
The hashtag #HNPCUNATLI — job ID, drop.
Now, let's structure:
Possible sections:
1. Job Details (or About the Role) — include profession, assignment length, shift, schedule, openings, start date, charting system, experience, licensure, charge nurse experience.
2. Facility & Unit Information — facility type, compact license accepted, charting experience, trauma level, magnet, bed count, patient ratios.
3. Pay — pay range.
4. Schedule — shift details (though schedule already in job details, but we can have separate Schedule section if specific).
5. Benefits — from Aya Delivers.
But the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state pay, schedule, and benefits (Aya Delivers). So we can create those sections.
However, we should avoid duplication. The schedule is mentioned in job details and also shift/schedule. We can have a Schedule section with the shift details.
Similarly, pay is in job details, but we can have a Pay section.
Benefits are in Aya Delivers.
We need to preserve all substantive information. So we should include all details.
Let's decide on sections:
- About the Role (or Job Details) — include profession, assignment length, shift, schedule, openings, start date, charting system, experience, licensure, charge nurse experience.
- Facility & Unit Information — facility details.
- Pay — pay range.
- Schedule — shift schedule (maybe combine with job details? But rule says use Schedule heading if posting states it. The posting has "Shift: Days" and "Schedule: 3, 12-Hour 06:45 - 19:15". That's specific, so we can have a Schedule section.
- Benefits — from Aya Delivers.
But note: "Prefer a few substantive sections over many thin ones." So maybe combine Job Details and Schedule? However, the rule says use for section headings like Schedule. It's okay to have a Schedule section.
Let's see the example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use those.
We don't have explicit responsibilities list, but we have requirements (experience, licensure, charge nurse). Could have a Requirements section.
We have qualifications: experience, licensure, charge nurse preferred.
We have skills: charting system Epic.
But the posting doesn't have a separate responsibilities list. It's a travel nurse job, so responsibilities are typical PCU RN duties, but not listed. We should not invent.
Thus, we can have:
- About the Role (or Job Overview) — include assignment length, shift, schedule, openings, start date, charting system.
- Requirements — experience, licensure, charge nurse experience.
- Facility & Unit Information — facility details.
- Pay — pay range.
- Schedule — shift schedule (maybe redundant with About the Role). Could include shift and schedule in About the Role and not have separate Schedule. But the rule says use Schedule heading if posting states it. The posting has "Shift" and "Schedule" as separate lines. I think it's okay to have a Schedule section.
- Benefits — from Aya Delivers.
We also have "Aya Delivers" which includes many benefits: competitive advantage, expedited licensing, career guidance, support system, weekly pay, benefits (medical, dental, vision, life insurance day one), keep insurance up to 24 days between assignments, 401(k) match, paid company housing or housing stipend, paid sick time, continuing education, licensure/relocation reimbursements, pay includes taxable wages and tax-free expense reimbursements.
That's a lot of benefits. So Benefits section is warranted.
Now, we need to output HTML fragment with and - or
.
Let's craft.
First, About the Role:
About the Role
Profession: Registered Nurse
Assignment Length: 13 weeks
Shift: Days
Schedule: 3, 12-Hour shifts (06:45 - 19:15)
Openings: 2
Start Date: 11/09/2026
Charting System: Epic
But maybe better as a list? The rule: use - for any list of duties/requirements/benefits, and
for prose. These are details, not a list of duties. Could be a list of details. I'll use
- for each detail.
But the rule says "use
- for any list of duties/requirements/benefits". These are not duties, but they are details. Could be either. I'll use
- for consistency.
Second, Requirements:
Requirements
- Experience: 1 Year
- Licensure: VA License or Compact License (Quick License State — application process takes 2 weeks or less)
- Previous Charge Nurse Experience: Preferred
Third, Facility & Unit Information:
Facility & Unit Information
- Facility Type: Acute Care Hospital
- Compact License Accepted: Yes
- Charting Experience: Yes
- Facility Level Trauma: Level 1
- Magnet Facility: Yes
- Facility Bed Count: 635
- Patient Ratios: Nights 5, Weekends 5
Fourth, Pay:
Pay
$1,854 to $2,084 weekly (includes taxable wages and tax-free expense reimbursements)
Fifth, Schedule: Already covered in About the Role. But we can have a separate Schedule section with shift details. However, to avoid duplication, maybe omit Schedule section and keep in About the Role. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states shift and schedule, so we could create a Schedule section. But we already have it in About the Role. I think it's okay to have a Schedule section with the same info? That would be duplication. Better to have one place. Since the rule says "Prefer a few substantive sections over many thin ones." So combine.
Thus, no separate Schedule section.
Sixth, Benefits:
Benefits
- Competitive advantage: largest job database, direct facility relationships, quick/same-day offers
- Expedited licensing and streamlined compliance with industry-leading on-time start rate
- Expert career guidance with dedicated recruiter
- Best-in-class support system: accurate weekly pay, 24/7 team dedicated to happiness on assignment
- Exceptional benefits including premium medical, dental, vision, and life insurance beginning day one of assignment
- Option to keep insurance coverage for up to 24 days between assignments
- Generous 401(k) match
- Paid company housing (pet-friendly) or generous housing stipend if eligible
- Paid sick time in accordance with applicable laws (accrue 1 hour per 30 hours worked)
- Access to unlimited continuing education units online
- Licensure, relocation, and other reimbursements when applicable
Note: The pay includes taxable wages and tax-free expense reimbursements — already in Pay section.
Also, the EEO statement is boilerplate, remove.
The hashtag #HNPCUNATLI — drop.
Now, ensure we don't have any placeholder text. All content is specific.
Now, output HTML fragment.
We'll write:
About the Role
- Profession: Registered Nurse
- Assignment Length: 13 weeks
- Shift: Days
- Schedule: 3, 12-Hour shifts (06:45 - 19:15)
- Openings: 2
- Start Date: 11/09/2026
- Charting System: Epic
Requirements
- Experience: 1 Year
- Licensure: VA License or Compact License (Quick License State — application process takes 2 weeks or less)
- Previous Charge Nurse Experience: Preferred
for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into 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 - Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's map the content to appropriate sections. The job title is "PCU Registered Nurse in Roanoke, VA" — we should not repeat as heading. We have pay information: "$1854 to $2084 weekly" — that's specific, so we can have a Pay section. Schedule: "Days", "3, 12-Hour 06:45 - 19:15" — specific, so Schedule section. Assignment length: 13 weeks — could be part of Job Details or Schedule. Openings: 2 — minor metadata, maybe fold into a short p. Start date: 11/09/2026 — specific. Charting system: Epic — requirement. Experience: 1 Year — requirement. Licensure: VA License or Compact License — requirement. Previous Charge Nurse Experience: Preferred — requirement. Facility & Unit Information: multiple details — could be a section "Facility & Unit Information" or "About the Facility". The rules mention headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We can use custom headings as long as they are semantic. The rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says e.g., so we can use other relevant headings.
We have "Aya Delivers" which is essentially benefits and perks. That's a Benefits section.
We also have "Aya is an Equal Employment Opportunity..." — that's boilerplate, remove.
The hashtag #HNPCUNATLI — job ID, drop.
Now, let's structure:
Possible sections:
1. Job Details (or About the Role) — include profession, assignment length, shift, schedule, openings, start date, charting system, experience, licensure, charge nurse experience.
2. Facility & Unit Information — facility type, compact license accepted, charting experience, trauma level, magnet, bed count, patient ratios.
3. Pay — pay range.
4. Schedule — shift details (though schedule already in job details, but we can have separate Schedule section if specific).
5. Benefits — from Aya Delivers.
But the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state pay, schedule, and benefits (Aya Delivers). So we can create those sections.
However, we should avoid duplication. The schedule is mentioned in job details and also shift/schedule. We can have a Schedule section with the shift details.
Similarly, pay is in job details, but we can have a Pay section.
Benefits are in Aya Delivers.
We need to preserve all substantive information. So we should include all details.
Let's decide on sections:
- About the Role (or Job Details) — include profession, assignment length, shift, schedule, openings, start date, charting system, experience, licensure, charge nurse experience.
- Facility & Unit Information — facility details.
- Pay — pay range.
- Schedule — shift schedule (maybe combine with job details? But rule says use Schedule heading if posting states it. The posting has "Shift: Days" and "Schedule: 3, 12-Hour 06:45 - 19:15". That's specific, so we can have a Schedule section.
- Benefits — from Aya Delivers.
But note: "Prefer a few substantive sections over many thin ones." So maybe combine Job Details and Schedule? However, the rule says use for section headings like Schedule. It's okay to have a Schedule section.
Let's see the example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use those.
We don't have explicit responsibilities list, but we have requirements (experience, licensure, charge nurse). Could have a Requirements section.
We have qualifications: experience, licensure, charge nurse preferred.
We have skills: charting system Epic.
But the posting doesn't have a separate responsibilities list. It's a travel nurse job, so responsibilities are typical PCU RN duties, but not listed. We should not invent.
Thus, we can have:
- About the Role (or Job Overview) — include assignment length, shift, schedule, openings, start date, charting system.
- Requirements — experience, licensure, charge nurse experience.
- Facility & Unit Information — facility details.
- Pay — pay range.
- Schedule — shift schedule (maybe redundant with About the Role). Could include shift and schedule in About the Role and not have separate Schedule. But the rule says use Schedule heading if posting states it. The posting has "Shift" and "Schedule" as separate lines. I think it's okay to have a Schedule section.
- Benefits — from Aya Delivers.
We also have "Aya Delivers" which includes many benefits: competitive advantage, expedited licensing, career guidance, support system, weekly pay, benefits (medical, dental, vision, life insurance day one), keep insurance up to 24 days between assignments, 401(k) match, paid company housing or housing stipend, paid sick time, continuing education, licensure/relocation reimbursements, pay includes taxable wages and tax-free expense reimbursements.
That's a lot of benefits. So Benefits section is warranted.
Now, we need to output HTML fragment with and - or
.
Let's craft.
First, About the Role:
About the Role
Profession: Registered Nurse
Assignment Length: 13 weeks
Shift: Days
Schedule: 3, 12-Hour shifts (06:45 - 19:15)
Openings: 2
Start Date: 11/09/2026
Charting System: Epic
But maybe better as a list? The rule: use - for any list of duties/requirements/benefits, and
for prose. These are details, not a list of duties. Could be a list of details. I'll use
- for each detail.
But the rule says "use
- for any list of duties/requirements/benefits". These are not duties, but they are details. Could be either. I'll use
- for consistency.
Second, Requirements:
Requirements
- Experience: 1 Year
- Licensure: VA License or Compact License (Quick License State — application process takes 2 weeks or less)
- Previous Charge Nurse Experience: Preferred
Third, Facility & Unit Information:
Facility & Unit Information
- Facility Type: Acute Care Hospital
- Compact License Accepted: Yes
- Charting Experience: Yes
- Facility Level Trauma: Level 1
- Magnet Facility: Yes
- Facility Bed Count: 635
- Patient Ratios: Nights 5, Weekends 5
Fourth, Pay:
Pay
$1,854 to $2,084 weekly (includes taxable wages and tax-free expense reimbursements)
Fifth, Schedule: Already covered in About the Role. But we can have a separate Schedule section with shift details. However, to avoid duplication, maybe omit Schedule section and keep in About the Role. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states shift and schedule, so we could create a Schedule section. But we already have it in About the Role. I think it's okay to have a Schedule section with the same info? That would be duplication. Better to have one place. Since the rule says "Prefer a few substantive sections over many thin ones." So combine.
Thus, no separate Schedule section.
Sixth, Benefits:
Benefits
- Competitive advantage: largest job database, direct facility relationships, quick/same-day offers
- Expedited licensing and streamlined compliance with industry-leading on-time start rate
- Expert career guidance with dedicated recruiter
- Best-in-class support system: accurate weekly pay, 24/7 team dedicated to happiness on assignment
- Exceptional benefits including premium medical, dental, vision, and life insurance beginning day one of assignment
- Option to keep insurance coverage for up to 24 days between assignments
- Generous 401(k) match
- Paid company housing (pet-friendly) or generous housing stipend if eligible
- Paid sick time in accordance with applicable laws (accrue 1 hour per 30 hours worked)
- Access to unlimited continuing education units online
- Licensure, relocation, and other reimbursements when applicable
Note: The pay includes taxable wages and tax-free expense reimbursements — already in Pay section.
Also, the EEO statement is boilerplate, remove.
The hashtag #HNPCUNATLI — drop.
Now, ensure we don't have any placeholder text. All content is specific.
Now, output HTML fragment.
We'll write:
About the Role
- Profession: Registered Nurse
- Assignment Length: 13 weeks
- Shift: Days
- Schedule: 3, 12-Hour shifts (06:45 - 19:15)
- Openings: 2
- Start Date: 11/09/2026
- Charting System: Epic
Requirements
- Experience: 1 Year
- Licensure: VA License or Compact License (Quick License State — application process takes 2 weeks or less)
- Previous Charge Nurse Experience: Preferred
and - or
.
Let's craft.
First, About the Role:
About the Role
Profession: Registered Nurse
Assignment Length: 13 weeks
Shift: Days
Schedule: 3, 12-Hour shifts (06:45 - 19:15)
Openings: 2
Start Date: 11/09/2026
Charting System: Epic
But maybe better as a list? The rule: use - for any list of duties/requirements/benefits, and
for prose. These are details, not a list of duties. Could be a list of details. I'll use
- for each detail.
But the rule says "use
- for any list of duties/requirements/benefits". These are not duties, but they are details. Could be either. I'll use
- for consistency.
Second, Requirements:
Requirements
- Experience: 1 Year
- Licensure: VA License or Compact License (Quick License State — application process takes 2 weeks or less)
- Previous Charge Nurse Experience: Preferred
Third, Facility & Unit Information:
Facility & Unit Information
- Facility Type: Acute Care Hospital
- Compact License Accepted: Yes
- Charting Experience: Yes
- Facility Level Trauma: Level 1
- Magnet Facility: Yes
- Facility Bed Count: 635
- Patient Ratios: Nights 5, Weekends 5
Fourth, Pay:
Pay
$1,854 to $2,084 weekly (includes taxable wages and tax-free expense reimbursements)
Fifth, Schedule: Already covered in About the Role. But we can have a separate Schedule section with shift details. However, to avoid duplication, maybe omit Schedule section and keep in About the Role. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states shift and schedule, so we could create a Schedule section. But we already have it in About the Role. I think it's okay to have a Schedule section with the same info? That would be duplication. Better to have one place. Since the rule says "Prefer a few substantive sections over many thin ones." So combine.
Thus, no separate Schedule section.
Sixth, Benefits:
Benefits
- Competitive advantage: largest job database, direct facility relationships, quick/same-day offers
- Expedited licensing and streamlined compliance with industry-leading on-time start rate
- Expert career guidance with dedicated recruiter
- Best-in-class support system: accurate weekly pay, 24/7 team dedicated to happiness on assignment
- Exceptional benefits including premium medical, dental, vision, and life insurance beginning day one of assignment
- Option to keep insurance coverage for up to 24 days between assignments
- Generous 401(k) match
- Paid company housing (pet-friendly) or generous housing stipend if eligible
- Paid sick time in accordance with applicable laws (accrue 1 hour per 30 hours worked)
- Access to unlimited continuing education units online
- Licensure, relocation, and other reimbursements when applicable
Note: The pay includes taxable wages and tax-free expense reimbursements — already in Pay section.
Also, the EEO statement is boilerplate, remove.
The hashtag #HNPCUNATLI — drop.
Now, ensure we don't have any placeholder text. All content is specific.
Now, output HTML fragment.
We'll write:
About the Role
- Profession: Registered Nurse
- Assignment Length: 13 weeks
- Shift: Days
- Schedule: 3, 12-Hour shifts (06:45 - 19:15)
- Openings: 2
- Start Date: 11/09/2026
- Charting System: Epic
Requirements
- Experience: 1 Year
- Licensure: VA License or Compact License (Quick License State — application process takes 2 weeks or less)
- Previous Charge Nurse Experience: Preferred
. Let's craft. First, About the Role:
About the Role
Profession: Registered Nurse
Assignment Length: 13 weeks
Shift: Days
Schedule: 3, 12-Hour shifts (06:45 - 19:15)
Openings: 2
Start Date: 11/09/2026
Charting System: Epic
But maybe better as a list? The rule: use- for any list of duties/requirements/benefits, and
for prose. These are details, not a list of duties. Could be a list of details. I'll use
- for each detail.
But the rule says "use
- for any list of duties/requirements/benefits". These are not duties, but they are details. Could be either. I'll use
- for consistency.
Second, Requirements:
Requirements
- Experience: 1 Year
- Licensure: VA License or Compact License (Quick License State — application process takes 2 weeks or less)
- Previous Charge Nurse Experience: Preferred
Facility & Unit Information
- Facility Type: Acute Care Hospital
- Compact License Accepted: Yes
- Charting Experience: Yes
- Facility Level Trauma: Level 1
- Magnet Facility: Yes
- Facility Bed Count: 635
- Patient Ratios: Nights 5, Weekends 5
Pay
$1,854 to $2,084 weekly (includes taxable wages and tax-free expense reimbursements)
Fifth, Schedule: Already covered in About the Role. But we can have a separate Schedule section with shift details. However, to avoid duplication, maybe omit Schedule section and keep in About the Role. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states shift and schedule, so we could create a Schedule section. But we already have it in About the Role. I think it's okay to have a Schedule section with the same info? That would be duplication. Better to have one place. Since the rule says "Prefer a few substantive sections over many thin ones." So combine. Thus, no separate Schedule section. Sixth, Benefits:Benefits
- Competitive advantage: largest job database, direct facility relationships, quick/same-day offers
- Expedited licensing and streamlined compliance with industry-leading on-time start rate
- Expert career guidance with dedicated recruiter
- Best-in-class support system: accurate weekly pay, 24/7 team dedicated to happiness on assignment
- Exceptional benefits including premium medical, dental, vision, and life insurance beginning day one of assignment
- Option to keep insurance coverage for up to 24 days between assignments
- Generous 401(k) match
- Paid company housing (pet-friendly) or generous housing stipend if eligible
- Paid sick time in accordance with applicable laws (accrue 1 hour per 30 hours worked)
- Access to unlimited continuing education units online
- Licensure, relocation, and other reimbursements when applicable
About the Role
- Profession: Registered Nurse
- Assignment Length: 13 weeks
- Shift: Days
- Schedule: 3, 12-Hour shifts (06:45 - 19:15)
- Openings: 2
- Start Date: 11/09/2026
- Charting System: Epic
Requirements
- Experience: 1 Year
- Licensure: VA License or Compact License (Quick License State — application process takes 2 weeks or less)
- Previous Charge Nurse Experience: Preferred
- for consistency.
Second, Requirements:
- for any list of duties/requirements/benefits". These are not duties, but they are details. Could be either. I'll use
- for each detail.
But the rule says "use