Jobs · Healthcare · Ohio

Travel Radiology Technician - $2,137 per week

Trustaff · Akron, OH · 1 mo ago
On-siteHealthcareInternship
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Let's parse the posting. Job title: Radiology Technician (already displayed, we should not repeat as heading). Content: - Specialty: Radiology Technician - Discipline: Allied Health Professional - Start Date: 10/19/2026 - Duration: 13 weeks - 40 hours per week - Shift: 10 hours, nights - Employment Type: Travel - Job ID #2195741 (metadata, can be folded into short p or dropped) - Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - Posted job title: Radiology Technician (duplicate) - About Trustaff Allied: description paragraphs. - Benefits list: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus. Also responsibilities: "As a Radiology Tech, you'll complete diagnostic procedures by working directly with the patient to capture images requested by the attending physician. Radiologists/Rad Techs and CT Techs must have expert knowledge of the imaging equipment, its operation, and the imaging processes." Requirements/Qualifications: Not explicitly listed besides maybe specialty/discipline? There's no explicit list of requirements like certifications, experience. So we may not have a Requirements section with specific content. Could we infer? The instruction: include a section ONLY when the posting has real, specific content for it. So we should not create a Requirements section if no specific content. Skills: Not listed explicitly. Pay: We have "Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's somewhat vague but includes specifics: based on 10 hour shifts, 40 hours per week, tax-free stipend amount to be determined. It's not a specific number but it's still content. The rule says: 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. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on 10 hour shifts and 40 hours per week with tax-free stipend amount to be determined. That's somewhat vague but still states something. However the phrase "tax-free stipend amount to be determined" is placeholder. Might be considered not specific enough. The rule says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "tax-free stipend amount to be determined" is similar to TBD. So maybe we should omit Pay section. Schedule: We have shift: 10 hours, nights; 40 hours per week. That's specific. So we can include Schedule section. Benefits: we have list: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus. That's specific. About the role: we have description of what they'll do. That's substantive. Responsibilities: we have the sentence about completing diagnostic procedures etc. Could be considered responsibilities. Could also be part of About the role. But we can separate. We need to decide sections: About the role (maybe includes overview), Responsibilities (specific duties), Benefits, Schedule. Possibly also Qualifications? Not present. We must not repeat job title as heading. Use

for section headings. We need to use
  • for any list of duties/requirements/benefits. So for Benefits list, use ul li. For Responsibilities list (if we have multiple items) we can use ul li. If only one sentence, we could still use p. But rule: use
    • for any list of duties/requirements/benefits. If it's not a list, we can use p. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract specifics: - Specialty: Radiology Technician - Discipline: Allied Health Professional - Start Date: 10/19/2026 - Duration: 13 weeks - Hours per week: 40 - Shift: 10 hours, nights - Employment Type: Travel - Job ID: #2195741 (metadata, can be short p) - Pay package: based on 10 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. (maybe we can include as short p under Pay? but we decided maybe omit.) - About Trustaff Allied: paragraphs. - Benefits: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus. Responsibilities: "As a Radiology Tech, you'll complete diagnostic procedures by working directly with the patient to capture images requested by the attending physician. Radiologists/Rad Techs and CT Techs must have expert knowledge of the imaging equipment, its operation, and the imaging processes." We could split into two sentences; still responsibilities. We need to avoid boilerplate: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes some boilerplate about Trustaff Allied (that's not boilerplate, it's company description). Keep. We need to output only HTML fragment. Let's craft:

      About the role

      Trustaff Allied is seeking a travel Radiology Technician for a travel job in Akron, Ohio. Specialty: Radiology Technician. Discipline: Allied Health Professional. Start Date: 10/19/2026. Duration: 13 weeks. Employment Type: Travel.

      But we already have shift/hours etc maybe in Schedule. Better: About the role could include description of role and responsibilities? But we have separate Responsibilities. Let's do:

      About the role

      Trustaff Allied is seeking a travel Radiology Technician for a travel job in Akron, Ohio. The position is for an Allied Health Professional specializing in Radiology.

      But we need to preserve all substantive information: start date, duration, etc. Those could go under Schedule or maybe a separate "Details" but not a heading. We could put them in a short p under About the role. But we have Schedule section for shift/hours. Start date and duration could be placed in About the role or maybe a separate "Assignment details" but not a required heading. Since we only have headings for specific sections, we can include start date and duration in About the role paragraph. Now Responsibilities:

      Responsibilities

      • Complete diagnostic procedures by working directly with the patient to capture images requested by the attending physician.
      • Demonstrate expert knowledge of imaging equipment, its operation, and the imaging processes.
      Benefits:

      Benefits

      • Dental benefits
      • Medical benefits
      • Vision benefits
      • Guaranteed hours
      • Referral bonus
      Schedule:

      Schedule

      40 hours per week, 10‑hour night shifts.

      We might also include shift details: nights. Now Pay: we might omit because it's vague. We also need to include Job ID maybe as short p but not heading. Could fold into About the role or a separate p without heading. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it. So we can add a p with Job ID. Let's add after About the role maybe a p: "Job ID: #2195741." But we need to avoid duplication. Already we have posted job title repeated; we can ignore. Now check for any other substantive content: "Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This is pay info but vague. Since we decided to omit Pay section, maybe we can include this as a short p under About the role or Schedule? But it's about pay. The rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay, albeit vague. However the phrase "tax-free stipend amount to be determined" is placeholder. The instruction about filler/placeholder text: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "tax-free stipend amount to be determined" is similar to TBD. So if we made a Pay heading, we would have filler. So better to omit Pay section entirely. However we could still include the pay info as a short p without a heading, maybe under About the role? But that would be mixing pay info with role description; still preserving info. The instruction didn't forbid including pay info in a paragraph without heading. It only forbids creating a Pay section unless the posting actually states them. It does state something about pay, but it's vague. However we could still include the info as a paragraph, but we risk including placeholder text. The rule about filler/placeholder text applies to headings followed by filler text. If we don't make a heading, it's okay to include the sentence? The instruction: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". So if we don't make a heading, it's fine to include the sentence. However we also have "never create Pay/Schedule/Benefits sections unless the posting actually states them." Since we are not creating a Pay section, we can include the pay info elsewhere. Thus we could add a short p under About the role or after it: "Pay package is based on 10‑hour shifts and 40 hours per week (subject to confirmation) with a tax‑free stipend amount to be determined." But that includes "subject to confirmation" and "to be determined" which is vague but it's still the info. It's not invented. It's preserving the detail. It's okay. Similarly, we could include start date and duration in About the role. Let's craft final HTML:

      About the role

      Trustaff Allied is seeking a travel Radiology Technician for a travel job in Akron, Ohio. Specialty: Radiology Technician. Discipline: Allied Health Professional. Start Date: 10/19/2026. Duration: 13 weeks. Employment Type: Travel. Job ID: #2195741. Pay package is based on 10‑hour shifts and 40 hours per week (subject to confirmation) with a tax‑free stipend amount to be determined.

      Responsibilities

      • Complete diagnostic procedures by working directly with the patient to capture images requested by the attending physician.
      • Demonstrate expert knowledge of imaging equipment, its operation, and the imaging processes.

      Benefits

      • Dental benefits
      • Medical benefits
      • Vision benefits
      • Guaranteed hours
      • Referral bonus

      Schedule

      40 hours per week, 10‑hour night shifts.

      Check

Similar jobs