Jobs · Healthcare · Ohio

Travel Polysomnographer - $1,786 per week

Trustaff · Delaware, OH · 4 days 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 sections: - About the role / Job Description: There's a description of what a Polysomnographic Technologist does. - Requirements: The posting mentions specialty, discipline, start date, duration, hours per week, shift, employment type. Also mentions "Polysomnographic Techs must be well-versed in polysomnographic testing..." but that's more description. There's no explicit requirements list like certifications, experience, etc. However, the job title includes (RPSGT) which suggests Registered Polysomnographic Technologist certification. But the posting doesn't explicitly state requirements. I should include what's there: maybe "Requirements" section with the details like specialty, discipline, start date, duration, hours, shift, employment type. But those are more job details than requirements. The user said: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I need to map content to appropriate headings. Let's parse the posting: "Trustaff Allied is seeking a travel Polysomnographer for a travel job in Delaware, Ohio." - This is intro. "Job Description & Requirements" - heading in original. "Specialty: Polysomnographer Discipline: Allied Health Professional Start Date: 11/02/2026 Duration: 13 weeks 36 hours per week Shift: 12 hours, nights Employment Type: Travel" - These are job details. "As a Polysomnographic Technologist, or Registered Sleep Tech, you'll help perform sleep studies for patients with suspected sleep disorders. Polysomnographic Techs must be well-versed in polysomnographic testing, so you must be able to explain the procedure to the patient and walk them through the process step-by-step. Sleep Techs must then be able to analyze and score the study results." - This is responsibilities/description. "Trustaff Allied Job ID #2181473. Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. Posted job title: Polysomnographer (RPSGT)" - Metadata, pay info. "About Trustaff Allied" - company description. "You decide when and where you want to work Enjoy industry-leading pay, benefits, and bonuses Experience new people and places Grow your clinical skills and expand your experience" - Benefits/perks. "Travel healthcare lets you take your professional career to the next level while maintaining your flexibility and freedom. At Trustaff, we put you first, so you never have to compromise your work or pay. We are proud to have one of the highest nurse retention rates in the country. Some of the other reasons people choose us include:" - More company info. "Priority access to thousands of travel healthcare jobs Industry-leading pay Guaranteed weekly hours Experienced recruiters Comprehensive benefits, including medical, dental, and vision 401k with employer match Assistance with travel, compliance, and housing Great bonuses for completions, referring friends, and more" - List of benefits/perks. "Benefits Dental benefits Medical benefits Vision benefits Guaranteed Hours Referral bonus" - Explicit benefits list. Now, rules: - Use

