Travel CVOR Technologist - $2,287 per week

The user wants me to reformat a job posting into clean semantic HTML. Let me analyze the content and apply the rules. First, identify sections: - The posting has a job description with details like specialty, discipline, start date, duration, hours, shift, employment type, location. - There's an "About Triage Staffing" section with company description. - There's a "Benefits" section with a list of benefits. Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). - Use

• for lists,

  for prose. - Do NOT repeat job title as heading (page already shows it). - 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/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. - 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. Now, parse the content: The posting starts with "Triage Staffing is seeking a travel CVOR Technologist for a travel job in Wausau, Wisconsin." That's a summary. Then "Job Description & Requirements" with bullet-like lines: Specialty: CVOR Technologist Discipline: Allied Health Professional Start Date: 11/02/2026 Duration: 9 weeks 40 hours per week Shift: 8 hours, days Employment Type: Travel Travel Nursing: Cardiovascular OR Tech Wausau Location: Wausau Start Date: 11/2/2026 Shift Details: 8H Days 40 hours per week Length: 9 WEEKS Apply for specific facility details. CVOR Tech Triage Staffing Job ID #67MCXTWK. Posted job title: Cardiovascular OR Tech This is metadata about the job. Could be folded into a short

  or a list. Since it's structured, maybe a

  of details. But the rule says use
  • for any list of duties/requirements/benefits. This is not duties/requirements/benefits, but job details. Could be a "Job Details" section. However, the allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Job Details" is not in that list. But the rule says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., so maybe we can use other headings? But the instruction: "include a section ONLY when the posting has real, specific content for it". The posting has job details. Could be "About the role" or "Schedule". The schedule info is there: shift, hours, duration. Could create a "Schedule" section. Also "About the role" could include specialty, discipline, location. But the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states schedule details (shift, hours, duration). So we can create a Schedule section. Also Benefits section is explicitly listed. The "About Triage Staffing" is company description. Could be "About the Company" but not in the example headings. However, 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, but we should stick to those if possible. "About the role" could encompass company description? Not really. The company description is about the staffing agency, not the role. But the posting includes it as part of the job posting. The user wants to preserve all substantive information. So we need to include it. Could create a section "About Triage Staffing" but that's not in the example list. However, the rule says "e.g." meaning examples. I think we can use a heading like "About the Company" or "About Triage Staffing". But to be safe, maybe we can put it under "About the role"? That would be misleading. Better to create a heading "About Triage Staffing" as it's substantive content. But the instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings. It says "e.g." So we can use other headings. However, the system might expect only those headings. But the user said "Prefer a few substantive sections over many thin ones." So we can group. Let's think: The job details (specialty, discipline, start date, duration, hours, shift, employment type, location) are all about the role. Could be under "About the role". The schedule details (shift, hours per week, length) could be under "Schedule". The benefits list under "Benefits". The company description under "About the Company" or "About Triage Staffing". But the example headings don't include "About the Company". However, the rule says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be that we should only use those headings. But the posting doesn't have Responsibilities, Requirements, Qualifications, Skills, Pay. It has Benefits and Schedule. It has company description. Could we put company description under "About the role"? That might be okay. But the instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." So Job ID should be folded into a short

    or dropped. We'll include it in a paragraph maybe. Also "Apply for specific facility details." is application instruction, should be removed. Duplicated lines: Start date appears twice, shift details duplicated. We'll deduplicate. Now, let's structure: We'll have: - A paragraph summarizing the job: "Triage Staffing is seeking a travel CVOR Technologist for a travel job in Wausau, Wisconsin." - Section "About the role" with details: specialty, discipline, employment type, location, start date, duration, shift, hours per week. Could be a list. - Section "Schedule" with shift details: 8-hour days, 40 hours per week, 9 weeks. - Section "Benefits" with the list of benefits. - Section "About Triage Staffing" with the company description. But "About the role" and "Schedule" might overlap. The schedule details are part of the role. Could combine into "About the role" and include schedule there. But the rule says we can have a Schedule section if the posting states them. The posting states shift details. So we can have a Schedule section. Let's see the example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So Schedule is allowed. Benefits allowed. About the role allowed. Responsibilities, Requirements, Qualifications, Skills not present. Pay not present. Thus we can have three sections: About the role, Schedule, Benefits. And maybe a company description section. But company description is not in the list. However, it's substantive. Could we put it under "About the role"? That would be weird. Could create a heading "About Triage Staffing" but that's not in the list. The instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use others. But to be safe, maybe we can include it as a subsection under "About the role"? Or just include it as a paragraph before sections? The rule: "Output ONLY the HTML fragment". We can have multiple

    sections. I think it's okay to have a heading "About Triage Staffing" because it's a real section with content. The rule says "include a section ONLY when the posting has real, specific content for it". The posting has real content about Triage Staffing. So we should include it. But the example headings are just examples. The user didn't restrict to only those. So I'll include it. Now, format: - Start with a

    for the opening summary. - Then

    About the role

    with a
    of details. - Then

    Schedule

    with a
    of schedule details. - Then

    Benefits

    with a
    of benefits. - Then

    About Triage Staffing

    with

    for the prose and maybe a

    for the offerings? The company description includes a list: "offering: - Competitive, custom pay packages - One point of contact ..." That's a list. So we can make a
    for those. But note: The company description also has a paragraph before the list: "At Triage, we prefer to be real... Will we work like hell to get you as close to your idea of heaven as possible? Yes. Yes, we will." That's prose. Then "offering:" with bullet points. So we can have a

    for the prose and a

    for the offerings. Now, the benefits list is separate: "Benefits: Day One comprehensive, nationwide insurance plans..." That's a list. We'll make a
    for benefits. Job ID: "Triage Staffing Job ID #67MCXTWK. Posted job title: Cardiovascular OR Tech" - fold into a short

    maybe at the end of About the role or a separate metadata paragraph. The rule says fold minor metadata into a short

    or drop it. We'll include a

    with the job ID and posted title. Also "Apply for specific facility details." remove. Now, ensure we don't duplicate info. The start date appears twice, shift details duplicated. We'll include once. Let's draft HTML. First, opening paragraph:

    Triage Staffing is seeking a travel CVOR Technologist for a travel job in Wausau, Wisconsin.

    Then About the role:

    About the role

    • Specialty: CVOR Technologist
    • Discipline: Allied Health Professional
    • Employment Type: Travel
    • Location: Wausau, Wisconsin
    • Start Date: 11/02/2026
    • Duration: 9 weeks
    • Shift: 8 hours, days
    • Hours per Week: 40

    Job ID: #67MCXTWK | Posted Title: Cardiovascular OR Tech

    But the rule says do NOT put Job ID as heading, fold into short

    . So that's fine. Schedule section:

    Schedule

    • Shift: 8-hour days
    • Hours per Week: 40
    • Assignment Length: 9 weeks
    Benefits section:

    Benefits

    • Day One comprehensive, nationwide insurance plans for health, vision, dental, and life—including a HSA option
    • Day One 401(k