Travel EP Technologist - $3,134 per week
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists,
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; do NOT invent or summarize away detail
- 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 structure:
1. Job Details (metadata) - can be a
or a list? The rule says fold minor metadata into a short
or drop it. But some details like start date, duration, hours, shift are substantive. I'll create a "Job Details" section with a list.
2. About the Role - there's not much description of the role itself, just the title and specialty. The posting doesn't have a detailed "About the role" section. It has "Job Description & Requirements" but then only lists metadata. No responsibilities or duties listed. So maybe no "Responsibilities" section.
3. Requirements / Qualifications - not explicitly listed. The posting mentions "Specialty: Electrophysiology Technician" and "Discipline: Allied Health Professional". But no specific requirements like certifications, experience, etc. So maybe no Requirements section.
4. Pay / Schedule - the posting says: "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined." Also shift: 12 hours, days; 36 hours per week. This is specific content, so include Pay and Schedule sections? Could combine into one "Pay & Schedule" section? The rule says use headings like Pay, Schedule. But we can have separate if both have content. Pay: tax-free stipend amount to be determined. Schedule: 12 hour shifts, days, 36 hours per week. I'll include both.
5. Benefits - the posting has two benefits lists: one under "What You Can Expect" and another at the end "Benefits". They overlap. I'll combine into one Benefits section with a list.
6. About Anders Group - there's a description about the company. Could include an "About the Company" section.
Now, ensure no filler. For Pay, the stipend amount is "to be determined" - that's not a placeholder, it's actual info (they haven't determined). But 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. However, it's the actual information provided. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state pay package details, albeit with stipend TBD. I think we should include it because it's the actual content. But the rule says "never emit a heading followed by filler/placeholder text". If the only content is "tax-free stipend amount to be determined", that might be considered placeholder. However, there is also "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation)". That's substantive. So I'll include Pay section with that info.
Similarly, Schedule: "12 hours, days" and "36 hours per week". That's specific.
Benefits: list is specific.
Now, Job ID: "Anders Group Job ID #1411599" - fold into a short
or drop. I'll include in Job Details list.
Let's craft HTML.
Sections:
- Job Details (h3)
- Pay (h3)
- Schedule (h3)
- Benefits (h3)
- About Anders Group (h3)
But the rule says "Prefer a few substantive sections over many thin ones." Could combine Job Details, Pay, Schedule into one "Job Details" section? But headings are predefined: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should use those headings when appropriate. For Job Details, maybe "About the Role" but that's more about the role description. The metadata is not exactly "About the role". Could use "Job Details" as a heading? The rule says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g.", so other headings allowed? But better to stick to those. However, "Job Details" is not in the list. Could use "About the Role" for the metadata? But the role description is missing. Might be better to include a "Job Details" heading anyway, but the rule says use those headings. I think it's okay to use a heading like "Job Details" as it's a section heading. The rule says "use for section headings (e.g. ...)" meaning those are examples, not exhaustive. But to be safe, I'll use "About the Role" for the metadata? Actually, the metadata includes start date, duration, hours, shift, employment type. That's more like "Schedule" and "Job Details". I'll create a "Job Details" section with a list.
Alternatively, I can put metadata in a
at the top without a heading. The rule says "fold minor metadata into a short
or drop it." But this metadata is not minor; it's important job details. However, the rule says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So maybe all metadata (start date, duration, hours, shift, employment type, job ID) can be folded into a short
. But that would be a long paragraph. Better to use a list under a heading "Job Details". I'll do that.
Let's write.
First, a paragraph for the job title? Not needed.
I'll start with a
Job Details
then with items.
But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings. I'll use "Job Details".
Now, Pay section: Pay
with
content.
Schedule section:
Schedule
with or .
Benefits:
Benefits
with .
About Anders Group: About Anders Group
with and maybe
for the benefits list? But benefits already covered. The "What You Can Expect" list is essentially benefits. The final "Benefits" list is a subset. I'll combine into one Benefits section.
The "About Anders Group" section includes a description and then a list of benefits. I'll separate: About Anders Group (prose) and Benefits (list). But the benefits list is part of "What You Can Expect". I'll include the company description in About Anders Group, and the benefits in Benefits section.
Let's parse the content:
"About Anders Group
About Anders Group Why Anders?
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
From your very first assignment, you’ll have access to a comprehensive benefits package designed to support you both professionally and personally:
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
And more The Anders Difference
You’re committed to providing exceptional patient care and we’re committed to supporting you every step of the way.
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
Medical benefits
Dental benefits
Vision benefits
Life insurance
401k retirement plan
License and certification reimbursement
Continuing Education
Referral bonus"
There is duplication. I'll merge the benefits lists into one comprehensive list.
Now, produce HTML.
I'll structure:
Job Details
- Specialty: Electrophysiology Technician
- Discipline: Allied Health Professional
- Start Date: ASAP
- Duration: 13 weeks
- Hours per Week: 36
- Shift: 12 hours, days
- Employment Type: Travel
- Job ID: #1411599
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.
Schedule
- 12-hour day shifts
- 36 hours per week
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
- Medical benefits
- Dental benefits
- Vision benefits
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; do NOT invent or summarize away detail - 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 structure: 1. Job Details (metadata) - can be a
or a list? The rule says fold minor metadata into a short
or drop it. But some details like start date, duration, hours, shift are substantive. I'll create a "Job Details" section with a list. 2. About the Role - there's not much description of the role itself, just the title and specialty. The posting doesn't have a detailed "About the role" section. It has "Job Description & Requirements" but then only lists metadata. No responsibilities or duties listed. So maybe no "Responsibilities" section. 3. Requirements / Qualifications - not explicitly listed. The posting mentions "Specialty: Electrophysiology Technician" and "Discipline: Allied Health Professional". But no specific requirements like certifications, experience, etc. So maybe no Requirements section. 4. Pay / Schedule - the posting says: "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined." Also shift: 12 hours, days; 36 hours per week. This is specific content, so include Pay and Schedule sections? Could combine into one "Pay & Schedule" section? The rule says use headings like Pay, Schedule. But we can have separate if both have content. Pay: tax-free stipend amount to be determined. Schedule: 12 hour shifts, days, 36 hours per week. I'll include both. 5. Benefits - the posting has two benefits lists: one under "What You Can Expect" and another at the end "Benefits". They overlap. I'll combine into one Benefits section with a list. 6. About Anders Group - there's a description about the company. Could include an "About the Company" section. Now, ensure no filler. For Pay, the stipend amount is "to be determined" - that's not a placeholder, it's actual info (they haven't determined). But 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. However, it's the actual information provided. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state pay package details, albeit with stipend TBD. I think we should include it because it's the actual content. But the rule says "never emit a heading followed by filler/placeholder text". If the only content is "tax-free stipend amount to be determined", that might be considered placeholder. However, there is also "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation)". That's substantive. So I'll include Pay section with that info. Similarly, Schedule: "12 hours, days" and "36 hours per week". That's specific. Benefits: list is specific. Now, Job ID: "Anders Group Job ID #1411599" - fold into a short
or drop. I'll include in Job Details list. Let's craft HTML. Sections: - Job Details (h3) - Pay (h3) - Schedule (h3) - Benefits (h3) - About Anders Group (h3) But the rule says "Prefer a few substantive sections over many thin ones." Could combine Job Details, Pay, Schedule into one "Job Details" section? But headings are predefined: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should use those headings when appropriate. For Job Details, maybe "About the Role" but that's more about the role description. The metadata is not exactly "About the role". Could use "Job Details" as a heading? The rule says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g.", so other headings allowed? But better to stick to those. However, "Job Details" is not in the list. Could use "About the Role" for the metadata? But the role description is missing. Might be better to include a "Job Details" heading anyway, but the rule says use those headings. I think it's okay to use a heading like "Job Details" as it's a section heading. The rule says "use for section headings (e.g. ...)" meaning those are examples, not exhaustive. But to be safe, I'll use "About the Role" for the metadata? Actually, the metadata includes start date, duration, hours, shift, employment type. That's more like "Schedule" and "Job Details". I'll create a "Job Details" section with a list.
Alternatively, I can put metadata in a
at the top without a heading. The rule says "fold minor metadata into a short
or drop it." But this metadata is not minor; it's important job details. However, the rule says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So maybe all metadata (start date, duration, hours, shift, employment type, job ID) can be folded into a short
. But that would be a long paragraph. Better to use a list under a heading "Job Details". I'll do that. Let's write. First, a paragraph for the job title? Not needed. I'll start with a
Job Details
then- with items.
But the rule says "use
- Specialty: Electrophysiology Technician
- Discipline: Allied Health Professional
- Start Date: ASAP
- Duration: 13 weeks
- Hours per Week: 36
- Shift: 12 hours, days
- Employment Type: Travel
- Job ID: #1411599
- 12-hour day shifts
- 36 hours per week
- 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
- Medical benefits
- Dental benefits
- Vision benefits
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings. I'll use "Job Details".
Now, Pay section: Pay
with
content. Schedule section:
Schedule
with- or
. Benefits:
Benefits
with- .
About Anders Group:
About Anders Group
withand maybe
- for the benefits list? But benefits already covered. The "What You Can Expect" list is essentially benefits. The final "Benefits" list is a subset. I'll combine into one Benefits section.
The "About Anders Group" section includes a description and then a list of benefits. I'll separate: About Anders Group (prose) and Benefits (list). But the benefits list is part of "What You Can Expect". I'll include the company description in About Anders Group, and the benefits in Benefits section.
Let's parse the content:
"About Anders Group
About Anders Group Why Anders?
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
From your very first assignment, you’ll have access to a comprehensive benefits package designed to support you both professionally and personally:
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
And more The Anders Difference
You’re committed to providing exceptional patient care and we’re committed to supporting you every step of the way.
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
Medical benefits
Dental benefits
Vision benefits
Life insurance
401k retirement plan
License and certification reimbursement
Continuing Education
Referral bonus"
There is duplication. I'll merge the benefits lists into one comprehensive list.
Now, produce HTML.
I'll structure:
Job Details
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.