Travel CT Tech - Make $2,549/week - $2,742/week
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for lists,
for prose. Do NOT repeat job title. Do NOT put Job ID/requisition numbers as headings. Fold minor metadata into short
or drop it. Preserve ALL substantive information. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, 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, the posting includes:
- Pay: $2549 to $2742 weekly (specific)
- Schedule: 3, 12-Hour 06:00 - 18:30 (specific)
- Benefits: listed under "Aya Delivers" and "Exceptional benefits, including premium medical, dental, vision and life insurance beginning day one of your assignment. Want to take time off? 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."
Also, there is "Experience: 1 Year" and "Charting System: Allscripts". Facility details.
The posting also includes marketing fluff: "Aya Delivers: The most jobs in the industry... Competitive advantage... Expedited licensing... Expert career guidance... A best-in-class support system..." This is promotional but still part of the posting. Should I include it? The rule says preserve ALL substantive information. But also remove boilerplate. The "Aya Delivers" section seems like company marketing, but it's part of the job posting. However, the rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The EEO statement at the end: "Aya is an Equal Employment Opportunity ("EEO") Employer and welcomes all to apply." That's EEO boilerplate, should be removed.
The "Aya Delivers" section is not exactly boilerplate; it's describing the company's offerings. But it's not specific to the role; it's generic company benefits. However, the benefits listed (medical, dental, vision, life insurance, 401k match, housing, sick time, CEUs, reimbursements) are specific benefits for the traveler. Those are substantive benefits. The marketing fluff about "most jobs in the industry", "front-of-the-line access", "expedited licensing", "expert career guidance", "best-in-class support system" might be considered promotional but still part of the posting. The rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should include the benefits details.
But also: "Prefer a few substantive sections over many thin ones." So I should group related info.
Let's structure:
Possible sections:
- Job Details (could be a section with list)
- Facility Information
- Benefits (since there are specific benefits)
- Pay (specific pay range)
- Schedule (specific schedule)
But the rule says: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So I can create headings for Pay, Schedule, Benefits, etc. But only if the posting actually states them. It does state Pay, Schedule, Benefits.
Also, there is "Experience: 1 Year" - that could be under Requirements or Qualifications.
The posting doesn't have explicit "Responsibilities" or "Requirements" sections. It has "Experience: 1 Year" and "Charting System: Allscripts". That could be under Qualifications.
I need to decide on sections. The rule: "include a section ONLY when the posting has real, specific content for it". So I'll create sections for:
- Job Details (maybe "Assignment Details" or "Job Details")
- Facility Information
- Qualifications (experience, charting system)
- Pay
- Schedule
- Benefits
But "Job Details" includes many metadata fields. Could be a list under a heading "Job Details". However, the rule says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." The job details include Profession, Pay, Assignment Length, Shift, Schedule, Openings, Start Date, Charting System, Experience. Some of these are minor metadata. But Pay and Schedule are significant enough to have their own sections. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. So I should create separate sections for Pay, Schedule, Benefits. The rest (Profession, Assignment Length, Shift, Openings, Start Date, Charting System, Experience) could be folded into a "Job Details" section or a "Assignment Details" section.
But the rule also says "Prefer a few substantive sections over many thin ones." So maybe combine some.
Let's think: The posting is for a travel CT Tech position. The key info: pay, schedule, assignment length, shift, start date, facility info, experience required, charting system, benefits.
I'll create:
-
Assignment Details
with a list of: Profession, Assignment Length, Shift, Start Date, Openings, Charting System, Experience.
- Facility Information
with list.
- Pay
with the pay range.
- Schedule
with schedule details.
- Benefits
with list of benefits.
But note: "Shift: Days" and "Schedule: 3, 12-Hour 06:00 - 18:30" are related. Could combine under Schedule.
Also, "Experience: 1 Year" could be under Qualifications.
I'll create a "Qualifications" section for experience and charting system.
Now, the "Aya Delivers" marketing fluff: Should I include? The rule says remove boilerplate. The marketing fluff is not exactly boilerplate; it's company description. But it's not specific to the job. However, the benefits are listed there. I'll extract the benefits and put them in Benefits section. The marketing fluff like "The most jobs in the industry... Front-of-the-line access... Expedited licensing... Expert career guidance... A best-in-class support system..." could be considered promotional and not substantive for the role. The rule says "Preserve ALL substantive information". Is that substantive? It's about the agency's services, not the job itself. But the job posting includes it. The user might want it. However, the instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This marketing fluff is not exactly those categories. But it's not "substantive information" about the role. I think it's safe to omit the marketing fluff and keep only the concrete benefits.
Also, the EEO statement at the end should be removed.
The line "Pay listed above includes taxable wages and tax-free expense reimbursements." That's a note about pay, include in Pay section.
Now, let's write HTML.
I'll start with Assignment Details:
Assignment Details
- Profession: Radiology / Cardiology
- Assignment Length: 13 weeks
- Shift: Days
- Start Date: 10/05/2026
- Openings: 1
- Charting System: Allscripts
- Experience: 1 Year
Facility Information:
Facility Information
- Facility Type: Acute Care Hospital
- Facility Level Trauma: Level 3
- Facility Bed Count: 192
Pay:
Pay
$2,549 to $2,742 weekly (includes taxable wages and tax-free expense reimbursements)
Schedule:
Schedule
3, 12-Hour shifts, 06:00 - 18:30
Benefits:
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 state, federal, and local laws (accrual: 1 hour per 30 hours worked)
- Access to unlimited continuing education units online
- Licensure, relocation, and other reimbursements when applicable
Qualifications? The experience and charting system are already in Assignment Details. Could create a separate Qualifications section, but that might be thin. The rule says prefer few substantive sections. I'll keep them in Assignment Details.
But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't require all. I'll include only those with content.
Now, check for any other content: The posting starts with "Aya Healthcare has an immediate opening for the following position: CT Tech in Wheeling, WV. We’ll work with you to build the healthcare career of your dreams. Whether you want a job close to home or across the country, we’ve got you." That's introductory prose. Could be a
at the top? But the rule says do NOT repeat the job title as a heading. The page already shows it. But this is a description. Could include as a
before sections. However, the rule says "Output ONLY the HTML fragment". It doesn't forbid a leading paragraph. But the example headings are for sections. I think it's okay to include a brief intro paragraph.
But the rule: "Do NOT repeat the job title as a heading (the page already shows it)". The intro mentions the title. That's fine.
I'll include a
for prose. Do NOT repeat job title. Do NOT put Job ID/requisition numbers as headings. Fold minor metadata into short
or drop it. Preserve ALL substantive information. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, 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, the posting includes: - Pay: $2549 to $2742 weekly (specific) - Schedule: 3, 12-Hour 06:00 - 18:30 (specific) - Benefits: listed under "Aya Delivers" and "Exceptional benefits, including premium medical, dental, vision and life insurance beginning day one of your assignment. Want to take time off? 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." Also, there is "Experience: 1 Year" and "Charting System: Allscripts". Facility details. The posting also includes marketing fluff: "Aya Delivers: The most jobs in the industry... Competitive advantage... Expedited licensing... Expert career guidance... A best-in-class support system..." This is promotional but still part of the posting. Should I include it? The rule says preserve ALL substantive information. But also remove boilerplate. The "Aya Delivers" section seems like company marketing, but it's part of the job posting. However, the rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The EEO statement at the end: "Aya is an Equal Employment Opportunity ("EEO") Employer and welcomes all to apply." That's EEO boilerplate, should be removed. The "Aya Delivers" section is not exactly boilerplate; it's describing the company's offerings. But it's not specific to the role; it's generic company benefits. However, the benefits listed (medical, dental, vision, life insurance, 401k match, housing, sick time, CEUs, reimbursements) are specific benefits for the traveler. Those are substantive benefits. The marketing fluff about "most jobs in the industry", "front-of-the-line access", "expedited licensing", "expert career guidance", "best-in-class support system" might be considered promotional but still part of the posting. The rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should include the benefits details. But also: "Prefer a few substantive sections over many thin ones." So I should group related info. Let's structure: Possible sections: - Job Details (could be a section with list) - Facility Information - Benefits (since there are specific benefits) - Pay (specific pay range) - Schedule (specific schedule) But the rule says: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So I can create headings for Pay, Schedule, Benefits, etc. But only if the posting actually states them. It does state Pay, Schedule, Benefits. Also, there is "Experience: 1 Year" - that could be under Requirements or Qualifications. The posting doesn't have explicit "Responsibilities" or "Requirements" sections. It has "Experience: 1 Year" and "Charting System: Allscripts". That could be under Qualifications. I need to decide on sections. The rule: "include a section ONLY when the posting has real, specific content for it". So I'll create sections for: - Job Details (maybe "Assignment Details" or "Job Details") - Facility Information - Qualifications (experience, charting system) - Pay - Schedule - Benefits But "Job Details" includes many metadata fields. Could be a list under a heading "Job Details". However, the rule says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." The job details include Profession, Pay, Assignment Length, Shift, Schedule, Openings, Start Date, Charting System, Experience. Some of these are minor metadata. But Pay and Schedule are significant enough to have their own sections. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. So I should create separate sections for Pay, Schedule, Benefits. The rest (Profession, Assignment Length, Shift, Openings, Start Date, Charting System, Experience) could be folded into a "Job Details" section or a "Assignment Details" section. But the rule also says "Prefer a few substantive sections over many thin ones." So maybe combine some. Let's think: The posting is for a travel CT Tech position. The key info: pay, schedule, assignment length, shift, start date, facility info, experience required, charting system, benefits. I'll create: -
Assignment Details
with a list of: Profession, Assignment Length, Shift, Start Date, Openings, Charting System, Experience. -Facility Information
with list. -Pay
with the pay range. -Schedule
with schedule details. -Benefits
with list of benefits. But note: "Shift: Days" and "Schedule: 3, 12-Hour 06:00 - 18:30" are related. Could combine under Schedule. Also, "Experience: 1 Year" could be under Qualifications. I'll create a "Qualifications" section for experience and charting system. Now, the "Aya Delivers" marketing fluff: Should I include? The rule says remove boilerplate. The marketing fluff is not exactly boilerplate; it's company description. But it's not specific to the job. However, the benefits are listed there. I'll extract the benefits and put them in Benefits section. The marketing fluff like "The most jobs in the industry... Front-of-the-line access... Expedited licensing... Expert career guidance... A best-in-class support system..." could be considered promotional and not substantive for the role. The rule says "Preserve ALL substantive information". Is that substantive? It's about the agency's services, not the job itself. But the job posting includes it. The user might want it. However, the instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This marketing fluff is not exactly those categories. But it's not "substantive information" about the role. I think it's safe to omit the marketing fluff and keep only the concrete benefits. Also, the EEO statement at the end should be removed. The line "Pay listed above includes taxable wages and tax-free expense reimbursements." That's a note about pay, include in Pay section. Now, let's write HTML. I'll start with Assignment Details:Assignment Details
- Profession: Radiology / Cardiology
- Assignment Length: 13 weeks
- Shift: Days
- Start Date: 10/05/2026
- Openings: 1
- Charting System: Allscripts
- Experience: 1 Year
Facility Information
- Facility Type: Acute Care Hospital
- Facility Level Trauma: Level 3
- Facility Bed Count: 192
Pay
$2,549 to $2,742 weekly (includes taxable wages and tax-free expense reimbursements)
Schedule:Schedule
3, 12-Hour shifts, 06:00 - 18:30
Benefits: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 state, federal, and local laws (accrual: 1 hour per 30 hours worked)
- Access to unlimited continuing education units online
- Licensure, relocation, and other reimbursements when applicable
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't require all. I'll include only those with content. Now, check for any other content: The posting starts with "Aya Healthcare has an immediate opening for the following position: CT Tech in Wheeling, WV. We’ll work with you to build the healthcare career of your dreams. Whether you want a job close to home or across the country, we’ve got you." That's introductory prose. Could be a
at the top? But the rule says do NOT repeat the job title as a heading. The page already shows it. But this is a description. Could include as a
before sections. However, the rule says "Output ONLY the HTML fragment". It doesn't forbid a leading paragraph. But the example headings are for sections. I think it's okay to include a brief intro paragraph. But the rule: "Do NOT repeat the job title as a heading (the page already shows it)". The intro mentions the title. That's fine. I'll include a