Travel CT Tech - $2,847 per week
LRS Healthcare · Chamberlain, SD · 4 wk ago
On-siteInternship
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the job posting.
Content:
- Title: LRS Healthcare - Allied is seeking a travel CT Technologist for a travel job in Chamberlain, South Dakota.
- Job Description & Requirements
Specialty: CT Technologist
Discipline: Allied Health Professional
Start Date: 11/16/2026
Duration: 13 weeks
40 hours per week
Shift: 8 hours, flexible
Employment Type: Travel
- Then description about LRS Healthcare (company description) repeated later.
- Benefits: list: Streamlined, simple credentialing process through the LRS Connect App; Health, Dental, and Vision Insurance; Life and Disability Insurance; 401(k) with Employer Match; Generous Referral Bonus Program; Employee Assistance Program (EAP); Weekly Direct Deposit; 24/7/365 Support
- "Adventure is Calling! Apply today!" (call to action, we should remove application instructions? It says remove application instructions. This is a call to apply; maybe considered application instruction. We should drop it.
- Then "LRS Healthcare - Allied Job ID #2643522. Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined."
- Then repeated "About LRS Healthcare - Allied" same as earlier description.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate, duplicated lines, EEO etc. There's no EEO here.
We need to decide sections.
We have:
- About the role: Could be the description of the role: travel CT Technologist in Chamberlain, SD. Could include specialty, discipline, start date, duration, hours, shift, employment type.
- Responsibilities: Not explicitly listed. The posting does not list duties/responsibilities. So we should not create a Responsibilities section if no specific content.
- Requirements: Not explicitly listed beyond specialty and discipline? Could be implied: CT Technologist, Allied Health Professional. Might be considered requirements. But we need specific content: The posting includes "Specialty: CT Technologist" and "Discipline: Allied Health Professional". Those could be considered requirements. We could put them under Requirements.
- Qualifications: Not given.
- Skills: Not given.
- Benefits: We have list.
- Pay: The posting mentions "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's vague but it's specific about basis and that stipend TBD. The instruction says: do NOT create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package basis, though stipend TBD. Should we include Pay section? It says "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's some info, albeit not specific numbers. The rule: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Here we have "tax-free stipend amount to be determined." That's TBD. So including Pay section would have placeholder text. We should avoid creating Pay section if it only contains TBD. However we do have basis: 8 hour shifts, 40 hours per week. That's not TBD. But the pay package itself is not specified. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them (pay package based on...). But then includes TBD. The rule about filler/placeholder text says never emit a heading followed by filler/placeholder text. If we include Pay section, we would have to include the statement which includes TBD. That might be considered filler? The statement includes both concrete (based on 8 hour shifts and 40 hours per week) and TBD stipend. It's not purely placeholder. I'd lean to include Pay section with that sentence.
- Schedule: We have shift: 8 hours, flexible; 40 hours per week. That's schedule info. So we can include Schedule section.
- Benefits: we have list.
- About the role: we can include description of role and location.
We must not repeat job title as heading. So no
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should stick to those? It says use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the job posting.
Content:
- Title: LRS Healthcare - Allied is seeking a travel CT Technologist for a travel job in Chamberlain, South Dakota.
- Job Description & Requirements
Specialty: CT Technologist
Discipline: Allied Health Professional
Start Date: 11/16/2026
Duration: 13 weeks
40 hours per week
Shift: 8 hours, flexible
Employment Type: Travel
- Then description about LRS Healthcare (company description) repeated later.
- Benefits: list: Streamlined, simple credentialing process through the LRS Connect App; Health, Dental, and Vision Insurance; Life and Disability Insurance; 401(k) with Employer Match; Generous Referral Bonus Program; Employee Assistance Program (EAP); Weekly Direct Deposit; 24/7/365 Support
- "Adventure is Calling! Apply today!" (call to action, we should remove application instructions? It says remove application instructions. This is a call to apply; maybe considered application instruction. We should drop it.
- Then "LRS Healthcare - Allied Job ID #2643522. Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined."
- Then repeated "About LRS Healthcare - Allied" same as earlier description.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate, duplicated lines, EEO etc. There's no EEO here.
We need to decide sections.
We have:
- About the role: Could be the description of the role: travel CT Technologist in Chamberlain, SD. Could include specialty, discipline, start date, duration, hours, shift, employment type.
- Responsibilities: Not explicitly listed. The posting does not list duties/responsibilities. So we should not create a Responsibilities section if no specific content.
- Requirements: Not explicitly listed beyond specialty and discipline? Could be implied: CT Technologist, Allied Health Professional. Might be considered requirements. But we need specific content: The posting includes "Specialty: CT Technologist" and "Discipline: Allied Health Professional". Those could be considered requirements. We could put them under Requirements.
- Qualifications: Not given.
- Skills: Not given.
- Benefits: We have list.
- Pay: The posting mentions "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's vague but it's specific about basis and that stipend TBD. The instruction says: do NOT create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package basis, though stipend TBD. Should we include Pay section? It says "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's some info, albeit not specific numbers. The rule: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Here we have "tax-free stipend amount to be determined." That's TBD. So including Pay section would have placeholder text. We should avoid creating Pay section if it only contains TBD. However we do have basis: 8 hour shifts, 40 hours per week. That's not TBD. But the pay package itself is not specified. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them (pay package based on...). But then includes TBD. The rule about filler/placeholder text says never emit a heading followed by filler/placeholder text. If we include Pay section, we would have to include the statement which includes TBD. That might be considered filler? The statement includes both concrete (based on 8 hour shifts and 40 hours per week) and TBD stipend. It's not purely placeholder. I'd lean to include Pay section with that sentence.
- Schedule: We have shift: 8 hours, flexible; 40 hours per week. That's schedule info. So we can include Schedule section.
- Benefits: we have list.
- About the role: we can include description of role and location.
We must not repeat job title as heading. So no Travel CT Technologist.
We need to avoid duplicating content. The company description appears twice; we should include it once.
We need to preserve all substantive information: location (Chamberlain, South Dakota), start date, duration, hours per week, shift, employment type, specialty, discipline, benefits list, pay package statement.
We should not include Job ID or requisition numbers as headings; we can drop them or fold into short p. Probably drop.
We need to output only HTML fragment.
Let's craft:
About the role
About the role
LRS Healthcare - Allied is seeking a travel CT Technologist for a travel assignment in Chamberlain, South Dakota. Specialty: CT Technologist; Discipline: Allied Health Professional. Start date: 11/16/2026. Duration: 13 weeks. Schedule: 40 hours per week, 8‑hour shifts (flexible). Employment type: Travel.
That's about role. Then Benefits:Benefits
- Streamlined, simple credentialing process through the LRS Connect App
- Health, Dental, and Vision Insurance
- Life and Disability Insurance
- 401(k) with Employer Match
- Generous Referral Bonus Program
- Employee Assistance Program (EAP)
- Weekly Direct Deposit
- 24/7/365 Support
Pay
Pay package is based on 8‑hour shifts and 40.0 hours per week (subject to confirmation) with a tax‑free stipend amount to be determined.
Schedule:Schedule
40 hours per week, 8‑hour shifts (flexible).
But note schedule already mentioned in About the role; we might duplicate. However we need to avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication but we should avoid redundant sections? It says "Prefer a few substantive sections over many thin ones." So maybe we combine schedule into About the role and not have separate Schedule section. Since schedule is already covered, we could omit Schedule section to avoid thin section. But we need to decide if schedule is substantive enough to warrant its own section. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid creating a Schedule section if the info is minor and can be included elsewhere. So we can omit Schedule section. Similarly Pay section: we have some info but it's vague; still it's substantive? It's about pay basis. Could be considered thin but it's the only pay info. I'd keep Pay section. Thus final HTML:About the role
LRS Healthcare - Allied is seeking a travel CT Technologist for a travel assignment in Chamberlain, South Dakota. Specialty: CT Technologist; Discipline: Allied Health Professional. Start date: 11/16/2026. Duration: 13 weeks. Schedule: 40 hours per week, 8‑hour shifts (flexible). Employment type: Travel.
Benefits
- Streamlined, simple credentialing process through the LRS Connect App
- Health, Dental, and Vision Insurance
- Life and Disability Insurance
- 401(k) with Employer Match
- Generous Referral Bonus Program
- Employee Assistance Program (EAP)
- Weekly Direct Deposit
- 24/7/365 Support
Pay
Pay package is based on 8‑hour shifts and 40.0 hours per week (subject to confirmation) with a tax‑free stipend amount to be determined.
We should not include any extra text like "Adventure is Calling! Apply today!" (application instruction). Also we should not include repeated company description. Check for any other substantive info: The posting also mentions "At LRS Healthcare, we connect skilled nursing and allied health professionals with rewarding opportunities at top healthcare facilities across the country..." That's company description; we could include as "About the company" but not required headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no heading for About the company. So we should not add a heading not in list. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should stick to those? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. So we cannot add a heading like "About LRS Healthcare". So we should omit the repeated company description entirely, as it's not under any allowed heading. However we need to preserve ALL substantive information. The company description is substantive but not under allowed headings. The instruction says to use those headings for sections; does it forbid other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't explicitly forbid other headings, but the examples suggest those are the expected sections. It also says "Prefer a few substantive sections over many thin ones." So we could include an "About the company" section if we want, but it's not in the list. Safer to stick to the given headings. The company description is generic boilerplate about LRS Healthcare; maybe considered boilerplate? It's repeated and could be considered boilerplate. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This company description is not exactly those categories but it's promotional. It might be considered boilerplate? Not sure. However it's duplicated; we could keep one instance but it's not under a heading. If we cannot add a heading, we could fold it into a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't explicitly forbid other headings, but the examples suggest those are the expected sections. It also says "Prefer a few substantive sections over many thin ones." So we could include an "About the company" section if we want, but it's not in the list. Safer to stick to the given headings. The company description is generic boilerplate about LRS Healthcare; maybe considered boilerplate? It's repeated and could be considered boilerplate. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This company description is not exactly those categories but it's promotional. It might be considered boilerplate? Not sure. However it's duplicated; we could keep one instance but it's not under a heading. If we cannot add a heading, we could fold it into a
under About the role? But that would mix role description with company description. Might be okay but could be considered not strictly about the role. However the instruction says preserve ALL substantive information; we could include it as a paragraph under About the role (since it's about the employer). That would preserve it without extra heading. Thus we can incorporate the company description into About the role paragraph. Let's craft About the role paragraph to include both role details and company overview. About the role paragraph: "LRS Healthcare - Allied is seeking a travel CT Technologist for a travel assignment in Chamberlain, South Dakota. Specialty: CT Technologist; Discipline: Allied Health Professional. Start date: 11/16/2026. Duration: 13 weeks. Schedule: 40 hours per week, 8‑hour shifts (flexible). Employment type: Travel. At LRS Healthcare, we connect skilled nursing and allied health professionals with rewarding opportunities at top healthcare facilities across the country. Whether you're looking to explore a new city, gain experience in a different clinical setting, or take the next step in your career, our specialized