Travel CT Tech - Make $2,657/week - $2,849/week
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading
- Do NOT put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, application instructions)
- Include section ONLY when real specific content exists
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Output ONLY HTML fragment, no /, no markdown code fences
Now, let's map the content:
The posting has:
- Job Details: Profession, Pay, Assignment Length, Shift, Schedule, Openings, Start Date, Charting System
- Requirements: Experience, Required Certifications & Skills (Skills list, Certifications list)
- Facility & Unit Information: Facility Type, Charting Experience, Facility Level Trauma, Facility Bed Count
- Aya Delivers: This is essentially benefits and company info. It lists many benefits: competitive advantage, expedited licensing, expert career guidance, best-in-class support, 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, pay includes taxable wages and tax-free expense reimbursements.
Also there's EEO statement at end - that's boilerplate to remove.
I need to decide on section headings. The rules suggest headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we should only include sections that have real content.
The posting doesn't have explicit "Responsibilities" or "About the role" sections. It has "Job Details" which includes pay, schedule, etc. It has "Requirements" with experience, skills, certifications. It has "Facility & Unit Information". It has "Aya Delivers" which is benefits.
I should create sections that match the content. Perhaps:
- Job Details (or "About the role"? but the rule says use h3 for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However, we can use other headings if they fit? The rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., so we can use other headings but should follow that pattern. I think we should use the suggested headings where appropriate.
But the posting doesn't have a clear "About the role" prose. It has job details. Could make a "Job Details" heading? The rule says use h3 for section headings (e.g. ...). It doesn't forbid other headings. But to be safe, I'll use the suggested ones where they fit.
Let's see:
- "Requirements" section: we have experience, skills, certifications. That fits "Requirements" heading.
- "Skills" section: the skills list is long, could be a separate "Skills" heading? But the rule says use h3 for section headings e.g. Skills. However, the skills are part of requirements. Could combine under Requirements with sublists. But the rule says use ul li for any list of duties/requirements/benefits. I think we can have a "Requirements" heading with sub-sections for Experience, Skills, Certifications. But the rule says use h3 for section headings. Could use h3 for Requirements, then maybe h4 for subsections? But the rule only mentions h3. It says "use for section headings". It doesn't mention h4. Probably we should keep it flat: each major section is h3. So we could have:
- Requirements (h3) with list items for experience, skills, certifications? But skills is a long list. Could make a "Skills" h3 separate? The posting groups "Required Certifications & Skills" together. Might be better to have "Requirements" h3 and then within it, use ul for experience, then another ul for skills, another for certifications. But the rule says use ul li for any list. That's fine.
- "Facility & Unit Information" could be a section. Not in the example list, but it's substantive. Could call it "Facility Information" or "Facility & Unit Details". The rule says use h3 for section headings e.g. ... but doesn't forbid others. I'll use "Facility Information" as h3.
- "Benefits" section: the Aya Delivers section lists many benefits. That fits "Benefits" heading.
- "Pay" section: the job details include pay range. Could have a "Pay" heading. But the rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states pay: "$2657 to $2849 weekly". So we can include a Pay section. However, the pay is also in Job Details. Could either include in Job Details or separate Pay section. The rule says prefer a few substantive sections over many thin ones. So maybe combine pay into Job Details? But the example headings include Pay and Schedule as separate. The posting has Schedule: "4, 10-Hour 10:30 - 21:00". That's schedule. Could have a "Schedule" section. But again, prefer fewer sections.
Let's decide on sections:
1. Job Details (h3) - includes profession, assignment length, shift, schedule, openings, start date, charting system. Pay could be here or separate. I'll include pay here as it's part of job details.
2. Requirements (h3) - experience, skills, certifications.
3. Facility Information (h3) - facility type, charting experience, trauma level, bed count.
4. Benefits (h3) - all the benefits from Aya Delivers.
That's four substantive sections.
Now, format each.
For Job Details: use
for prose? The details are key-value pairs. Could use a
with - for each detail. The rule says use
- for any list of duties/requirements/benefits. Job details are not duties/requirements/benefits, but they are a list of details. Could use
or . I think
is fine for a list of details. But the rule says "use - for any list of duties/requirements/benefits, and
for prose." Job details are not prose, they are a list. I'll use
.
For Requirements: Experience is a single line, could be a or
- . Skills is a long list, use
. Certifications is a list of two items, use . Could structure as:
Requirements
Experience: 1 Year
Skills
but no h4 allowed. So maybe just use for skills and certifications under Requirements heading. Could do:
Requirements
- Experience: 1 Year
- Skills: ...
but skills are many. Better to have a nested list? But HTML fragment only, we can do nested ul. That's allowed. Let's do:
Requirements
- Experience: 1 Year
- Skills:
- 3D rendering (Maximum intensity projection, Surface shaded displays, Volume rendering)
... etc
- Certifications:
- ARRT R
- BLS
But the rule says use - for any list. Nested ul is okay.
For Facility Information: similar, a list of details.
For Benefits: list of benefits.
Now, remove boilerplate: "Aya Healthcare has an immediate opening for the following position: CT Tech in Brownwood, TX. 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." This is marketing fluff, but it's about the role. Could be considered "About the role" prose. The rule says do NOT repeat the job title as a heading (the page already shows it). But this is a paragraph describing the role. Could include as a
under a "About the role" heading? The rule says include a section ONLY when the posting has real, specific content for it. This is generic marketing. Might be considered boilerplate. The rule says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those, but it's generic recruiter talk. I'd lean to remove it because it's not substantive job detail. The user said "Preserve ALL substantive information". This is not substantive. So I'll drop it.
Also remove "Aya Delivers: The most jobs in the industry... competitive advantage..." that's marketing but also includes benefits. The benefits are substantive. I'll extract the benefits list and discard the marketing fluff.
Also remove EEO statement at end.
Now, write HTML.
Let's craft.
First, Job Details section:
Job Details
- Profession: Radiology / Cardiology
- Pay: $2,657 to $2,849 weekly
- Assignment Length: 13 weeks
- Shift: Days
- Schedule: 4, 10-Hour shifts (10:30 - 21:00)
- Openings: 1
- Start Date: 11/16/2026
- Charting System: Altera
Note: Pay format: "$2657 to $2849 weekly" I'll keep as is but add commas for readability? The original has no commas. I'll keep as original: "$2657 to $2849 weekly". But it's fine.
Second, Requirements:
Requirements
- Experience: 1 Year
- Skills:
- 3D rendering (Maximum intensity projection, Surface shaded displays, Volume rendering)
- Abdomen without and/or with contrast
- Adult Acute Care
- Carotid
- Cervical
- Chest without and/or with contrast
- Emergency Department
- Head without and/or with contrast
- Isolation Precautions/PPE
- Level II Trauma Center
for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, application instructions) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no /, no markdown code fences Now, let's map the content: The posting has: - Job Details: Profession, Pay, Assignment Length, Shift, Schedule, Openings, Start Date, Charting System - Requirements: Experience, Required Certifications & Skills (Skills list, Certifications list) - Facility & Unit Information: Facility Type, Charting Experience, Facility Level Trauma, Facility Bed Count - Aya Delivers: This is essentially benefits and company info. It lists many benefits: competitive advantage, expedited licensing, expert career guidance, best-in-class support, 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, pay includes taxable wages and tax-free expense reimbursements. Also there's EEO statement at end - that's boilerplate to remove. I need to decide on section headings. The rules suggest headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we should only include sections that have real content. The posting doesn't have explicit "Responsibilities" or "About the role" sections. It has "Job Details" which includes pay, schedule, etc. It has "Requirements" with experience, skills, certifications. It has "Facility & Unit Information". It has "Aya Delivers" which is benefits. I should create sections that match the content. Perhaps: - Job Details (or "About the role"? but the rule says use h3 for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However, we can use other headings if they fit? The rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., so we can use other headings but should follow that pattern. I think we should use the suggested headings where appropriate.
But the posting doesn't have a clear "About the role" prose. It has job details. Could make a "Job Details" heading? The rule says use h3 for section headings (e.g. ...). It doesn't forbid other headings. But to be safe, I'll use the suggested ones where they fit.
Let's see:
- "Requirements" section: we have experience, skills, certifications. That fits "Requirements" heading.
- "Skills" section: the skills list is long, could be a separate "Skills" heading? But the rule says use h3 for section headings e.g. Skills. However, the skills are part of requirements. Could combine under Requirements with sublists. But the rule says use ul li for any list of duties/requirements/benefits. I think we can have a "Requirements" heading with sub-sections for Experience, Skills, Certifications. But the rule says use h3 for section headings. Could use h3 for Requirements, then maybe h4 for subsections? But the rule only mentions h3. It says "use for section headings". It doesn't mention h4. Probably we should keep it flat: each major section is h3. So we could have:
- Requirements (h3) with list items for experience, skills, certifications? But skills is a long list. Could make a "Skills" h3 separate? The posting groups "Required Certifications & Skills" together. Might be better to have "Requirements" h3 and then within it, use ul for experience, then another ul for skills, another for certifications. But the rule says use ul li for any list. That's fine.
- "Facility & Unit Information" could be a section. Not in the example list, but it's substantive. Could call it "Facility Information" or "Facility & Unit Details". The rule says use h3 for section headings e.g. ... but doesn't forbid others. I'll use "Facility Information" as h3.
- "Benefits" section: the Aya Delivers section lists many benefits. That fits "Benefits" heading.
- "Pay" section: the job details include pay range. Could have a "Pay" heading. But the rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states pay: "$2657 to $2849 weekly". So we can include a Pay section. However, the pay is also in Job Details. Could either include in Job Details or separate Pay section. The rule says prefer a few substantive sections over many thin ones. So maybe combine pay into Job Details? But the example headings include Pay and Schedule as separate. The posting has Schedule: "4, 10-Hour 10:30 - 21:00". That's schedule. Could have a "Schedule" section. But again, prefer fewer sections.
Let's decide on sections:
1. Job Details (h3) - includes profession, assignment length, shift, schedule, openings, start date, charting system. Pay could be here or separate. I'll include pay here as it's part of job details.
2. Requirements (h3) - experience, skills, certifications.
3. Facility Information (h3) - facility type, charting experience, trauma level, bed count.
4. Benefits (h3) - all the benefits from Aya Delivers.
That's four substantive sections.
Now, format each.
For Job Details: use
for prose? The details are key-value pairs. Could use a
- with
- for each detail. The rule says use
- for any list of duties/requirements/benefits. Job details are not duties/requirements/benefits, but they are a list of details. Could use
- or
- for any list of duties/requirements/benefits, and
for prose." Job details are not prose, they are a list. I'll use
- .
For Requirements: Experience is a single line, could be a
- . Skills is a long list, use
- . Certifications is a list of two items, use
- Experience: 1 Year
- Skills: ... but skills are many. Better to have a nested list? But HTML fragment only, we can do nested ul. That's allowed. Let's do:
- Experience: 1 Year
- Skills:
- 3D rendering (Maximum intensity projection, Surface shaded displays, Volume rendering) ... etc
- Certifications:
- ARRT R
- BLS
- for any list. Nested ul is okay.
For Facility Information: similar, a list of details.
For Benefits: list of benefits.
Now, remove boilerplate: "Aya Healthcare has an immediate opening for the following position: CT Tech in Brownwood, TX. 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." This is marketing fluff, but it's about the role. Could be considered "About the role" prose. The rule says do NOT repeat the job title as a heading (the page already shows it). But this is a paragraph describing the role. Could include as a
under a "About the role" heading? The rule says include a section ONLY when the posting has real, specific content for it. This is generic marketing. Might be considered boilerplate. The rule says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those, but it's generic recruiter talk. I'd lean to remove it because it's not substantive job detail. The user said "Preserve ALL substantive information". This is not substantive. So I'll drop it. Also remove "Aya Delivers: The most jobs in the industry... competitive advantage..." that's marketing but also includes benefits. The benefits are substantive. I'll extract the benefits list and discard the marketing fluff. Also remove EEO statement at end. Now, write HTML. Let's craft. First, Job Details section:
Job Details
- Profession: Radiology / Cardiology
- Pay: $2,657 to $2,849 weekly
- Assignment Length: 13 weeks
- Shift: Days
- Schedule: 4, 10-Hour shifts (10:30 - 21:00)
- Openings: 1
- Start Date: 11/16/2026
- Charting System: Altera
Requirements
- Experience: 1 Year
- Skills:
- 3D rendering (Maximum intensity projection, Surface shaded displays, Volume rendering)
- Abdomen without and/or with contrast
- Adult Acute Care
- Carotid
- Cervical
- Chest without and/or with contrast
- Emergency Department
- Head without and/or with contrast
- Isolation Precautions/PPE
- Level II Trauma Center
- . Could structure as:
Requirements
Experience: 1 Year
Skills
but no h4 allowed. So maybe just use- for skills and certifications under Requirements heading. Could do:
Requirements
Requirements
or
- . Skills is a long list, use
. I think
- is fine for a list of details. But the rule says "use
- for any list of duties/requirements/benefits, and
- for any list of duties/requirements/benefits. Job details are not duties/requirements/benefits, but they are a list of details. Could use