Travel Vascular Sonographer - $2,375 per week
for section headings
- Use - for lists
- Use
for prose
- Don't repeat job title as heading
- Don't put Job ID as heading - fold into short
or drop
- 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 (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
Let me parse the content:
Job Summary: "A Vascular Sonographer position located in the designated healthcare setting. This role involves performing general ultrasound, obstetric, small parts, and vascular ultrasound studies, supporting diagnostic imaging needs in a fast-paced environment."
Job Details Required Qualifications: list of certifications and requirements.
Schedule: "Rotating shifts, 12 hours per shift, with a minimum of 36 hours per week."
Additional Information: equipment, orientation, submission requirements.
Benefits: list of benefits.
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 has some info but stipend is TBD. The rule says never create Pay section unless posting actually states them. It does state pay package based on shifts/hours, but stipend TBD. Might include as short p.
Job ID: #1338013 - fold into short p or drop.
About Cross Country Allied: boilerplate company description - remove.
Benefits duplicated at end - already captured.
Submission Requirements: "Candidates must submit a copy of their unexpired driver's license with their application." This is application instruction - remove per rules.
Now structure sections:
1. About the role (Job Summary)
2. Responsibilities (from Job Summary: performing general ultrasound, obstetric, small parts, vascular ultrasound studies)
3. Requirements (Required Qualifications list)
4. Schedule (Rotating shifts, 12 hours, 36 hours/week)
5. Additional Details (equipment, orientation, license submission? but submission is application instruction - maybe include equipment and orientation as additional info)
6. Benefits (list)
7. Pay (maybe include as p: "Pay package based on 12-hour shifts and 36 hours per week; tax-free stipend amount to be determined." But rule says never create Pay section unless posting actually states them. It does state pay package based on shifts/hours. Could include as a short p under a Pay heading? But "tax-free stipend amount to be determined" is placeholder. Might skip Pay section entirely and fold into a short p elsewhere? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule and benefits. Pay is stated but with TBD. I think include Pay as a section with the substantive part: "Pay package based on 12-hour shifts and 36 hours per week." The stipend TBD is placeholder, but the base info is there. However, the rule says "never emit a heading followed by filler/placeholder text". If I include Pay heading and then say "tax-free stipend amount to be determined" that's placeholder. Could just include the known part. But better to omit Pay section and maybe mention in a short p at end? The rule says "fold minor metadata into a short
or drop it." Pay is not minor metadata. But the stipend is TBD. I'll include a Pay section with the known info and note stipend TBD? That might be placeholder. Let's see examples: "commensurate with experience" is placeholder. "tax-free stipend amount to be determined" is similar. So maybe omit Pay section entirely.
But the posting says "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." That's the only pay info. Could include as a short p under a "Compensation" heading? But rule says never create Pay section unless posting actually states them. It does state pay package based on shifts/hours. I'll include a Pay section with that sentence, but it includes TBD. Might be okay.
Alternatively, fold into a short p at end: "Pay package based on 12-hour shifts and 36 hours per week; tax-free stipend to be determined." But that's still placeholder.
I think I'll include a Pay section with the substantive part: "Pay package based on 12-hour shifts and 36 hours per week." and omit the TBD part? But that would be removing info. The rule: "Preserve ALL substantive information". The stipend TBD is not substantive. So I can include the known part.
Let's decide sections:
- About the role
- Responsibilities
- Requirements
- Schedule
- Additional Details (equipment, orientation)
- Benefits
- Pay (maybe)
But "Additional Details" might be better as "Work Environment" or "Additional Information". The posting has "Additional Information:" heading. I'll use that.
Also, the job details include "No float requirement; the department utilizes Siemens S2000 radiology equipment, and EMR-Community Works with PACS-Intellirad/Intelliconnect. A departmental orientation of 5 shifts with a preceptor is provided." That's substantive.
Submission Requirements is application instruction - remove.
Job ID - fold into short p at top or bottom? The rule: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I'll add a short p at beginning or end with Job ID.
Now, let's write HTML.
Start with a short p for metadata: "Job ID: 1338013 | Start Date: 11/16/2026 | Duration: 13 weeks | Employment Type: Travel | Location: Weirton, West Virginia"
But the rule says "fold minor metadata into a short
or drop it." I'll include a short p at top.
Then sections.
Note: The job title is "Vascular Sonographer" but we don't repeat as heading.
Now, write HTML.
I'll use
for each section.
Let's draft:
Job ID: 1338013 | Start Date: 11/16/2026 | Duration: 13 weeks | Employment Type: Travel | Location: Weirton, West Virginia
About the role
A Vascular Sonographer position located in the designated healthcare setting. This role involves performing general ultrasound, obstetric, small parts, and vascular ultrasound studies, supporting diagnostic imaging needs in a fast-paced environment.
Responsibilities
- Perform general ultrasound studies
- Perform obstetric ultrasound studies
- Perform small parts ultrasound studies
- Perform vascular ultrasound studies
- Support diagnostic imaging needs in a fast-paced environment
Requirements
- ARDMS certification
- BLS certification
- Registered Vascular Technologist (RVT) via ARDMS
- West Virginia license
- WV CARES required prior to start
- OB and Arterial Extremity Doppler experience required
- Minimum 1 year of experience
- Ability to multitask and work in a fast-paced environment
Schedule
Rotating shifts, 12 hours per shift, with a minimum of 36 hours per week.
Additional Information
- No float requirement
- Department utilizes Siemens S2000 radiology equipment
- EMR: Community Works with PACS-Intellirad/Intelliconnect
- Departmental orientation of 5 shifts with a preceptor provided
Benefits
- Private housing or generous housing allowance
- Comprehensive health insurance with prescription coverage
- Dependent health insurance with prescription coverage
- Competitive salaries
- Referral bonuses
- Travel reimbursement
- 401(k) retirement plan
- Direct deposit/free checking
- Unlimited free CE credits
Pay
Pay package based on 12-hour shifts and 36 hours per week (subject to confirmation); tax-free stipend amount to be determined.
But the Pay section includes "to be determined" which is placeholder. The rule says never emit a heading followed by filler/placeholder text. The heading is Pay, and the content includes placeholder. Could omit Pay section entirely. But the pay package based on shifts/hours is substantive. The stipend TBD is additional. I'll keep Pay section but maybe phrase without "to be determined"? But that would be removing info. The rule: "Preserve ALL substantive information". The stipend TBD is not substantive. So I can include the known part and omit the TBD? But the posting says "with tax-free stipend amount to be determined." That's part of the pay info. It's not filler; it's a statement that stipend is TBD. That's factual. However, the rule says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "to be determined" is similar to TBD. So I should not include that. But the pay package based on shifts/hours is not placeholder. Could have a Pay section with just that sentence without the TBD part? But that would be altering. Better to omit Pay section and fold the known part into a short p elsewhere? But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package based on shifts/hours. So it's stated. But the stipend TBD is placeholder. I think I'll include Pay section with the substantive part only: "Pay package based on 12-hour shifts and 36 hours per week (subject to confirmation)." That's substantive. The stipend TBD is placeholder, so omit.
But the posting says "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." If I omit the stipend part, I'm preserving the substantive part. That seems okay.
Alternatively, include both but the rule says never emit heading followed by filler/placeholder text. The heading would be followed by text that includes placeholder. That might violate. So I'll omit Pay section entirely and maybe include the pay info in a short p at the end? But that would be creating a Pay-like info without heading. The rule says "fold minor metadata into a short or drop it." Pay is not minor metadata. But the stipend TBD makes it incomplete. I'll drop
for prose - Don't repeat job title as heading - Don't put Job ID as heading - fold into short
or drop - 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 (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 Let me parse the content: Job Summary: "A Vascular Sonographer position located in the designated healthcare setting. This role involves performing general ultrasound, obstetric, small parts, and vascular ultrasound studies, supporting diagnostic imaging needs in a fast-paced environment." Job Details Required Qualifications: list of certifications and requirements. Schedule: "Rotating shifts, 12 hours per shift, with a minimum of 36 hours per week." Additional Information: equipment, orientation, submission requirements. Benefits: list of benefits. 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 has some info but stipend is TBD. The rule says never create Pay section unless posting actually states them. It does state pay package based on shifts/hours, but stipend TBD. Might include as short p. Job ID: #1338013 - fold into short p or drop. About Cross Country Allied: boilerplate company description - remove. Benefits duplicated at end - already captured. Submission Requirements: "Candidates must submit a copy of their unexpired driver's license with their application." This is application instruction - remove per rules. Now structure sections: 1. About the role (Job Summary) 2. Responsibilities (from Job Summary: performing general ultrasound, obstetric, small parts, vascular ultrasound studies) 3. Requirements (Required Qualifications list) 4. Schedule (Rotating shifts, 12 hours, 36 hours/week) 5. Additional Details (equipment, orientation, license submission? but submission is application instruction - maybe include equipment and orientation as additional info) 6. Benefits (list) 7. Pay (maybe include as p: "Pay package based on 12-hour shifts and 36 hours per week; tax-free stipend amount to be determined." But rule says never create Pay section unless posting actually states them. It does state pay package based on shifts/hours. Could include as a short p under a Pay heading? But "tax-free stipend amount to be determined" is placeholder. Might skip Pay section entirely and fold into a short p elsewhere? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule and benefits. Pay is stated but with TBD. I think include Pay as a section with the substantive part: "Pay package based on 12-hour shifts and 36 hours per week." The stipend TBD is placeholder, but the base info is there. However, the rule says "never emit a heading followed by filler/placeholder text". If I include Pay heading and then say "tax-free stipend amount to be determined" that's placeholder. Could just include the known part. But better to omit Pay section and maybe mention in a short p at end? The rule says "fold minor metadata into a short
or drop it." Pay is not minor metadata. But the stipend is TBD. I'll include a Pay section with the known info and note stipend TBD? That might be placeholder. Let's see examples: "commensurate with experience" is placeholder. "tax-free stipend amount to be determined" is similar. So maybe omit Pay section entirely. But the posting says "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." That's the only pay info. Could include as a short p under a "Compensation" heading? But rule says never create Pay section unless posting actually states them. It does state pay package based on shifts/hours. I'll include a Pay section with that sentence, but it includes TBD. Might be okay. Alternatively, fold into a short p at end: "Pay package based on 12-hour shifts and 36 hours per week; tax-free stipend to be determined." But that's still placeholder. I think I'll include a Pay section with the substantive part: "Pay package based on 12-hour shifts and 36 hours per week." and omit the TBD part? But that would be removing info. The rule: "Preserve ALL substantive information". The stipend TBD is not substantive. So I can include the known part. Let's decide sections: - About the role - Responsibilities - Requirements - Schedule - Additional Details (equipment, orientation) - Benefits - Pay (maybe) But "Additional Details" might be better as "Work Environment" or "Additional Information". The posting has "Additional Information:" heading. I'll use that. Also, the job details include "No float requirement; the department utilizes Siemens S2000 radiology equipment, and EMR-Community Works with PACS-Intellirad/Intelliconnect. A departmental orientation of 5 shifts with a preceptor is provided." That's substantive. Submission Requirements is application instruction - remove. Job ID - fold into short p at top or bottom? The rule: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I'll add a short p at beginning or end with Job ID. Now, let's write HTML. Start with a short p for metadata: "Job ID: 1338013 | Start Date: 11/16/2026 | Duration: 13 weeks | Employment Type: Travel | Location: Weirton, West Virginia" But the rule says "fold minor metadata into a short
or drop it." I'll include a short p at top. Then sections. Note: The job title is "Vascular Sonographer" but we don't repeat as heading. Now, write HTML. I'll use
for each section. Let's draft:
Job ID: 1338013 | Start Date: 11/16/2026 | Duration: 13 weeks | Employment Type: Travel | Location: Weirton, West Virginia
About the role
A Vascular Sonographer position located in the designated healthcare setting. This role involves performing general ultrasound, obstetric, small parts, and vascular ultrasound studies, supporting diagnostic imaging needs in a fast-paced environment.
Responsibilities
- Perform general ultrasound studies
- Perform obstetric ultrasound studies
- Perform small parts ultrasound studies
- Perform vascular ultrasound studies
- Support diagnostic imaging needs in a fast-paced environment
Requirements
- ARDMS certification
- BLS certification
- Registered Vascular Technologist (RVT) via ARDMS
- West Virginia license
- WV CARES required prior to start
- OB and Arterial Extremity Doppler experience required
- Minimum 1 year of experience
- Ability to multitask and work in a fast-paced environment
Schedule
Rotating shifts, 12 hours per shift, with a minimum of 36 hours per week.
Additional Information
- No float requirement
- Department utilizes Siemens S2000 radiology equipment
- EMR: Community Works with PACS-Intellirad/Intelliconnect
- Departmental orientation of 5 shifts with a preceptor provided
Benefits
- Private housing or generous housing allowance
- Comprehensive health insurance with prescription coverage
- Dependent health insurance with prescription coverage
- Competitive salaries
- Referral bonuses
- Travel reimbursement
- 401(k) retirement plan
- Direct deposit/free checking
- Unlimited free CE credits
Pay
Pay package based on 12-hour shifts and 36 hours per week (subject to confirmation); tax-free stipend amount to be determined.
But the Pay section includes "to be determined" which is placeholder. The rule says never emit a heading followed by filler/placeholder text. The heading is Pay, and the content includes placeholder. Could omit Pay section entirely. But the pay package based on shifts/hours is substantive. The stipend TBD is additional. I'll keep Pay section but maybe phrase without "to be determined"? But that would be removing info. The rule: "Preserve ALL substantive information". The stipend TBD is not substantive. So I can include the known part and omit the TBD? But the posting says "with tax-free stipend amount to be determined." That's part of the pay info. It's not filler; it's a statement that stipend is TBD. That's factual. However, the rule says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "to be determined" is similar to TBD. So I should not include that. But the pay package based on shifts/hours is not placeholder. Could have a Pay section with just that sentence without the TBD part? But that would be altering. Better to omit Pay section and fold the known part into a short p elsewhere? But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package based on shifts/hours. So it's stated. But the stipend TBD is placeholder. I think I'll include Pay section with the substantive part only: "Pay package based on 12-hour shifts and 36 hours per week (subject to confirmation)." That's substantive. The stipend TBD is placeholder, so omit. But the posting says "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." If I omit the stipend part, I'm preserving the substantive part. That seems okay. Alternatively, include both but the rule says never emit heading followed by filler/placeholder text. The heading would be followed by text that includes placeholder. That might violate. So I'll omit Pay section entirely and maybe include the pay info in a short p at the end? But that would be creating a Pay-like info without heading. The rule says "fold minor metadata into a shortor drop it." Pay is not minor metadata. But the stipend TBD makes it incomplete. I'll drop