Travel ICU RN - $2,000 per week

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Posting content: - Title: Medical Solutions is seeking a travel nurse RN ICU - Intensive Care Unit for a travel nursing job in Sierra Vista, Arizona. - Job Description & Requirements Specialty: ICU - Intensive Care Unit Discipline: RN Duration: 13 weeks 36 hours per week Shift: 12 hours, nights Employment Type: Travel - Then a paragraph: "We’re seeking talented healthcare professionals whose adventure game is as strong as their clinical game. Those that want flexibility and high pay, we have the positions for you!" - Then list of benefits: bullet list (some lines): Day One Medical, Dental, and Vision with low premiums Day One 401(k) with Company Contribution Personalized Compensation Packages Paid, Private, Fully Furnished, Pet-Friendly Housing Dedicated Recruiter and 24/7 Customer Care Line Per Diem Allowance and Paid Travel Licensure and Certification Reimbursement Free Liability Coverage Voluntary Benefits: Critical Illness, Hospital Indemnity, Accident, and Pet Insurance Equal Employment Opportunity (boilerplate to remove) And More! - Then: "Estimated pay package based on bill rate at time job was posted. Bill rates can change frequently and without notice. Exact pay package may vary based on guaranteed hours, distance being traveled, and customizations available for travelers." - Then: "Medical Solutions Job ID #1180597. 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: ICU (Intensive Care Unit)" - Then About Medical Solutions paragraph (company description). This is boilerplate? It's about the company, maybe we can include as "About the role"? Actually "About the role" is not present; we have "About Medical Solutions". The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to these headings if appropriate. The posting includes "Job Description & Requirements" which could be considered Responsibilities/Requirements. It includes Specialty, Discipline, Duration, hours, shift, employment type. That's more like Requirements/Qualifications. There's no explicit responsibilities list. There's a paragraph about seeking talent (maybe responsibilities). We'll need to decide. We must not repeat the job title as a heading. Also not put Job ID as heading. We need to include sections only when posting has real specific content. So we can have: -

About the role

maybe containing the paragraph about seeking talent and the description? Or we could use

Responsibilities

but there is no explicit responsibilities list. Could combine description into About the role. -

Requirements

or

Qualifications

containing Specialty, Discipline, Duration, hours, shift, employment type. -

Benefits

containing the list of benefits (excluding EEO boilerplate). Should we include "Equal Employment Opportunity" line? It's boilerplate, remove. -

Pay

maybe containing info about pay package based on bill rate, etc. The posting includes "Estimated pay package based on bill rate at time job was posted..." and "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 enough? It mentions pay package but not actual numbers. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package info (though not exact numbers). So we can include Pay section with that prose. -

Schedule

maybe containing shift details: 12 hours, nights, 36 hours per week. That's specific. So we can include Schedule. We must not include sections with filler like "commensurate with experience". Our content is specific enough. We need to use

