Registered Nurse - Regional Float Pool | LDRP
for section headings, - for lists,
for prose.
Let me map the content:
1. Overview/About the role: The first paragraph describes the role - "Make a Difference as a Float Pool RN! Join Novant Health's Regional Resource Team..." This could be "About the role" or similar.
2. Benefits: "Why Join Us?" lists float pay premiums, night shift/weekend differentials, relocation assistance, diverse clinical experiences. This is a Benefits section.
3. Requirements: "What We're Looking For" has Education, Experience, Licensure/Certification, Additional Skills (required), Additional Skills (preferred). This should be broken into Requirements and maybe Qualifications/Skills.
4. Company culture: "Why Choose Novant Health?" - this could be a "About the company" or "Culture" section.
The rules say: use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when there's real content.
Let me structure:
- About the role (the intro paragraph)
- Benefits (the "Why Join Us?" list)
- Requirements (education, experience, licensure)
- Skills (additional skills required and preferred)
- About the company (the Novant Health values paragraph)
I should not include Job Opening ID 186501 as a heading - fold into a short
or drop it. I'll drop it as it's minor metadata.
Now, for the Requirements section, I have multiple subcategories. I could use a single Requirements section with a list, or break into Education, Experience, Licensure. The rules say prefer a few substantive sections over many thin ones. So maybe one Requirements section with a structured list.
But the content has clear categories: Education, Experience, Licensure/Certification, Additional Skills (required), Additional Skills (preferred). I could make them sub-lists within a Requirements section.
Alternatively, I could have:
- Requirements (education, experience, licensure)
- Skills (additional skills required and preferred)
Let me think about the HTML structure.
I'll create:
About the role
Make a Difference as a Float Pool RN! Join Novant Health's Regional Resource Team and bring your skills where they're needed most. As a Float Pool RN, you'll provide exceptional LDRP care across multiple locations, support teams during critical staffing needs, and gain valuable experience across a variety of clinical settings.
Benefits
- Float pay premiums up to $15/hour
- Night shift and weekend differentials
- Potential relocation assistance
- Diverse clinical experiences and growth opportunities
Requirements
- Education: Associate Degree (ADN) required; Bachelor's Degree (BSN) preferred
- Experience: 2 years consecutive experience within defined specialty (Med Surg, Tele, Critical Care, ED, or Women's) required
- Licensure/Certification: Current compact licensure in appropriate state required; NC state approved curricula for restrictive interventions (facility specific) within 3 months of hire for Emergency Departments and Behavioral Health units required; Specialty certification preferred
Skills
- Required: Appropriate customer service, effective customer relations, verbal and non-verbal communication techniques, interpersonal relationship skills, conflict resolution, critical thinking, computer literacy; advanced training as required by department/unit/facility; ability to complete generic and department-specific skills validation and competency testing; ability to interpret information and identify patient's age-specific care needs; knowledge and skill to modify care according to patient age; successful completion of Cardiac dysrhythmia test or course within 3 months of hire; NIH Stroke Scale certification upon hire
- Preferred: Specialty certification within two years of hire
About the company
At Novant Health, we believe remarkable care starts with compassion for our patients, our communities, and each other. We value belonging, courage, personal growth, and teamwork, creating a space where everyone is respected, supported, and safe to show up as their full selves.
I need to ensure I'm not inventing or summarizing away detail. The original text has "Additional Skills (required):" with a long list. I should preserve all items. In my list above, I combined them into one bullet but that might be too long. Better to break into separate list items for each skill? But the rule says use - for any list of duties/requirements/benefits. The original has a paragraph with commas. I could split each skill into separate
- items.
Let me re-read: "Additional Skills (required): Appropriate customer service, effective and appropriate customer relations, verbal and non-verbal communication techniques, interpersonal relationship skills, conflict resolution, critical thinking and computer literacy. Advanced training as required by department/unit/facility per identified skill set/sub category. Ability to successfully complete generic and department specific skills validation and competency testing. Has the ability to interpret information and identify each patient's requirement for care relative to his/her age specific need. Has the knowledge and skill necessary to modify care according to patient(s) age. Successfully complete the Cardiac dysrhythmia test or Cardiac dysrhythmia course within 3 months of hire. NIH Stroke Scale certification upon hire."
These are distinct requirements. I should list each as a separate
- for clarity.
Similarly for preferred: "Specialty certification within two years of hire." Just one.
So for Skills section, I'll have two sub-lists: Required and Preferred, each with multiple
- .
But the HTML structure: I can have a
Skills
then a with - Required: ...
but that would be one bullet with a long list. Better to have a nested list or separate lists.
The rules don't forbid nested lists. I can do:
Skills
Required
- Appropriate customer service
- Effective and appropriate customer relations
...
Preferred
- Specialty certification within two years of hire
But the rules say use for section headings. It doesn't mention . But it's semantic HTML, so is fine for subsections. However, the user didn't specify about subheadings. To be safe, I'll keep it simple with for main sections and use - for lists. I can use within
- to denote categories.
Alternatively, I can make "Requirements" include education, experience, licensure, and required skills, and "Preferred qualifications" for preferred skills and BSN.
But the original has "Education: ... required/preferred", "Experience: ... required", "Licensure/Certification: ... required/preferred", "Additional Skills (required)", "Additional Skills (preferred)".
I think a good structure:
- About the role
- Benefits
- Requirements (with sub-items for education, experience, licensure, required skills)
- Preferred qualifications (preferred education, preferred certification, preferred skills)
- About the company
But the rules say "Prefer a few substantive sections over many thin ones." So maybe combine required and preferred into one Requirements section with clear labeling.
Let me look at the example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So Requirements and Qualifications are separate? Qualifications might be preferred.
I'll do:
About the role
...
Benefits
...
Requirements
- Education: Associate Degree (ADN) required; Bachelor's Degree (BSN) preferred
- Experience: 2 years consecutive experience within defined specialty (Med Surg, Tele, Critical Care, ED, or Women's) required
- Licensure/Certification: Current compact licensure in appropriate state required; NC state approved curricula for restrictive interventions (facility specific) within 3 months of hire for Emergency Departments and Behavioral Health units required; Specialty certification preferred
- Required skills: Appropriate customer service; effective and appropriate customer relations; verbal and non-verbal communication techniques; interpersonal relationship skills; conflict resolution; critical thinking; computer literacy; advanced training as required by department/unit/facility per identified skill set/sub category; ability to successfully complete generic and department specific skills validation and competency testing; ability to interpret information and identify each patient's requirement for care relative to age specific need; knowledge and skill necessary to modify care according to patient age; successful completion of Cardiac dysrhythmia test or Cardiac dysrhythmia course within 3 months of hire; NIH Stroke Scale certification upon hire
Preferred qualifications
- Specialty certification within two years of hire
About the company
...
But the preferred qualifications only has one item. Might be thin. Could merge into Requirements as a note.
The rules: "never emit a heading followed by filler/placeholder text" and "include a section ONLY when the posting has real, specific content for it". Preferred qualifications has one specific item, so it's okay.
But the user said "Prefer a few substantive sections over many thin ones." So maybe keep it in Requirements.
I'll include a "Preferred qualifications" section with that one item, as it's specific.
Now, for the skills list, I used semicolons in one bullet. That's not ideal; each skill should be a separate - . But the original groups them in a paragraph. I think it's acceptable to list them as separate bullets for readability.
Let me restructure the Requirements section with nested lists or separate bullets for each skill.
I'll do:
Requirements
- Education: Associate Degree (ADN) required; Bachelor's Degree (BSN) preferred
- Experience: 2 years consecutive experience within defined specialty (Med Surg, Tele, Critical Care, ED, or Women's) required
- Licensure/Certification:
- Current compact licensure in appropriate state required
- NC state approved curricula for restrictive interventions (facility specific) within 3 months of hire for Emergency Departments and Behavioral Health units required
- Specialty certification preferred
- Required skills:
- Appropriate customer service
- Effective and appropriate customer relations
- Verbal and non-verbal communication techniques
- Interpersonal relationship skills
- Conflict resolution
- Critical thinking
- Computer literacy
- Advanced training as required by department/unit/facility per identified skill set/sub category
- Ability to successfully complete
for prose. Let me map the content: 1. Overview/About the role: The first paragraph describes the role - "Make a Difference as a Float Pool RN! Join Novant Health's Regional Resource Team..." This could be "About the role" or similar. 2. Benefits: "Why Join Us?" lists float pay premiums, night shift/weekend differentials, relocation assistance, diverse clinical experiences. This is a Benefits section. 3. Requirements: "What We're Looking For" has Education, Experience, Licensure/Certification, Additional Skills (required), Additional Skills (preferred). This should be broken into Requirements and maybe Qualifications/Skills. 4. Company culture: "Why Choose Novant Health?" - this could be a "About the company" or "Culture" section. The rules say: use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when there's real content. Let me structure: - About the role (the intro paragraph) - Benefits (the "Why Join Us?" list) - Requirements (education, experience, licensure) - Skills (additional skills required and preferred) - About the company (the Novant Health values paragraph) I should not include Job Opening ID 186501 as a heading - fold into a short
or drop it. I'll drop it as it's minor metadata. Now, for the Requirements section, I have multiple subcategories. I could use a single Requirements section with a list, or break into Education, Experience, Licensure. The rules say prefer a few substantive sections over many thin ones. So maybe one Requirements section with a structured list. But the content has clear categories: Education, Experience, Licensure/Certification, Additional Skills (required), Additional Skills (preferred). I could make them sub-lists within a Requirements section. Alternatively, I could have: - Requirements (education, experience, licensure) - Skills (additional skills required and preferred) Let me think about the HTML structure. I'll create:
About the role
Make a Difference as a Float Pool RN! Join Novant Health's Regional Resource Team and bring your skills where they're needed most. As a Float Pool RN, you'll provide exceptional LDRP care across multiple locations, support teams during critical staffing needs, and gain valuable experience across a variety of clinical settings.
Benefits
- Float pay premiums up to $15/hour
- Night shift and weekend differentials
- Potential relocation assistance
- Diverse clinical experiences and growth opportunities
Requirements
- Education: Associate Degree (ADN) required; Bachelor's Degree (BSN) preferred
- Experience: 2 years consecutive experience within defined specialty (Med Surg, Tele, Critical Care, ED, or Women's) required
- Licensure/Certification: Current compact licensure in appropriate state required; NC state approved curricula for restrictive interventions (facility specific) within 3 months of hire for Emergency Departments and Behavioral Health units required; Specialty certification preferred
Skills
- Required: Appropriate customer service, effective customer relations, verbal and non-verbal communication techniques, interpersonal relationship skills, conflict resolution, critical thinking, computer literacy; advanced training as required by department/unit/facility; ability to complete generic and department-specific skills validation and competency testing; ability to interpret information and identify patient's age-specific care needs; knowledge and skill to modify care according to patient age; successful completion of Cardiac dysrhythmia test or course within 3 months of hire; NIH Stroke Scale certification upon hire
- Preferred: Specialty certification within two years of hire
About the company
At Novant Health, we believe remarkable care starts with compassion for our patients, our communities, and each other. We value belonging, courage, personal growth, and teamwork, creating a space where everyone is respected, supported, and safe to show up as their full selves.
I need to ensure I'm not inventing or summarizing away detail. The original text has "Additional Skills (required):" with a long list. I should preserve all items. In my list above, I combined them into one bullet but that might be too long. Better to break into separate list items for each skill? But the rule says use- for any list of duties/requirements/benefits. The original has a paragraph with commas. I could split each skill into separate
- items. Let me re-read: "Additional Skills (required): Appropriate customer service, effective and appropriate customer relations, verbal and non-verbal communication techniques, interpersonal relationship skills, conflict resolution, critical thinking and computer literacy. Advanced training as required by department/unit/facility per identified skill set/sub category. Ability to successfully complete generic and department specific skills validation and competency testing. Has the ability to interpret information and identify each patient's requirement for care relative to his/her age specific need. Has the knowledge and skill necessary to modify care according to patient(s) age. Successfully complete the Cardiac dysrhythmia test or Cardiac dysrhythmia course within 3 months of hire. NIH Stroke Scale certification upon hire." These are distinct requirements. I should list each as a separate
- for clarity. Similarly for preferred: "Specialty certification within two years of hire." Just one. So for Skills section, I'll have two sub-lists: Required and Preferred, each with multiple
- .
But the HTML structure: I can have a
Skills
then a- with
- Required: ... but that would be one bullet with a long list. Better to have a nested list or separate lists. The rules don't forbid nested lists. I can do:
- Appropriate customer service
- Effective and appropriate customer relations ...
- Specialty certification within two years of hire
- for lists. I can use within
- to denote categories. Alternatively, I can make "Requirements" include education, experience, licensure, and required skills, and "Preferred qualifications" for preferred skills and BSN. But the original has "Education: ... required/preferred", "Experience: ... required", "Licensure/Certification: ... required/preferred", "Additional Skills (required)", "Additional Skills (preferred)". I think a good structure: - About the role - Benefits - Requirements (with sub-items for education, experience, licensure, required skills) - Preferred qualifications (preferred education, preferred certification, preferred skills) - About the company But the rules say "Prefer a few substantive sections over many thin ones." So maybe combine required and preferred into one Requirements section with clear labeling. Let me look at the example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So Requirements and Qualifications are separate? Qualifications might be preferred. I'll do:
About the role
...
Benefits
- ...
Requirements
- Education: Associate Degree (ADN) required; Bachelor's Degree (BSN) preferred
- Experience: 2 years consecutive experience within defined specialty (Med Surg, Tele, Critical Care, ED, or Women's) required
- Licensure/Certification: Current compact licensure in appropriate state required; NC state approved curricula for restrictive interventions (facility specific) within 3 months of hire for Emergency Departments and Behavioral Health units required; Specialty certification preferred
- Required skills: Appropriate customer service; effective and appropriate customer relations; verbal and non-verbal communication techniques; interpersonal relationship skills; conflict resolution; critical thinking; computer literacy; advanced training as required by department/unit/facility per identified skill set/sub category; ability to successfully complete generic and department specific skills validation and competency testing; ability to interpret information and identify each patient's requirement for care relative to age specific need; knowledge and skill necessary to modify care according to patient age; successful completion of Cardiac dysrhythmia test or Cardiac dysrhythmia course within 3 months of hire; NIH Stroke Scale certification upon hire
Preferred qualifications
- Specialty certification within two years of hire
About the company
...
But the preferred qualifications only has one item. Might be thin. Could merge into Requirements as a note. The rules: "never emit a heading followed by filler/placeholder text" and "include a section ONLY when the posting has real, specific content for it". Preferred qualifications has one specific item, so it's okay. But the user said "Prefer a few substantive sections over many thin ones." So maybe keep it in Requirements. I'll include a "Preferred qualifications" section with that one item, as it's specific. Now, for the skills list, I used semicolons in one bullet. That's not ideal; each skill should be a separate- . But the original groups them in a paragraph. I think it's acceptable to list them as separate bullets for readability. Let me restructure the Requirements section with nested lists or separate bullets for each skill. I'll do:
Requirements
- Education: Associate Degree (ADN) required; Bachelor's Degree (BSN) preferred
- Experience: 2 years consecutive experience within defined specialty (Med Surg, Tele, Critical Care, ED, or Women's) required
- Licensure/Certification:
- Current compact licensure in appropriate state required
- NC state approved curricula for restrictive interventions (facility specific) within 3 months of hire for Emergency Departments and Behavioral Health units required
- Specialty certification preferred
- Required skills:
- Appropriate customer service
- Effective and appropriate customer relations
- Verbal and non-verbal communication techniques
- Interpersonal relationship skills
- Conflict resolution
- Critical thinking
- Computer literacy
- Advanced training as required by department/unit/facility per identified skill set/sub category
- Ability to successfully complete
- to denote categories. Alternatively, I can make "Requirements" include education, experience, licensure, and required skills, and "Preferred qualifications" for preferred skills and BSN. But the original has "Education: ... required/preferred", "Experience: ... required", "Licensure/Certification: ... required/preferred", "Additional Skills (required)", "Additional Skills (preferred)". I think a good structure: - About the role - Benefits - Requirements (with sub-items for education, experience, licensure, required skills) - Preferred qualifications (preferred education, preferred certification, preferred skills) - About the company But the rules say "Prefer a few substantive sections over many thin ones." So maybe combine required and preferred into one Requirements section with clear labeling. Let me look at the example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So Requirements and Qualifications are separate? Qualifications might be preferred. I'll do:
Skills
Required
Preferred
for section headings. It doesn't mention
. But it's semantic HTML, so
is fine for subsections. However, the user didn't specify about subheadings. To be safe, I'll keep it simple with
for main sections and use