Travel Emergency Dept RN - $2,707 per week

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. Let's parse the posting. Content: - Job title: travel nurse RN ED - Emergency Department (but we don't repeat as heading) - Specialty: ED - Emergency Department - Discipline: RN - Start Date: ASAP - Duration: 13 weeks - 48 hours per week - Shift: 12 hours - Employment Type: Travel - All positions require at least two proven years experience - Job ID #1811958 (metadata, not heading) - Pay package is based on 12 hour shifts and 48.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - Posted job title: Registered Nurse (RN) - Emergency Room (duplicate) - About Aequor Healthcare: description. - Benefits: Weekly pay, Holiday Pay, 401k retirement plan, Referral bonus, Medical benefits, Dental benefits, Vision benefits. We need sections: About the role (maybe description of role?), Responsibilities (none given), Requirements (experience, specialty, discipline, start date, duration, hours, shift, employment type), Qualifications (maybe none), Skills (none), Benefits (list), Pay (pay package info), Schedule (hours per week, shift). We must not create sections with placeholder or vague content like "not specified". We need to include only sections with real specific content. Let's see what we have: - About the role: Could be the description of role? The posting includes "Specialty: ED - Emergency Department", "Discipline: RN", "Start Date: ASAP", "Duration: 13 weeks", "48 hours per week", "Shift: 12 hours", "Employment Type: Travel". That could be considered role details. Could put under "About the role". Or we could split: "About the role" could include specialty, discipline, start date, duration, hours, shift, employment type. That seems appropriate. - Responsibilities: Not provided. So we should not include. - Requirements: "All positions require at least two proven years experience". Also maybe the specialty and discipline are requirements? But they are already in role. Could include experience requirement. Also maybe "RN license"? Not mentioned. So we can include experience. - Qualifications: Not specific beyond experience? Could be same as requirements. Might not need separate. - Skills: Not provided. - Benefits: List given. - Pay: "Pay package is based on 12 hour shifts and 48.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's specific enough? It mentions basis but stipend TBD. It's still some info. Should we include? It says "Pay package is based on 12 hour shifts and 48.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's not a specific number, but it's still info about basis. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here we have "tax-free stipend amount to be determined" which is TBD. Also "subject to confirmation". This might be considered placeholder. However we still have basis: 12 hour shifts and 48 hours per week. That is specific. But the pay amount is not given. The rule says do not create Pay section unless posting actually states them. It does state pay package is based on ... but not actual pay. Might be considered insufficient. However we could still include Pay section with that info? It includes "tax-free stipend amount to be determined" which is TBD. Might be considered placeholder. Safer to omit Pay section if no concrete pay. But we have schedule info: 48 hours per week, shift 12 hours. That's schedule. - Schedule: we have 48 hours per week, shift 12 hours. That's specific. Thus sections: About the role, Requirements, Benefits, Schedule. Possibly also Qualifications? Not needed. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Do not put Job ID as heading. We must preserve all substantive information. So include details: Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type, Experience requirement, Benefits list, Schedule details. We need to decide where each piece goes. About the role: Could include specialty, discipline, start date, duration, employment type. Could also include shift? But shift is schedule. Let's put shift under Schedule. Thus About the role: Specialty: ED - Emergency Department; Discipline: RN; Start Date: ASAP; Duration: 13 weeks; Employment Type: Travel. We can format as

  or

  . Since it's not a list of duties, we can use

  with sentences. Requirements: At least two proven years experience. Could also include that they need RN license? Not mentioned. So just experience. Benefits: list: Weekly pay, Holiday Pay, 401k retirement plan, Referral bonus, Medical benefits, Dental benefits, Vision benefits. Schedule: 48 hours per week; Shift: 12 hours. We might also include Pay? Not sure. Let's omit Pay because no concrete amount. Now produce HTML fragment. Structure:

  About the role

  Specialty: ED - Emergency Department. Discipline: RN. Start Date: ASAP. Duration: 13 weeks. Employment Type: Travel.

  Requirements

  • At least two proven years of experience.
  • .

    Benefits

    • Weekly pay
    • Holiday Pay
    • 401k retirement plan
    • Referral bonus
    • Medical benefits
    • Dental benefits
    • Vision benefits

    Schedule

    48 hours per week. Shift: 12 hours.

    Check for any other info: The posting also mentions "All positions require at least two proven years experience". Already captured. We should not include "Job ID #1811958". That's minor metadata, we can drop. We should not include "Posted job title: Registered Nurse (RN) - Emergency Room". That's duplicate. We should not include "Aequor Healthcare" description? That's boilerplate about the agency; maybe considered not substantive about the role? It's about the company. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Aequor Healthcare" paragraph is company description; not strictly boilerplate but could be considered generic. However it's substantive about the agency. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we might need to include that info somewhere. Where? Could be under "About the role" or a separate section like "About the employer". But we only have allowed headings list; we could add a section like "About the employer" but not in list. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? 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. The "About Aequor Healthcare" is company info; maybe we can fold into "About the role" as a brief note? But it's not about the role. However we could include it as a paragraph under About the role? Might be stretching. Alternatively, we could treat it as boilerplate and remove? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not explicitly say to remove company description. But it's not about the job. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company description is substantive about the employer. If we drop it, we lose info. But maybe it's considered boilerplate because it's generic staffing agency description. Many job posts have similar "About X" blurbs. Might be considered boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. It doesn't mention company description. But to be safe, we could include it as a paragraph under a heading like "About the employer" but not allowed. Could we put it under "About the role"? Might be misrepresenting. Given the examples, they likely expect only those sections. I'd omit the company description, assuming it's boilerplate. The instruction says "Preserve ALL substantive information". If we drop it, we might be violating. But maybe they consider it not substantive to the job posting. I'd keep it as a

    without heading? But they said use

    for section headings. It doesn't forbid having

    without heading. We could just add a

    after the heading sections, containing the company description. That would preserve info without extra heading. That seems acceptable: we can have prose

    elements anywhere. The rule: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

    • for any list of duties/requirements/benefits, and

      for prose. So we can have

      for prose anywhere. So we can add a

      with the company description after the sections, without a heading. That preserves info. Thus final HTML:

      About the role

      Specialty: ED - Emergency Department. Discipline: RN. Start Date: ASAP. Duration: 13 weeks. Employment Type: Travel.

      Requirements

      • At least two proven years of experience.

      Benefits

      • Weekly pay
      • Holiday Pay
      • 401k retirement plan
      • Referral bonus
      • Medical benefits
      • Dental benefits
      • Vision benefits

      Schedule

      48 hours per week. Shift: 12 hours.

      Aequor Travel Nursing is a premiere healthcare staffing agency that specializes in placing healthcare travelers in short term contracts throughout the US. Whether you’re a seasoned healthcare professional looking for your next great adventure or just starting out and looking for your first big opportunity, Aequor has the inside track on the top jobs available in today’s healthcare and clinical markets. At Aequor, our top priority is to be the best resource to help you connect with the perfect career opportunity and take the best care of you from the moment we first connect until your last shift is worked. We pride ourselves on always offering top industry competitive pay. We have positions for nationwide covering every single state and ranging from 4 weeks – 26 weeks.

      Check for any other info: "Pay package is based on 12 hour shifts and 48.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." We omitted Pay section. Could we include that as a

      under Schedule or separate? It's about pay. Might be considered substantive but includes TBD. The rule: never emit a