• for any list of duties/requirements/benefits. For Benefits we have a list; we should output
  • each benefit. For Requirements maybe we can list items as
    • . For Schedule maybe just a

      (since it's not a list). For Pay maybe a

      . We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep all details: Specialty, Discipline, Duration, 36 hours per week, Shift: 12 hours, nights, Employment Type: Travel. Also the paragraph about seeking talent. Also the benefits list exactly as given (excluding EEO). Also the pay package statements. Also the company description? The "About Medical Solutions" paragraph is substantive but maybe not required? It's about the company, not the role. The instruction says preserve ALL substantive information; do not invent or summarize away detail. Should we include it? It's about the company, but it's substantive. However the headings we have are limited to those examples; we could include an

      About the company

      but not in the list. The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive list? It says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not add other headings like About the company. But we must preserve all substantive information; if we omit the company description, we are losing substantive info. However maybe the company description is considered boilerplate? It's not standard boilerplate like EEO; it's a marketing paragraph. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This paragraph is not those. So we should keep it. But we need a heading for it. Could we put it under

      About the role

      ? That might be a stretch but maybe acceptable. The "About the role" heading could contain description of the role and also company info? Might be okay. Alternatively we could not include a heading for it and just put it as a

      without heading? The instruction says use

      for section headings (e.g...). It doesn't say every paragraph must be under a heading, but likely they expect sections. However we could output a

      directly after the fragment without heading? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It doesn't forbid stray

      without heading. But they said "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies if we have a section, we use h3. If we have a paragraph that's not a section, maybe we just put

      . But they also said "Prefer a few substantive sections over many thin ones." So we could combine company description into About the role section. Thus we will have sections: About the role (containing the talent-seeking paragraph and company description), Requirements (or Qualifications) containing specialty etc, Benefits, Pay, Schedule. We need to decide which heading to use for the specialty/details: Could be Requirements or Qualifications. Both are examples. We'll pick Requirements. Now we need to ensure we don't repeat the job title as heading. We'll not. Now we need to remove duplicated lines: The posting includes "Benefits" heading later with a list of benefits (Weekly pay etc). Actually after the company description there is a "Benefits" section with a list: Weekly pay, Holiday Pay, Guaranteed Hours, Continuing Education, 401k retirement plan, Pet insurance, Company provided housing options, Cancelation protection, Wellness and fitness programs, Mileage reimbursement, Referral bonus, Employee assistance programs, Medical benefits, Dental benefits, Vision benefits, Benefits start day 1, License and certification reimbursement, Life insurance, Discount program. This is another benefits list, possibly overlapping with earlier benefits list. We need to preserve ALL substantive information; we must not lose any benefit details. So we need to combine both lists, removing duplicates. Let's extract all benefit items from both sections. First benefits list (after "We’re seeking talented..."): - Day One Medical, Dental, and Vision with low premiums - Day One 401(k) with Company Contribution - Personalized Compensation Packages - Paid, Private, Fully Furnished, Pet-Friendly Housing - Dedicated Recruiter and 24/7 Customer Care Line - Per Diem Allowance and Paid Travel - Licensure and Certification Reimbursement - Free Liability Coverage - Voluntary Benefits: Critical Illness, Hospital Indemnity, Accident, and Pet Insurance - Equal Employment Opportunity (remove) - And More! (maybe not a specific benefit, we can ignore as filler) Second benefits list (under "Benefits" heading): - Weekly pay - Holiday Pay - Guaranteed Hours - Continuing Education - 401k retirement plan - Pet insurance - Company provided housing options - Cancelation protection - Wellness and fitness programs - Mileage reimbursement - Referral bonus - Employee assistance programs - Medical benefits - Dental benefits - Vision benefits - Benefits start day 1 - License and certification reimbursement - Life insurance - Discount program We need to combine and deduplicate. Some items overlap: Medical, Dental, Vision appear in both; 401k vs Day One 401(k) with Company Contribution similar; Pet insurance appears both; Housing options similar; License and certification reimbursement appears both; etc. We should keep unique items, but preserve all substantive info. If we deduplicate, we might lose some nuance (e.g., "Day One Medical, Dental, and Vision with low premiums" vs "Medical benefits", "Dental benefits", "Vision benefits". The first is more specific about Day One and low premiums. The second just lists benefits. We should keep both? They are somewhat overlapping but not identical. To preserve all substantive info, we could keep both but maybe combine into a more detailed statement. However the instruction says do NOT invent or summarize away detail. Summarizing could be considered summarizing away detail. But we could keep both as separate list items; that preserves detail, even if somewhat redundant. Duplicated lines: we should remove duplicated lines. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. If we have two items that are essentially the same meaning, they might be considered duplicated lines. But they are not exact duplicates; they differ in wording. The instruction likely refers to exact duplicated lines. So we can keep both if they are not exact duplicates. Thus we will keep all items from both lists, except exact duplicates (like "Pet insurance" appears twice exactly? Actually first list has "Pet-Friendly Housing" not pet insurance. Second list has "Pet insurance". So not duplicate. "License and certification reimbursement" appears exactly same in both lists? First list: "Licensure and Certification Reimbursement". Second: "License and certification reimbursement". Slight difference in capitalization and "Licensure" vs "License". Not exact