Jobs · Healthcare · Utah

Travel Cath Lab Radiology Technologist - $2,755 per week

Slate Healthcare · Salt Lake City, UT · 6 days ago
On-siteHealthcareInternship
The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, identify sections: - About the role / Description: There's a description paragraph about the role. - Highlights: There's a "Highlights" section with bullet points. - Requirements: There's a "Requirements" section with specific requirements. - About Slate Healthcare: There's an "About Slate Healthcare" section with company info. - Pay/Schedule: There's some pay/package info in the job details and at the end. Rules: - Use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). - Use
  • for lists,

    for prose. - Do NOT repeat job title as heading (page already shows it). - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. - Preserve ALL substantive information; do NOT invent or summarize away detail. - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. - Include a section ONLY when the posting has real, specific content for it — 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. - Prefer a few substantive sections over many thin ones. - Output ONLY the HTML fragment — no /, no markdown code fences. Now, parse the input: Job title: "Slate Healthcare is seeking a travel Cath Lab Radiology Technologist for a travel job in Salt Lake City, Utah." This is the title, but we shouldn't repeat as heading. Job Description & Requirements: This is a heading in the source, but we need to map to our sections. Specialty, Discipline, Start Date, Duration, hours per week, Shift, Employment Type: These are metadata. Should we include? The rule says fold minor metadata into a short

    or drop it. Could include in a "Job Details" section? But the allowed headings are specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Job Details" not listed. Could incorporate into "About the role" or a short paragraph. Description: "As a Cath Lab Technologist, you will play a critical role... balanced work-life schedule. This role not only offers professional growth but also the opportunity to work with advanced technology in a supportive setting." This is prose about the role. Highlights: "Work in a state-of-the-art Cath Lab environment. Flexible 4x10 shift schedule. Collaborative team culture with a focus on patient care." This is a list. Requirements: "EMR System: EPIC/Merge 2 years of experience required RCIS or RT or CVT or RN that scrubs certification" This is a list. Slate Healthcare Job ID: metadata, drop or fold into a short p. Pay package: "Pay package is based on 10 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This is pay info. Should we create a Pay section? The rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package details, albeit vague. It says "tax-free stipend amount to be determined." That's somewhat specific. Could include a Pay section with that info. But also schedule info: "36 hours per week", "Shift: 10 hours, days", "4x10 hour shifts". Could create a Schedule section? The rule says include only when real specific content. There is schedule info. But the allowed headings include Schedule. Could create a Schedule section with the shift details. However, the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state schedule and pay. So we can include them. About Slate Healthcare: company description. Could be "About the Company" but not in allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the Company" not listed. Could fold into a paragraph at the end? But the rule says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning those are examples, but we should stick to those? The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those. However, "About Slate Healthcare" is about the company, not the role. Could be considered "About the Company" but not in list. Might be better to include as a section with heading "About the Company"? But the rule says "use

    for section headings (e.g. ...)". It doesn't say we cannot use other headings. But to be safe, maybe we can include it as a section with heading "About the Company"? However, the rule also says "Prefer a few substantive sections over many thin ones." The company description is substantive. But the allowed headings are examples; we can use other relevant headings. However, the user might expect only those headings. Let's see: The job posting has "About Slate Healthcare". That's a section. I think we should include it as a section with heading "About the Company" or "About Slate Healthcare". But the rule says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must only use those. It says "e.g." meaning for example. So we can use other headings if they fit. But to be consistent, maybe we can map "About Slate Healthcare" to "About the Company". However, the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings". It doesn't forbid company about section. But the instruction also says: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The company description is real content. I'll include sections: About the Role (description), Highlights (maybe as part of About the Role or separate?), Requirements, Pay, Schedule, About the Company. But Highlights could be a list under About the Role or separate. The allowed headings include "Responsibilities" but not "Highlights". Could use "Highlights" as a heading? Not in list. Could incorporate into "About the Role" as a list. But the posting has a distinct "Highlights" section. I'll create a section "Highlights" with

    ? The rule says use

    for section headings (e.g. ...). It doesn't forbid "Highlights". I'll use "Highlights" as a heading. Similarly, "Requirements" is in the list. Now, metadata: Specialty, Discipline, Start Date, Duration, hours per week, Shift, Employment Type. These are details. Could be included in a "Job Details" paragraph or folded into Schedule/About the Role. I'll create a short paragraph at the beginning with key details: "Specialty: Cath Lab Radiology Technologist; Discipline: Allied Health Professional; Start Date: ASAP; Duration: 13 weeks; 36 hours per week; Shift: 10 hours, days; Employment Type: Travel." That's a paragraph. Job ID: drop. Pay package: include in Pay section. Schedule: include in Schedule section. Now, structure: -

    with job details metadata. -

    About the Role

    -

    Description paragraph. -

    Highlights

    -
    • ...
    -

    Requirements

    -
    • ...
    -

    Pay

    -

    Pay package details. -

    Schedule

    -

    Schedule details (36 hours/week, 10-hour days, 4x10 shifts). -

    About the Company

    -

    Company description. But note: The description already mentions "You will typically work 4x10 hour shifts, providing you with a balanced work-life schedule." That's schedule info. Could be in Schedule section. Also, the "Highlights" includes "Flexible 4x10 shift schedule." That's duplicate. We'll keep both but maybe avoid duplication? The rule says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep both mentions. Now, ensure we don't include boilerplate: The "About Slate Healthcare" is not boilerplate; it's company info. No EEO, legal, etc. Now, write HTML. Let's craft. First, metadata paragraph:

    Specialty: Cath Lab Radiology Technologist; Discipline: Allied Health Professional; Start Date: ASAP; Duration: 13 weeks; 36 hours per week; Shift: 10 hours, days; Employment Type: Travel.

    Then About the Role:

    About the Role

    As a Cath Lab Technologist, you will play a critical role in performing diagnostic and interventional procedures. You will collaborate with a skilled team, ensuring patient safety and comfort. The position requires flexibility and a commitment to high standards in a fast-paced environment. You will typically work 4x10 hour shifts, providing you with a balanced work-life schedule. This role not only offers professional growth but also the opportunity to work with advanced technology in a supportive setting.

    Highlights:

    Highlights

    • Work in a state-of-the-art Cath Lab environment.
    • Flexible 4x10 shift schedule.
    • Collaborative team culture with a focus on patient care.
    Requirements:

    Requirements

    • EMR System: EPIC/Merge
    • 2 years of experience required
    • RCIS or RT or CVT or RN that scrubs certification
    Pay:

    Pay

    Pay package is based on 10 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined.

    Schedule:

    Schedule

    36 hours per week, 10-hour day shifts, typically 4x10 hour shifts.

    About the Company:

    About the Company

    Slate Healthcare is a premier travel healthcare staffing agency, connecting healthcare professionals with thousands of opportunities at top-tier hospitals and facilities across the country. We’re committed to supporting nurses and allied health professionals in building stable, fulfilling careers—while embracing the freedom and excitement that comes with travel. Our goal is simple: to offer flexibility, competitive pay, and personalized placements that align with each clinician’s lifestyle and career goals. At Slate, we empower our professionals to choose when and where they work, while ensuring they receive the highest compensation possible—because we believe that exceptional care starts with empowered caregivers.

    Check for any missing info: The job ID is dropped. The "Slate Healthcare Job ID #5a016373-788d-49a3-8f55-a9c84020ec5b." is minor metadata, dropped. The "Pay package is based on 10 hour shifts

Similar jobs