Travel Respiratory Therapist - $1,458 per week

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, identify the job title: "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 present in the posting: - Job Description & Requirements (but this seems like a heading for the whole thing) - Specialty, Discipline, Start Date, Duration, hours per week, Shift, Employment Type - these are metadata details. - Benefits: listed with bullet points. - About the Company: prose. - Uniti Med Job ID #863320 - minor metadata, fold into short p or drop. - Pay package info: "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." This is pay info but not specific numbers; it says "tax-free stipend amount to be determined." The rule: never create Pay section unless posting actually states them. It does state pay package basis but not actual pay. Might include as a short p under a Pay section? But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits, so Benefits section is warranted. Pay: it states pay package basis but not actual pay. Could include a Pay section with that info? The rule says "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')". The pay info says "tax-free stipend amount to be determined." That's essentially TBD. So maybe not include a Pay section. However, the posting does have a line about pay package based on shifts and hours. That's specific about the basis. But the stipend amount is TBD. I think we can include a Pay section with the known details: "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 real content, not filler. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package basis. I'll include a Pay section with that paragraph. Schedule: The posting includes shift: 12 hours, nights, 36 hours per week. That's schedule info. Could create a Schedule section. The rule says never create Schedule section unless posting actually states them. It does state shift and hours. So include Schedule section. Benefits: clearly listed, so Benefits section. About the Company: prose, so About the Company section. Requirements: The posting doesn't have explicit requirements list beyond the metadata (specialty, discipline, etc.). There's no "Requirements" section with bullet points. The "Job Description & Requirements" heading might be a section but the content under it is just metadata lines. Could create a "Requirements" section with those details as a list? But they are not typical requirements like certifications, experience. They are job parameters. Might be better to put them under a "Job Details" or "Assignment Details" section. The rule says use h3 for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "Requirements" for the metadata? But the metadata includes start date, duration, hours, shift, employment type. That's more like "Assignment Details". However, the rule says use h3 for those specific headings. It doesn't forbid other headings, but prefers those. I think we can create a "Requirements" section with the details as a list. But the rule says "Preserve ALL substantive information". So we need to include all those details. Let's structure: - About the role (maybe not, but we have "About the Company" which is about the company, not the role). The posting doesn't have an "About the role" section. It has "Job Description & Requirements" but no description. So maybe skip. - Responsibilities: none listed. - Requirements: could include the specialty, discipline, start date, duration, hours, shift, employment type. But those are not requirements per se. They are job parameters. Might be better to create a "Job Details" section? But the rule says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." so we can use other headings? 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, but we should prefer those. However, we must include a section ONLY when the posting has real, specific content for it. The posting has specific content for Benefits, Pay (maybe), Schedule, About the Company. It also has metadata that could go under "Requirements" or "Qualifications". But there's no explicit qualifications list. The "Specialty: Respiratory Therapist" and "Discipline: Allied Health Professional" are essentially the role. The start date, duration, hours, shift, employment type are assignment details. I think we can create a "Requirements" section with a list of those details. But the rule says "never emit a heading followed by filler/placeholder text". The details are real. Alternatively, we can fold the metadata into a short

at the top. The rule: "fold minor metadata into a short