for section headings. - Use
  • for lists. - Use

    for prose. - Do NOT repeat job title as heading (page already shows it). So no heading for "Polysomnographer". - 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 cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. - Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and 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, decide sections: 1. About the role (or Job Description) - includes the paragraph about duties. 2. Responsibilities - could be same as above, but the paragraph describes responsibilities. Could make a Responsibilities section with list? The paragraph is prose. Could keep as prose under About the role. 3. Requirements - The posting doesn't have explicit requirements list. It has job details (specialty, discipline, start date, duration, hours, shift, employment type). Those are more like "Job Details" or "Schedule". The user example headings include "Schedule". Could create a "Schedule" section with those details. Also "Requirements" might be empty. Better to not create empty sections. 4. Qualifications - Not explicitly stated. 5. Skills - Not explicitly stated. 6. Benefits - There is a Benefits section with list. Also the earlier list includes benefits. Should combine. 7. Pay - The posting says "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's specific pay info. Should include Pay section. 8. Schedule - The shift details: 12 hours, nights, 36 hours per week, 13 weeks duration. Could be Schedule section. Also there is "About Trustaff Allied" - company description. Could include as "About the Company" or similar. But the user didn't list that as example heading. However, they said "e.g." so we can add other relevant headings. But prefer few substantive sections. The company description is boilerplate? It's specific to Trustaff Allied. Might be considered boilerplate but it's part of the posting. The rule: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Company description might be considered marketing boilerplate. But it's part of the job posting. I think we should include it as "About the Company" or fold into a paragraph. However, the user said "Preserve ALL substantive information". The company description is substantive? It's generic but specific to this agency. I'll include it as a section "About Trustaff Allied" with prose and list. But the user said "Prefer a few substantive sections over many thin ones." So maybe combine company info into a single section. Let's structure: - About the Role (or Job Description) - includes the paragraph about duties. - Responsibilities - could be a list extracted from the paragraph? The paragraph says: "help perform sleep studies for patients with suspected sleep disorders", "explain the procedure to the patient and walk them through the process step-by-step", "analyze and score the study results". Could make a list. But the rule: use

    • for any list of duties/requirements/benefits. The paragraph is prose, but we can convert to list. However, "Preserve ALL substantive information; do NOT invent or summarize away detail." Converting to list might be okay as long as we keep all details. But the original is prose. Could keep as prose under About the Role. I'll keep as prose. - Job Details (or Schedule) - include specialty, discipline, start date, duration, hours per week, shift, employment type. Could be a list. - Pay - include pay package details. - Benefits - include the benefits list (dental, medical, vision, guaranteed hours, referral bonus) and also the earlier list (priority access, industry-leading pay, guaranteed weekly hours, experienced recruiters, comprehensive benefits, 401k, assistance, bonuses). But note "Industry-leading pay" is also in pay. Might duplicate. The explicit "Benefits" heading at the end lists: Dental benefits, Medical benefits, Vision benefits, Guaranteed Hours, Referral bonus. The earlier list includes more. I'll combine into one Benefits section with all unique items. - About Trustaff Allied - company description. Now, metadata: Job ID #2181473 and posted job title. Fold into a short

      maybe at the end or beginning. The rule: "fold minor metadata into a short

      or drop it." I'll include a

      with Job ID and posted title. Also, the start date is 11/02/2026 (future). That's specific. Now, ensure no filler. For Pay, the posting says "tax-free stipend amount to be determined." That's specific, not filler. So include. For Schedule, we have specific shift details. Now, write HTML. Sections:

      About the Role

      As a Polysomnographic Technologist, or Registered Sleep Tech, you'll help perform sleep studies for patients with suspected sleep disorders. Polysomnographic Techs must be well-versed in polysomnographic testing, so you must be able to explain the procedure to the patient and walk them through the process step-by-step. Sleep Techs must then be able to analyze and score the study results.

      Job Details

      • Specialty: Polysomnographer
      • Discipline: Allied Health Professional
      • Start Date: 11/02/2026
      • Duration: 13 weeks
      • Hours per Week: 36
      • Shift: 12 hours, nights
      • Employment Type: Travel

      Pay

      Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined.

      Benefits

      • Dental benefits
      • Medical benefits
      • Vision benefits
      • Guaranteed hours
      • Referral bonus
      • Priority access to thousands of travel healthcare jobs
      • Industry-leading pay
      • Guaranteed weekly hours
      • Experienced recruiters
      • Comprehensive benefits, including medical, dental, and vision
      • 401k with employer match
      • Assistance with travel, compliance, and housing
      • Great bonuses for completions, referring friends, and more
      But note: "Industry-leading pay" and "Guaranteed weekly hours" appear in both lists. Also "Comprehensive benefits, including medical, dental, and vision" duplicates the specific benefits. Should we deduplicate? The rule: preserve all substantive information. But duplication is not needed. However, the posting has two separate lists. The first list under "Some of the other reasons people choose us include:" includes those items. The second under "Benefits" includes specific benefits. I think we should include all unique items. But "Industry-leading pay" is not a benefit per se, but it's listed. I'll include all unique items, but avoid exact duplicates. "Guaranteed weekly hours" vs "Guaranteed hours" similar. I'll keep both but maybe combine. However, the rule: do not summarize away detail. So keep both? Might be okay to keep as separate list items. But they are essentially same. I'll keep as they appear in the posting, but maybe combine into one list with all items from both sections. The user said "Preserve ALL substantive information". So include all. But the list under "Benefits" heading is explicit. The

Similar jobs