Travel CT Technologist - $1,699 per week
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content.
We need to parse the posting.
Content:
- Job title: travel CT Technologist (but we don't repeat as heading)
- Location: Naples, Florida
- Specialty: CT Technologist
- Discipline: Allied Health Professional
- Start Date: 10/05/2026
- Duration: 13 weeks
- 36 hours per week
- Shift: 12 hours, nights
- Employment Type: Travel
Then description about LRS Healthcare (company description). Then Benefits list (first list). Then "Adventure is Calling! Apply today!" (application instruction, remove). Then Job ID line (metadata). Then "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 pay info (though vague). Then "About LRS Healthcare - Allied" paragraph. Then another Benefits list (second list). So we need to combine benefits? There's duplicate content; we should preserve all substantive info but remove duplicated lines. So we need to merge benefits, removing duplicates.
First 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
Second benefits list:
- Medical, Dental, and Vision
- Short-Term Disability
- Long-Term Disability
- Life Insurance
- 401(k)
- Certification & License Reimbursement
- Refer-a-friend Bonus Program
- Direct Deposit - Weekly
- 24-Hour Support
We need to combine, removing duplicates. Overlap: Health/Dental/Vision vs Medical/Dental/Vision similar; we can keep one. Life and Disability Insurance vs Short-Term Disability, Long-Term Disability, Life Insurance: we can keep separate items but avoid duplication. 401(k) with Employer Match vs 401(k) (maybe keep with match). Referral Bonus Program vs Refer-a-friend Bonus Program similar. Weekly Direct Deposit vs Direct Deposit - Weekly similar. 24/7/365 Support vs 24-Hour Support similar.
Also unique items: Streamlined credentialing process, Employee Assistance Program (EAP), Certification & License Reimbursement.
Thus final benefits list should contain unique items, maybe combine similar.
We'll produce a - list.
Now sections: We have "About the role" maybe we can include description of role? The posting includes job description & requirements but not detailed responsibilities. It includes Specialty, Discipline, Start Date, Duration, Hours, Shift, Employment Type. That could be considered "About the role" or "Job Details". Since we need headings only for sections with real specific content. We could create a section "About the role" with a
containing the details: Specialty, Discipline, Start Date, Duration, Hours, Shift, Employment Type, Location.
Alternatively we could create a section "Job Details". But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings if appropriate.
We have no explicit Responsibilities list. Could we infer? Probably not; we should not create a Responsibilities section if no specific content. So we skip Responsibilities.
Requirements? Not listed besides being a CT Technologist (specialty). Could be considered Requirements: CT Technologist certification, etc. Not explicit. Might skip.
Qualifications? Not explicit.
Skills? Not explicit.
Benefits: we have content.
Pay: we have "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 somewhat vague but it's specific about basis. It says "subject to confirmation" and "tax-free stipend amount to be determined." This is somewhat vague but still some info. The instruction says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here we have "subject to confirmation" and "tax-free stipend amount to be determined." That is somewhat placeholder. Might be considered not specific enough. However we have actual basis: 12 hour shifts, 36 hours per week. That's specific. The stipend amount TBD is placeholder. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on 12 hour shifts and 36 hours per week. So we can include Pay section with that sentence, maybe we can omit the TBD part? But we must preserve ALL substantive information; do not invent or summarize away detail. We can include the sentence as is, even if contains TBD. But the instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "tax-free stipend amount to be determined" is TBD-like. Might be considered filler. However we could still include the Pay section but maybe we should rephrase to keep substantive part and drop the TBD? But that would be summarizing away detail (removing TBD). The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the TBD part as it's part of the posting. However the instruction about not emitting a heading followed by filler/placeholder text seems to conflict. But maybe they mean if the only content under that heading is filler like "TBD" then don't create heading. If there is also substantive info, it's okay. So we can include Pay section with the sentence.
Schedule: we have shift: 12 hours, nights; 36 hours per week; start date, duration. That's schedule info. So we can include Schedule section.
Now About the role: we can include location, specialty, discipline, start date, duration, hours, shift, employment type.
We need to avoid repeating job title as heading.
We need to remove boilerplate like "Adventure is Calling! Apply today!" and Job ID line.
Also remove duplicated lines: we already merged benefits.
Now produce HTML fragment:
About the role
Location: Naples, Florida. Specialty: CT Technologist. Discipline: Allied Health Professional. Start Date: 10/05/2026. Duration: 13 weeks. Hours: 36 hours per week. Shift: 12 hours, nights. Employment Type: Travel.
Benefits
- Streamlined, simple credentialing process through the LRS Connect App
- Health, Dental, and Vision Insurance
- Life and Disability Insurance (includes Short-Term and Long-Term Disability)
- 401(k) with Employer Match
- Generous Referral Bonus Program / Refer-a-friend Bonus Program
- Employee Assistance Program (EAP)
- Weekly Direct Deposit
- 24/7/365 Support
- Certification & License Reimbursement
But we need to avoid duplication; we combined Life and Disability Insurance with short/long term. Might be okay but we need to preserve all info: we have Life and Disability Insurance (first list) and Short-Term Disability, Long-Term Disability, Life Insurance (second list). Combining into one line may lose nuance but still preserves. Could list them separately but avoid duplication: we could list Life Insurance, Short-Term Disability, Long-Term Disability as separate items, and also note Life and Disability Insurance (which is redundant). Better to list each distinct: Life Insurance, Short-Term Disability, Long-Term Disability. The first list's "Life and Disability Insurance" is essentially same as those two combined; we can keep the separate items and drop the combined. So final benefits:
- Streamlined, simple credentialing process through the LRS Connect App
- Health, Dental, and Vision Insurance
- Life Insurance
- Short-Term Disability
- Long-Term Disability
- 401(k) with Employer Match
- Generous Referral Bonus Program (Refer-a-friend Bonus Program)
- Employee Assistance Program (EAP)
- Weekly Direct Deposit
- 24/7/365 Support
- Certification & License Reimbursement
We need to avoid duplication: Referral Bonus Program and Refer-a-friend Bonus Program are same; we can keep one.
Now Pay section:
Pay
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.
Schedule section:
Schedule
Shift: 12 hours, nights. Hours per week: 36. Start date: 10/05/2026. Duration: 13 weeks.
We might also include employment type? Already in About the role.
Now ensure no extra sections like Responsibilities, Requirements, Qualifications, Skills.
Now output only HTML fragment.
Check for any leftover boilerplate: removed Adventure is Calling! Apply today!, Job ID line, duplicated benefits, company description paragraphs? We included some of the company description in About the role? Actually we included only job specifics; we omitted the descriptive paragraph about LRS Healthcare (the fluff). That's considered boilerplate? It's not navigation/legal/EEO but it's generic marketing. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The descriptive paragraph about LRS Healthcare is not explicitly listed as boilerplate but could be considered fluff. However we need to preserve ALL substantive information; is that substantive? It's about the company, not the job. Might be considered not essential to the job posting. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company description is substantive? It's about the employer, not the job. Might be considered not required but could be kept. However the instruction to prefer a few substantive sections over many thin ones suggests we could keep it as part of About the role or a separate section like "About the employer". But we only allowed headings from list; we could put it under About the role as well. The About the role section currently contains job specifics; we could add the employer description after that. That would preserve it.
Thus About the role could include both job specifics and the employer description.
Let's incorporate the employer description paragraph: "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 recruiters are here to help you find travel assignments that align with your personal goals, professional aspirations, and sense of adventure. From your first conversation to your final day on assignment, you'll have a dedicated team in your corner. Our experienced recruiters, credentialing specialists, payroll professionals, and HR team work together to ensure a smooth, stress-free experience so you can focus on what matters most—caring for patients and making the most of every opportunity. Wherever your journey takes you, LRS Healthcare is here to support you every step of the way."
That's substantive about the employer. We'll include it.
Now About the role paragraph will be long but okay.
Now ensure we didn't include any duplicated lines.
containing the details: Specialty, Discipline, Start Date, Duration, Hours, Shift, Employment Type, Location. Alternatively we could create a section "Job Details". But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings if appropriate. We have no explicit Responsibilities list. Could we infer? Probably not; we should not create a Responsibilities section if no specific content. So we skip Responsibilities. Requirements? Not listed besides being a CT Technologist (specialty). Could be considered Requirements: CT Technologist certification, etc. Not explicit. Might skip. Qualifications? Not explicit. Skills? Not explicit. Benefits: we have content. Pay: we have "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 somewhat vague but it's specific about basis. It says "subject to confirmation" and "tax-free stipend amount to be determined." This is somewhat vague but still some info. The instruction says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here we have "subject to confirmation" and "tax-free stipend amount to be determined." That is somewhat placeholder. Might be considered not specific enough. However we have actual basis: 12 hour shifts, 36 hours per week. That's specific. The stipend amount TBD is placeholder. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on 12 hour shifts and 36 hours per week. So we can include Pay section with that sentence, maybe we can omit the TBD part? But we must preserve ALL substantive information; do not invent or summarize away detail. We can include the sentence as is, even if contains TBD. But the instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "tax-free stipend amount to be determined" is TBD-like. Might be considered filler. However we could still include the Pay section but maybe we should rephrase to keep substantive part and drop the TBD? But that would be summarizing away detail (removing TBD). The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the TBD part as it's part of the posting. However the instruction about not emitting a heading followed by filler/placeholder text seems to conflict. But maybe they mean if the only content under that heading is filler like "TBD" then don't create heading. If there is also substantive info, it's okay. So we can include Pay section with the sentence. Schedule: we have shift: 12 hours, nights; 36 hours per week; start date, duration. That's schedule info. So we can include Schedule section. Now About the role: we can include location, specialty, discipline, start date, duration, hours, shift, employment type. We need to avoid repeating job title as heading. We need to remove boilerplate like "Adventure is Calling! Apply today!" and Job ID line. Also remove duplicated lines: we already merged benefits. Now produce HTML fragment:
About the role
Location: Naples, Florida. Specialty: CT Technologist. Discipline: Allied Health Professional. Start Date: 10/05/2026. Duration: 13 weeks. Hours: 36 hours per week. Shift: 12 hours, nights. Employment Type: Travel.
Benefits
- Streamlined, simple credentialing process through the LRS Connect App
- Health, Dental, and Vision Insurance
- Life and Disability Insurance (includes Short-Term and Long-Term Disability)
- 401(k) with Employer Match
- Generous Referral Bonus Program / Refer-a-friend Bonus Program
- Employee Assistance Program (EAP)
- Weekly Direct Deposit
- 24/7/365 Support
- Certification & License Reimbursement
Pay
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.
Schedule section:Schedule
Shift: 12 hours, nights. Hours per week: 36. Start date: 10/05/2026. Duration: 13 weeks.
We might also include employment type? Already in About the role. Now ensure no extra sections like Responsibilities, Requirements, Qualifications, Skills. Now output only HTML fragment. Check for any leftover boilerplate: removed Adventure is Calling! Apply today!, Job ID line, duplicated benefits, company description paragraphs? We included some of the company description in About the role? Actually we included only job specifics; we omitted the descriptive paragraph about LRS Healthcare (the fluff). That's considered boilerplate? It's not navigation/legal/EEO but it's generic marketing. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The descriptive paragraph about LRS Healthcare is not explicitly listed as boilerplate but could be considered fluff. However we need to preserve ALL substantive information; is that substantive? It's about the company, not the job. Might be considered not essential to the job posting. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company description is substantive? It's about the employer, not the job. Might be considered not required but could be kept. However the instruction to prefer a few substantive sections over many thin ones suggests we could keep it as part of About the role or a separate section like "About the employer". But we only allowed headings from list; we could put it under About the role as well. The About the role section currently contains job specifics; we could add the employer description after that. That would preserve it. Thus About the rolecould include both job specifics and the employer description. Let's incorporate the employer description paragraph: "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 recruiters are here to help you find travel assignments that align with your personal goals, professional aspirations, and sense of adventure. From your first conversation to your final day on assignment, you'll have a dedicated team in your corner. Our experienced recruiters, credentialing specialists, payroll professionals, and HR team work together to ensure a smooth, stress-free experience so you can focus on what matters most—caring for patients and making the most of every opportunity. Wherever your journey takes you, LRS Healthcare is here to support you every step of the way." That's substantive about the employer. We'll include it. Now About the role paragraph will be long but okay. Now ensure we didn't include any duplicated lines.