Travel CVOR Certified Surgical Technologist - $2,354 per week

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections from the posting: - Job details (specialty, discipline, start date, duration, hours, shift, employment type, job ID) - About Anders Group (company description) - Benefits (listed twice - once in "What You Can Expect" and again at the end) - Pay information (mentioned but vague: "Pay package is based on 8 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined") Rules: - Use

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 as heading - 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 - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment - no /, no markdown code fences Looking at the content: 1. Job details: specialty, discipline, start date, duration, hours, shift, employment type, job ID - this is metadata about the role. Could be "About the role" section. 2. About Anders Group: company description - could be "About the company" or similar, but the rules mention specific headings like "About the role". The rules list example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About Anders Group" is about the company, not the role. Might not fit exactly. Could include as "About the company" but not in the example list. Might skip or include as a section. 3. Benefits: listed twice with specific items. Definitely a Benefits section. 4. Pay: mentioned but vague - "tax-free stipend amount to be determined". This is placeholder/filler. Should NOT create Pay section. 5. Schedule: shift info given: "8 hours, rotating", "40 hours per week". Could be Schedule section. 6. Responsibilities/Requirements/Qualifications/Skills: NOT provided in the posting. No list of duties or requirements. So no those sections. The posting has: - Job metadata (specialty, discipline, start date, duration, hours, shift, employment type, job ID) - Company description (About Anders Group) - Benefits (detailed list) - Pay info (vague) - Schedule info (shift details) I should create sections for: - About the role (with job details) - Schedule (since shift details are specific) - Benefits (since detailed list) - Possibly About the company (but not in example headings; maybe include as "About the company" or fold into About the role? The rules say use

  for section headings e.g. About the role, Responsibilities, etc. It doesn't forbid other headings, but says "Prefer a few substantive sections over many thin ones." The company description is substantive. I'll include as "About the company" or "About Anders Group". But the example headings are just examples. I think it's okay to have a heading for company description. But the rule: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Certified Surgical Tech - CVOR" or "travel CVOR Technologist". Not to repeat. Job ID: fold into short

  or drop. I'll include in About the role as a paragraph. Pay: vague, so no Pay section. Schedule: specific shift info, so include Schedule section. Benefits: detailed, include. Responsibilities/Requirements: none, so omit. Now structure:

  About the role

  Specialty: CVOR Technologist

  Discipline: Allied Health Professional

  Start Date: 11/16/2026

  Duration: 13 weeks

  Hours: 40 hours per week

  Shift: 8 hours, rotating

  Employment Type: Travel

  Job ID: #1414569

  But better to use a list for these details? The rules say use
  • for any list of duties/requirements/benefits, and

    for prose. These are metadata, not a list of duties. Could be a list or separate paragraphs. I'll use a list for clarity.

    About the role

    • Specialty: CVOR Technologist
    • Discipline: Allied Health Professional
    • Start Date: 11/16/2026
    • Duration: 13 weeks
    • Hours: 40 hours per week
    • Shift: 8 hours, rotating
    • Employment Type: Travel
    • Job ID: #1414569
    But the shift is also schedule. Could put shift in Schedule section. However, the shift is part of role details. I'll keep in About the role and also have Schedule section with shift details? Might duplicate. Better to have Schedule section with shift info, and About the role with other metadata. Let's see: The posting has "Shift: 8 hours, rotating" and "40 hours per week". That's schedule. I'll create a Schedule section.

    Schedule

    • 40 hours per week
    • Shift: 8 hours, rotating
    But also "8 Hour Variable" in posted job title. Might include. Now Benefits: two lists. Combine. First list under "What You Can Expect": - 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 Second list under "Benefits": - Medical benefits - Dental benefits - Vision benefits - Life insurance - 401k retirement plan - License and certification reimbursement - Continuing Education - Referral bonus Some overlap. Combine unique items. I'll create a Benefits section with a combined list.

    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
    • Life insurance
    • 401k retirement plan
    • License and certification reimbursement
    • Continuing Education
    • Referral bonus
    But there are duplicates (Medical benefits vs Day One Health Insurance, etc.). The posting lists them separately. I should preserve all substantive information, but not duplicate. However, the rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should include both lists? But they are essentially the same benefits. The first list is more detailed. The second list is a summary. I'll include the first list as it's more detailed, and maybe note the second list is a summary. But to preserve all, I could include both but that's redundant. I think it's okay to combine and deduplicate while keeping all unique items. The rule says preserve all substantive information, not necessarily duplicate lines. I'll combine unique items. Let's list unique benefits from both: - Day One Health Insurance (with buy-up options) - Dental & Vision Insurance (or separate Dental benefits, Vision benefits) - 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 (maybe same as Day One Health Insurance) - Dental benefits - Vision benefits - Life insurance (duplicate) - 401k retirement plan (duplicate) - License and certification reimbursement (similar to Licensure & CEU Reimbursement) - Continuing Education (similar to Continuing Education Resources) - Referral bonus (duplicate) I'll keep the more detailed descriptions from the first list and add any unique from second. But "Medical benefits" might be same as "Day One Health Insurance". I'll include both as separate items? Might be okay. Better to present as two sublists? But the rule says use
    • for any list. Could have two lists under Benefits with subheadings? But only

      for section headings. Could use

      ? Not specified. The rules only mention

      for section headings. Could use

      for subheadings? Not ideal. I'll just create one list with all items, but avoid exact duplicates. I'll include both "Day One Health Insurance (with buy-up options)" and "Medical benefits" as separate if they are distinct. But likely same. I'll include the first list as it's more descriptive, and then add any from second that are not covered. The second list has "License and certification reimbursement" which is similar to "Licensure & CEU Reimbursement". "Continuing Education" vs "Continuing Education Resources". "Referral bonus" vs "Referral Bonuses". So essentially same. I'll just use the first list (What You Can Expect) as it's more detailed, and maybe add a note that benefits also include medical, dental, vision, etc. But to preserve all, I'll include both lists but separate with a paragraph? The rule says use

      • for any list of duties/requirements/benefits. Could have two
        s. I'll do:

        Benefits

        Comprehensive benefits package includes:

        • 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

        Additional benefits:

        • Medical benefits
        • Dental benefits
        • Vision benefits
        • Life insurance
        • 401k retirement plan
        • License and certification reimbursement
        • Continuing Education
        • Referral bonus
        But that's repetitive. However, the posting has both sections. I'll keep both to preserve all information. Now About Anders Group: company description. I'll create a section "About the company" or "About Anders Group". Since the rules