Travel Interventional Radiology Technologist - $3,535 per week

We need to output HTML fragment with sections for headings that have content. The posting includes: - Job title: travel Interventional Radiology Technologist (not to be repeated as heading) - Job Description & Requirements: includes Specialty, Discipline, Start Date, Duration, 40 hours per week, Shift, Employment Type. - Then description about LRS Healthcare (some repeated). - Benefits: list. - Then "About LRS Healthcare - Allied" repeated description. - Pay package line: "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." This is pay info but says tax-free stipend amount to be determined => we should not create Pay section if it's not specific? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Here pay package is mentioned but stipend amount to be determined => not specific. So we should not create a Pay section. Similarly schedule: they gave shift 8 hours, flexible, 40 hours per week. That's schedule info. Should we create a Schedule section? The rule: only create Schedule section if posting actually states them. It does state shift and hours. So we can include Schedule section with details. Benefits: they list specific benefits, so we can include Benefits section. We also need About the role, Responsibilities, Requirements, Qualifications, Skills sections if content exists. The posting includes "Job Description & Requirements" which includes Specialty, Discipline, Start Date, Duration, 40 hours per week, Shift, Employment Type. That's more like requirements. There's no explicit responsibilities list. So we could have a section "Requirements" with those details. Or maybe "About the role" could contain the description about the role (specialty, discipline). But we should not create empty sections. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions, cookie/navigation/legal/EEO etc. Also remove duplicated description (the "About LRS Healthcare - Allied" appears twice). We should keep only one copy. We need to include Job ID? The rule: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we could include Job ID in a short paragraph maybe at top? But they said fold minor metadata into a short

  or drop it. Probably we can drop it as it's minor. But we need to preserve all substantive information; Job ID is not substantive? Probably minor metadata, can drop. We'll drop. We need to avoid repeating the same content. Let's extract substantive content: - Specialty: Interventional Radiology Technologist - Discipline: Allied Health Professional - Start Date: ASAP - Duration: 12 weeks - Hours: 40 hours per week - Shift: 8 hours, flexible - Employment Type: Travel - Description about LRS Healthcare (the paragraph about connecting professionals, recruiters, etc.) This appears twice; we keep one. - Benefits list: - Streamlined, simple credentialing process through the LRS Connect App - Health, Dental, and Vision Insurance - Life and Disability Insurance - 401(k) with Employer Match - Generous Referral Bonus Program - Employee Assistance Program (EAP) - Weekly Direct Deposit - 24/7/365 Support - Also "Adventure is Calling! Apply today!" is a call to action, but we should remove application instructions. That's likely boilerplate; we can drop. - Pay package line: we decided not to include Pay section because stipend amount to be determined (non-specific). However we could still include a Pay section with the info we have? The rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That's stating something about pay but not specific amount. It's vague. The rule says never create Pay section unless posting actually states them. It does state something about pay, but it's not specific. However the instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay (pay package based on...). So maybe we should include a Pay section with that sentence. But also they said "Prefer a few substantive sections over many thin ones." The pay info is thin. Might be better to incorporate into Schedule or Requirements? But they said use sections for Pay, Schedule, Benefits only if posting actually states them. So we could include a Pay section with that sentence. However the stipend amount to be determined is vague; but it's still stating something. I'd lean to include a Pay section with that sentence as a

  . But we need to check if they want to avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". The phrase "tax-free stipend amount to be determined" is similar to TBD. That's essentially unspecified. So we should avoid creating a Pay section because it's not specific. The rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, but it's not specific. However the examples of filler include "varies", "TBD". So "tax-free stipend amount to be determined" is akin to TBD. So we should not create Pay section. Thus we will have sections: About the role? Maybe we can combine the description of the role (specialty, discipline) into an "About the role" section. Then Responsibilities? Not present. Requirements? Could include start date, duration, hours, shift, employment type. Qualifications? Not given. Skills? Not given. Benefits we have. Schedule we have shift/hours. But we might incorporate schedule into Requirements or a separate Schedule section. Since we have schedule info (8 hour shifts, flexible, 40 hours per week). We could create a Schedule section with that. But we also have hours in Requirements. To avoid duplication, we could put schedule info in Schedule section and other requirements (start date, duration, employment type) in Requirements. Let's decide: - About the role: paragraph describing the role: "Interventional Radiology Technologist travel position in Columbia, Missouri." plus maybe the specialty/discipline. We'll write a short prose. - Requirements: list: Start Date: ASAP; Duration: 12 weeks; Employment Type: Travel. - Schedule: 8 hours per shift, flexible, 40 hours per week. - Benefits: list as given. - About LRS Healthcare - Allied: the paragraph about the company (we keep one copy). Could be a section "About LRS Healthcare - Allied" or maybe "About the Company". But headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list "About the Company". So we should not create a heading not in the list. The allowed headings are those enumerated. So we must only use those headings. So we cannot create "About LRS Healthcare - Allied". We must fit that content into one of the allowed headings. Perhaps we can put it under "About the role" as it's about the role and the company? But "About the role" is for role description. The company description could be considered part of "About the role"? Might be okay. Or we could drop it as boilerplate? It's descriptive of the company, but it's repeated and maybe considered boilerplate? However it's substantive about the recruiter support etc. Could be considered part of the job posting's description of the employer. The allowed headings do not include a company section, but we could incorporate it into "About the role" or maybe "Requirements"? Not ideal. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should stick to those. So we need to map content to those headings. We have: - About the role: can include specialty, discipline, location, maybe brief description of role. - Responsibilities: not provided; we should not create empty. - Requirements: can include start date, duration, employment type. - Qualifications: not provided. - Skills: not provided. - Benefits: list. - Pay: we decided not to include. - Schedule: shift/hours. Thus we will output sections: About the role, Requirements, Schedule, Benefits. We need to ensure we don't repeat info. Let's craft: About the role:

  Interventional Radiology Technologist travel position in Columbia, Missouri. Specialty: Interventional Radiology Technologist. Discipline: Allied Health Professional.

  Requirements:

  • Start Date: ASAP
  • Duration: 12 weeks
  • Employment Type: Travel

  Schedule:

  8‑hour shifts, flexible scheduling; 40 hours per week.

  Benefits:

  • Streamlined, simple credentialing process through the LRS Connect App
  • Health, Dental, and Vision Insurance
  • Life and Disability Insurance
  • 401(k) with Employer Match
  • Generous Referral Bonus Program
  • Employee Assistance Program (EAP)
  • Weekly Direct Deposit
  • 24/7/365 Support

  We should also maybe include location? Already in About the role. We need to ensure we don't include any boilerplate like "Adventure is Calling! Apply today!" or repeated paragraphs. We should not include the Job ID line. We should not include the repeated "About LRS Healthcare - Allied" paragraph. Check for any other substantive info: The description about LRS Healthcare (the paragraph about recruiters etc.) is substantive but not covered by allowed headings. Could we incorporate into About the role? It's more about the company/agency. But maybe we can treat it as part of About the role? The heading "About the role" could include info about the role and the employer's support. It's a stretch but maybe acceptable. However the instruction says "Prefer a few substantive sections over many thin ones." If we omit that paragraph, we lose some substantive info about recruiter support, credentialing specialists, etc. That is substantive. We need to preserve ALL substantive information. So we must include that info somewhere. Since we cannot create a custom heading, we need to fit it into one of the allowed headings. Which one fits best? Perhaps "About the role" could include the employer's support as part of the role context. Or "Requirements" could include? No. "Benefits" already covers benefits; the paragraph about recruiters, credentialing, payroll, HR team is not a benefit but rather support. Could be considered part of "About the role". I'd put it in About the role as additional prose. Thus About the role will have two paragraphs: first about the role specialty/discipline/location, second about LRS Healthcare support. We must not repeat the paragraph twice. Let's craft About the role:

  Interventional Radiology Technologist travel position in Columbia, Missouri. Specialty: Interventional Radiology Technologist. Discipline: Allied Health Professional.

  At LRS Healthcare, we connect skilled nursing and allied health professionals with rewarding opportunities at top healthcare facilities across the country. Whether you're looking to explore a new city, gain experience in a different