Travel CT Tech - Make $3,370/week - $3,563/week
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 sections.
The job title is "CT Tech in Turnersville, NJ" - but we don't repeat it as heading.
We have Pay information: "$3370 to $3563 weekly" - that's specific, so we can have a Pay section.
Schedule: "Days", "4, 12-Hour 07:00 - 19:30" - specific, so Schedule section.
Assignment Length: "13 weeks" - could be part of Job Details or Schedule.
Start Date: "11/30/2026" - specific.
Charting System: "Epic" - could be part of Requirements or Facility.
Requirements: Experience: 1 Year, Required Certifications & Skills (Skills list, Certifications list). This is a Requirements section.
Facility & Unit Information: Facility Type: Acute Care Hospital, Facility Bed Count: 202 - could be a Facility section.
Aya Delivers: This is benefits and support information. It includes:
- Competitive advantage, front-of-the-line access, expedited licensing, expert career guidance, best-in-class support system, exceptional benefits (medical, dental, vision, life insurance day one, keep insurance up to 24 days between assignments), 401(k) match, paid company housing or housing stipend, paid sick time, unlimited CEUs, licensure/relocation reimbursements.
- Also note: "Pay listed above includes taxable wages and tax-free expense reimbursements." That's pay detail.
We need to decide which sections to include. The rules say: include a section ONLY when the posting has real, specific content for it. So we can have:
- Pay (since specific pay range)
- Schedule (specific shift and hours)
- Requirements (experience, skills, certifications)
- Facility (type, bed count)
- Benefits (the Aya Delivers section has many specific benefits)
But note: "Aya Delivers" is a mix of company selling points and benefits. The benefits are specific: medical, dental, vision, life insurance day one, keep insurance 24 days between assignments, 401(k) match, paid housing or stipend, paid sick time, unlimited CEUs, licensure/relocation reimbursements. That's substantive.
Also, there is "Assignment Length: 13 weeks" and "Start Date: 11/30/2026" - could be part of a "Job Details" section or "Schedule". The rules mention headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". We don't have "Responsibilities" explicitly, but we have skills which are like duties? The skills listed are technical skills (Abdomen without and/or with contrast, etc.) - those are more like qualifications/skills.
We could have a "Qualifications" or "Skills" section. The posting says "Required Certifications & Skills" with two sublists: Skills and Certifications. That fits "Requirements" or "Qualifications". The rules mention "Requirements" and "Qualifications" as possible headings. I'll use "Requirements" for the experience, skills, certifications.
We also have "Charting System: Epic" - could be part of Requirements or Facility.
Let's structure:
Pay
$3,370 to $3,563 weekly (includes taxable wages and tax-free expense reimbursements)
Schedule
- Shift: Days
- Schedule: 4, 12-hour shifts (07:00–19:30)
- Assignment length: 13 weeks
- Start date: 11/30/2026
Requirements
- Experience: 1 year
- Skills: Abdomen without and/or with contrast, Adult Acute Care, Emergency Department, GE, ICU, Adult Outpatient, Enterography study, PACS, Pelvis without and/or with contrast
- Certifications: BLS, ARRT (R)
Facility
- Type: Acute Care Hospital
- Bed count: 202
- Charting system: Epic
Benefits
- Premium medical, dental, vision, and life insurance beginning day one of assignment
- Option to keep insurance coverage for up to 24 days between assignments
- Generous 401(k) match
- Paid company housing (pet-friendly) or generous housing stipend (if eligible)
- Paid sick time in accordance with applicable laws (accrue one hour per 30 hours worked)
- Unlimited continuing education units (CEUs) online
- Licensure, relocation, and other reimbursements when applicable
Also, there is "Aya Delivers" which includes other points like "Competitive advantage...", "Expedited licensing...", "Expert career guidance...", "Best-in-class support system...". These are more about the agency's services, not direct benefits to the employee? They are part of the value proposition. The rules say preserve ALL substantive information. But we should avoid boilerplate. The "Aya Delivers" section is marketing but includes specific benefits. I've captured the benefits. The other points (largest job database, front-of-the-line access, expedited licensing, dedicated recruiter, 24/7 support) are also substantive about the agency's offering. Should we include them? They are not typical "Benefits" but could be "Support" or "Agency Benefits". The rules say "Prefer a few substantive sections over many thin ones." We could add a "Support & Services" section or include in Benefits. But the rules mention "Benefits" as a heading. The posting says "Aya Delivers: ... Exceptional benefits, including ..." So the benefits are listed. The other points are more about the recruitment process. I think we can include them as a separate section "Agency Support" or fold into Benefits. However, the rules say never create a section unless real specific content. The agency support points are specific: largest job database, direct facility relationships, quick offers, expedited licensing, dedicated recruiter, 24/7 support, weekly pay. That's substantive. But the user might consider that as part of the company description, not the job posting per se. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "Aya Delivers" is not boilerplate; it's part of the job posting. However, it's more about the staffing agency. The job is for a CT Tech at a facility, but the employer is Aya Healthcare (staffing agency). So the benefits and support are from Aya. I think we should include them.
But we must not create too many thin sections. Let's see: we have Pay, Schedule, Requirements, Facility, Benefits. That's five sections. Could add "Agency Support" but maybe combine with Benefits? The benefits list already includes many items. The other points are not benefits per se but services. I'll create a separate section "Agency Support" or "Additional Support". However, the rules say "include a section ONLY when the posting has real, specific content for it". The posting has specific content for agency support. But the suggested headings are "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "Agency Support" is not in that list, but we can use other headings if appropriate. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." means examples, not exhaustive. So we can use other headings.
But to keep it simple, maybe we can include the agency support points in a "Benefits" section? They are not benefits but support. Alternatively, we can create a "Why Aya Healthcare" section. However, the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must include those points. Let's include them as a separate section "Agency Support & Services".
But the user might expect only the standard sections. Let's examine the example headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". The posting doesn't have "About the role" or "Responsibilities". It has "Job Details" which includes pay, schedule, assignment length, etc. We've split Pay and Schedule. We have Requirements. We have Facility. We have Benefits. The agency support could be "About the Company" but not required.
I think we should include the agency support points because they are part of the posting and substantive. But we must not create a heading with filler. The content is specific. So I'll add a section "Agency Support" with a list.
Let's draft:
Agency Support
- Largest healthcare staffing job database with real-time updates
- Direct facility relationships for front-of-the-line access and quick offers
- Expedited licensing and streamlined compliance across all 50 states
- Dedicated recruiter for career guidance (travel, per diem, permanent)
- 24/7 support team and accurate weekly pay
That seems good.
Now, also note: "Openings: 1" - minor metadata, can be dropped or folded into a short
. The rules: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Openings is minor metadata. We can drop it.
"Profession: Radiology / Cardiology" - that's the job category, but the title is CT Tech. Could be part of a short intro paragraph? The rules say do NOT repeat the job title as a heading. We could have a short
at the beginning describing the role. But the instruction: "Output ONLY the HTML fragment". We can start with sections. Maybe we can have an "About the Role" section with a brief description. The posting says "Aya Healthcare has an immediate opening for
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 sections. The job title is "CT Tech in Turnersville, NJ" - but we don't repeat it as heading. We have Pay information: "$3370 to $3563 weekly" - that's specific, so we can have a Pay section. Schedule: "Days", "4, 12-Hour 07:00 - 19:30" - specific, so Schedule section. Assignment Length: "13 weeks" - could be part of Job Details or Schedule. Start Date: "11/30/2026" - specific. Charting System: "Epic" - could be part of Requirements or Facility. Requirements: Experience: 1 Year, Required Certifications & Skills (Skills list, Certifications list). This is a Requirements section. Facility & Unit Information: Facility Type: Acute Care Hospital, Facility Bed Count: 202 - could be a Facility section. Aya Delivers: This is benefits and support information. It includes: - Competitive advantage, front-of-the-line access, expedited licensing, expert career guidance, best-in-class support system, exceptional benefits (medical, dental, vision, life insurance day one, keep insurance up to 24 days between assignments), 401(k) match, paid company housing or housing stipend, paid sick time, unlimited CEUs, licensure/relocation reimbursements. - Also note: "Pay listed above includes taxable wages and tax-free expense reimbursements." That's pay detail. We need to decide which sections to include. The rules say: include a section ONLY when the posting has real, specific content for it. So we can have: - Pay (since specific pay range) - Schedule (specific shift and hours) - Requirements (experience, skills, certifications) - Facility (type, bed count) - Benefits (the Aya Delivers section has many specific benefits) But note: "Aya Delivers" is a mix of company selling points and benefits. The benefits are specific: medical, dental, vision, life insurance day one, keep insurance 24 days between assignments, 401(k) match, paid housing or stipend, paid sick time, unlimited CEUs, licensure/relocation reimbursements. That's substantive. Also, there is "Assignment Length: 13 weeks" and "Start Date: 11/30/2026" - could be part of a "Job Details" section or "Schedule". The rules mention headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". We don't have "Responsibilities" explicitly, but we have skills which are like duties? The skills listed are technical skills (Abdomen without and/or with contrast, etc.) - those are more like qualifications/skills. We could have a "Qualifications" or "Skills" section. The posting says "Required Certifications & Skills" with two sublists: Skills and Certifications. That fits "Requirements" or "Qualifications". The rules mention "Requirements" and "Qualifications" as possible headings. I'll use "Requirements" for the experience, skills, certifications. We also have "Charting System: Epic" - could be part of Requirements or Facility. Let's structure:
Pay
$3,370 to $3,563 weekly (includes taxable wages and tax-free expense reimbursements)
Schedule
- Shift: Days
- Schedule: 4, 12-hour shifts (07:00–19:30)
- Assignment length: 13 weeks
- Start date: 11/30/2026
Requirements
- Experience: 1 year
- Skills: Abdomen without and/or with contrast, Adult Acute Care, Emergency Department, GE, ICU, Adult Outpatient, Enterography study, PACS, Pelvis without and/or with contrast
- Certifications: BLS, ARRT (R)
Facility
- Type: Acute Care Hospital
- Bed count: 202
- Charting system: Epic
Benefits
- Premium medical, dental, vision, and life insurance beginning day one of assignment
- Option to keep insurance coverage for up to 24 days between assignments
- Generous 401(k) match
- Paid company housing (pet-friendly) or generous housing stipend (if eligible)
- Paid sick time in accordance with applicable laws (accrue one hour per 30 hours worked)
- Unlimited continuing education units (CEUs) online
- Licensure, relocation, and other reimbursements when applicable
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." means examples, not exhaustive. So we can use other headings.
But to keep it simple, maybe we can include the agency support points in a "Benefits" section? They are not benefits but support. Alternatively, we can create a "Why Aya Healthcare" section. However, the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must include those points. Let's include them as a separate section "Agency Support & Services".
But the user might expect only the standard sections. Let's examine the example headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". The posting doesn't have "About the role" or "Responsibilities". It has "Job Details" which includes pay, schedule, assignment length, etc. We've split Pay and Schedule. We have Requirements. We have Facility. We have Benefits. The agency support could be "About the Company" but not required.
I think we should include the agency support points because they are part of the posting and substantive. But we must not create a heading with filler. The content is specific. So I'll add a section "Agency Support" with a list.
Let's draft:
Agency Support
- Largest healthcare staffing job database with real-time updates
- Direct facility relationships for front-of-the-line access and quick offers
- Expedited licensing and streamlined compliance across all 50 states
- Dedicated recruiter for career guidance (travel, per diem, permanent)
- 24/7 support team and accurate weekly pay
That seems good.
Now, also note: "Openings: 1" - minor metadata, can be dropped or folded into a short
. The rules: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Openings is minor metadata. We can drop it. "Profession: Radiology / Cardiology" - that's the job category, but the title is CT Tech. Could be part of a short intro paragraph? The rules say do NOT repeat the job title as a heading. We could have a short
at the beginning describing the role. But the instruction: "Output ONLY the HTML fragment". We can start with sections. Maybe we can have an "About the Role" section with a brief description. The posting says "Aya Healthcare has an immediate opening for