Local Contract X-ray Technician - $51-55 per hour

We need to produce HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. We need to parse the posting. Given text: Host Healthcare is seeking a local contract Radiology Technologist for a local contract job in Concord, Massachusetts. Job Description & Requirements Specialty: Radiology Technologist Discipline: Allied Health Professional Start Date: 10/20/2026 Duration: 13 weeks 32 hours per week Shift: 8 hours, days Employment Type: Local Contract Host Healthcare Job ID #La1fVX0000044ArJYAU. Pay package is based on 8 hour shifts and 32.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. Posted job title: Radiology Tech About Host Healthcare [... description ...] Benefits [list of benefits] We need sections: About the role (maybe description of role?), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content for each. From posting: "Job Description & Requirements" includes specialty, discipline, start date, duration, hours per week, shift, employment type. That could be considered "About the role" maybe. But we need to decide. We have no explicit responsibilities list. Could infer from specialty? But we must not invent. So we should not create a Responsibilities section if no specific content. Similarly Requirements: maybe the specialty and discipline are requirements? Could be considered requirements. But we need to see if there is explicit "Requirements" heading in posting. Not present. However we can treat the details under "Job Description & Requirements" as requirements? The instruction: "Prefer a few substantive sections over many thin ones." So we can combine. We have Benefits list: many items. Pay: "Pay package is based on 8 hour shifts and 32.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This is vague; says tax-free stipend amount to be determined. That's not specific; it's "to be determined". According to rule: do NOT include Pay section unless posting actually states them, and never emit heading followed by filler/placeholder text like "not specified", "N/A", "varies", "TBD". Here it's "tax-free stipend amount to be determined." That's placeholder. So we should NOT include Pay section. Schedule: we have shift: 8 hours, days; 32 hours per week; duration 13 weeks. That's schedule info. Could be considered schedule. It's specific: 8 hour shifts, days, 32 hours per week. So we can include Schedule section. About the role: we have description of role: local contract Radiology Technologist in Concord, Massachusetts. Could be considered About the role. Responsibilities: none specific. Requirements: maybe the specialty and discipline are requirements. Could be considered Requirements. But we need to decide if we should create Requirements section with those details. The posting says "Job Description & Requirements" then lists Specialty, Discipline, Start Date, Duration, etc. Those could be considered requirements. However we already used About the role for location and role. Could split: About the role: brief description; Requirements: specialty, discipline, start date, duration, hours, shift, employment type. That seems reasonable. Qualifications: not explicit; maybe license/certification? Not given. So skip. Skills: not explicit; skip. Benefits: we have list. Thus sections: About the role, Requirements, Benefits, Schedule. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Not include Job ID. We must preserve all substantive information; do not invent or summarize away detail. Let's extract details: About the role: "Host Healthcare is seeking a local contract Radiology Technologist for a local contract job in Concord, Massachusetts." Also maybe "Posted job title: Radiology Tech". But we should not repeat job title as heading; but we can include that as prose? The posted job title is Radiology Tech, which is essentially same as Radiology Technologist. Might be considered duplicate. We could include it as part of About the role prose: "Posted job title: Radiology Tech." It's substantive but maybe redundant. We'll include. Requirements: list items: - Specialty: Radiology Technologist - Discipline: Allied Health Professional - Start Date: 10/20/2026 - Duration: 13 weeks - 32 hours per week - Shift: 8 hours, days - Employment Type: Local Contract Also maybe "Host Healthcare Job ID #La1fVX0000044ArJYAU." but we should drop Job ID per instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we could drop it entirely. It's minor metadata; we can drop. Pay package line: we decided not to include Pay section because placeholder. But we could include that info in Schedule? No, it's about pay. Since it's placeholder, we should not include Pay section. Could we include the sentence about pay package in a

  under About the role? It says "Pay package is based on 8 hour shifts and 32.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's partially placeholder but includes concrete info: based on 8 hour shifts and 32 hours per week. However the stipend amount TBD. The rule: never emit 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. For Pay section, we would have heading Pay and then content that includes placeholder. That's not allowed. But we could embed the pay info in another section like Requirements or About the role? The rule about not creating Pay section unless posting actually states them. It does state pay package based on 8 hour shifts and 32 hours per week, but stipend TBD. It's partially stated. However the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state some pay info, but also includes TBD. The rule about not emitting heading followed by filler/placeholder text: if we made a Pay section, we would have to include the placeholder "tax-free stipend amount to be determined." That's filler/placeholder. So we should avoid Pay section. Could we include the concrete part (based on 8 hour shifts and 32 hours per week) in Schedule? That seems misfit. Better to omit pay details entirely? But we must preserve ALL substantive information. The concrete part "based on 8 hour shifts and 32.0 hours per week" is substantive. However that is already covered by Schedule (hours per week, shift). So we can incorporate that into Schedule section. The stipend TBD we can drop as placeholder. Thus Schedule section: we have shift: 8 hours, days; 32 hours per week; duration: 13 weeks. Also maybe "local contract" employment type? That's more about Requirements. We'll put Schedule:

  • Shift: 8 hours, days
  • 32 hours per week
  • Duration: 13 weeks
  Now Benefits: list given: - Referral bonus - School loan reimbursement - Vision benefits - Wellness and fitness programs - Company provided housing options - License and certification reimbursement - Life insurance - Medical benefits - Mileage reimbursement - Pet insurance - Discount program - Employee assistance programs - Guaranteed Hours - Health savings account - Holiday Pay - 401k retirement plan - Continuing Education - Dental benefits We need to output as
  • each. Now About the role: we need prose

    . Include: "Host Healthcare is seeking a local contract Radiology Technologist for a local contract job in Concord, Massachusetts. Posted job title: Radiology Tech." Also maybe mention "At Host Healthcare, we provide a truly comfortable experience..." That's from About Host Healthcare paragraph. That's more about the company, not the role. Could be considered About the role? Actually "About Host Healthcare" is company description. Could be considered "About the role"? Not exactly. But we could include it as part of About the role? The instruction: "About the role" heading likely for role description. The company description could be considered "About Host Healthcare" but we don't have a heading for that. We could incorporate that prose under About the role as it's substantive about the employer. However the rule: "Prefer a few substantive sections over many thin ones." So we could combine company description into About the role. Thus About the role paragraph: combine the initial sentence and the Host Healthcare description. Let's extract Host Healthcare description: "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." Note that benefits mentioned here overlap with Benefits list; but we should not duplicate. However we must preserve ALL substantive information; we can include it but risk duplication. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Duplicated lines: we should avoid duplicating the same benefit statements that are already in Benefits list. The Host Healthcare description includes some benefits that are also in the Benefits list (Day 1 medical, 401K matching, travel reimbursements, dedicated housing support, 24/7 support, on-staff clinicians). Those are duplicated with the Benefits list. We should avoid duplication. So we should either omit those duplicated sentences from the About the role paragraph, or we could keep them but risk duplication. Better to remove duplicated content. Thus we need to craft About the role paragraph that includes non-duplicated substantive info: The initial sentence about seeking Radiology Technologist in Concord, MA. Posted job title. Maybe also mention that it's a local contract job. The Host Healthcare description includes mission statement etc. Some of that is not duplicated: "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." Also "Travel comfortably with Host Healthcare." That's not duplicated. We should avoid sentences that mention benefits already listed: "During your assignment, get access to premium benefits, including Day 1 medical that continues up to 30 days between assignments, 401K