Travel Oncology RN - $1,930 per week

We need to output HTML fragment with sections: About the role? Actually we have job description & requirements: Specialty, Discipline, Start Date, Duration, Hours, Shift, Employment Type, Job ID (metadata). Then About Prime Time Healthcare Nursing (company description). Then Benefits list. We must not repeat job title as heading. Use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We have: About Prime Time Healthcare Nursing (company description) - could be "About the role"? Actually "About the role" is not present; we have "About Prime Time Healthcare Nursing". Could map to "About the role"? Probably better to use "About the company" but not allowed headings list. The allowed headings are given as examples; we can use those headings but not required to exactly match? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we should use them when appropriate. We have content about the role? Not really; we have job description & requirements (specialty, discipline, start date, duration, hours, shift, employment type). That could go under "Requirements" or "About the role". Probably "Requirements" for specialty, discipline, etc. "About the role" could be a brief description but we don't have. So we can use "Requirements" heading. We have Benefits list. We have Pay info: "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This is vague; not specific amount. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state pay package based on shifts and hours, but amount TBD. That's not specific; it's "tax-free stipend amount to be determined." That's placeholder. Should we include Pay section? The rule says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state something about pay package but it's not a concrete amount; it's still stating something. However they say "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." That's TBD. So we should not create a Pay section because it would be filler. Similarly Schedule: we have shift details (12 hours, days) and 36 hours per week. That is specific schedule info. So we could create a Schedule section with that info. The rule: never create Schedule section unless posting actually states them. It does state shift and hours. So we can include Schedule. We also have Start Date, Duration - could be part of Requirements or maybe separate? Could be under Requirements. We have About Prime Time Healthcare Nursing - could be under "About the role"? Not exactly. Could be under "About the role" but it's about company. Maybe we can use "About the role" heading for company description? Might be okay. But better to use "About the role" for role description; we don't have that. Could we omit that heading and just have Requirements, Benefits, Schedule? The instruction: Prefer a few substantive sections over many thin ones. So we can have Requirements (including specialty, discipline, start date, duration, hours, shift, employment type), Benefits, Schedule. We must not include Job ID as heading; we can fold into a short

or drop it. Probably drop it. We must remove boilerplate etc. Thus output:

Requirements

Specialty: Oncology

Discipline: RN

Start Date: 10/19/2026

Duration: 13 weeks

Employment Type: Travel

Shift: 12 hours, days

Hours per week: 36

But we could combine into a

• list. The rule: Use
  • for any list of duties/requirements/benefits. So requirements list should be
    • ... each item. Similarly benefits list. Thus:

      Requirements

      • Specialty: Oncology
      • Discipline: RN
      • Start Date: 10/19/2026
      • Duration: 13 weeks
      • Employment Type: Travel
      • Shift: 12 hours, days
      • Hours per week: 36
      Benefits:

      Benefits

      • 401k retirement plan
      • Health savings account
      • Referral bonus
      • Medical benefits
      • Dental benefits
      • Vision benefits
      Schedule:

      Schedule

      Shift: 12 hours, days; 36 hours per week.

      But schedule could also be list; but it's not a list of multiple items; we can use

      . We must not include Pay section. Check for any other content: "Prime Time Healthcare Nursing Job ID #80430243." We drop. "About Prime Time Healthcare Nursing" paragraph: we haven't used it. Should we include? It's substantive info about company. Could be placed under "About the role"? But we don't have that heading. Could we create a section "About the company"? Not in allowed list but we could still use

      for any heading? The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate, but we could also use other headings? It says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections; but we can also use other headings if needed? Safer to stick to those. The company description could go under "About the role"? Not exactly but maybe acceptable. However "About the role" would be weird for company description. Could we omit it? The instruction: Prefer a few substantive sections over many thin ones. If we omit company description, we lose some substantive info. But maybe it's not essential; the job posting already shows job title; company description may be considered boilerplate? It's not boilerplate; it's describing the agency. Might be considered relevant. Could we incorporate it into Requirements? Not really. Maybe we can create a section "About the role" and put the company description there, even though it's about the company. It's still "about the role" in a sense? Might be okay. Alternatively, we could create a section "About the role" with a paragraph describing the role (which we don't have) and then add company description as a separate paragraph? But that would be mixing. Better to include a section "About the role" with the company description paragraph. The instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid using About the role for company description. Thus:

      About the role

      Prime Time Healthcare is a leading provider of traveling healthcare professionals nationwide. Our agency specializes in the placement of RNs, LPNs, CNAs, and Allied Health professionals. Join the fun and experience why healthcare professionals and client facilities are joining the Prime Time TEAM.

      That seems fine. Now we have three sections: About the role, Requirements, Benefits, Schedule. That's four sections. Check for any filler: none. Now output HTML fragment only. Make sure to close tags properly. Let's craft:

      About the role

      Prime Time Healthcare is a leading provider of traveling healthcare professionals nationwide. Our agency specializes in the placement of RNs, LPNs, CNAs, and Allied Health professionals. Join the fun and experience why healthcare professionals and client facilities are joining the Prime Time TEAM.

      Requirements

      • Specialty: Oncology
      • Discipline: RN
      • Start Date: 10/19/2026
      • Duration: 13 weeks
      • Employment Type: Travel
      • Shift: 12 hours, days
      • Hours per week: 36

      Benefits

      • 401k retirement plan
      • Health savings account
      • Referral bonus
      • Medical benefits
      • Dental benefits
      • Vision benefits

      Schedule

      Shift: 12 hours, days; 36 hours per week.

      Check: we used Shift both in Requirements and Schedule; maybe redundant. In Requirements we listed Shift and Hours per week; Schedule repeats. Could we remove Shift from Requirements and keep only in Schedule? But we need to preserve all substantive information; we can keep both but it's duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay as long as we preserve. However we might want to avoid duplication but it's not prohibited. However we could shift the shift info to Schedule only and keep other details in Requirements. Let's see: Requirements currently includes Shift and Hours per week. If we move them to Schedule, we lose them from Requirements unless we keep them there too. But we can keep them only in Schedule and remove from Requirements to avoid duplication. The requirement list would then lack shift/hours; but those are substantive. So we need to keep them somewhere. We could keep them in Requirements and not have Schedule separate; but we have schedule info, we could make Schedule section just a paragraph referencing the same info; duplication is okay. Alternatively, we could combine Requirements and Schedule into one section? But we prefer few sections; maybe we can have Requirements (including shift/hours) and Benefits, and About the role. Then we don't need separate Schedule section. The rule: never create Schedule section unless posting actually states them. It does state them, but we can choose not to create a separate section if we include them elsewhere. The instruction: Prefer a few substantive sections over many thin ones. So we could omit Schedule section and keep shift/hours in Requirements. That reduces sections. Thus we have About the role, Requirements, Benefits. Check if we need to include Pay? No. Thus final HTML:

      About the role

      Prime Time Healthcare is a leading provider of traveling healthcare professionals nationwide. Our agency specializes in the placement of RNs, LPNs, CNAs, and Allied Health professionals. Join the fun and experience why healthcare professionals and client facilities are joining the Prime Time TEAM.

      Requirements

      • Specialty: Oncology
      • Discipline: RN
      • Start Date: 10/19/2026
      • Duration: 13 weeks
      • Employment Type: Travel
      • Shift: 12 hours, days
      • Hours per week: 36

      Benefits

      • 401k retirement plan
      • Health savings account
      • Referral bonus
      • Medical benefits
      • Dental benefits