Travel Nurse RN - PACU - Post Anesthesia Care - $2,683 per week

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc as headings; can fold minor metadata into short

or drop it. Must preserve all substantive info; remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must not invent or summarize away detail. Must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. Let's parse the posting: - Trustaff is seeking a travel nurse RN PACU - Post Anesthesia Care for a travel nursing job in Elmira, New York. - Job Description & Requirements - Specialty: PACU - Post Anesthesia Care - Discipline: RN - Start Date: 10/11/2026 - Duration: 13 weeks - 40 hours per week - Shift: 8 hours, evenings - Employment Type: Travel - Also known as recovery room nurses, post-anesthesia care unit or PACU nurses care for patients who are recovering from anesthesia after surgery. They monitor post-operation vital signs, assess levels of consciousness, and carefully observe patients for any side effects from anesthesia. - Trustaff Job ID #2180247. - Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - Posted job title: PACU - About Trustaff (paragraph) - Benefits section: Weekly pay, Guaranteed Hours, Wellness and fitness programs, Referral bonus, Medical benefits, Dental benefits, Vision benefits We need to produce sections: About the role (maybe description of role), Responsibilities (list duties), Requirements (maybe specialty, discipline, start date, duration, hours, shift, employment type?), Qualifications (maybe RN license?), Skills (maybe monitoring vitals, assessing consciousness, observing side effects), Benefits (list), Pay (maybe mention pay package based on 8 hour shifts and 40 hours per week with tax-free stipend amount to be determined - but that's vague; it's not a specific amount, but it's still some info. The rule: do NOT include Pay section unless posting actually states them. It does state "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's not a specific amount, but it's still stating something about pay. However the instruction says: 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. Here we have some info: based on 8 hour shifts and 40 hours per week, tax-free stipend amount to be determined. That's somewhat placeholder (amount to be determined). Might be considered filler? It says "tax-free stipend amount to be determined." That's placeholder. The phrase "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation)" is somewhat specific about shift and hours but not actual pay. The rule says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "tax-free stipend amount to be determined" is similar to TBD. So maybe we should not include Pay section because it's not a concrete amount. However we could include Pay section with the info we have? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay package, albeit vague. But it's still stating something. However the instruction also says: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The Pay section would contain that placeholder text. So better to omit Pay section. Schedule: we have shift: 8 hours, evenings; 40 hours per week. That's specific. So we can include Schedule section with that info. Benefits: we have list: Weekly pay, Guaranteed Hours, Wellness and fitness programs, Referral bonus, Medical benefits, Dental benefits, Vision benefits. That's specific. So include Benefits. About the role: we have description of PACU nurses duties. Could be About the role or Responsibilities. We need to decide sections. We have: "Also known as recovery room nurses, post-anesthesia care unit or PACU nurses care for patients who are recovering from anesthesia after surgery. They monitor post-operation vital signs, assess levels of consciousness, and carefully observe patients for any side effects from anesthesia." That's responsibilities/duties. We also have description of Trustaff (About Trustaff) which is about the company, not the role. Could be "About the role" maybe not. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (maybe a brief summary of the role), Responsibilities (list of duties), Requirements (maybe specialty, discipline, start date, duration, hours, shift, employment type), Qualifications (maybe RN license?), Skills (maybe monitoring vitals, assessing consciousness, observing side effects). But we must not invent or summarize away detail. We need to preserve all substantive information. So we need to include all specifics: Specialty: PACU - Post Anesthesia Care; Discipline: RN; Start Date: 10/11/2026; Duration: 13 weeks; 40 hours per week; Shift: 8 hours, evenings; Employment Type: Travel; Location: Elmira, New York (mentioned at start). Also the job description: monitoring vital signs, assessing consciousness, observing side effects. We also have Trustaff description (About Trustaff) which is about the company; maybe we can put that under "About Trustaff" but not in the list of allowed headings. The allowed headings are limited to those examples; but we could still use other headings? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, but we should likely stick to those. It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those headings only. So we need to map content to those headings. Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include those with real specific content. Let's see what we have for each: - About the role: Could be a brief summary: "Travel nurse RN PACU - Post Anesthesia Care position in Elmira, New York." That's specific. Also maybe mention that it's a travel nursing job. That's substantive. - Responsibilities: list duties: monitor post-operation vital signs, assess levels of consciousness, carefully observe patients for any side effects from anesthesia. Also maybe "care for patients recovering from anesthesia after surgery." That's from description. - Requirements: Could include specialty, discipline, start date, duration, hours per week, shift, employment type, location. Also maybe RN license implied. But we need to not invent. So we can list: Specialty: PACU - Post Anesthesia Care; Discipline: RN; Start Date: 10/11/2026; Duration: 13 weeks; Hours: 40 per week; Shift: 8 hours, evenings; Employment Type: Travel; Location: Elmira, New York. - Qualifications: Could be RN license, maybe BLS/ACLS? Not mentioned. So we might not have specific qualifications beyond RN discipline. Could we put "RN license" as qualification? It's implied by discipline RN. But we should not invent. The posting does not explicitly state qualifications like "active RN license". It says Discipline: RN. That could be considered a qualification. But we already used discipline under Requirements. Might be better to put Qualifications as "Active RN license" but that's not explicitly stated. Safer to omit Qualifications if no explicit content. - Skills: Could be monitoring vital signs, assessing consciousness, observing side effects. Those are skills. So we can list those. - Benefits: list: Weekly pay, Guaranteed Hours, Wellness and fitness programs, Referral bonus, Medical benefits, Dental benefits, Vision benefits. - Pay: we have vague statement; maybe we omit. - Schedule: we have shift: 8 hours, evenings; 40 hours per week. That's schedule. Thus we will include sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule. Possibly also Qualifications if we can derive from discipline RN? But we already used discipline in Requirements. Could we put Qualifications as "RN license"? Might be considered inventing. Better to omit. Now we need to format:

About the role

then

...

for prose. For lists, use

• . We must not repeat job title as heading. The job title is PACU - Post Anesthesia Care RN? Actually posted job title: PACU. We must not repeat it as heading. We'll not. We must not put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can drop Job ID. We must remove boilerplate: navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. The posting includes "About Trustaff" paragraph which is not boilerplate but is about the company. Should we include that? It's not in allowed headings but could be part of About the role? Actually About the role is about the role, not the company. The About Trustaff paragraph is about the company, not the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. Where can we put it? Possibly under About the role? But that's about the role, not the company. However we could treat About the role as including both role and company info? The examples list About the role as a heading; we could put the Trustaff description there as it's about the employer. But the heading is About the role, not About the company. However 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 use those for section headings. It might be okay to use About the role to include both role and company overview. But to be safe, we could include a separate heading like "About Trustaff" but that's not in the list. The instruction says use

  for section headings (e.g. ...). It doesn't say you cannot use other headings, but it's implied to use those. Safer to stick to those headings and incorporate the Trustaff description under About the role or maybe under Responsibilities? Not appropriate. Perhaps we can put it under About the role as a brief description of the employer. The role is a travel nurse position with Trustaff; describing Trustaff is relevant to the role. So we can include that. Thus About the role paragraph: "Trustaff is seeking a travel nurse RN PACU - Post Anesthesia Care for a travel nursing job in Elmira, New York. Trustaff’s nurse-first attitude ... (the paragraph about Trustaff)." We'll include the Trustaff description as given. Now Responsibilities: list duties. Requirements: list specifics. Skills: list skills (monitoring vital signs, assessing