Jobs · Healthcare · South Carolina

Travel CT Tech - Make $2,532/week - $2,725/week

Aya Healthcare · Murrells Inlet, SC · 5 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, I need to identify the sections. The posting has: - Job details (profession, pay, assignment length, shift, schedule, openings, start date, charting system, experience) - Facility & Unit Information (facility type, bed count) - Aya Delivers section (benefits, support, etc.) Rules: - Use

for section headings (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 - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include section ONLY when posting has real, specific content for it - Never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's map the content to appropriate sections. The job title is "CT Tech in Murrells Inlet, SC" but we shouldn't repeat it as heading. We have: - Pay: $2532 to $2725 weekly (specific) - Schedule: Nights, 4, 10-Hour 20:30 - 07:00 (specific) - Assignment Length: 13 weeks - Shift: Nights - Openings: 1 - Start Date: 11/09/2026 - Charting System: Epic - Experience: 1 Year - Facility Type: Acute Care Hospital - Facility Bed Count: 124 Then there's a long "Aya Delivers" section that describes benefits and support. This includes: - Competitive advantage, front-of-the-line access, expedited licensing, expert career guidance, best-in-class support system - Exceptional benefits: premium medical, dental, vision, life insurance day one - Keep insurance coverage up to 24 days between assignments - Generous 401(k) match - Paid company housing or housing stipend - Paid sick time (with details) - Access to unlimited CEUs online - Licensure, relocation and other reimbursements - Pay includes taxable wages and tax-free expense reimbursements - EEO statement (boilerplate, should remove) We need to decide on sections. The rules suggest headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we only include if there's real content. The posting doesn't have explicit "Responsibilities" or "Requirements" lists. It has experience requirement (1 year) and charting system (Epic). Could be under "Requirements" or "Qualifications". Also facility info could be under "About the role" or "Facility Information". We have specific pay and schedule, so we can include Pay and Schedule sections. Benefits are detailed, so Benefits section. We also have assignment details (length, shift, openings, start date) — could be under "Assignment Details" or "Job Details". The rules mention "Schedule" as a heading, but also "Pay". We can create a "Job Details" section for the metadata. But the rules say: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we can use those headings. We can also create other headings if needed, but prefer those. Let's structure: 1. About the role: Could include profession, facility info, assignment length, shift, schedule, openings, start date, charting system, experience. But that's a lot. Maybe split: "About the role" for overview, "Assignment Details" for length, shift, schedule, openings, start date, "Requirements" for experience and charting system, "Facility Information" for facility type and bed count. But the rules say prefer few substantive sections over many thin ones. So we can combine. Let's see: The posting has "Job Details" and "Facility & Unit Information". We can create two sections: "Job Details" and "Facility Information". But the example headings don't include "Job Details". However, we can use "About the role" for the job details. Alternatively, we can use "Assignment Details" for assignment length, shift, schedule, openings, start date. And "Requirements" for experience and charting system. And "Facility Information" for facility type and bed count. But the rules say: "include a section ONLY when the posting has real, specific content for it". All these have specific content. We also have Pay and Benefits. Let's decide on sections: - About the role: brief prose describing the role (CT Tech, travel assignment, etc.) - Assignment Details: list of assignment length, shift, schedule, openings, start date, charting system - Requirements: experience, charting system (maybe duplicate) - Facility Information: facility type, bed count - Pay: pay range - Schedule: shift and schedule details (but schedule already in assignment details) - Benefits: list of benefits But we must avoid duplication. The schedule is already in assignment details. The rules have "Schedule" as a possible heading. Since the posting has specific schedule (Nights, 4, 10-Hour 20:30 - 07:00), we can include a Schedule section. Similarly, Pay is specific. Benefits are extensive. We also have "Aya Delivers" which is mostly benefits and support. That can be Benefits section. Now, we need to remove boilerplate: "Aya Delivers: The most jobs in the industry...", "Aya is an Equal Employment Opportunity...", "#HP". Also remove "We’ll work with you to build the healthcare career of your dreams...". That's marketing fluff. We need to preserve substantive information. The marketing fluff about Aya's advantages (largest job database, front-of-the-line access, expedited licensing, expert career guidance, best-in-class support) is not directly about the job but about the agency. The user said "Preserve ALL substantive information". But also "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The Aya Delivers section is essentially agency marketing. However, it includes specific benefits (insurance, 401k, housing, sick time, CEUs, reimbursements). Those are benefits for the employee. So we should keep the benefits but maybe not the agency marketing. The benefits listed are: - Exceptional benefits, including premium medical, dental, vision and life insurance beginning day one of your assignment. - Keep insurance coverage for up to 24 Days between assignments. - A generous 401(k) match. - Paid company housing (we’ll help you bring your pets along, too!) or a generous housing stipend, if eligible. - Paid sick time in accordance with all applicable state, federal, and local laws. Aya’s general sick leave policy is that employees accrue one hour of paid sick leave for every 30 hours worked. However, to the extent any provisions of the statement above conflict with any applicable paid sick leave laws, the applicable paid sick leave laws are controlling. - Access to unlimited continuing education units online. - Licensure, relocation and other reimbursements, when applicable. - Pay listed above includes taxable wages and tax-free expense reimbursements. These are specific benefits. We'll include them in Benefits section. The agency marketing (largest job database, front-of-the-line access, expedited licensing, expert career guidance, best-in-class support) is not a benefit per se but could be considered "Support" or "Agency Benefits". However, the rules say "Preserve ALL substantive information". But also "Prefer a few substantive sections over many thin ones." We could include a "Support & Resources" section for those, but they are somewhat fluffy. The user might want them. However, the example headings don't include "Support". The rules say "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we can stick to those. Maybe we can include the agency support under "Benefits" as well, but they are not typical benefits. I think we should include them as they are part of the posting's substantive content. But we need to avoid boilerplate. The EEO statement is boilerplate, remove. Let's structure:

    About the role

    Travel CT Tech position at an acute care hospital in Murrells Inlet, SC. 13-week assignment with night shifts.

    Assignment Details

    • Assignment Length: 13 weeks
    • Shift: Nights
    • Schedule: 4, 10-Hour shifts (20:30 - 07:00)
    • Openings: 1
    • Start Date: 11/09/2026
    • Charting System: Epic

    Requirements

    • Minimum 1 year of experience
    • Proficiency with Epic charting system

    Facility Information

    • Facility Type: Acute Care Hospital
    • Bed Count: 124

    Pay

    $2,532 to $2,725 weekly (includes taxable wages and tax-free expense reimbursements)

    Schedule

    Night shift, four 10-hour shifts per week (20:30 - 07:00)

    Benefits

    • Premium medical, dental, vision, and life insurance starting day one of assignment
    • Option to maintain insurance coverage for up to 24 days between assignments
    • Generous 401(k) match
    • Paid company housing (pet-friendly) or housing stipend, if eligible
    • Paid sick time: accrual of one hour per 30 hours worked, in compliance with applicable laws
    • Unlimited continuing education units (CEUs) online
    • Licensure, relocation, and other reimbursements when applicable
    We also have "Aya Delivers" marketing points. Should we include? They are not benefits but agency features. The user said "Preserve ALL substantive information". But also "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The agency marketing might be considered boilerplate? It's not legal boilerplate, but it's promotional. However, it's part of the job posting. I think we should include them as they are specific to this agency and might be relevant to the candidate. But the rules say "Prefer a few substantive sections over many thin ones." Adding another section for "Agency Support" might be thin. We could incorporate into Benefits or a separate section. But the example headings don't include "Agency Support". We could add a section "Agency Support" but the rules say "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay,

Similar jobs