Travel Echo/Vascular Tech - $2,339 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 into short
or drop
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/scam-warning)
- Include section ONLY when posting has real, specific content
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Output ONLY HTML fragment
Looking at the content:
- There's no explicit "Responsibilities" or "Requirements" section - just job details
- There's "About Anders Group" with company info
- There's benefits listed in two places (should consolidate)
- Pay is mentioned: "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This is somewhat specific but says "to be determined" for stipend. The rule says never create Pay section unless posting actually states them. It does state pay package details, but the stipend is TBD. I think I should include a Pay section with what's stated.
- Schedule: "36 hours per week, Shift: 12 hours, rotating" - this is specific schedule info. Could be a Schedule section.
- Benefits: listed specifically.
I need to decide on sections:
1. About the role (or Job Details) - for the job specifics
2. About Anders Group - company description
3. Benefits - consolidated benefits
4. Pay - since pay package details are given
5. Schedule - since schedule details are given
But the rules say: "Prefer a few substantive sections over many thin ones." And "include a section ONLY when the posting has real, specific content for it".
Let me structure:
- Job Details (could be "About the role"): includes specialty, discipline, start date, duration, hours, shift, employment type. Job ID can be in a
.
- About Anders Group: the company description.
- Benefits: the list of benefits.
- Pay: the pay package description.
- Schedule: the schedule details.
But "Schedule" might be redundant with Job Details. The rules mention "Schedule" as a possible heading. Since shift and hours are given, I could include a Schedule section.
However, the job details are all metadata. The rules say "fold minor metadata into a short
or drop it." But these are substantive job details. I think a "Job Details" section with a list is appropriate.
The user said: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "About the role" is an example. I'll use "About the role" for the job details.
Now, the benefits are listed twice. I'll consolidate into one list.
The "About Anders Group" section has two parts: "Why Anders?" and "The Anders Difference". I'll include both as prose.
Let me draft the HTML.
First, Job Details:
About the role
- Specialty: Echo-Vascular Technician
- Discipline: Allied Health Professional
- Start Date: 11/16/2026
- Duration: 13 weeks
- Hours: 36 hours per week
- Shift: 12 hours, rotating
- Employment Type: Travel
Anders Group Job ID #1415971
But the rule says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." So I'll put Job ID in a
.
Second, About Anders Group:
About Anders Group
At Anders Group, we do things differently. As a Joint Commission–accredited healthcare staffing agency, we’re committed to one thing above all else—you.
Our travelers aren’t just placements, they’re partners. That’s why we focus on delivering exceptional customer service, personalized support, and access to some of the best-paying travel opportunities nationwide.
What You Can Expect
... but the rule says use for section headings. Should I use for subsections? The rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't mention subsections. I think I should keep it flat: only for main sections. So I'll incorporate the "What You Can Expect" and "The Anders Difference" as prose under About Anders Group.
Third, Benefits:
Benefits
- Day One Health Insurance (with buy-up options)
- Dental & Vision Insurance
- Life Insurance
- 401(k) Retirement Plan
- Competitive, Premium Pay Packages
- Licensure & CEU Reimbursement
- Daily Per Diems & Travel Reimbursements
- Rental Car Allowances
- Continuing Education Resources
- Referral Bonuses
But note the benefits are listed twice: once in "What You Can Expect" and again at the end. The second list is shorter: Medical benefits, Dental benefits, Vision benefits, Life insurance, 401k retirement plan, License and certification reimbursement, Continuing Education, Referral bonus. I should combine and deduplicate. The first list is more detailed. I'll use the first list and add any missing from second. The second list has "Medical benefits" which is covered by "Day One Health Insurance". "Dental benefits", "Vision benefits" covered. "Life insurance" covered. "401k retirement plan" covered. "License and certification reimbursement" covered by "Licensure & CEU Reimbursement". "Continuing Education" covered by "Continuing Education Resources". "Referral bonus" covered. So the first list is comprehensive. I'll use that.
Fourth, Pay:
Pay
Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined.
Fifth, Schedule:
Schedule
36 hours per week, 12-hour rotating shifts.
But the schedule info is already in Job Details. The rules say "Prefer a few substantive sections over many thin ones." So maybe I should not create a separate Schedule section if it's already in About the role. However, the example headings include Schedule. The posting has specific schedule info. I think it's okay to have a Schedule section.
But the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state them. So I can create them.
However, the Job Details section already includes hours and shift. If I create a Schedule section, it's duplication. I could omit Schedule from Job Details and put it in Schedule section. But the Job Details section would then be missing that info. Better to have Job Details include all job metadata, and then have separate Pay and Benefits sections. Schedule could be part of Job Details.
Let me re-read: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests Schedule is a possible section. But the posting may not have a separate schedule section; it's just details. I think I'll include a Schedule section with the schedule details, and in About the role, I'll keep the other details.
But to avoid duplication, I'll put schedule in Schedule section and not in About the role. However, the start date, duration, employment type are not schedule. So About the role can have those.
Let me structure:
About the role
- Specialty: Echo-Vascular Technician
- Discipline: Allied Health Professional
- Start Date: 11/16/2026
- Duration: 13 weeks
- Employment Type: Travel
Anders Group Job ID #1415971
Schedule
36 hours per week, 12-hour rotating shifts.
Pay
Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined.
About Anders Group
At Anders Group, we do things differently. As a Joint Commission–accredited healthcare staffing agency, we’re committed to one thing above all else—you.
Our travelers aren’t just placements, they’re partners. That’s why we focus on delivering exceptional customer service, personalized support, and access to some of the best-paying travel opportunities nationwide.
Founded in 2010 by experienced healthcare recruiters, Anders Group was built on a simple idea: people come before numbers. While many staffing firms focus on volume, we focus on relationships, quality placements, and your long-term success.
By aligning your goals with the needs of top healthcare facilities across the country, we create assignments that truly fit, professionally and personally.
Benefits
- Day One Health Insurance (with buy-up options)
- Dental & Vision Insurance
- Life Insurance
- 401(k) Retirement Plan
- Competitive, Premium Pay Packages
- Licensure & CEU Reimbursement
- Daily Per Diems & Travel Reimbursements
- Rental Car Allowances
- Continuing Education Resources
- Referral Bonuses
That seems comprehensive. I removed the duplicate benefits list. I kept the Job ID in a paragraph. I didn't include any boilerplate. The posting didn't have responsibilities or requirements, so no those sections.
Now, check rules: "Do NOT repeat the job title as a heading (the page already shows it)" - I didn't. "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." - I put in
. "Preserve ALL substantive information" - I think I did. "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate" - none present. "Include a section ONLY when the posting has real, specific content for it" - each section has content. "Never emit a heading followed by filler/placeholder text" - no filler. "Never create Pay/Schedule/Benefits sections unless the posting actually states them" - they are stated. "Prefer a few substantive sections over many thin ones" - I have 5 sections, each substantive.
Output ONLY HTML fragment, no markdown code fences. So I'll output the HTML as plain
for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings - fold into short
or drop - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning) - Include section ONLY when posting has real, specific content - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment Looking at the content: - There's no explicit "Responsibilities" or "Requirements" section - just job details - There's "About Anders Group" with company info - There's benefits listed in two places (should consolidate) - Pay is mentioned: "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This is somewhat specific but says "to be determined" for stipend. The rule says never create Pay section unless posting actually states them. It does state pay package details, but the stipend is TBD. I think I should include a Pay section with what's stated. - Schedule: "36 hours per week, Shift: 12 hours, rotating" - this is specific schedule info. Could be a Schedule section. - Benefits: listed specifically. I need to decide on sections: 1. About the role (or Job Details) - for the job specifics 2. About Anders Group - company description 3. Benefits - consolidated benefits 4. Pay - since pay package details are given 5. Schedule - since schedule details are given But the rules say: "Prefer a few substantive sections over many thin ones." And "include a section ONLY when the posting has real, specific content for it". Let me structure: - Job Details (could be "About the role"): includes specialty, discipline, start date, duration, hours, shift, employment type. Job ID can be in a
. - About Anders Group: the company description. - Benefits: the list of benefits. - Pay: the pay package description. - Schedule: the schedule details. But "Schedule" might be redundant with Job Details. The rules mention "Schedule" as a possible heading. Since shift and hours are given, I could include a Schedule section. However, the job details are all metadata. The rules say "fold minor metadata into a short
or drop it." But these are substantive job details. I think a "Job Details" section with a list is appropriate. The user said: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "About the role" is an example. I'll use "About the role" for the job details.
Now, the benefits are listed twice. I'll consolidate into one list.
The "About Anders Group" section has two parts: "Why Anders?" and "The Anders Difference". I'll include both as prose.
Let me draft the HTML.
First, Job Details:
About the role
- Specialty: Echo-Vascular Technician
- Discipline: Allied Health Professional
- Start Date: 11/16/2026
- Duration: 13 weeks
- Hours: 36 hours per week
- Shift: 12 hours, rotating
- Employment Type: Travel
Anders Group Job ID #1415971
But the rule says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." So I'll put Job ID in a
. Second, About Anders Group:
About Anders Group
At Anders Group, we do things differently. As a Joint Commission–accredited healthcare staffing agency, we’re committed to one thing above all else—you.
Our travelers aren’t just placements, they’re partners. That’s why we focus on delivering exceptional customer service, personalized support, and access to some of the best-paying travel opportunities nationwide.
What You Can Expect
... but the rule says use for section headings. Should I use for subsections? The rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't mention subsections. I think I should keep it flat: only for main sections. So I'll incorporate the "What You Can Expect" and "The Anders Difference" as prose under About Anders Group.
Third, Benefits:
Benefits
- Day One Health Insurance (with buy-up options)
- Dental & Vision Insurance
- Life Insurance
- 401(k) Retirement Plan
- Competitive, Premium Pay Packages
- Licensure & CEU Reimbursement
- Daily Per Diems & Travel Reimbursements
- Rental Car Allowances
- Continuing Education Resources
- Referral Bonuses
But note the benefits are listed twice: once in "What You Can Expect" and again at the end. The second list is shorter: Medical benefits, Dental benefits, Vision benefits, Life insurance, 401k retirement plan, License and certification reimbursement, Continuing Education, Referral bonus. I should combine and deduplicate. The first list is more detailed. I'll use the first list and add any missing from second. The second list has "Medical benefits" which is covered by "Day One Health Insurance". "Dental benefits", "Vision benefits" covered. "Life insurance" covered. "401k retirement plan" covered. "License and certification reimbursement" covered by "Licensure & CEU Reimbursement". "Continuing Education" covered by "Continuing Education Resources". "Referral bonus" covered. So the first list is comprehensive. I'll use that.
Fourth, Pay:
Pay
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't mention subsections. I think I should keep it flat: only for main sections. So I'll incorporate the "What You Can Expect" and "The Anders Difference" as prose under About Anders Group.
Third, Benefits:
Benefits
- Day One Health Insurance (with buy-up options)
- Dental & Vision Insurance
- Life Insurance
- 401(k) Retirement Plan
- Competitive, Premium Pay Packages
- Licensure & CEU Reimbursement
- Daily Per Diems & Travel Reimbursements
- Rental Car Allowances
- Continuing Education Resources
- Referral Bonuses
But note the benefits are listed twice: once in "What You Can Expect" and again at the end. The second list is shorter: Medical benefits, Dental benefits, Vision benefits, Life insurance, 401k retirement plan, License and certification reimbursement, Continuing Education, Referral bonus. I should combine and deduplicate. The first list is more detailed. I'll use the first list and add any missing from second. The second list has "Medical benefits" which is covered by "Day One Health Insurance". "Dental benefits", "Vision benefits" covered. "Life insurance" covered. "401k retirement plan" covered. "License and certification reimbursement" covered by "Licensure & CEU Reimbursement". "Continuing Education" covered by "Continuing Education Resources". "Referral bonus" covered. So the first list is comprehensive. I'll use that.
Fourth, Pay:
Pay
Benefits
- Day One Health Insurance (with buy-up options)
- Dental & Vision Insurance
- Life Insurance
- 401(k) Retirement Plan
- Competitive, Premium Pay Packages
- Licensure & CEU Reimbursement
- Daily Per Diems & Travel Reimbursements
- Rental Car Allowances
- Continuing Education Resources
- Referral Bonuses
Pay
Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined.
Fifth, Schedule:Schedule
36 hours per week, 12-hour rotating shifts.
But the schedule info is already in Job Details. The rules say "Prefer a few substantive sections over many thin ones." So maybe I should not create a separate Schedule section if it's already in About the role. However, the example headings include Schedule. The posting has specific schedule info. I think it's okay to have a Schedule section. But the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state them. So I can create them. However, the Job Details section already includes hours and shift. If I create a Schedule section, it's duplication. I could omit Schedule from Job Details and put it in Schedule section. But the Job Details section would then be missing that info. Better to have Job Details include all job metadata, and then have separate Pay and Benefits sections. Schedule could be part of Job Details. Let me re-read: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests Schedule is a possible section. But the posting may not have a separate schedule section; it's just details. I think I'll include a Schedule section with the schedule details, and in About the role, I'll keep the other details.
But to avoid duplication, I'll put schedule in Schedule section and not in About the role. However, the start date, duration, employment type are not schedule. So About the role can have those.
Let me structure:
About the role
- Specialty: Echo-Vascular Technician
- Discipline: Allied Health Professional
- Start Date: 11/16/2026
- Duration: 13 weeks
- Employment Type: Travel
Anders Group Job ID #1415971
Schedule
36 hours per week, 12-hour rotating shifts.
Pay
Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined.
About Anders Group
At Anders Group, we do things differently. As a Joint Commission–accredited healthcare staffing agency, we’re committed to one thing above all else—you.
Our travelers aren’t just placements, they’re partners. That’s why we focus on delivering exceptional customer service, personalized support, and access to some of the best-paying travel opportunities nationwide.
Founded in 2010 by experienced healthcare recruiters, Anders Group was built on a simple idea: people come before numbers. While many staffing firms focus on volume, we focus on relationships, quality placements, and your long-term success.
By aligning your goals with the needs of top healthcare facilities across the country, we create assignments that truly fit, professionally and personally.
Benefits
- Day One Health Insurance (with buy-up options)
- Dental & Vision Insurance
- Life Insurance
- 401(k) Retirement Plan
- Competitive, Premium Pay Packages
- Licensure & CEU Reimbursement
- Daily Per Diems & Travel Reimbursements
- Rental Car Allowances
- Continuing Education Resources
- Referral Bonuses
or drop it." - I put in
. "Preserve ALL substantive information" - I think I did. "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate" - none present. "Include a section ONLY when the posting has real, specific content for it" - each section has content. "Never emit a heading followed by filler/placeholder text" - no filler. "Never create Pay/Schedule/Benefits sections unless the posting actually states them" - they are stated. "Prefer a few substantive sections over many thin ones" - I have 5 sections, each substantive. Output ONLY HTML fragment, no markdown code fences. So I'll output the HTML as plain