Travel X-Ray Technician - $2,370 per 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 — fold minor metadata into a 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")
- 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
Let me map the content to appropriate sections:
- "About the role" could cover the job description and details
- "Responsibilities" - there's a list
- "Requirements" or "Qualifications" - required experience and certifications
- "Schedule" - there are specific schedule details (13 hours per day, 39 hours per week, rotating 7-week schedule 6 PM to 7 AM, no call required)
- "Benefits" - the company mentions "Medical Benefits Company-matched 401K" and other benefits in the About ARMStaffing section
- "Pay" - mentions pay package based on 12 hour shifts and 36 hours per week, tax-free stipend amount to be determined. This is somewhat specific but the stipend is TBD. The rule says never create Pay section unless posting actually states them. It does state a pay package structure but the amount is TBD. I think we can include a Pay section with the details given.
- "About ARMStaffing" - company info, but this might be considered boilerplate? The user said remove boilerplate but "About ARMStaffing" seems like company description. However, the rule says "include a section ONLY when the posting has real, specific content for it". The company description is fairly detailed. But the user also said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Company description might be considered boilerplate? But it's specific to this employer. I'll include it as a section maybe "About the Company" or similar.
But the headings should be from the suggested list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the Company" is not in that list. However, the rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests these are examples, not exhaustive. But we should stick to those if possible. The company info could be folded into a short
or dropped. The user said "fold minor metadata into a short
or drop it." The company description is not minor metadata; it's a substantial paragraph. But it's not directly about the job. I think we can include it as a section "About ARMStaffing" but the heading should be
. The example headings include "About the role". Could use "About the Company". I'll include it.
Now, let's structure:
- Job details metadata: Start Date, Duration, Hours per week, Shift, Employment Type, Location, Assignment Duration, Schedule/Shift details. These can be in a short
under "About the role" or a separate "Schedule" section. The schedule details are specific: "13 hours per day, 39 hours per week, on a rotating 7-week schedule from 6 PM to 7 AM. No call required." That's good for a Schedule section.
- Job Description: prose.
- Responsibilities: list.
- Required Experience: prose.
- Certifications/Licensure: prose.
- Pay: "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This is specific about the basis but amount TBD. I'll include a Pay section with that info.
- Benefits: "Medical Benefits Company-matched 401K" and other benefits listed in the second About ARMStaffing paragraph: "Long-term and temporary career options with outstanding employee benefits Medical Benefits Company-matched 401K". Also earlier: "outstanding employee benefits". Could create a Benefits section.
- About ARMStaffing: company description. I'll include as a section.
But we must avoid thin sections. Let's see.
I'll create sections:
1. About the role (includes job description and key details)
2. Responsibilities
3. Requirements (combining Required Experience and Certifications/Licensure)
4. Schedule
5. Pay
6. Benefits
7. About ARMStaffing
But the rule: "Prefer a few substantive sections over many thin ones." So maybe combine some.
Let's examine each:
- About the role: can include the job description prose and the quick look details (location, duration, schedule summary). But schedule has its own details, so maybe separate Schedule section.
- Responsibilities: list, substantive.
- Requirements: two prose paragraphs (Required Experience and Certifications/Licensure). Could be combined under "Requirements" or "Qualifications". Use "Requirements" as heading.
- Schedule: specific details, good for a section.
- Pay: specific basis, though amount TBD. Still substantive.
- Benefits: listed benefits, substantive.
- About ARMStaffing: company info, substantive.
That's 7 sections. Might be okay.
But note: the job posting has two "About ARMStaffing" sections. The first is a paragraph, the second is a longer description with services and benefits. I'll combine them.
Also, the Job ID #38491258 should be folded into a short
or dropped. I'll drop it as it's minor metadata.
The posted job title "Radiology:X-Ray,19:00:00-07:00:00" is essentially the shift, already covered.
Now, write HTML.
I'll start with
About the role
then a with job description and key details.
But the job description is: "The position requires a committed professional to provide high-quality care in a fast-paced environment. Candidates should be adaptable and patient-focused, ensuring exceptional service delivery to all patients."
Then details: Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type, Location, Assignment Duration. I'll include those in a paragraph or maybe a list? The rule says use
- for any list of duties/requirements/benefits. These are not duties/requirements/benefits; they are job metadata. Could be a
with line breaks or a list. I think a
with sentences is fine.
But the schedule details are more specific: "13 hours per day, 39 hours per week, on a rotating 7-week schedule from 6 PM to 7 AM. No call required." That's good for Schedule section.
Let's structure:
About the role
ARMStaffing is seeking a travel Radiology Technician for a 13-week contract in Morristown, New Jersey. The position starts on 11/02/2026 and involves 36 hours per week on 12-hour night shifts (19:00–07:00). The role requires a dedicated professional to provide high-quality care in a fast-paced environment, with adaptability and a patient-focused approach to ensure exceptional service delivery.
Responsibilities
- Delivering comprehensive patient care
- Collaborating with a multidisciplinary team
- Monitoring and documenting patient progress
- Adhering to facility protocols and standards
- Participating in continuous education and training
Requirements
Qualified candidates should possess relevant experience in a similar role, demonstrating strong clinical skills and a commitment to patient care.
Applicants must have the appropriate licensure and certifications relevant to the role.
Schedule
The assignment follows a rotating 7-week schedule with 13-hour shifts, 39 hours per week, from 6:00 PM to 7:00 AM. No call is required.
Pay
The pay package is based on 12-hour shifts and 36.0 hours per week (subject to confirmation), with a tax-free stipend amount to be determined.
Benefits
- Medical benefits
- Company-matched 401K
- Long-term and temporary career options
- Outstanding employee benefits
About ARMStaffing
Founded in 2011 and a member of the ARGroup, LLC, ARMStaffing connects dedicated nurses and allied health professionals with facilities nationwide. As a three-time winner of the Top Workplaces Award and named to SIA’s Largest Staffing Firms in the U.S., ARMStaffing has built a reputation on relationships. The company serves hospitals, rehab centers, and long-term care facilities, offering local and travel contracts, temp-to-perm, per diem, and direct-hire placements across all healthcare segments. Services include 24-hour customer support, a full-time registered nurse for screening and compliance, and a diverse pool of medical professionals.
Check for any duplicate or boilerplate: The second About ARMStaffing paragraph lists services and benefits. I've incorporated benefits into Benefits section, and services into About ARMStaffing. The benefits list in the second paragraph includes "Medical Benefits Company-matched 401K" and "Long-term and temporary career options with outstanding employee benefits". I've added those to Benefits list. The services list (local and travel contracts, etc.) I've summarized in About ARMStaffing.
The user said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." There's none of that.
Also, "Do NOT repeat the job title as a heading" - I didn't.
"Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." I dropped Job ID.
"Preserve ALL substantive information" - I think I have.
"Never emit a heading followed by filler/placeholder text" - all sections have content.
"Never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states schedule details, pay basis, and benefits. So okay.
Now, output only the HTML fragment. No markdown fences.
Let's write the final
for prose - Do NOT repeat job title as heading - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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") - 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 Let me map the content to appropriate sections: - "About the role" could cover the job description and details - "Responsibilities" - there's a list - "Requirements" or "Qualifications" - required experience and certifications - "Schedule" - there are specific schedule details (13 hours per day, 39 hours per week, rotating 7-week schedule 6 PM to 7 AM, no call required) - "Benefits" - the company mentions "Medical Benefits Company-matched 401K" and other benefits in the About ARMStaffing section - "Pay" - mentions pay package based on 12 hour shifts and 36 hours per week, tax-free stipend amount to be determined. This is somewhat specific but the stipend is TBD. The rule says never create Pay section unless posting actually states them. It does state a pay package structure but the amount is TBD. I think we can include a Pay section with the details given. - "About ARMStaffing" - company info, but this might be considered boilerplate? The user said remove boilerplate but "About ARMStaffing" seems like company description. However, the rule says "include a section ONLY when the posting has real, specific content for it". The company description is fairly detailed. But the user also said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Company description might be considered boilerplate? But it's specific to this employer. I'll include it as a section maybe "About the Company" or similar. But the headings should be from the suggested list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the Company" is not in that list. However, the rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests these are examples, not exhaustive. But we should stick to those if possible. The company info could be folded into a short
or dropped. The user said "fold minor metadata into a short
or drop it." The company description is not minor metadata; it's a substantial paragraph. But it's not directly about the job. I think we can include it as a section "About ARMStaffing" but the heading should be
. The example headings include "About the role". Could use "About the Company". I'll include it. Now, let's structure: - Job details metadata: Start Date, Duration, Hours per week, Shift, Employment Type, Location, Assignment Duration, Schedule/Shift details. These can be in a short
under "About the role" or a separate "Schedule" section. The schedule details are specific: "13 hours per day, 39 hours per week, on a rotating 7-week schedule from 6 PM to 7 AM. No call required." That's good for a Schedule section. - Job Description: prose. - Responsibilities: list. - Required Experience: prose. - Certifications/Licensure: prose. - Pay: "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This is specific about the basis but amount TBD. I'll include a Pay section with that info. - Benefits: "Medical Benefits Company-matched 401K" and other benefits listed in the second About ARMStaffing paragraph: "Long-term and temporary career options with outstanding employee benefits Medical Benefits Company-matched 401K". Also earlier: "outstanding employee benefits". Could create a Benefits section. - About ARMStaffing: company description. I'll include as a section. But we must avoid thin sections. Let's see. I'll create sections: 1. About the role (includes job description and key details) 2. Responsibilities 3. Requirements (combining Required Experience and Certifications/Licensure) 4. Schedule 5. Pay 6. Benefits 7. About ARMStaffing But the rule: "Prefer a few substantive sections over many thin ones." So maybe combine some. Let's examine each: - About the role: can include the job description prose and the quick look details (location, duration, schedule summary). But schedule has its own details, so maybe separate Schedule section. - Responsibilities: list, substantive. - Requirements: two prose paragraphs (Required Experience and Certifications/Licensure). Could be combined under "Requirements" or "Qualifications". Use "Requirements" as heading. - Schedule: specific details, good for a section. - Pay: specific basis, though amount TBD. Still substantive. - Benefits: listed benefits, substantive. - About ARMStaffing: company info, substantive. That's 7 sections. Might be okay. But note: the job posting has two "About ARMStaffing" sections. The first is a paragraph, the second is a longer description with services and benefits. I'll combine them. Also, the Job ID #38491258 should be folded into a short
or dropped. I'll drop it as it's minor metadata. The posted job title "Radiology:X-Ray,19:00:00-07:00:00" is essentially the shift, already covered. Now, write HTML. I'll start with
About the role
then awith job description and key details. But the job description is: "The position requires a committed professional to provide high-quality care in a fast-paced environment. Candidates should be adaptable and patient-focused, ensuring exceptional service delivery to all patients." Then details: Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type, Location, Assignment Duration. I'll include those in a paragraph or maybe a list? The rule says use
- for any list of duties/requirements/benefits. These are not duties/requirements/benefits; they are job metadata. Could be a
with line breaks or a list. I think a
with sentences is fine. But the schedule details are more specific: "13 hours per day, 39 hours per week, on a rotating 7-week schedule from 6 PM to 7 AM. No call required." That's good for Schedule section. Let's structure:
About the role
ARMStaffing is seeking a travel Radiology Technician for a 13-week contract in Morristown, New Jersey. The position starts on 11/02/2026 and involves 36 hours per week on 12-hour night shifts (19:00–07:00). The role requires a dedicated professional to provide high-quality care in a fast-paced environment, with adaptability and a patient-focused approach to ensure exceptional service delivery.
Responsibilities
- Delivering comprehensive patient care
- Collaborating with a multidisciplinary team
- Monitoring and documenting patient progress
- Adhering to facility protocols and standards
- Participating in continuous education and training
Requirements
Qualified candidates should possess relevant experience in a similar role, demonstrating strong clinical skills and a commitment to patient care.
Applicants must have the appropriate licensure and certifications relevant to the role.
Schedule
The assignment follows a rotating 7-week schedule with 13-hour shifts, 39 hours per week, from 6:00 PM to 7:00 AM. No call is required.
Pay
The pay package is based on 12-hour shifts and 36.0 hours per week (subject to confirmation), with a tax-free stipend amount to be determined.
Benefits
- Medical benefits
- Company-matched 401K
- Long-term and temporary career options
- Outstanding employee benefits
About ARMStaffing
Founded in 2011 and a member of the ARGroup, LLC, ARMStaffing connects dedicated nurses and allied health professionals with facilities nationwide. As a three-time winner of the Top Workplaces Award and named to SIA’s Largest Staffing Firms in the U.S., ARMStaffing has built a reputation on relationships. The company serves hospitals, rehab centers, and long-term care facilities, offering local and travel contracts, temp-to-perm, per diem, and direct-hire placements across all healthcare segments. Services include 24-hour customer support, a full-time registered nurse for screening and compliance, and a diverse pool of medical professionals.
Check for any duplicate or boilerplate: The second About ARMStaffing paragraph lists services and benefits. I've incorporated benefits into Benefits section, and services into About ARMStaffing. The benefits list in the second paragraph includes "Medical Benefits Company-matched 401K" and "Long-term and temporary career options with outstanding employee benefits". I've added those to Benefits list. The services list (local and travel contracts, etc.) I've summarized in About ARMStaffing. The user said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." There's none of that. Also, "Do NOT repeat the job title as a heading" - I didn't. "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." I dropped Job ID. "Preserve ALL substantive information" - I think I have. "Never emit a heading followed by filler/placeholder text" - all sections have content. "Never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states schedule details, pay basis, and benefits. So okay. Now, output only the HTML fragment. No markdown fences. Let's write the final