or drop it." The metadata includes Job ID, start date, duration, hours, shift, employment type. That's minor metadata. So we can put them in a paragraph. Let's see: The posting starts with "Uniti Med is seeking a travel Respiratory Therapist for a travel job in Hartsville, Tennessee." That's a prose intro. Then "Job Description & Requirements" heading, then lines: Specialty, Discipline, Start Date, Duration, 36 hours per week, Shift, Employment Type. Then Benefits list. Then About the Company. Then Uniti Med Job ID. Then Pay package line. Then Posted job title. Then About Uniti Med (duplicate of About the Company?). Then Benefits again (referral bonus, benefits start day 1, employee assistance programs). There's duplication. We need to remove duplicated lines. The benefits list appears twice: once with more details, once with three bullet points. We should combine. Also, "About Uniti Med" seems like a duplicate of "About the Company". We'll keep one. Now, let's decide sections: 1. About the Company (or About Uniti Med) - prose. 2. Benefits - list. 3. Pay - paragraph with pay package basis. 4. Schedule - shift and hours. 5. Maybe "Assignment Details" for start date, duration, employment type? But the rule says use h3 for those example headings. Could use "Requirements" for the metadata? But the metadata includes start date, duration, etc. That's not requirements. Could use "Qualifications"? Not exactly. The rule: "Prefer a few substantive sections over many thin ones." So we can combine metadata into a short paragraph under a "Job Details" heading? But the rule says use h3 for section headings like those examples. It doesn't forbid other headings, but we should use semantic headings. I think we can create a "Job Details" section with a list of the metadata. However, the rule says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those standard headings. But we can also use other headings if needed. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's a guideline. I'll use standard headings where appropriate. Let's map: - Benefits -> Benefits - Pay -> Pay - Schedule -> Schedule - About the Company -> About the Company (or About the Role? but it's about company) - The metadata (specialty, discipline, start date, duration, hours, shift, employment type) could go under "Requirements" or "Qualifications". But they are not requirements for the candidate; they are job parameters. Could be "Assignment Details". But the rule says "never emit a heading followed by filler/placeholder text". If we create a "Requirements" heading and list those, it's not filler. But it might be misleading. Alternatively, we can fold all metadata into a single paragraph at the beginning, as the rule says "fold minor metadata into a short

or drop it." That seems appropriate. The metadata includes: Specialty, Discipline, Start Date, Duration, 36 hours per week, Shift, Employment Type, Job ID. That's minor metadata. We can put them in a paragraph. Then we have substantive sections: Benefits, Pay, Schedule, About the Company. But Schedule is already partially in metadata (shift, hours). The Pay section includes hours per week again. We can have a Schedule section with shift and hours. The metadata paragraph can include start date, duration, employment type, specialty, discipline. Let's craft: First, a paragraph: "This travel Respiratory Therapist position in Hartsville, Tennessee starts on 10/26/2026 for a 13-week assignment. It is a travel role with 36 hours per week on 12-hour night shifts. Specialty: Respiratory Therapist; Discipline: Allied Health Professional." But the rule says "Do NOT repeat the job title as a heading (the page already shows it)". The job title is Respiratory Therapist. We can mention it in the paragraph. Now, sections: - About the Company (from "About the Company" and "About Uniti Med" combined) - Benefits (combine both benefits lists) - Pay (the pay package line) - Schedule (shift and hours) But the Pay line 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 pay info. The Schedule section would duplicate hours and shift. Could combine Pay and Schedule? But the rule says separate sections for Pay and Schedule if they have content. The posting has both. However, the Pay line includes schedule info. But we can still have a Schedule section with shift details. The Pay section can just have the pay package basis. Let's see the benefits: first list: "Day 1 Insurance Cigna medical, MetLife dental and vision insurance License reimbursement for new licenses needed for each assignment Discounts with hotels and rental cars A dedicated recruiter and support team that will help you every step of the way to sure you start on time and have an exceptional experience Referral bonus up to $700". Second list: "Referral bonus Benefits start day 1 Employee assistance programs". We'll combine into one list, removing duplicates. Now, About the Company: two paragraphs: "Finding the right role is about more than just matching skills to a job—it’s about aligning with your goals, values, and the way you want to work. As an award-winning talent partner, we support healthcare professionals through every step of that process, offering meaningful opportunities, clear guidance, and long-term partnership. From our first conversation to your first day on the job (and beyond!), we’re here to help you move forward with confidence." And "Uniti Med meticulously matches your talents to our open needs to ensure the ultimate travel experience. Tell us where you want to go and let our experienced staff lead the way!" We'll combine. Now, output HTML fragment with h3 headings and ul/li for lists, p for prose. We must not include any boilerplate, navigation, legal, EEO, scam warnings, application instructions. The posting doesn't have those