Travel RRT - Make $1,729 - $1,954/week
` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use `- ` for lists 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 carefully go through the provided job posting text. It's from Aya Healthcare, for an RRT position in Roanoke, VA.
Key parts:
- "Aya Healthcare has an immediate opening for the following position: RRT in Roanoke, VA."
- "We’ll work with you to build the healthcare career of your dreams."
- "Whether you want a job close to home or across the country, we’ve got you."
- "Job Details"
- "Profession: Respiratory / Neuro Diagnostics"
- "Pay: $1729 to $1954 weekly"
- "Assignment Length: 13 weeks"
- "Shift: Nights"
- "Schedule: 3, 12-Hour 19:00 - 07:00"
- "Openings: 1"
- "Start Date: 10/05/2026"
- "Charting System: Epic"
- "Requirements"
- "Experience: 1 Year"
- "Required Certifications & Skills" (this seems like a combined section)
- Then a long list of skills/certifications:
"Skills: Adult Critical Care, BiPAP, CPAP, Extubation, High Flow Nasal Cannula (HFNC), Interpretation of Arterial Blood Gases (ABGs), Nasal airway placement, Nasal airway suctioning, Oral airway placement, Oral/nasal Suctioning, Aerosol set up mask, Aerosol set up trach, Albuterol, Atrovent, Bicarbonate, Combivent, Flovent, Flow-by, Hand held, Inhaled Flolan, Inhaled steroids, Lidocaine, Medihaler, Metered Dose Inhaler (MDI), Mucomyst, Sputum specimen collection, T-piece, Trach collar, Trach collar, Tracheostomy care/management, Troubleshooting high pressure alarms, Pulmicort, Racemic epinephrine, Ultrasonic, Weaning from mechanical ventilation"
"Certifications: ACLS, BLS, RRT"
- "Facility & Unit Information"
- "Facility Type: Acute Care Hospital"
- "Charting Experience: Yes"
- "Facility Level Trauma: Level 1"
- "Magnet Facility: 1"
- "Facility Bed Count: 635"
- "Patient RatiosNights: 25Weekends: 25" (probably "Nights: 25%, Weekends: 25%" or just "Nights 25, Weekends 25" - need to preserve as is, but it's a bit messy. I'll treat it as text.)
- "Aya Delivers: ..." - this is boilerplate/recruiting fluff. The rules say to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This "Aya Delivers" section seems like marketing boilerplate. I should remove it or fold it? Rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It doesn't explicitly say remove all marketing text, but "boilerplate" often includes such sections. However, it also says "Preserve ALL substantive information; do NOT invent or summarize away detail." The "Aya Delivers" part has some substantive info about their advantages, but it's mostly marketing. I need to decide. Looking at the rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The EEO statement is at the end: "Aya is an Equal Employment Opportunity ("EEO") Employer and welcomes all to apply." That must be removed per rules. The "Aya Delivers" section might be considered boilerplate too. I'll evaluate each part.
- The end has: "Aya is an Equal Employment Opportunity ("EEO") Employer and welcomes all to apply." -> Must remove.
Let me list all sections and determine what to keep, per rules:
Allowed headings (h3): About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But only include if the posting has real specific content. Never emit a heading followed by filler/placeholder text.
Let's map the content to these headings, but carefully, since the rules say "Prefer a few substantive sections over many thin ones" and "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text".
The posting has:
- Pay: "$1729 to $1954 weekly" -> Pay section is valid, has specific content.
- Schedule: "3, 12-Hour 19:00 - 07:00" and "Shift: Nights" and "Assignment Length: 13 weeks" -> Schedule section could be valid. But need to be careful: "Schedule: 3, 12-Hour 19:00 - 07:00" is specific. I'll use Schedule heading.
- Assignment Length: 13 weeks -> could be part of Schedule or a separate meta, but rules say fold minor metadata into a short
or drop it. I'll consider putting assignment length in a
or under Schedule.
- Start Date: 10/05/2026 -> minor metadata, fold into
.
- Openings: 1 -> minor metadata.
- Profession: Respiratory / Neuro Diagnostics -> could be "About the role" or part of intro.
- Requirements Experience: 1 Year -> Requirements section.
- Required Certifications & Skills -> Skills section, but also Certifications. The heading "Skills" is allowed. I'll put certifications and skills under Skills, or maybe "Qualifications". Rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I can use Skills, Requirements, Qualifications. I need to map appropriately.
Let's parse the "Required Certifications & Skills" block:
It lists Skills (long list) and Certifications (ACLS, BLS, RRT). I'll use Skills
for the skills list, and maybe mention certifications within or as a sub-list. But rules say use - for any list of duties/requirements/benefits. So I'll make an unordered list of skills, and maybe a small list for certifications. Or I could combine under "Qualifications". Let's see.
Facility & Unit Information:
- Facility Type: Acute Care Hospital
- Charting Experience: Yes
- Facility Level Trauma: Level 1
- Magnet Facility: 1
- Facility Bed Count: 635
- Patient RatiosNights: 25Weekends: 25 -> This is patient ratios. Could be under "Requirements" or a separate thing, but rules limit headings. I'll maybe fold into a
or use one heading. "Patient Ratios" might be considered part of the job details. I'll see.
"Aya Delivers:" section: This has text about most jobs, competitive advantage, expedited licensing, expert career guidance, best-in-class support system. This is marketing boilerplate. Rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This seems like boilerplate recruiter fluff. I should remove it. However, it does contain some specific info about benefits, but it's not direct from the job posting's core details. I'll remove it to keep it clean and focused on the job itself, as per "Prefer a few substantive sections over many thin ones" and removing boilerplate.
EEO at the end: Must remove.
Now, let's structure the HTML fragment.
Allowed headings: I need to decide which ones have real, specific content.
Let's go through the posting systematically and extract only substantive, non-boilerplate, specific info.
Intro/Job identity: "Aya Healthcare has an immediate opening for the following position: RRT in Roanoke, VA." This is the job title and location. Rules: "Do NOT repeat the job title as a heading (the page already shows it)". So I shouldn't have an or
for "RRT in Roanoke, VA". I can include it in a
maybe, or just start with the details. The rules say output ONLY the HTML fragment, no /. I'll probably start with a
containing the job title and location, or just the details directly. But careful: "Do NOT repeat the job title as a heading (the page already shows it)" - so I won't use an heading for it. I can put it in a
at the top, or just omit and let the context be. I think I'll put it in a
at the very top, as provenance, but not as a heading. Actually, the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use those headings only for sections that have content. I'll not put a heading for the job title.
Let's list what to include:
1. Job details that are specific and not boilerplate:
- Profession: Respiratory / Neuro Diagnostics
- Pay: $1729 to $1954 weekly
- Assignment Length: 13 weeks
- Shift: Nights
- Schedule: 3, 12-Hour 19:00 - 07:00
- Openings: 1 (maybe fold into
)
- Start Date: 10/05/2026 (fold into
)
- Charting System: Epic
2. Requirements:
- Experience: 1 Year
- Required Certifications & Skills (the list)
3. Skills list (long list) - under
Skills
or Qualifications
. The posting says "Required Certifications & Skills". I'll 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 carefully go through the provided job posting text. It's from Aya Healthcare, for an RRT position in Roanoke, VA. Key parts: - "Aya Healthcare has an immediate opening for the following position: RRT in Roanoke, VA." - "We’ll work with you to build the healthcare career of your dreams." - "Whether you want a job close to home or across the country, we’ve got you." - "Job Details" - "Profession: Respiratory / Neuro Diagnostics" - "Pay: $1729 to $1954 weekly" - "Assignment Length: 13 weeks" - "Shift: Nights" - "Schedule: 3, 12-Hour 19:00 - 07:00" - "Openings: 1" - "Start Date: 10/05/2026" - "Charting System: Epic" - "Requirements" - "Experience: 1 Year" - "Required Certifications & Skills" (this seems like a combined section) - Then a long list of skills/certifications: "Skills: Adult Critical Care, BiPAP, CPAP, Extubation, High Flow Nasal Cannula (HFNC), Interpretation of Arterial Blood Gases (ABGs), Nasal airway placement, Nasal airway suctioning, Oral airway placement, Oral/nasal Suctioning, Aerosol set up mask, Aerosol set up trach, Albuterol, Atrovent, Bicarbonate, Combivent, Flovent, Flow-by, Hand held, Inhaled Flolan, Inhaled steroids, Lidocaine, Medihaler, Metered Dose Inhaler (MDI), Mucomyst, Sputum specimen collection, T-piece, Trach collar, Trach collar, Tracheostomy care/management, Troubleshooting high pressure alarms, Pulmicort, Racemic epinephrine, Ultrasonic, Weaning from mechanical ventilation" "Certifications: ACLS, BLS, RRT" - "Facility & Unit Information" - "Facility Type: Acute Care Hospital" - "Charting Experience: Yes" - "Facility Level Trauma: Level 1" - "Magnet Facility: 1" - "Facility Bed Count: 635" - "Patient RatiosNights: 25Weekends: 25" (probably "Nights: 25%, Weekends: 25%" or just "Nights 25, Weekends 25" - need to preserve as is, but it's a bit messy. I'll treat it as text.) - "Aya Delivers: ..." - this is boilerplate/recruiting fluff. The rules say to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This "Aya Delivers" section seems like marketing boilerplate. I should remove it or fold it? Rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It doesn't explicitly say remove all marketing text, but "boilerplate" often includes such sections. However, it also says "Preserve ALL substantive information; do NOT invent or summarize away detail." The "Aya Delivers" part has some substantive info about their advantages, but it's mostly marketing. I need to decide. Looking at the rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The EEO statement is at the end: "Aya is an Equal Employment Opportunity ("EEO") Employer and welcomes all to apply." That must be removed per rules. The "Aya Delivers" section might be considered boilerplate too. I'll evaluate each part. - The end has: "Aya is an Equal Employment Opportunity ("EEO") Employer and welcomes all to apply." -> Must remove. Let me list all sections and determine what to keep, per rules: Allowed headings (h3): About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But only include if the posting has real specific content. Never emit a heading followed by filler/placeholder text. Let's map the content to these headings, but carefully, since the rules say "Prefer a few substantive sections over many thin ones" and "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The posting has: - Pay: "$1729 to $1954 weekly" -> Pay section is valid, has specific content. - Schedule: "3, 12-Hour 19:00 - 07:00" and "Shift: Nights" and "Assignment Length: 13 weeks" -> Schedule section could be valid. But need to be careful: "Schedule: 3, 12-Hour 19:00 - 07:00" is specific. I'll use Schedule heading. - Assignment Length: 13 weeks -> could be part of Schedule or a separate meta, but rules say fold minor metadata into a short
or drop it. I'll consider putting assignment length in a
or under Schedule. - Start Date: 10/05/2026 -> minor metadata, fold into
. - Openings: 1 -> minor metadata. - Profession: Respiratory / Neuro Diagnostics -> could be "About the role" or part of intro. - Requirements Experience: 1 Year -> Requirements section. - Required Certifications & Skills -> Skills section, but also Certifications. The heading "Skills" is allowed. I'll put certifications and skills under Skills, or maybe "Qualifications". Rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I can use Skills, Requirements, Qualifications. I need to map appropriately.
Let's parse the "Required Certifications & Skills" block:
It lists Skills (long list) and Certifications (ACLS, BLS, RRT). I'll use Skills
for the skills list, and maybe mention certifications within or as a sub-list. But rules say use - for any list of duties/requirements/benefits. So I'll make an unordered list of skills, and maybe a small list for certifications. Or I could combine under "Qualifications". Let's see.
Facility & Unit Information:
- Facility Type: Acute Care Hospital
- Charting Experience: Yes
- Facility Level Trauma: Level 1
- Magnet Facility: 1
- Facility Bed Count: 635
- Patient RatiosNights: 25Weekends: 25 -> This is patient ratios. Could be under "Requirements" or a separate thing, but rules limit headings. I'll maybe fold into a
or use one heading. "Patient Ratios" might be considered part of the job details. I'll see.
"Aya Delivers:" section: This has text about most jobs, competitive advantage, expedited licensing, expert career guidance, best-in-class support system. This is marketing boilerplate. Rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This seems like boilerplate recruiter fluff. I should remove it. However, it does contain some specific info about benefits, but it's not direct from the job posting's core details. I'll remove it to keep it clean and focused on the job itself, as per "Prefer a few substantive sections over many thin ones" and removing boilerplate.
EEO at the end: Must remove.
Now, let's structure the HTML fragment.
Allowed headings: I need to decide which ones have real, specific content.
Let's go through the posting systematically and extract only substantive, non-boilerplate, specific info.
Intro/Job identity: "Aya Healthcare has an immediate opening for the following position: RRT in Roanoke, VA." This is the job title and location. Rules: "Do NOT repeat the job title as a heading (the page already shows it)". So I shouldn't have an or
for "RRT in Roanoke, VA". I can include it in a
maybe, or just start with the details. The rules say output ONLY the HTML fragment, no /. I'll probably start with a
containing the job title and location, or just the details directly. But careful: "Do NOT repeat the job title as a heading (the page already shows it)" - so I won't use an heading for it. I can put it in a
at the top, or just omit and let the context be. I think I'll put it in a
at the very top, as provenance, but not as a heading. Actually, the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use those headings only for sections that have content. I'll not put a heading for the job title.
Let's list what to include:
1. Job details that are specific and not boilerplate:
- Profession: Respiratory / Neuro Diagnostics
- Pay: $1729 to $1954 weekly
- Assignment Length: 13 weeks
- Shift: Nights
- Schedule: 3, 12-Hour 19:00 - 07:00
- Openings: 1 (maybe fold into
)
- Start Date: 10/05/2026 (fold into
)
- Charting System: Epic
2. Requirements:
- Experience: 1 Year
- Required Certifications & Skills (the list)
3. Skills list (long list) - under
Skills
or Qualifications
. The posting says "Required Certifications & Skills". I'll use
or use one heading. "Patient Ratios" might be considered part of the job details. I'll see. "Aya Delivers:" section: This has text about most jobs, competitive advantage, expedited licensing, expert career guidance, best-in-class support system. This is marketing boilerplate. Rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This seems like boilerplate recruiter fluff. I should remove it. However, it does contain some specific info about benefits, but it's not direct from the job posting's core details. I'll remove it to keep it clean and focused on the job itself, as per "Prefer a few substantive sections over many thin ones" and removing boilerplate. EEO at the end: Must remove. Now, let's structure the HTML fragment. Allowed headings: I need to decide which ones have real, specific content. Let's go through the posting systematically and extract only substantive, non-boilerplate, specific info. Intro/Job identity: "Aya Healthcare has an immediate opening for the following position: RRT in Roanoke, VA." This is the job title and location. Rules: "Do NOT repeat the job title as a heading (the page already shows it)". So I shouldn't have an or
for "RRT in Roanoke, VA". I can include it in a
maybe, or just start with the details. The rules say output ONLY the HTML fragment, no /. I'll probably start with a
containing the job title and location, or just the details directly. But careful: "Do NOT repeat the job title as a heading (the page already shows it)" - so I won't use an heading for it. I can put it in a
at the top, or just omit and let the context be. I think I'll put it in a
at the very top, as provenance, but not as a heading. Actually, the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use those headings only for sections that have content. I'll not put a heading for the job title. Let's list what to include: 1. Job details that are specific and not boilerplate: - Profession: Respiratory / Neuro Diagnostics - Pay: $1729 to $1954 weekly - Assignment Length: 13 weeks - Shift: Nights - Schedule: 3, 12-Hour 19:00 - 07:00 - Openings: 1 (maybe fold into
) - Start Date: 10/05/2026 (fold into
) - Charting System: Epic 2. Requirements: - Experience: 1 Year - Required Certifications & Skills (the list) 3. Skills list (long list) - under