Travel Respiratory Therapist - Pediatric/Neonatal - $2,557 per 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 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
- 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")
- 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
Now, parse the posting:
Job title: "Slate Healthcare is seeking a travel Respiratory Therapist for a travel job in Rapid City, South Dakota." - This is the title, but we shouldn't repeat as heading.
Metadata: Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type. These are details about the job. Could be folded into a short
or included in a "Job Details" section? The rules say use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not "Job Details". But we can include metadata in a paragraph under About the role or a separate section? The rules say "fold minor metadata into a short
or drop it." So we can include a paragraph with key details.
Description: "As a Respiratory Therapist, you will provide critical care to pediatric and neonatal patients, ensuring the highest level of respiratory support. Your role will involve assessing patients, administering treatments, and collaborating with a multidisciplinary team. You will work in a dynamic hospital environment, contributing to exceptional patient outcomes while enjoying a supportive work culture."
Highlights: "Position available for Respiratory Therapists with pediatric and neonatal expertise Supportive team environment with 24/7 charge RT coverage Opportunity to work in a Level II Trauma Center and Magnet-designated facility" - This is a list of highlights. Could be part of "About the role" or separate "Highlights" section. The rules don't list "Highlights" as a standard heading, but we can use
for it if it's substantive. It's a list, so we can use - .
Requirements: Listed as bullet points: South Dakota RCP License, Minimum 1 year experience preferred, NRP certification required for NICU work, BLS, ACLS, PALS certifications required, Registered Respiratory Therapist (RRT) certification required. This is a clear Requirements section.
Pay package: "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 is Pay information. The rules say never create Pay section unless posting actually states them. It does state pay details, albeit not a specific number. It says "tax-free stipend amount to be determined." That's a placeholder? It's not "commensurate with experience" but "to be determined". Might be considered filler. However, it does state the basis (12 hour shifts, 36 hours per week). Could include a Pay section with that info. But the rule: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "to be determined" is similar to TBD. So maybe we should not create a Pay section. But the posting does have a sentence about pay package. Could fold into a paragraph under "About the role" or "Job Details". The rules say "fold minor metadata into a short
or drop it." Pay info might be considered minor metadata? But it's substantive. However, the rule about Pay section: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, but the content is vague. I think we can include a Pay section with the given details, but avoid placeholder. The phrase "tax-free stipend amount to be determined" is placeholder. Could we omit that phrase? The rule says preserve ALL substantive information; do NOT invent or summarize away detail. But also "never emit a heading followed by filler/placeholder text". If we include a Pay heading, we must include the text. That text includes "to be determined". That might be considered filler. Safer to fold into a paragraph without a heading.
Schedule: The posting includes "36 hours per week Shift: 12 hours, rotating". That's schedule info. Could be included in a Schedule section? The rules say never create Schedule section unless posting actually states them. It does state schedule. But again, it's minor metadata. Could fold into a paragraph.
About Slate Healthcare: This is company description. Could be a section "About the Company" or "About Slate Healthcare". The rules don't list that as a standard heading, but we can use
for it. It's substantive.
Job ID: "Slate Healthcare Job ID #3bebdc56-ddbc-47fb-9e87-d936edc6ea4f." This is minor metadata, fold into a short
or drop. We'll drop it or include in a metadata paragraph.
Now, decide on sections:
1. About the role (or Description) - includes the description paragraph and highlights list.
2. Requirements - list of requirements.
3. Schedule & Pay Details - maybe combine? But rules prefer separate headings if substantive. However, the pay info is vague. I'll create a "Schedule" section with the hours and shift, and a "Pay" section with the pay package description? But the pay description includes "to be determined". Might be better to combine into a "Job Details" paragraph. But the rules say use
for section headings like Pay, Schedule. If we have specific content, we can include. The posting states: "36 hours per week Shift: 12 hours, rotating" 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." That's two pieces. Could make a "Schedule" section with the hours/shift, and a "Pay" section with the pay package basis. But the pay section would have placeholder. I think we should not create a Pay section because the stipend amount is not determined. The rule says never create Pay section unless posting actually states them. It states a pay package but not the amount. It's still a statement about pay. However, the example of filler includes "commensurate with experience", "not specified", "N/A", "varies", "TBD". "to be determined" is essentially TBD. So we should not create a Pay section. We'll fold the pay info into a paragraph under "Job Details" or "About the role".
Similarly, Schedule: we have specific hours and shift. That's substantive. Could create a Schedule section. But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule. So we can create a Schedule section. But the schedule is just "36 hours per week, 12-hour rotating shifts". That's a single line. Could be a list with one item? Might be thin. The rules: "Prefer a few substantive sections over many thin ones." So maybe combine schedule and pay into a "Job Details" paragraph. But the rules say use for section headings like Schedule. If we have a schedule, we can include. I'll include a Schedule section with the details.
Let's structure:
- About the Role
Description paragraph.
Highlights
(or include as list under About the Role)
- ...
- Requirements
- ...
- Schedule
36 hours per week, 12-hour rotating shifts.
(or list)
- About Slate Healthcare
Company description.
But the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So "Highlights" is not in the example list, but we can still use for it. It's a section heading.
We must not repeat job title as heading. The page already shows it. So we start with About the Role.
Now, metadata: Specialty, Discipline, Start Date, Duration, Employment Type. These are minor metadata. Fold into a short
at the top of About the Role or separate. I'll include a paragraph at the beginning of About the Role with key details: "Specialty: Respiratory Therapist; Discipline: Allied Health Professional; Start Date: 11/16/2026; Duration: 13 weeks; Employment Type: Travel; Location: Rapid City, South Dakota." That's a paragraph.
Now, the description: "As a Respiratory Therapist, you will provide critical care to pediatric and neonatal patients, ensuring the highest level of respiratory support. Your role will involve assessing patients, administering treatments, and collaborating with a multidisciplinary team. You will work in a dynamic hospital environment, contributing to exceptional patient outcomes while enjoying a supportive work culture."
Highlights: three bullet points.
Requirements: five bullet points.
Schedule: "36 hours per week, 12-hour rotating shifts." Could be a paragraph.
Pay: I'll omit a separate section, but maybe include a sentence in Schedule or a separate paragraph? The rule says never create Pay section unless posting actually states them. It does state pay package basis. But it's vague. I'll include a paragraph under Schedule or a separate "Compensation" paragraph? But the rules say use
for Pay. If we don't create a Pay heading, we can just include a paragraph somewhere. I'll include a paragraph after Schedule: "Pay package is based on 12-hour shifts and 36 hours per week (subject to confirmation), with tax-free stipend amount to be determined." But that includes "to be determined". That's placeholder. The rule says never emit a heading followed by filler/placeholder text. But if it's not a heading, just a paragraph, is that okay? The rule says "never emit a heading followed by filler/placeholder text". It doesn't say we can't have placeholder text in a paragraph. But we should preserve ALL substantive information. The pay info is substantive even if amount TBD. I'll include it as a paragraph under a "Compensation" heading? But that would be a heading. Better to fold into a "Job Details" paragraph at the top.
Let's create a "Job Details" paragraph at the top of About the Role that includes all metadata: location, specialty, discipline, start date, duration, hours per week, shift, employment type, and pay basis. Then we don't need separate Schedule/Pay sections. That would be a single substantive paragraph. Then we have About the Role description, Highlights, Requirements, About Slate Healthcare
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 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 - 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") - 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 Now, parse the posting: Job title: "Slate Healthcare is seeking a travel Respiratory Therapist for a travel job in Rapid City, South Dakota." - This is the title, but we shouldn't repeat as heading. Metadata: Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type. These are details about the job. Could be folded into a short
or included in a "Job Details" section? The rules say use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not "Job Details". But we can include metadata in a paragraph under About the role or a separate section? The rules say "fold minor metadata into a short
or drop it." So we can include a paragraph with key details. Description: "As a Respiratory Therapist, you will provide critical care to pediatric and neonatal patients, ensuring the highest level of respiratory support. Your role will involve assessing patients, administering treatments, and collaborating with a multidisciplinary team. You will work in a dynamic hospital environment, contributing to exceptional patient outcomes while enjoying a supportive work culture." Highlights: "Position available for Respiratory Therapists with pediatric and neonatal expertise Supportive team environment with 24/7 charge RT coverage Opportunity to work in a Level II Trauma Center and Magnet-designated facility" - This is a list of highlights. Could be part of "About the role" or separate "Highlights" section. The rules don't list "Highlights" as a standard heading, but we can use
for it if it's substantive. It's a list, so we can use - .
Requirements: Listed as bullet points: South Dakota RCP License, Minimum 1 year experience preferred, NRP certification required for NICU work, BLS, ACLS, PALS certifications required, Registered Respiratory Therapist (RRT) certification required. This is a clear Requirements section.
Pay package: "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 is Pay information. The rules say never create Pay section unless posting actually states them. It does state pay details, albeit not a specific number. It says "tax-free stipend amount to be determined." That's a placeholder? It's not "commensurate with experience" but "to be determined". Might be considered filler. However, it does state the basis (12 hour shifts, 36 hours per week). Could include a Pay section with that info. But the rule: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "to be determined" is similar to TBD. So maybe we should not create a Pay section. But the posting does have a sentence about pay package. Could fold into a paragraph under "About the role" or "Job Details". The rules say "fold minor metadata into a short
or drop it." Pay info might be considered minor metadata? But it's substantive. However, the rule about Pay section: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, but the content is vague. I think we can include a Pay section with the given details, but avoid placeholder. The phrase "tax-free stipend amount to be determined" is placeholder. Could we omit that phrase? The rule says preserve ALL substantive information; do NOT invent or summarize away detail. But also "never emit a heading followed by filler/placeholder text". If we include a Pay heading, we must include the text. That text includes "to be determined". That might be considered filler. Safer to fold into a paragraph without a heading.
Schedule: The posting includes "36 hours per week Shift: 12 hours, rotating". That's schedule info. Could be included in a Schedule section? The rules say never create Schedule section unless posting actually states them. It does state schedule. But again, it's minor metadata. Could fold into a paragraph.
About Slate Healthcare: This is company description. Could be a section "About the Company" or "About Slate Healthcare". The rules don't list that as a standard heading, but we can use
for it. It's substantive.
Job ID: "Slate Healthcare Job ID #3bebdc56-ddbc-47fb-9e87-d936edc6ea4f." This is minor metadata, fold into a short
or drop. We'll drop it or include in a metadata paragraph.
Now, decide on sections:
1. About the role (or Description) - includes the description paragraph and highlights list.
2. Requirements - list of requirements.
3. Schedule & Pay Details - maybe combine? But rules prefer separate headings if substantive. However, the pay info is vague. I'll create a "Schedule" section with the hours and shift, and a "Pay" section with the pay package description? But the pay description includes "to be determined". Might be better to combine into a "Job Details" paragraph. But the rules say use
for section headings like Pay, Schedule. If we have specific content, we can include. The posting states: "36 hours per week Shift: 12 hours, rotating" 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." That's two pieces. Could make a "Schedule" section with the hours/shift, and a "Pay" section with the pay package basis. But the pay section would have placeholder. I think we should not create a Pay section because the stipend amount is not determined. The rule says never create Pay section unless posting actually states them. It states a pay package but not the amount. It's still a statement about pay. However, the example of filler includes "commensurate with experience", "not specified", "N/A", "varies", "TBD". "to be determined" is essentially TBD. So we should not create a Pay section. We'll fold the pay info into a paragraph under "Job Details" or "About the role".
Similarly, Schedule: we have specific hours and shift. That's substantive. Could create a Schedule section. But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule. So we can create a Schedule section. But the schedule is just "36 hours per week, 12-hour rotating shifts". That's a single line. Could be a list with one item? Might be thin. The rules: "Prefer a few substantive sections over many thin ones." So maybe combine schedule and pay into a "Job Details" paragraph. But the rules say use for section headings like Schedule. If we have a schedule, we can include. I'll include a Schedule section with the details.
Let's structure:
- About the Role
Description paragraph.
Highlights
(or include as list under About the Role)
- ...
- Requirements
- ...
- Schedule
36 hours per week, 12-hour rotating shifts.
(or list)
- About Slate Healthcare
Company description.
But the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So "Highlights" is not in the example list, but we can still use for it. It's a section heading.
We must not repeat job title as heading. The page already shows it. So we start with About the Role.
Now, metadata: Specialty, Discipline, Start Date, Duration, Employment Type. These are minor metadata. Fold into a short
at the top of About the Role or separate. I'll include a paragraph at the beginning of About the Role with key details: "Specialty: Respiratory Therapist; Discipline: Allied Health Professional; Start Date: 11/16/2026; Duration: 13 weeks; Employment Type: Travel; Location: Rapid City, South Dakota." That's a paragraph.
Now, the description: "As a Respiratory Therapist, you will provide critical care to pediatric and neonatal patients, ensuring the highest level of respiratory support. Your role will involve assessing patients, administering treatments, and collaborating with a multidisciplinary team. You will work in a dynamic hospital environment, contributing to exceptional patient outcomes while enjoying a supportive work culture."
Highlights: three bullet points.
Requirements: five bullet points.
Schedule: "36 hours per week, 12-hour rotating shifts." Could be a paragraph.
Pay: I'll omit a separate section, but maybe include a sentence in Schedule or a separate paragraph? The rule says never create Pay section unless posting actually states them. It does state pay package basis. But it's vague. I'll include a paragraph under Schedule or a separate "Compensation" paragraph? But the rules say use
for Pay. If we don't create a Pay heading, we can just include a paragraph somewhere. I'll include a paragraph after Schedule: "Pay package is based on 12-hour shifts and 36 hours per week (subject to confirmation), with tax-free stipend amount to be determined." But that includes "to be determined". That's placeholder. The rule says never emit a heading followed by filler/placeholder text. But if it's not a heading, just a paragraph, is that okay? The rule says "never emit a heading followed by filler/placeholder text". It doesn't say we can't have placeholder text in a paragraph. But we should preserve ALL substantive information. The pay info is substantive even if amount TBD. I'll include it as a paragraph under a "Compensation" heading? But that would be a heading. Better to fold into a "Job Details" paragraph at the top.
Let's create a "Job Details" paragraph at the top of About the Role that includes all metadata: location, specialty, discipline, start date, duration, hours per week, shift, employment type, and pay basis. Then we don't need separate Schedule/Pay sections. That would be a single substantive paragraph. Then we have About the Role description, Highlights, Requirements, About Slate Healthcare
or drop it." Pay info might be considered minor metadata? But it's substantive. However, the rule about Pay section: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, but the content is vague. I think we can include a Pay section with the given details, but avoid placeholder. The phrase "tax-free stipend amount to be determined" is placeholder. Could we omit that phrase? The rule says preserve ALL substantive information; do NOT invent or summarize away detail. But also "never emit a heading followed by filler/placeholder text". If we include a Pay heading, we must include the text. That text includes "to be determined". That might be considered filler. Safer to fold into a paragraph without a heading. Schedule: The posting includes "36 hours per week Shift: 12 hours, rotating". That's schedule info. Could be included in a Schedule section? The rules say never create Schedule section unless posting actually states them. It does state schedule. But again, it's minor metadata. Could fold into a paragraph. About Slate Healthcare: This is company description. Could be a section "About the Company" or "About Slate Healthcare". The rules don't list that as a standard heading, but we can use
for it. It's substantive. Job ID: "Slate Healthcare Job ID #3bebdc56-ddbc-47fb-9e87-d936edc6ea4f." This is minor metadata, fold into a short
or drop. We'll drop it or include in a metadata paragraph. Now, decide on sections: 1. About the role (or Description) - includes the description paragraph and highlights list. 2. Requirements - list of requirements. 3. Schedule & Pay Details - maybe combine? But rules prefer separate headings if substantive. However, the pay info is vague. I'll create a "Schedule" section with the hours and shift, and a "Pay" section with the pay package description? But the pay description includes "to be determined". Might be better to combine into a "Job Details" paragraph. But the rules say use
for section headings like Pay, Schedule. If we have specific content, we can include. The posting states: "36 hours per week Shift: 12 hours, rotating" 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." That's two pieces. Could make a "Schedule" section with the hours/shift, and a "Pay" section with the pay package basis. But the pay section would have placeholder. I think we should not create a Pay section because the stipend amount is not determined. The rule says never create Pay section unless posting actually states them. It states a pay package but not the amount. It's still a statement about pay. However, the example of filler includes "commensurate with experience", "not specified", "N/A", "varies", "TBD". "to be determined" is essentially TBD. So we should not create a Pay section. We'll fold the pay info into a paragraph under "Job Details" or "About the role".
Similarly, Schedule: we have specific hours and shift. That's substantive. Could create a Schedule section. But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule. So we can create a Schedule section. But the schedule is just "36 hours per week, 12-hour rotating shifts". That's a single line. Could be a list with one item? Might be thin. The rules: "Prefer a few substantive sections over many thin ones." So maybe combine schedule and pay into a "Job Details" paragraph. But the rules say use for section headings like Schedule. If we have a schedule, we can include. I'll include a Schedule section with the details.
Let's structure:
- About the Role
About the Role
Description paragraph.
Highlights
(or include as list under About the Role)- ...
Requirements
- ...
Schedule
36 hours per week, 12-hour rotating shifts.
(or list) -About Slate Healthcare
Company description.
But the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So "Highlights" is not in the example list, but we can still use for it. It's a section heading.
We must not repeat job title as heading. The page already shows it. So we start with About the Role.
Now, metadata: Specialty, Discipline, Start Date, Duration, Employment Type. These are minor metadata. Fold into a short
at the top of About the Role or separate. I'll include a paragraph at the beginning of About the Role with key details: "Specialty: Respiratory Therapist; Discipline: Allied Health Professional; Start Date: 11/16/2026; Duration: 13 weeks; Employment Type: Travel; Location: Rapid City, South Dakota." That's a paragraph. Now, the description: "As a Respiratory Therapist, you will provide critical care to pediatric and neonatal patients, ensuring the highest level of respiratory support. Your role will involve assessing patients, administering treatments, and collaborating with a multidisciplinary team. You will work in a dynamic hospital environment, contributing to exceptional patient outcomes while enjoying a supportive work culture." Highlights: three bullet points. Requirements: five bullet points. Schedule: "36 hours per week, 12-hour rotating shifts." Could be a paragraph. Pay: I'll omit a separate section, but maybe include a sentence in Schedule or a separate paragraph? The rule says never create Pay section unless posting actually states them. It does state pay package basis. But it's vague. I'll include a paragraph under Schedule or a separate "Compensation" paragraph? But the rules say use