Travel Radiology Technician - $1,958 per week

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting. Content: - Job title: Radiology Technician (already shown, not repeat) - Location: Midland, Michigan - Specialty: Radiology Technician - Discipline: Allied Health Professional - Start Date: 10/12/2026 - Duration: 13 weeks - 40 hours per week - Shift: 8 hours, days - Employment Type: Travel - Description: 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. - Job ID #2193167 (metadata, can be short p or drop) - 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. - Posted job title: Radiology Technician (duplicate) - About Trustaff Allied paragraph (company description) - Benefits list: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus (also earlier: Comprehensive benefits, including medical, dental, and vision; 401k with employer match; Assistance with travel, compliance, and housing; Great bonuses for completions, referring friends, and more) We need sections: About the role (maybe description), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have real content. - About the role: Could be the description paragraph about what Radiology Tech does. That's substantive. - Responsibilities: Could be derived from description: "complete diagnostic procedures by working directly with the patient to capture images requested by the attending physician." Also "must have expert knowledge of the imaging equipment, its operation, and the imaging processes." Could be responsibilities. - Requirements: Might include specialty, discipline, maybe certification? Not explicit. The posting doesn't list specific requirements like ARRT certification, state license, etc. It only mentions specialty and discipline. Could we treat that as Requirements? It says "Specialty: Radiology Technician Discipline: Allied Health Professional". That's more like qualifications. But we need to avoid filler. If we put Requirements with just those two lines, it's substantive? Might be okay. However we need to avoid creating sections with placeholder like "not specified". These are actual values. - Qualifications: Could be similar to Requirements; maybe we can combine. But we need to avoid duplicate content. Perhaps we put Qualifications as the specialty/discipline, and Requirements as something else? Not much else. - Skills: Not explicitly listed. Could infer "expert knowledge of imaging equipment, its operation, and imaging processes" as skill. Could be a skill. - Benefits: We have list: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus, also 401k with employer match, Assistance with travel, compliance, and housing, Great bonuses for completions, referring friends, and more. So we have substantive benefits. - Pay: We have "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 somewhat vague but still mentions pay based on shifts and hours, tax-free stipend TBD. It's not a specific number but it's real content. According to rules, we should not create Pay section if it's only placeholder like "commensurate with experience", "not specified", "N/A", "varies", "TBD". Here it says "tax-free stipend amount to be determined." That's TBD. The pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation). That's still vague but not exactly TBD. It says subject to confirmation. Might be considered not specific enough? The rule: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state 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 stating something, albeit with TBD stipend. I'd say we can include Pay section with that sentence. - Schedule: We have Shift: 8 hours, days; 40 hours per week. That's schedule info. So we can include Schedule section. Now we need to avoid repeating job title as heading. Also drop Job ID/requisition numbers as headings; we can put them in a short p or drop. We'll likely drop. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Not present. We need to output only HTML fragment. Structure: We'll have sections as needed. Let's decide which sections to include: - About the role: description paragraph. - Responsibilities: maybe the same as description? Could split: Responsibilities: "Complete diagnostic procedures by working directly with the patient to capture images requested by the attending physician." plus maybe "Maintain expert knowledge of imaging equipment, its operation, and imaging processes." - Requirements: Could list "Specialty: Radiology Technician; Discipline: Allied Health Professional; Start Date: 10/12/2026; Duration: 13 weeks; 40 hours per week; Shift: 8 hours, days; Employment Type: Travel". But some of those are schedule/employment type. Might be better to put those under Schedule/About the role? However we already have Schedule section for shift/hours. Start date and duration could be in About the role or a separate "Job Details" but we don't have heading for that. Could incorporate into About the role paragraph. But we must not invent sections. We can include a short p for metadata like Start Date, Duration, etc. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can put start date, duration, etc in a short p. Thus:

Start Date: 10/12/2026 • Duration: 13 weeks • 40 hours per week • Shift: 8 hours, days • Employment Type: Travel

That's minor metadata. Now About the role: we can have a paragraph describing role. Responsibilities: we can have bullet list. Requirements: maybe we can list "Specialty: Radiology Technician; Discipline: Allied Health Professional". But that's also minor metadata; could be in same p. However we need a section only if real content. Could we put Requirements as empty? Better to omit Requirements if not substantive beyond what we already covered. The posting does not list specific requirements like certification, experience, etc. So we might skip Requirements. Qualifications: similarly. Skills: we could list "Expert knowledge of imaging equipment, its operation, and imaging processes". That's a skill. Benefits: list. Pay: paragraph. Schedule: we already put shift/hours in metadata p; but we could also have Schedule section with that info. However we already used shift/hours in metadata p; we could avoid duplication. The instruction: prefer a few substantive sections over many thin ones. So maybe we combine schedule info into About the role or a separate Schedule section? Since we already have metadata p with shift/hours, we could keep Schedule section empty? Better to not create Schedule section if we already put that info in metadata p. But the rule says: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. If we put schedule info in a p, we don't need a Schedule heading. So we can omit Schedule section. Similarly Pay: we have info about pay package; we can put that in a Pay section. Benefits: we have list; we can put Benefits section. About the role: we have description. Responsibilities: we have bullet list. Skills: we have bullet list maybe. We need to avoid duplication: The description already mentions completing diagnostic procedures and expert knowledge. Responsibilities could be same; but we can still separate. Let's craft:

About the role

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.

Responsibilities

• Complete diagnostic imaging procedures per physician orders.
• Operate imaging equipment and ensure proper functioning.
• Maintain expert knowledge of imaging equipment, its operation, and imaging processes.

Skills

• Expert knowledge of imaging equipment operation and processes.
• Patient care and communication.
• Ability to follow physician directives and safety protocols.

But some of these may be inferred; we must not invent detail. The posting only explicitly states: "complete diagnostic procedures by working directly with the patient to capture images requested by the attending physician." and "must have expert knowledge of the imaging equipment, its operation, and the imaging processes." That's it. So we should not add extra items like "Patient care and communication" unless explicitly stated. So we need to stick to what's given. Thus Responsibilities could be just the two sentences split into bullets? But we must not invent. We can make a bullet list with those two points. Responsibilities: - Complete diagnostic procedures by working directly with the patient to capture images requested by the attending physician. - Maintain expert knowledge of the imaging equipment, its operation, and the imaging processes. Skills: The posting does not list skills separately; the expert knowledge could be considered a skill. But we already used that in responsibilities. Might be redundant. Better to not create Skills section if it's just repeating. We could omit Skills. Benefits: we have list: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus, 401k with employer match, Assistance with travel, compliance, and housing, Great bonuses for completions, referring friends, and more. We need to output as

• each. Pay: we have sentence: "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." We can put that in a

  under Pay heading. Now About the role: we already used the description; maybe we can keep that as About the role. Now we need to include minor metadata p for start date, duration, etc. We'll put that before sections or after About the role? Probably after About the role as a short p. We must not repeat job title as heading. Good. We must not include Job ID as heading; we can drop it. Now check for any duplicated lines: The posting had "Posted job title: Radiology Technician" duplicate; we ignore. Now ensure we don't include boilerplate like "About Trustaff Allied" paragraph? That's company description; could be considered part of About the role? But it's about the company, not the role. The instruction: we should preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that company description somewhere. Where? Could be part of About the role? But About the role is about the role, not company. However we could include a separate section like "About Trustaff Allied" but we don't have a heading for that; we only allowed specific headings list. We could incorporate it into About the role as a paragraph after role description? But that would mix role and company info. The instruction says we can use headings only from the list; we cannot