Jobs · OTHR · Washington

Travel CVOR Technologist - $2,216 per week

Triage Staffing | Healthcare Staffing · Bellingham, WA · 1 wk ago
On-siteOTHRInternship
The user wants me to reformat a job posting into clean semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: - About the role (job description) - Requirements/Qualifications - Benefits - Possibly Schedule/Pay details The posting includes: - Job title: CVOR Technologist / Cardiovascular OR Tech - Location: Bellingham, Washington - Start Date: 11/23/2026 - Duration: 13 weeks - Hours: 40 hours per week - Shift: 10 hours, days - Employment Type: Travel - Specialty: CVOR Technologist - Discipline: Allied Health Professional - Job ID: TG9XAUAQ (should fold into a short

or drop) - About Triage Staffing (company description) - Benefits list 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, duplicated lines, application instructions) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no /, no markdown code fences Let me structure: 1. About the role: includes job description, location, start date, duration, hours, shift, employment type, specialty, discipline. Could be a prose paragraph or list. Since there are multiple details, maybe a

    with key details and a list for specifics. 2. Requirements/Qualifications: The posting doesn't explicitly list requirements for the CVOR Tech role. It mentions "Apply for specific facility details." No specific requirements listed. So maybe no Requirements section. 3. Benefits: There's a detailed benefits list. That should be a Benefits section with

    • . 4. About the company: "About Triage Staffing" - could be an "About the company" section, but the allowed headings are limited to: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the company" is not in the list. However, the rule says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests those are examples, but we should stick to those. The company description is substantive but not a standard heading. Could fold into About the role? Or maybe create a section "About the company"? The instruction says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings, but says "Prefer a few substantive sections over many thin ones." The company description is substantive. However, the user might expect only those headings. I think it's safe to include an "About the company" heading? But the rule says "use

      for section headings (e.g. ...)". It's ambiguous. To be safe, I'll include it as a section because it's real content. But the instruction says "include a section ONLY when the posting has real, specific content for it". The posting has "About Triage Staffing" with details. So I'll create a section "About the company" or "About Triage Staffing". However, the example headings don't include that. Might be better to fold into a

      under About the role? But it's a separate paragraph about the company. I'll create a section "About the company" with

      . The rule says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say "only these". So I'll include. But the user might have a strict expectation. Let's see: The system prompt says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". That's a list of typical headings. It doesn't forbid others. I'll include "About the company" as a heading. Alternatively, I could put the company description under "About the role" as a separate paragraph. But the company description is about the staffing agency, not the role. It's separate. I'll create sections: - About the role - About the company - Benefits Schedule details are in the job details (shift, hours). Could be a Schedule section. The posting states: "Shift: 10 hours, days", "40 hours per week". That's schedule info. So I'll create a Schedule section. Pay: The posting mentions "Competitive, custom pay packages" but no specific pay numbers. It says "Weekly paychecks via direct deposit". That's pay-related but not a specific pay rate. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states schedule details, so Schedule section is okay. Pay: it mentions "Competitive, custom pay packages" and "Weekly paychecks via direct deposit". That's some pay info. But is that enough? The rule says "unless the posting actually states them." It states pay frequency and that packages are custom. Could include a Pay section with that info. But the example says "Pay" as a heading. I'll include a Pay section with the details. But the rule also says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Here we have "Competitive, custom pay packages" which is somewhat generic but it's what the posting says. I'll include it. Now, let's draft HTML. First, About the role: include job description, location, start date, duration, hours, shift, employment type, specialty, discipline. Could be a paragraph and a list. I'll do:

      About the role

      Triage Staffing is seeking a travel CVOR Technologist for a travel job in Bellingham, Washington.

      • Specialty: CVOR Technologist
      • Discipline: Allied Health Professional
      • Start Date: 11/23/2026
      • Duration: 13 weeks
      • Hours: 40 hours per week
      • Shift: 10 hours, days
      • Employment Type: Travel

      Apply for specific facility details. Job ID: TG9XAUAQ.

      But the Job ID should be folded into a short

      or dropped. I'll include in a paragraph. Now, About the company:

      About the company

      At Triage, we prefer to be real. Real about expectations—both ours and yours. Real about how a decision you make today could affect your tomorrows. Real about how compensation actually works. Real about how great—or grating—your next supervisor may be. Being real allows everyone at Triage to be ready. Ready to serve you with real honesty. So if that gig near the ocean is really no day at the beach, or that third shift comes with a second-class rate, we tell you. So you can be ready, too. We staff all five major divisions of acute care—nursing, lab, radiology, cardiopulmonary and rehab therapy.

      Then maybe a list of what they offer? The posting says "offering:" and then a list. That could be a list under About the company.
      • Competitive, custom pay packages
      • One point of contact for both travelers and facilities (per division)
      • A reliable recruiter who's got your back throughout your entire assignment
      • In-house compliance and accounting specialists
      • A clinical liaison team available 24/7 to offer medical and professional support and career development
      • A mentoring program that is run and managed by actual clinicians
      • And more
      But the "And more" is filler. Might keep it as it's in the posting. Now Benefits section:

      Benefits

      • Day One comprehensive, nationwide insurance plans for health, vision and dental and life—including a HSA option
      • Day One 401(k) program with employer-matching contributions once eligible
      • Facility cancelling protection—your time is money on and off-the-clock
      • Guaranteed hours
      • Weekly paychecks via direct deposit
      • Earned vacation bonuses for time worked
      • Paid holidays
      • Employee assistance program (EAP)—your mental health is important, too
      • Continuing education, certification and licensing reimbursement
      • Workers comp—because accidents happen
      • Top-rated professional liability insurance
      • Company provided housing options
      • Referral bonus—$750 in your pocket after they've completed a 13-week assignment
      Schedule section:

      Schedule

      • Shift: 10 hours, days
      • Hours per week: 40
      Pay section:

      Pay

      • Competitive, custom pay packages
      • Weekly paychecks via direct deposit
      But note: "Weekly paychecks via direct deposit" appears in both Benefits and Pay. In the posting, it's under Benefits. But it's also pay-related. I'll keep it in Benefits as per the posting. For Pay, I'll only include "Competitive, custom pay packages". However, the posting says "offering: - Competitive, custom pay packages" under About Triage Staffing. That's more about what they offer. The Benefits list includes "Weekly paychecks via direct deposit". So maybe Pay section only with "Competitive, custom pay packages". But that's thin. The rule says never create Pay section unless posting actually states them. It does state "Competitive, custom pay packages". That's a statement about pay. I'll include. But the posting also says "Weekly paychecks via direct deposit" under Benefits. That's pay frequency. Could be in Pay section. I'll include both in Pay section? But they are already in Benefits. To avoid duplication, I'll put pay-related items in Pay section and keep Benefits as is. However, the posting lists "Weekly paychecks via direct deposit" under Benefits. I'll keep it there. For Pay section, I'll just mention "Competitive, custom pay packages". That might be too thin. Maybe omit Pay section and only have Schedule and Benefits. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states schedule and benefits clearly. Pay is mentioned but not detailed. I'll include a Pay section with the one line. Alternatively, I could fold pay into About the company or Benefits. But the user expects Pay section if there is pay info. I'll include. Now, ensure no duplicate headings, no filler. Also, remove "Apply for specific facility details." That's application instruction? It's a line in the job description. The rule says "remove application instructions". "Apply for specific facility details." is an instruction. I'll drop it. Also, "CVOR Tech

Similar jobs