Travel RN - $1,777 per week

We need to output HTML fragment with sections only if real content. The posting includes: - Job title: travel nurse RN ED - Emergency Department (but we should not repeat as heading) - Description: includes details: Specialty, Discipline, Duration, Shift, Employment Type, etc. - Then a paragraph about Advantis Medical being #1 rated etc. - Then job details: Facility, Location, Contract Length, Shift, Start Date. - Qualifications list bullet points. - Then a line: "If you are an experienced Med Surg RN Registered Nurse (RN) with a passion for providing exceptional patient care, just let us know you’re interested. We'll get you started on your next travel nurse adventure in Austell, GA 30106." (application instruction? maybe we should remove application instructions? The instruction says remove application instructions. That line is basically a call to apply, so we should remove it.) - Then "Advantis Medical Job ID #870387. 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 includes Pay info but says tax-free stipend amount to be determined (vague). According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It mentions Pay package based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That's somewhat vague; but it does state shift and hours. However "tax-free stipend amount to be determined" is not specified. The rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not create a Pay section if the pay details are not specific. The posting does not give actual pay numbers, just says based on 12 hour shifts and 36 hours per week, stipend TBD. That's placeholder. So we should not create Pay section. - Benefits: they list a Benefits section with items: Weekly pay, Holiday Pay, Guaranteed Hours, 401k retirement plan, Referral bonus, Employee assistance programs, Medical benefits, Dental benefits, Vision benefits. That's specific benefits list. So we should include a Benefits section with ul li. - About Advantis Medical paragraph: we can include as a section? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no explicit heading for "About Advantis Medical". But we could treat that as part of the description; maybe we can put it under a generic

without heading. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should only use those headings if we have content for those sections. We have Qualifications (list). We have Benefits (list). We might have Responsibilities? Not explicitly; the job description includes some duties: "As a Med Surg RN travel nurse, you will provide compassionate and high-quality care to patients ensuring their well-being and recovery." That's a responsibility. Could be under Responsibilities. Also earlier: "As a Med Surg RN travel nurse, you will provide compassionate and high-quality care to patients ensuring their well-being and recovery." That's the main duty. Could also include "provide compassionate and high-quality care". That's it. So we can create a Responsibilities section with that sentence. - About the role: maybe we can combine the initial description about the job (specialty, discipline, duration, shift, employment type) as About the role. Or we could put that in a

without heading. But we have a heading "About the role" allowed. Let's see: The posting starts: "Advantis Medical is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Austell, Georgia.Job Description & RequirementsSpecialty: ED - Emergency DepartmentDiscipline: RNDuration: 13 weeks36 hours per weekShift: 12 hours, nightsEmployment Type: Travel". That's basically about the role. So we can make an About the role section with that info. - Requirements: maybe we can separate qualifications as Requirements? But we already have Qualifications heading. The instruction includes Qualifications as a possible heading. So we will use Qualifications for the bullet list. - Responsibilities: we have the sentence about providing care. - Benefits: we have list. - Pay: we should not include because not specific. - Schedule: we have shift info (12 hours, nights) and hours per week (36). That's schedule info. Could we create a Schedule section? The instruction says include a section ONLY when posting has real, specific content for it. We have shift and hours. That's specific. So we could create a Schedule section with that info. However we already have shift/hours mentioned in About the role. But we could still create a Schedule section with details: Shift: 12 hours, nights; Hours per week: 36. That's specific. Let's do that. - Also we have Facility, Location, Contract Length, Start Date. Those could be under About the role or maybe a separate section like Job Details. But not in allowed headings list. We could incorporate them into About the role paragraph. - Also we have "Start Date: ASAP". That's schedule? Could be part of About the role. We must not include boilerplate like EEO, etc. There's none. We must not include duplicated lines. We must not include navigation, cookie, legal, etc. We must not include application instructions (the line about letting us know you're interested). Remove that. We must not include Job ID/requisition numbers as headings; we can fold minor metadata into a short p or drop it. The Job ID line: "Advantis Medical Job ID #870387." We can drop it or put in a short p. Probably drop it as minor metadata. Now produce HTML fragment: We'll have:

About the role

Advantis Medical is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Austell, Georgia. Specialty: ED - Emergency Department; Discipline: RN; Duration: 13 weeks; 36 hours per week; Shift: 12 hours, nights; Employment Type: Travel.

Maybe also include facility and location: "Facility: WellStar - Cobb Hospital; Location: Austell, GA 30106; Contract Length: 13 Weeks; Start Date: ASAP." We can combine.

Responsibilities

As a Med Surg RN travel nurse, you will provide compassionate and high-quality care to patients ensuring their well-being and recovery.

Qualifications

• 2 years of Med Surg RN staff experience or equivalent
• BSN Degree or Associate of Science in Nursing
• Current nursing license
• A valid State Issued Driver's License or State ID

Benefits

• Weekly pay
• Holiday Pay
• Guaranteed Hours
• 401k retirement plan
• Referral bonus
• Employee assistance programs
• Medical benefits
• Dental benefits
• Vision benefits

Schedule

Shift: 12 hours, nights; Hours per week: 36.

We should not include Pay section. Check for any duplicated content: we have shift/hours in About the role and Schedule; that's okay but maybe redundant. Could we avoid duplication by putting schedule only in Schedule and not repeat in About the role? The About the role currently includes shift/hours. We could remove from About the role to avoid duplication. But the instruction says preserve ALL substantive information; we can keep it in either place but not duplicate. Better to avoid duplication: put schedule details only in Schedule section, and About the role can omit shift/hours. However About the role currently includes shift/hours; we could keep but it's duplication. Let's avoid duplication: In About the role we keep specialty, discipline, duration, employment type, facility, location, contract length, start date. Then Schedule section has shift and hours. Let's craft About the role: "Advantis Medical is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Austell, Georgia. Specialty: ED - Emergency Department; Discipline: RN; Duration: 13 weeks; Employment Type: Travel. Facility: WellStar - Cobb Hospital; Location: Austell, GA 30106; Contract Length: 13 Weeks; Start Date: ASAP." That's good. Now Schedule: "Shift: 12 hours, nights; Hours per week: 36." Now check for any other info: The posting also mentions "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." We decided not to include Pay section because stipend TBD. However we already have schedule with shift and hours; that's fine. Now ensure we didn't include any boilerplate: The "About Advantis Medical" paragraph is not included; we omitted it. Is that substantive? It's about the company; could be considered boilerplate but it's descriptive. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The About Advantis Medical paragraph is not explicitly listed as boilerplate to remove, but it's more like marketing. However we might keep it as a section? There's no heading for "About the company". Could we put it under a generic

without heading? 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

for section headings (e.g...). It implies we should use those headings for sections; we could still have other headings but better to stick to those. The About Advantis Medical paragraph is not required to be preserved? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it if it's substantive. It's about the company; could be considered substantive. But we could incorporate it into About the role? Not really. Maybe we can add a section "About Advantis Medical" using

but not in the list; but 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 suggests those are typical. Safer to include it as a

without heading? But then it's not a section heading; still we preserve info. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but we should use

for section headings. If we make a heading for About Advantis Medical, we would be using

for a heading not in the example list; that's probably okay. However the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It may be interpreted that we should only use those headings. To be safe, we can incorporate the About Advantis Medical info into a

under About the role or as a separate

without heading. But we already have