Jobs · Management · Washington

Travel RRT - Make $1,857 - $2,055/week

Aya Healthcare · Walla Walla, WA · 3 days ago
On-siteManagementInternship
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: - Job Details: Profession, Pay, Assignment Length, Shift, Schedule, Openings, Start Date, Charting System - Requirements: Experience, Required Certifications & Skills (Skills list, Certifications list) - Facility & Unit Information: Facility Type, Charting Experience, Facility Level Trauma, Facility Bed Count - Aya Delivers: Benefits and company info 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/requisition numbers as headings - 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 - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment, no /, no markdown code fences Now, let's map the content to sections. The posting has: - Pay: $1857 to $2055 weekly (specific) - Schedule: Nights, 3, 12-Hour 19:00 - 07:00 (specific) - Assignment Length: 13 weeks - Start Date: 11/30/2026 - Charting System: Epic - Requirements: Experience 1 Year, Skills list, Certifications list - Facility info: Critical Access, Charting Experience Yes, Level 3 Trauma, 85 beds - Aya Delivers: Benefits (medical, dental, vision, life insurance day one, 24 days coverage between assignments, 401k match, paid housing or stipend, paid sick time, CEUs, licensure/relocation reimbursements) I should create sections for: - Pay (since specific) - Schedule (since specific) - Assignment Details (could combine assignment length, start date, shift, openings, charting system) - Requirements (experience, skills, certifications) - Facility Information - Benefits (from Aya Delivers) But note: "About the role" might be appropriate for the general description. However, the posting starts with "Aya Healthcare has an immediate opening..." which is more of an intro. The user said "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "RRT in Walla Walla, WA". The first paragraph is marketing fluff. I could include a brief "About the role" section with the opening paragraph? But the rule says "Preserve ALL substantive information". The first paragraph is not very substantive. However, the "Job Details" section has many specifics. I think I'll create sections: - Pay - Schedule - Assignment Details - Requirements - Facility Information - Benefits But the user said "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can use those exact headings or similar. Let's structure:

    Pay

    $1,857 to $2,055 weekly (includes taxable wages and tax-free expense reimbursements)

    Schedule

    Nights, 3 × 12-hour shifts (19:00–07:00)

    Assignment Details

    • Length: 13 weeks
    • Start date: 11/30/2026
    • Openings: 1
    • Charting system: Epic

    Requirements

    Minimum 1 year of experience.

    Skills

      ... list of skills ...

    Certifications

      ... list of certs ...
    But the user said use

    for section headings. Should I use

    for subsections? The rule says "use

    for section headings". It doesn't forbid

    for subsections. But to keep it simple, maybe just use

    for main sections and use
      for lists. The skills and certifications are part of Requirements. I could make them separate

      sections: "Skills" and "Certifications". But the rule says "Prefer a few substantive sections over many thin ones." So maybe keep Requirements as one section with sub-lists. However, the example headings include "Skills" as a possible heading. The posting has a long list of skills and a list of certifications. They are substantive. I could make separate sections for Skills and Certifications. But the rule says "include a section ONLY when the posting has real, specific content for it". Both have real content. But "Prefer a few substantive sections over many thin ones." So maybe combine under Requirements. Let's see: The posting has "Requirements Experience: 1 Year Required Certifications & Skills Skills: ... Certifications: ...". So it's all under Requirements. I'll make one Requirements section with two sub-lists. But the user said "use

      for section headings". If I use

      for Requirements, then for Skills and Certifications I could use

      or just labels. However, the output should be semantic HTML. Using

      is fine. But the instruction says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It lists Skills as an example heading. So maybe they expect Skills as a separate

      section. But then we'd have many sections. Let's decide: I'll create sections for Pay, Schedule, Assignment Details, Requirements (with experience), Skills, Certifications, Facility Information, Benefits. That's 8 sections. Might be okay. But the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states Pay, Schedule, Benefits (in Aya Delivers). So those are fine. Now, the "Aya Delivers" section is mostly benefits and company perks. I'll extract the benefits list. Also, note: "Pay listed above includes taxable wages and tax-free expense reimbursements." I'll include that in Pay section. Now, remove boilerplate: "Aya is an Equal Employment Opportunity ("EEO") Employer and welcomes all to apply. #HP" - remove. Also remove "Aya Delivers: The most jobs in the industry..." marketing fluff, but keep the actual benefits. Let's parse the benefits from Aya Delivers: - Exceptional benefits, including premium medical, dental, vision and life insurance beginning day one of your assignment. - Keep insurance coverage for up to 24 Days between assignments. - A generous 401(k) match. - Paid company housing (we’ll help you bring your pets along, too!) or a generous housing stipend, if eligible. - Paid sick time in accordance with all applicable state, federal, and local laws. (details about accrual) - Access to unlimited continuing education units online. - Licensure, relocation and other reimbursements, when applicable. Also: "Expedited licensing and streamlined compliance." "Expert career guidance." "Best-in-class support system." These are more marketing. But they are substantive? The rule says preserve ALL substantive information. I'll include them as benefits or perks. I'll create a Benefits section with a list. Now, Facility Information: Facility Type: Critical Access, Charting Experience: Yes, Facility Level Trauma: Level 3, Facility Bed Count: 85. I'll make a section. Now, the opening paragraph: "Aya Healthcare has an immediate opening for the following position: RRT in Walla Walla, WA. We’ll work with you to build the healthcare career of your dreams. Whether you want a job close to home or across the country, we’ve got you." This is marketing. But it's the only description of the role. Could be "About the role". I'll include a brief About the role section with that paragraph. But the rule: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "RRT in Walla Walla, WA". The paragraph mentions it. I can include a

      under About the role. Now, let's write the HTML. I'll structure:

      About the role

      Aya Healthcare has an immediate opening for an RRT in Walla Walla, WA. We’ll work with you to build the healthcare career of your dreams, whether you want a job close to home or across the country.

      Pay

      $1,857 to $2,055 weekly (includes taxable wages and tax-free expense reimbursements)

      Schedule

      Nights, 3 × 12-hour shifts (19:00–07:00)

      Assignment Details

      • Length: 13 weeks
      • Start date: 11/30/2026
      • Openings: 1
      • Charting system: Epic

      Requirements

      Minimum 1 year of experience required.

      Skills

      • Adult Critical Care
      • Aerosol set up mask
      • Albuterol
      • Atrovent
      • Basic EKG
      • BiPAP
      • Combivent
      • CPAP
      • Extubation
      • Flovent
      • Hand held
      • High Flow Nasal Cannula (HFNC)
      • Inhaled steroids
      • Interpretation of Arterial Blood Gases (ABGs)
      • Isuprel
      • Lidocaine
      • Medihaler
      • Metered Dose Inhaler (MDI)
      • Nasal airway placement
      • Nasal airway suctioning
      • Oral airway placement
      • Oral/nasal Suctioning
      • Aerosol set up trach
      • Emergency Department
      • Perforomist
      • Pulmicort
      • Pulmonary Hygiene
      • Racemic epinephrine
      • Spiriva
      • Sputum specimen collection
      • T-piece
      • Terbutaline Sulfate
      • Tobramycin
      • Trach collar
      • Tracheostomy care/management
      • Troubleshooting high pressure alarms
      • Weaning from mechanical ventilation
      • Xopenex

      Certifications

      • ACLS
      • BLS
      • PALS

      Facility Information

      • Facility type: Critical Access
      • Charting experience: Yes
      • Trauma level: Level 3
      • Bed count:

Similar jobs