Travel RRT - Make $1,885 - $2,115/week
Aya Healthcare · Albuquerque, NM · 4 days ago
On-siteManagementInternship
The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules.
First, I need to identify the sections. The posting has:
- Job details (profession, pay, assignment length, shift, schedule, openings, start date, charting system)
- Requirements (experience, required certifications & skills - both skills list and certifications list)
- Facility & Unit Information (facility type, charting experience, facility level trauma, facility bed count)
- Aya Delivers section (benefits, support, etc.)
Rules:
- Use for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading (page already shows it)
- Do NOT put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions)
- Include 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 few substantive sections over many thin ones
- Output ONLY HTML fragment, no /, no markdown code fences
Now, let's map the content to sections.
The job title is "RRT in Albuquerque, NM" - but we shouldn't repeat it as heading.
We have:
- Pay: $1885 to $2115 weekly (specific)
- Schedule: 3, 12-Hour 06:00 - 18:30 (specific)
- Assignment Length: 13 weeks
- Shift: Days
- Openings: 1
- Start Date: 12/07/2026
- Charting System: Cerner
These could go under "Job Details" or "About the role". The rules mention headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We should use those when appropriate.
We have a "Requirements" section with experience, skills, certifications. That's a clear "Requirements" heading.
We have "Facility & Unit Information" - could be "About the facility" or similar, but the rules don't specify that heading. Could be "About the role" or maybe "Facility Information". The rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" for general job details, "Requirements" for requirements, "Benefits" for benefits.
The "Aya Delivers" section contains benefits and support details. That's a "Benefits" section.
Also there is "Pay" mentioned specifically, so we could have a "Pay" section.
"Schedule" is also specific.
But the rules say: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state them, so we can include.
However, we should avoid too many thin sections. For example, "Pay" could be a short paragraph under "About the role". But the rules say use for Pay, Schedule, Benefits if they have content. The example headings include Pay, Schedule, Benefits. So we can create separate sections for each if they have substantive content.
Let's decide on sections:
1. About the role: could include profession, assignment length, shift, schedule, openings, start date, charting system, facility info.
2. Requirements: experience, skills, certifications, travel experience required.
3. Benefits: the Aya Delivers benefits list.
4. Pay: the pay range.
5. Schedule: the schedule details.
But note: the schedule is already in job details. Could combine.
The rules: "Prefer a few substantive sections over many thin ones." So maybe combine pay and schedule into "Job Details" or "About the role". But the example headings include Pay and Schedule as separate. However, the posting has specific pay and schedule, so we could make them separate sections.
Let's see the content: Pay is a single line: "$1885 to $2115 weekly". That's thin. Schedule is "3, 12-Hour 06:00 - 18:30". Also thin. Could be combined into a "Job Details" section with a list.
But the rules say: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we must use all; only when there is real content.
I think we can create:
- About the role (includes job details, facility info)
- Requirements (experience, skills, certifications)
- Benefits (the Aya Delivers list)
- Pay (the pay range)
- Schedule (the schedule)
But Pay and Schedule are very short. Could be a single "Compensation & Schedule" section? But the rules list them separately. However, the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, but they are minimal. The rule also says "never emit a heading followed by filler/placeholder text". A single line is not filler, it's specific. So it's okay.
But to avoid many thin sections, maybe combine Pay and Schedule into "Job Details" under "About the role". However, the example headings include Pay and Schedule as separate, so maybe they expect separate sections when present.
Let's look at the user's instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we can use those headings. The posting has no "Responsibilities" or "Qualifications" separate from Requirements. It has "Requirements" with experience, skills, certifications. That's essentially qualifications and skills.
We have "Skills" listed as a long list. Could be a "Skills" section. But the rules say "Skills" as a heading example. However, the posting has "Required Certifications & Skills" with two sublists: Skills and Certifications. That could be under "Requirements" with sublists.
I think the best is:
- About the role: includes profession, assignment length, shift, schedule, openings, start date, charting system, facility info.
- Requirements: experience, travel experience required, skills list, certifications list.
- Benefits: the Aya Delivers benefits.
- Pay: the pay range.
Schedule is already in About the role.
But the schedule is specific: "3, 12-Hour 06:00 - 18:30". Could be a separate Schedule section. But it's just one line. I'll include it in About the role.
Now, we must remove boilerplate: "Aya Healthcare has an immediate opening for the following position: RRT in Albuquerque, NM. 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." That's marketing fluff, but it's part of the posting. The rules say "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The EEO statement at the end: "Aya is an Equal Employment Opportunity ("EEO") Employer and welcomes all to apply. #HP" should be removed. Also the "Aya Delivers" marketing paragraphs about most jobs, competitive advantage, etc. are somewhat promotional but they also contain benefits. The benefits are listed after that. We should keep the benefits list but maybe not the promotional paragraphs. However, the promotional paragraphs contain some substantive info like "Exceptional benefits, including premium medical, dental, vision and life insurance beginning day one of your assignment." That's a benefit. The rest is fluff. We need to preserve ALL substantive information. So we should extract the actual benefits from that section.
Let's parse the Aya Delivers section:
"The most jobs in the industry. We have the largest and most reliable job database, which means the jobs you see are open, updated in real time and ready for you!" - fluff.
"Competitive advantage over other agencies. Front-of-the-line access through our direct facility relationships — many with quick (even same-day) offers, giving you the best chance of securing your ideal opportunity." - fluff.
"Expedited licensing and streamlined compliance. An industry-leading on-time start rate and strong relationships with boards of nursing across the country to accelerate the process in all 50 states." - fluff.
"Expert career guidance. A dedicated recruiter to help you achieve your dream career. Travel, per diem, permanent — we have the reach and access to get you the jobs you want, and the expertise to help you realize your long-term goals." - fluff.
"A best-in-class support system and an exceptional experience. Enjoy accurate, weekly pay, and an entire team dedicated to your happiness on assignment, 24/7. Plus, you get everything you expect from the largest healthcare staffing company in the industry:" - fluff.
Then list of benefits:
- Exceptional benefits, including premium medical, dental, vision and life insurance beginning day one of your assignment.
- Want to take time off? Keep insurance coverage for up to 24 Days between assignments.
- A generous 401(k) match.
- Paid company housing (we’ll help you bring your pets along, too!) or a generous housing stipend, if eligible.
- Paid sick time in accordance with all applicable state, federal, and local laws. Aya’s general sick leave policy is that employees accrue one hour of paid sick leave for every 30 hours worked. However, to the extent any provisions of the statement above conflict with any applicable paid sick leave laws, the applicable paid sick leave laws are controlling.
- Access to unlimited continuing education units online.
- Licensure, relocation and other reimbursements, when applicable.
Then: "Pay listed above includes taxable wages and tax-free expense reimbursements." That's about pay.
Then EEO statement.
So for Benefits section, we should list those bullet points.
Now, for Requirements: we have "Experience: 1 Year", "Required Certifications & Skills" with Skills list and Certifications list, "Travel Experience Required: Yes". Also "Charting Experience: Yes" under Facility & Unit Information.
We should include all.
Now, let's structure HTML.
We'll have:
About the role
Profession: Respiratory / Neuro Diagnostics
Assignment Length: 13 weeks
Shift: Days
Schedule: 3, 12-Hour 06:00 - 18:30
Openings: 1
Start Date: 12/07/2026
Charting System: Cerner
Facility Information
(but not in example headings; maybe "About the role" includes facility info)
The rules don't have "Facility Information" as example, but we can use "About the role" to include facility details. Or create a separate "Facility" heading? The rules say 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 headings if needed. But to stay consistent, maybe include facility info under "About the role".
Alternatively, create a "Facility Details" heading. But
for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include 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 few substantive sections over many thin ones - Output ONLY HTML fragment, no /, no markdown code fences Now, let's map the content to sections. The job title is "RRT in Albuquerque, NM" - but we shouldn't repeat it as heading. We have: - Pay: $1885 to $2115 weekly (specific) - Schedule: 3, 12-Hour 06:00 - 18:30 (specific) - Assignment Length: 13 weeks - Shift: Days - Openings: 1 - Start Date: 12/07/2026 - Charting System: Cerner These could go under "Job Details" or "About the role". The rules mention headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We should use those when appropriate. We have a "Requirements" section with experience, skills, certifications. That's a clear "Requirements" heading. We have "Facility & Unit Information" - could be "About the facility" or similar, but the rules don't specify that heading. Could be "About the role" or maybe "Facility Information". The rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" for general job details, "Requirements" for requirements, "Benefits" for benefits.
The "Aya Delivers" section contains benefits and support details. That's a "Benefits" section.
Also there is "Pay" mentioned specifically, so we could have a "Pay" section.
"Schedule" is also specific.
But the rules say: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state them, so we can include.
However, we should avoid too many thin sections. For example, "Pay" could be a short paragraph under "About the role". But the rules say use for Pay, Schedule, Benefits if they have content. The example headings include Pay, Schedule, Benefits. So we can create separate sections for each if they have substantive content.
Let's decide on sections:
1. About the role: could include profession, assignment length, shift, schedule, openings, start date, charting system, facility info.
2. Requirements: experience, skills, certifications, travel experience required.
3. Benefits: the Aya Delivers benefits list.
4. Pay: the pay range.
5. Schedule: the schedule details.
But note: the schedule is already in job details. Could combine.
The rules: "Prefer a few substantive sections over many thin ones." So maybe combine pay and schedule into "Job Details" or "About the role". But the example headings include Pay and Schedule as separate. However, the posting has specific pay and schedule, so we could make them separate sections.
Let's see the content: Pay is a single line: "$1885 to $2115 weekly". That's thin. Schedule is "3, 12-Hour 06:00 - 18:30". Also thin. Could be combined into a "Job Details" section with a list.
But the rules say: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we must use all; only when there is real content.
I think we can create:
- About the role (includes job details, facility info)
- Requirements (experience, skills, certifications)
- Benefits (the Aya Delivers list)
- Pay (the pay range)
- Schedule (the schedule)
But Pay and Schedule are very short. Could be a single "Compensation & Schedule" section? But the rules list them separately. However, the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, but they are minimal. The rule also says "never emit a heading followed by filler/placeholder text". A single line is not filler, it's specific. So it's okay.
But to avoid many thin sections, maybe combine Pay and Schedule into "Job Details" under "About the role". However, the example headings include Pay and Schedule as separate, so maybe they expect separate sections when present.
Let's look at the user's instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we can use those headings. The posting has no "Responsibilities" or "Qualifications" separate from Requirements. It has "Requirements" with experience, skills, certifications. That's essentially qualifications and skills.
We have "Skills" listed as a long list. Could be a "Skills" section. But the rules say "Skills" as a heading example. However, the posting has "Required Certifications & Skills" with two sublists: Skills and Certifications. That could be under "Requirements" with sublists.
I think the best is:
- About the role: includes profession, assignment length, shift, schedule, openings, start date, charting system, facility info.
- Requirements: experience, travel experience required, skills list, certifications list.
- Benefits: the Aya Delivers benefits.
- Pay: the pay range.
Schedule is already in About the role.
But the schedule is specific: "3, 12-Hour 06:00 - 18:30". Could be a separate Schedule section. But it's just one line. I'll include it in About the role.
Now, we must remove boilerplate: "Aya Healthcare has an immediate opening for the following position: RRT in Albuquerque, NM. 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." That's marketing fluff, but it's part of the posting. The rules say "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The EEO statement at the end: "Aya is an Equal Employment Opportunity ("EEO") Employer and welcomes all to apply. #HP" should be removed. Also the "Aya Delivers" marketing paragraphs about most jobs, competitive advantage, etc. are somewhat promotional but they also contain benefits. The benefits are listed after that. We should keep the benefits list but maybe not the promotional paragraphs. However, the promotional paragraphs contain some substantive info like "Exceptional benefits, including premium medical, dental, vision and life insurance beginning day one of your assignment." That's a benefit. The rest is fluff. We need to preserve ALL substantive information. So we should extract the actual benefits from that section.
Let's parse the Aya Delivers section:
"The most jobs in the industry. We have the largest and most reliable job database, which means the jobs you see are open, updated in real time and ready for you!" - fluff.
"Competitive advantage over other agencies. Front-of-the-line access through our direct facility relationships — many with quick (even same-day) offers, giving you the best chance of securing your ideal opportunity." - fluff.
"Expedited licensing and streamlined compliance. An industry-leading on-time start rate and strong relationships with boards of nursing across the country to accelerate the process in all 50 states." - fluff.
"Expert career guidance. A dedicated recruiter to help you achieve your dream career. Travel, per diem, permanent — we have the reach and access to get you the jobs you want, and the expertise to help you realize your long-term goals." - fluff.
"A best-in-class support system and an exceptional experience. Enjoy accurate, weekly pay, and an entire team dedicated to your happiness on assignment, 24/7. Plus, you get everything you expect from the largest healthcare staffing company in the industry:" - fluff.
Then list of benefits:
- Exceptional benefits, including premium medical, dental, vision and life insurance beginning day one of your assignment.
- Want to take time off? Keep insurance coverage for up to 24 Days between assignments.
- A generous 401(k) match.
- Paid company housing (we’ll help you bring your pets along, too!) or a generous housing stipend, if eligible.
- Paid sick time in accordance with all applicable state, federal, and local laws. Aya’s general sick leave policy is that employees accrue one hour of paid sick leave for every 30 hours worked. However, to the extent any provisions of the statement above conflict with any applicable paid sick leave laws, the applicable paid sick leave laws are controlling.
- Access to unlimited continuing education units online.
- Licensure, relocation and other reimbursements, when applicable.
Then: "Pay listed above includes taxable wages and tax-free expense reimbursements." That's about pay.
Then EEO statement.
So for Benefits section, we should list those bullet points.
Now, for Requirements: we have "Experience: 1 Year", "Required Certifications & Skills" with Skills list and Certifications list, "Travel Experience Required: Yes". Also "Charting Experience: Yes" under Facility & Unit Information.
We should include all.
Now, let's structure HTML.
We'll have:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we must use all; only when there is real content.
I think we can create:
- About the role (includes job details, facility info)
- Requirements (experience, skills, certifications)
- Benefits (the Aya Delivers list)
- Pay (the pay range)
- Schedule (the schedule)
But Pay and Schedule are very short. Could be a single "Compensation & Schedule" section? But the rules list them separately. However, the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, but they are minimal. The rule also says "never emit a heading followed by filler/placeholder text". A single line is not filler, it's specific. So it's okay.
But to avoid many thin sections, maybe combine Pay and Schedule into "Job Details" under "About the role". However, the example headings include Pay and Schedule as separate, so maybe they expect separate sections when present.
Let's look at the user's instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we can use those headings. The posting has no "Responsibilities" or "Qualifications" separate from Requirements. It has "Requirements" with experience, skills, certifications. That's essentially qualifications and skills.
We have "Skills" listed as a long list. Could be a "Skills" section. But the rules say "Skills" as a heading example. However, the posting has "Required Certifications & Skills" with two sublists: Skills and Certifications. That could be under "Requirements" with sublists.
I think the best is:
- About the role: includes profession, assignment length, shift, schedule, openings, start date, charting system, facility info.
- Requirements: experience, travel experience required, skills list, certifications list.
- Benefits: the Aya Delivers benefits.
- Pay: the pay range.
Schedule is already in About the role.
But the schedule is specific: "3, 12-Hour 06:00 - 18:30". Could be a separate Schedule section. But it's just one line. I'll include it in About the role.
Now, we must remove boilerplate: "Aya Healthcare has an immediate opening for the following position: RRT in Albuquerque, NM. 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." That's marketing fluff, but it's part of the posting. The rules say "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The EEO statement at the end: "Aya is an Equal Employment Opportunity ("EEO") Employer and welcomes all to apply. #HP" should be removed. Also the "Aya Delivers" marketing paragraphs about most jobs, competitive advantage, etc. are somewhat promotional but they also contain benefits. The benefits are listed after that. We should keep the benefits list but maybe not the promotional paragraphs. However, the promotional paragraphs contain some substantive info like "Exceptional benefits, including premium medical, dental, vision and life insurance beginning day one of your assignment." That's a benefit. The rest is fluff. We need to preserve ALL substantive information. So we should extract the actual benefits from that section.
Let's parse the Aya Delivers section:
"The most jobs in the industry. We have the largest and most reliable job database, which means the jobs you see are open, updated in real time and ready for you!" - fluff.
"Competitive advantage over other agencies. Front-of-the-line access through our direct facility relationships — many with quick (even same-day) offers, giving you the best chance of securing your ideal opportunity." - fluff.
"Expedited licensing and streamlined compliance. An industry-leading on-time start rate and strong relationships with boards of nursing across the country to accelerate the process in all 50 states." - fluff.
"Expert career guidance. A dedicated recruiter to help you achieve your dream career. Travel, per diem, permanent — we have the reach and access to get you the jobs you want, and the expertise to help you realize your long-term goals." - fluff.
"A best-in-class support system and an exceptional experience. Enjoy accurate, weekly pay, and an entire team dedicated to your happiness on assignment, 24/7. Plus, you get everything you expect from the largest healthcare staffing company in the industry:" - fluff.
Then list of benefits:
- Exceptional benefits, including premium medical, dental, vision and life insurance beginning day one of your assignment.
- Want to take time off? Keep insurance coverage for up to 24 Days between assignments.
- A generous 401(k) match.
- Paid company housing (we’ll help you bring your pets along, too!) or a generous housing stipend, if eligible.
- Paid sick time in accordance with all applicable state, federal, and local laws. Aya’s general sick leave policy is that employees accrue one hour of paid sick leave for every 30 hours worked. However, to the extent any provisions of the statement above conflict with any applicable paid sick leave laws, the applicable paid sick leave laws are controlling.
- Access to unlimited continuing education units online.
- Licensure, relocation and other reimbursements, when applicable.
Then: "Pay listed above includes taxable wages and tax-free expense reimbursements." That's about pay.
Then EEO statement.
So for Benefits section, we should list those bullet points.
Now, for Requirements: we have "Experience: 1 Year", "Required Certifications & Skills" with Skills list and Certifications list, "Travel Experience Required: Yes". Also "Charting Experience: Yes" under Facility & Unit Information.
We should include all.
Now, let's structure HTML.
We'll have:
About the role
About the role
Profession: Respiratory / Neuro Diagnostics
Assignment Length: 13 weeks
Shift: Days
Schedule: 3, 12-Hour 06:00 - 18:30
Openings: 1
Start Date: 12/07/2026
Charting System: Cerner