Local Contract CT Technologist - $49-53 per hour
- each.
- 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: based on 12 hour shifts and 36 hours per week, tax-free stipend amount TBD. It says "subject to confirmation" and "tax-free stipend amount to be determined". This is somewhat placeholder but still mentions pay structure. The instruction: "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" which is TBD-like. Also "subject to confirmation". This might be considered placeholder. However we also have "Pay package is based on 12 hour shifts and 36.0 hours per week". That's specific. But the amount is TBD. The instruction says do not create Pay section unless posting actually states them. It does state pay package based on shifts and hours, but amount TBD. Is that considered filler? It says "tax-free stipend amount to be determined" which is TBD. The phrase "based on 12 hour shifts and 36.0 hours per week" is specific. I'd lean to include Pay section with that sentence, but we must avoid filler. Could we rephrase to just state the known specifics? The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". If we include the sentence that includes "tax-free stipend amount to be determined", that includes TBD. That might be considered filler. Better to omit Pay section if it's mostly placeholder. However we could include a short
that says "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation)." That still includes "subject to confirmation" which is vague but not exactly TBD. Might be okay. The instruction says avoid filler like "TBD". "subject to confirmation" is not exactly TBD but still uncertain. Might be acceptable. I'd include Pay section with that sentence. - Schedule: We have shift: 12 hours, nights; 36 hours per week. That's schedule specifics. So include Schedule section. Thus sections: About the role, Benefits, Pay, Schedule. We need headings
for each. Inside About the role: we can put a
with the description. We should not include Job ID etc. Could fold minor metadata into short
or drop it. The Job ID is minor metadata; we could include in About the role paragraph maybe. But instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include Job ID in a short
maybe within About the role or separate small paragraph. Probably better to include it in About the role paragraph. Thus About the role paragraph: "Host Healthcare is seeking a local contract CT Technologist for a local contract job in Sanford, North Carolina. Specialty: CT Technologist; Discipline: Allied Health Professional; Start Date: 10/19/2026; Duration: 13 weeks; 36 hours per week; Shift: 12 hours, nights; Employment Type: Local Contract. Host Healthcare Job ID #La1fVX0000044zsDYAQ." That's a lot but okay. Benefits: list each benefit as
- .
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.
Might still have TBD. Could we drop the "tax-free stipend amount to be determined" part? That would be removing detail. We must preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep that detail. So we keep the sentence as is. It includes TBD but it's part of the posting. The instruction says never emit a heading followed by filler/placeholder text. The heading would be Pay, and the content includes TBD. Is that considered filler? The phrase "tax-free stipend amount to be determined" is placeholder. Might be considered filler. However the instruction says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". That seems to refer to the content under the heading being just filler. If we include other specifics besides TBD, maybe it's okay. The sentence also includes "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation)". That's substantive. So heading Pay with that sentence is not solely filler. So acceptable. Schedule:Shift: 12 hours, nights; 36 hours per week.
Or we could incorporate into About the role but we already have schedule details there. However we need to avoid duplication. The About the role already includes shift and hours. If we also include Schedule section, we'd duplicate. The instruction: "Prefer a few substantive sections over many thin ones." Duplication might be thin. Better to combine schedule info into About the role and not have separate Schedule section. But we need to decide. We have schedule specifics: 12 hour shifts, nights; 36 hours per week. Already in About the role. If we make a Schedule section, we would repeat. Might be considered duplication but still okay? The instruction says "Prefer a few substantive sections over many thin ones." Having both About the role and Schedule might be thin. Better to keep schedule within About the role and not create separate Schedule section. However the instruction says to include a section ONLY when the posting has real, specific content for it. It does have schedule content, but we already used it in About the role. Could we still have a Schedule section with that content, and not duplicate in About the role? We could remove schedule from About the role and put it in Schedule. But About the role would lose some specifics. However we could keep About the role more general: mention seeking CT Technologist, location, specialty, discipline, start date, duration, employment type, Job ID. Then schedule separate. That seems reasonable. Let's restructure: About the role: Host Healthcare is seeking a local contract CT Technologist for a local contract job in Sanford, North Carolina. Specialty: CT Technologist; Discipline: Allied Health Professional; Start Date: 10/19/2026; Duration: 13 weeks; Employment Type: Local Contract. Host Healthcare Job ID #La1fVX0000044zsDYAQ. Schedule: Shift: 12 hours, nights; 36 hours per week. 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. Benefits: list. That avoids duplication. Now ensure we don't include any boilerplate like "About Host Healthcare" paragraph? That is about the company, not the role. Should we include that? The instruction: "Prefer a few substantive sections over many thin ones." The About Host Healthcare paragraph is descriptive of the company, not the role. Could be considered boilerplate? It's not a standard heading like Benefits etc. It's more like company overview. The instruction didn't forbid including it, but we have sections limited to those headings. We could incorporate that into About the role? But it's not about the role. However we could treat it as part of About the role? Might be okay to include as aunder About the role? But the heading is About the role, not About Host Healthcare. The content could include both role and company info. It's not prohibited. However we might be adding fluff. The instruction says "Prefer a few substantive sections over many thin ones." Including company overview might be thin but still substantive. I'd include it as part of About the role paragraph. Thus About the role paragraph: combine role details and company overview. Let's craft:
Host Healthcare is seeking a local contract CT Technologist for a local contract job in Sanford, North Carolina. Specialty: CT Technologist; Discipline: Allied Health Professional; Start Date: 10/19/2026; Duration: 13 weeks; Employment Type: Local Contract. Host Healthcare Job ID #La1fVX0000044zsDYAQ. At Host Healthcare, we provide a truly comfortable experience as you explore your travel nursing, therapy, or allied career. We make your travel healthcare journey easy by taking care of all the details, so you don’t have to. We are on a mission to help others live better and we do this by helping the healers of the world be as comfortable as possible. With access to tens of thousands of travel nursing, therapy, and allied jobs in all 50 states, our responsive and friendly recruiters find your dream position based on what’s important to you. During your assignment, get access to premium benefits, including Day 1 medical that continues up to 30 days between assignments, 401K matching, travel reimbursements, dedicated housing support, and more. We also offer 24/7 support from our team and access to our on-staff clinicians so you can feel comfortable and confident throughout your entire assignment. Travel comfortably with Host Healthcare.
But note that the benefits description overlaps with Benefits section. We might duplicate. The About Host Healthcare paragraph includes a summary of benefits. Then we also have a Benefits section with list. That could be duplication but still okay? Might be considered thin. Better to keep About the role focused on role specifics, not include