Jobs · Healthcare · Washington

Travel Respiratory Therapist - $2,150 per week

Triage Staffing | Healthcare Staffing · Wenatchee, WA · 1 wk ago
On-siteHealthcareInternship
The user wants me to reformat a job posting into clean semantic HTML. Let me analyze the content and apply the rules. First, identify the job title: "Travel Respiratory Therapist" - but the rule says do NOT repeat the job title as a heading (the page already shows it). So I won't include an h3 for the title. Now, sections to include based on content: 1. About the role / Job Description - there's a description of the position: travel Respiratory Therapist in Wenatchee, WA, start date, duration, hours, shift, etc. This could be "About the role" or "Job Details". The rule says use h3 for section headings like "About the role". I'll create an "About the role" section with prose and maybe a list for key details. 2. Requirements / Qualifications - The posting doesn't explicitly list requirements like certifications, experience, etc. It mentions "Respiratory Therapist" specialty and discipline. But no specific requirements listed. Might not have enough for a Requirements section. 3. Benefits - There's a detailed benefits list. That should be a section with ul/li. 4. About Triage Staffing - There's a paragraph about the company. Could be "About the company" or "About Triage Staffing". The rule says headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". "About the company" isn't listed but could be considered similar. However, 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 might be okay. But I should only include sections with real content. The company description is substantive. 5. Pay / Schedule - The posting mentions "Competitive, custom pay packages", "Weekly paychecks via direct deposit", "Guaranteed hours", "36 hours per week", "Shift: 12 hours, nights". That could be a "Pay" and "Schedule" section. But the rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state some pay info (competitive custom pay packages, weekly paychecks) and schedule (36 hours/week, 12H nights). However, "competitive, custom pay packages" is vague. The rule says never emit a heading followed by filler/placeholder text like "commensurate with experience", "not specified", etc. "Competitive, custom pay packages" might be considered filler? But it's a statement. Also "Weekly paychecks via direct deposit" is specific. "Guaranteed hours" is specific. So maybe include a "Pay & Schedule" section? But the example headings are separate: Pay, Schedule. Could combine or separate. I'll create a "Pay" section with the pay details and a "Schedule" section with hours/shift. But the rule: "Prefer a few substantive sections over many thin ones." So maybe combine pay and schedule into one section? Or keep separate if enough content. Let's list all substantive content: - Job details: specialty, discipline, start date, duration, hours per week, shift, employment type, location. This is metadata about the job. Could be in "About the role" as a list. - Company description: "At Triage, we prefer to be real..." That's prose. - Benefits: list of benefits. - Pay info: "Competitive, custom pay packages", "Weekly paychecks via direct deposit", "Guaranteed hours", "Earned vacation bonuses for time worked", "Paid holidays". Some of these are benefits, but pay-related. - Schedule: "36 hours per week", "Shift: 12 hours, nights". - Other: "Facility cancelling protection", "In-house compliance...", "Clinical liaison team...", "Mentoring program...". These are more about company offerings, could be in "About Triage Staffing" or "Benefits". The benefits list already includes many items. The company description includes some of these as bullet points in the "offering:" list. Actually the posting has a bullet list under "offering:" which includes: competitive custom pay packages, one point of contact, reliable recruiter, in-house compliance, clinical liaison team, mentoring program, and more. Then a separate "Benefits:" list. So there are two lists: one under "offering:" (company perks) and one under "Benefits:" (employee benefits). I should include both. Thus sections: - About the role (job details) - About Triage Staffing (company description and offerings) - Benefits (the benefits list) - Pay (pay details from offerings and benefits) - Schedule (hours and shift) But Pay and Schedule might be thin. Let's see. Pay: "Competitive, custom pay packages", "Weekly paychecks via direct deposit", "Guaranteed hours", "Earned vacation bonuses for time worked", "Paid holidays". That's 5 items. Could be a list. Schedule: "36 hours per week", "Shift: 12 hours, nights". That's two items. Could be a list. But the rule says never create Pay/Schedule sections unless the posting actually states them. It does state them. However, "competitive, custom pay packages" is somewhat generic. But it's stated. I'll include. Alternatively, combine Pay and Schedule into "Compensation & Schedule". But the example headings are separate. I'll follow the example headings: "Pay" and "Schedule". Now, the job ID and posted job title: "Triage Staffing Job ID #AN9NNW7A. Posted job title: Cardiopulmonary: Respiratory Therapy" - rule says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So I'll include a short paragraph at the top with that metadata. Also, "Apply for specific facility details." - that's application instruction, remove. Now, structure: Start with a short paragraph for metadata: job ID, posted title, location, start date, etc. But the job details are also in the "About the role". I'll include a brief intro paragraph with key metadata, then sections. Let's draft HTML. First, a paragraph: "Triage Staffing Job ID #AN9NNW7A. Posted title: Cardiopulmonary: Respiratory Therapy. Location: Wenatchee, WA. Start: 11/09/2026. Duration: 13 weeks. Employment type: Travel." Then sections. Section 1: About the role - Prose: "Triage Staffing is seeking a travel Respiratory Therapist for a travel job in Wenatchee, Washington." - List of details: specialty, discipline, start date, duration, hours per week, shift, employment type. But the rule says use

  • for any list of duties/requirements/benefits, and

    for prose. So for job details, a list is appropriate. Section 2: About Triage Staffing - Prose: the paragraph about being real. - List of offerings: the bullet points under "offering:". Section 3: Benefits - List of benefits from the "Benefits:" section. Section 4: Pay - List of pay-related items: competitive custom pay packages, weekly paychecks via direct deposit, guaranteed hours, earned vacation bonuses, paid holidays. Section 5: Schedule - List: 36 hours per week, 12-hour night shifts. But note: "Guaranteed hours" and "Earned vacation bonuses" and "Paid holidays" are also in the Benefits list. The Benefits list includes: "Day One comprehensive...", "Day One 401(k)...", "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...", "Continuing education...", "Workers comp...", "Top-rated professional liability insurance", "Company provided housing options", "Referral bonus...". So many of these are benefits. The "offering:" list includes "Competitive, custom pay packages", "One point of contact...", "A reliable recruiter...", "In-house compliance...", "Clinical liaison team...", "Mentoring program...", "And more". So there is overlap. I should not duplicate. The "Benefits:" section is explicitly labeled "Benefits:". The "offering:" list is part of the company description. I'll keep them separate: "About Triage Staffing" includes the offerings list, "Benefits" includes the benefits list. Pay and Schedule can be derived from both, but to avoid duplication, I'll include Pay and Schedule only if they have unique info not in Benefits. However, "Weekly paychecks via direct deposit" and "Guaranteed hours" appear in Benefits. "Competitive, custom pay packages" appears in offerings. "Earned vacation bonuses" and "Paid holidays" appear in Benefits. So Pay section would duplicate. Schedule info appears in job details. So maybe skip separate Pay and Schedule sections, and just include the job details in About the role, and the benefits in Benefits. The company offerings in About Triage Staffing. But the rule says "include a section ONLY when the posting has real, specific content for it". The posting has specific content for Pay? It mentions "Competitive, custom pay packages" and "Weekly paychecks via direct deposit". That's specific. But it's also in benefits. However, the user might expect a Pay section if pay is mentioned. The example headings include Pay. I'll include a Pay section with the pay-specific items, but avoid duplicating benefits. I'll include: "Competitive, custom pay packages", "Weekly paychecks via direct deposit", "Guaranteed hours". But "Guaranteed hours" is also a benefit. Hmm. Better to follow the posting's structure: The posting has "offering:" list (company perks) and "Benefits:" list (employee benefits). I'll create two sections: "What We Offer" (for the offerings) and "Benefits" (for the benefits). And "About the Role" for job details. And "About Triage Staffing" for the company philosophy paragraph. But the rule says headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "What We Offer" is not in the example, but it's similar to "Benefits". However, the offerings are not exactly benefits; they are company services. I'll use "Company Offerings" or "What We Offer". But to stick to the example, maybe "Benefits" covers both? The example includes "Benefits". The posting has two distinct lists. I'll create "Company Offerings" and "Benefits". 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, but says "e.g." So I can use other headings. However, "Prefer a few substantive sections over many thin ones." So maybe combine company offerings and benefits into one "Benefits & Offerings" section? But they are distinct. I'll keep separate. Let's decide on sections: 1. About the role (job details) 2. About Triage Staffing (company philosophy) 3. Company Offerings (the bullet list under "offering:") 4. Benefits (the bullet list under "Benefits:") 5. Pay (maybe not, as pay info is in offerings and benefits) 6. Schedule (maybe not, as schedule is in job details) But the job details include schedule. So I'll

Similar jobs