We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like navigation, EEO, etc. The posting includes many details: location, start date, duration, hours, shift, employment type, title, etc. Also includes responsibilities list, skills list, requirements (experience, license, certification, etc). Also includes on-call details, etc. Also includes pay package mention: "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 not a specific amount, but it's still some content about pay. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on 8 hour shifts and 40 hours per week with tax-free stipend amount to be determined. That's somewhat vague but it's still stating something about pay. 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 not a specific number but it's still content. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here "tax-free stipend amount to be determined" is placeholder/TBD. So we should not create a Pay section if it's just placeholder. The phrase "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation)" is somewhat specific about shift and hours but not actual pay. Might be considered filler. Safer to omit Pay section.
Schedule: The posting includes schedule details: "Schedule: Day Shift 5x8-Hour 40hours/week", "Schedule: Monday–Friday, Day Shift", "Shift: 8-hour shifts", "On-Call: 2–3 call shifts/month", "Callback/Holidays: Per unit needs", "On-Call Response: Must be able to report within 30 minutes". That's specific schedule info. So we should include a Schedule section.
Benefits: Not mentioned explicitly. No benefits listed. So omit Benefits.
About the role: Could include a brief description: "TalentBurst, Inc is seeking a travel Radiology Technician for a travel job in Rochester, New York." plus maybe description of company? The "About TalentBurst, Inc" paragraph is boilerplate about the company; might be considered not specific to role. But we could include a short "About the role" summarizing the job: travel Radiology Technician, location, start date, duration, etc. However we must not repeat job title as heading. We can include a paragraph under About the role that includes location, start date, duration, etc. But we must preserve all substantive information; we can put those details in other sections like Requirements, Qualifications, Skills, Schedule. The start date, duration, location, hours, shift could go under About the role or maybe under Schedule. The instructions: Use headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can put location, start date, duration, employment type under About the role. That seems appropriate.
Responsibilities: list bullet points.
Requirements: maybe include mandatory items like experience, license, certification, BLS, trauma center experience, etc. Qualifications could be similar; but we need to decide split. The posting has "Experience: 2 years X-Ray Technologist experience required", "Trauma: Level 1 Trauma Center experience required OR Experience: Recent OR experience required", "C-Arm/O-Arm: Experience within the past 8 months required", "License: NYS license required or must be obtainable before start", "Certification: ARRT – Required", "BLS: Required", "Additional Requirements: Formal Radiologic Technology training Ability to lift/move patients Ability to stand for extended periods Strong communication and teamwork skills". Also there is a "Skills" section later with a table: Skill Required / Desired Amount of Experience Expertise Rating Move Technician License (currently ANY Tech License is accepted in the state of NY) Required Two (2) years experience Required BLS (American Heart Association ONLY) Required Experience using c-arm/o-arm Required 8 Months trauma 1 center experience Required OR experience at a trauma 1 center Required. That's redundant.
We need to avoid duplication. We should consolidate substantive info without repeating. We'll create sections:
- About the role: paragraph with location, start date, duration, employment type (Travel), shift basics maybe.
- Responsibilities: ul list of responsibilities.
- Requirements: ul list of mandatory requirements: 2 years X-Ray Tech experience, Level 1 Trauma Center experience (or recent OR experience), C-Arm/O-Arm experience within past 8 months, NYS license (or obtainable), ARRT certification, BLS (AHA), Formal Radiologic Technology training, ability to lift/move patients, ability to stand for extended periods, strong communication and teamwork skills, ability to report within 30 minutes for on-call, ability to obtain TB skin test? Actually that's a question in the posting: "Question 2 Is HCP able to obtain TB skin test?" That's a question for applicant, not a requirement. Might be considered a requirement? It's a question; we could treat as requirement: must be able to obtain TB skin test. But it's phrased as a question. Might be considered part of screening. We'll include as requirement: able to obtain TB skin test.
- Qualifications: maybe we can include "Travel Radiology Technician" specialty, Allied Health Professional discipline, etc. But we might not need Qualifications if we already covered requirements. However we need to follow instruction: prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one? But headings are predefined; we can omit Qualifications if no specific content beyond requirements. The posting does not have separate qualifications beyond requirements. So we can omit Qualifications.
- Skills: we can list skills from the Skills table: Move Technician License (any NY Tech License), 2 years experience, BLS (AHA), experience using c-arm/o-arm, 8 months trauma 1 center experience, OR experience at trauma 1 center. However many of these overlap with requirements. To avoid duplication, we could list skills as: proficiency with radiographic equipment, patient positioning, radiation safety, PACS, communication, teamwork, ability to lift/move patients, ability to stand long periods, etc. But the posting's skills section is basically a table repeating requirements. We could still include a Skills section with bullet points derived from that table, but ensure not to just repeat requirements verbatim? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. If we put it in Requirements, we can omit Skills to avoid duplication. But we must preserve all substantive info; if we put it in Requirements, it's preserved. So we can omit Skills section if its content is covered elsewhere. However the Skills section includes some nuance: "Move Technician License (currently ANY Tech License is accepted in the state of NY)" which is about license acceptance. That's covered under License requirement. "Two (2) years experience Required" covered. "BLS (American Heart Association ONLY) Required" covered. "Experience using c-arm/o-arm Required" covered. "8 Months trauma 1 center experience Required" covered. "OR experience at a trauma 1 center Required" covered. So we can omit Skills.
- Schedule: we need to include schedule specifics: Day Shift 5x8-Hour 40hours/week, Monday–Friday, Day Shift, 8-hour shifts, On-Call: 2–3 call shifts/month, Callback/Holidays: Per unit needs, On-Call Response: Must be able to report within 30 minutes.
- Pay: we determined to omit because it's placeholder.
- Benefits: omit.
Now we need to output only HTML fragment, no markdown fences.
We'll structure:
About the role
TalentBurst, Inc is seeking a travel Radiology Technician for a travel position in Rochester, New York. The assignment starts 11/02/2026 (or 10/19/2026? There are two start dates: earlier in description: Start Date: 10/19/2026 Duration: 12 weeks; later in job title block: Start Date: 11/02/2026 Duration: 13 weeks. There's inconsistency. We must preserve all substantive information; we cannot choose one over the other. We need to include both? The posting includes both sets; maybe it's a copy-paste error. We should include both as separate sentences: "Start date listed as 10/19/2026 for a 12‑week assignment; also noted as 11/02/2026 for a 13‑week assignment." We'll preserve both.
Also include location: 601 Elmwood Ave, Rochester, NY 14642.
Employment type: Travel.
Shift: 8‑hour days, 40 hours per week.
We'll put that in About the role.
Then Responsibilities ul.
Then Requirements ul.
Then Schedule ul.
We must not include any boilerplate like "About TalentBurst, Inc" paragraph; that's company description, not role-specific. Could we include it under About the role? It's about the company, not the role. The instruction: "About the role" heading for section headings (e.g. About the role, Responsibilities...). So we should put role-specific info there, not company boilerplate. So we omit the company description.
Now let's craft.
Responsibilities list:
- Perform diagnostic X-rays and produce high-quality images
- Safely operate radiologic equipment while minimizing patient radiation exposure
- Position and assist patients appropriately
- Verify patient identity, orders, and exam details
- Maintain accurate records and ensure images are properly sent to PACS
- Report damaged or malfunctioning equipment promptly
Requirements list:
- 2 years X‑Ray Technologist experience
- Level 1 Trauma Center experience (or recent OR experience)
- C‑Arm/O‑Arm experience within the past 8 months
- Valid New York State radiology license (or ability to obtain before start)
- ARRT certification
- BLS certification (American Heart Association only)
- Formal Radiologic Technology training
- Ability to lift and move patients
- Ability to stand for extended periods
- Strong communication and teamwork skills
- Able to report to an on‑call shift within 30 minutes
- Able to obtain a TB skin test
Schedule list:
- Day shift, 5 × 8‑hour shifts per week (40 hours/week)
- Monday–Friday day shift
- 8‑hour shifts
- On‑call: 2–3 call shifts per month
- Callback/holidays: as needed by unit
- Must be able to report within 30 minutes for an on‑call call
We should not repeat the on-call response twice; we have it in requirements and schedule. It's okay to appear in both? Might be duplication. But we need to preserve all info; we could keep it only in Schedule, but it's also a requirement. To avoid duplication, we could mention it only in Schedule, but then we lose it as a requirement. However the requirement list includes "Able to report to an on‑call shift within 30 minutes". That's a requirement. So we need to keep it somewhere. We could keep it in Requirements and not repeat in Schedule; but schedule also includes on-call details. We could keep schedule without repeating the 30 minute response, but schedule