New Graduate Nurse (RN) - Cardiac Surgical
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, but we should use those headings when appropriate. It doesn't forbid other headings, but says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we should map content to those headings.
We have content for About the role (intro + location description maybe). Responsibilities (What You’ll Do). Requirements (We’re Looking For). Qualifications maybe same as Requirements? Could separate but we have both license etc. Could put license under Qualifications, and interest/teamwork under Skills? But better to follow typical: Requirements = licensure, education, certifications. Qualifications = maybe experience/skills? But we have "Strong interest and passion for cardiac care", "commitment to teamwork, communication, and continual professional growth" could be Skills. However we can also put them under Requirements.
We need to avoid filler like "commensurate with experience". Not present.
We need to use - for any list of duties/requirements/benefits. So for responsibilities we can list bullet points? The responsibilities paragraph is a sentence; we could break into bullet points but not required; we can keep as
. However if we have a list, we should use
- . The posting does not have explicit bullet lists; but we could still format as paragraphs.
Physical Requirements And Working Conditions: that is a list of requirements; we could put under Requirements or maybe a separate section like "Physical Requirements". Not in allowed headings; maybe we can incorporate into Requirements as a list.
We must not include boilerplate like EEO etc. Not present.
We must not repeat job title as heading. Not needed.
We must not include Job ID etc.
We must output only HTML fragment.
Thus produce something like:
About the role
Our Cardiac Surgical unit is seeking a dynamic New Grad Nurse to join our team of nursing excellence. Join Aurora St. Luke's a 6 times Magnet designated Medical Center! Be The Nurse Who Redefines Care. At Advocate Health, being a nurse means more than delivering exceptional clinical care—it means leading with purpose, compassion, and boldness. As part of our One Advocate Nurse community, you’ll join a unified team committed to lifting others up, embracing innovation, and creating inclusive spaces where everyone can thrive. You’ll be empowered to think boldly, collaborate with humility, and drive change through fearless curiosity. Whether you're at the bedside, in the community, or advancing care through research and education, you’ll help shape the future of health—because here, we’re redefining care for you, for us, for all. Your feedback matters. Every nurse’s voice is vital in shaping our culture and improving care. We value your insights and experiences because they help us grow stronger together.
Where You Will Work
maybe not allowed. Could incorporate into About the role? But we have a separate location description. Could make a section "About This Location" but not in allowed list. Might be okay to use a heading not in list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say you cannot use other headings, but suggests those are typical. Safer to stick to those. So we could merge location description into About the role or Responsibilities? Probably About the role includes location.
Thus About the role paragraph can include both intro and location description.
Then Responsibilities: Responsibilities
As a skilled and compassionate RN, you will play a pivotal role in providing and coordinating comprehensive patient care through the nursing process to deliver safe, therapeutic care in accordance with established standards, policies, and procedures. Using evidence-based practice, clinical decision making, compassion, and skills communication while leading efforts to create the safest patient environment and the best patient experience across the continuum.
Then Requirements: Requirements
- Completion of an accredited or approved nursing program
- Registered Nurse license issued by the state in which you practice
- Basic Life Support (BLS) for Healthcare Providers certification issued by the American Heart Association
- New graduates welcome
- Strong interest and passion for cardiac care
- Commitment to teamwork, communication, and continual professional growth
Physical requirements could be another list under Requirements or maybe a separate section "Physical Requirements" but not allowed. Could add to Requirements as additional items.
Thus Requirements list includes physical abilities.
We need to ensure we preserve all substantive information. Let's extract physical requirements:
- Must be able to sit, stand, walk, lift, squat, bend, reach above shoulders, and twist frequently throughout the workday.
- Must be able to lift and support the weight of 35 pounds in handling patients, medical equipment, and supplies.
- Must be able to: push/pull with 30 lbs. of force and perform a sliding transfer of 150 lbs. with a second person present.
- Must have functional speech, vision, hearing, and touch with ability to use fine hand manipulation skills for IV insertion and other procedures/functions.
- Maneuver foot pedals on carts or machines.
- Perform physical safety interventions such as patient restraint and verbal de-escalation, if needed.
- May be exposed to chemical and hazardous waste as well as blood and body fluids and communicable disease. Therefore, protective clothing and equipment must be worn as necessary.
- Must be able to respond quickly to changes in patient and/or unit conditions.
- Physical Abilities Testing may be required.
- Additional department specific physical requirements may be identified for unique responsibilities within the department by the nurse leader.
We should include these as list items.
Thus Requirements list will be long.
We also have "Orientation to our unit is completed in two phases..." that's location description; we included in About the role.
We also have "9ST is proud of our quality and patient satisfaction scores." etc.
We also have "This is an excellent environment for both experienced nurses and new graduate RNs, who are strongly encouraged to apply." That's about role.
We also have "Ready To Take The Next Step Apply Now..." we should remove as application instruction.
Thus final HTML:
About the role
... (intro + location description + orientation + quality scores + environment encouragement)
Responsibilities
... (What You’ll Do)
Requirements
- Completion of an accredited or approved nursing program
- Registered Nurse license issued by the state in which you practice
- Basic Life Support (BLS) for Healthcare Providers certification issued by the American Heart Association
- New graduates welcome
- Strong interest and passion for cardiac care
- Commitment to teamwork, communication, and continual professional growth
- Must be able to sit, stand, walk, lift, squat, bend, reach above shoulders, and twist frequently throughout the workday.
- Must be able to lift and support the weight of 35 pounds in handling patients, medical equipment, and supplies.
- Must be able to push/pull with 30 lbs. of force and perform a sliding transfer
- for any list of duties/requirements/benefits. So for responsibilities we can list bullet points? The responsibilities paragraph is a sentence; we could break into bullet points but not required; we can keep as
. However if we have a list, we should use
- . The posting does not have explicit bullet lists; but we could still format as paragraphs.
Physical Requirements And Working Conditions: that is a list of requirements; we could put under Requirements or maybe a separate section like "Physical Requirements". Not in allowed headings; maybe we can incorporate into Requirements as a list.
We must not include boilerplate like EEO etc. Not present.
We must not repeat job title as heading. Not needed.
We must not include Job ID etc.
We must output only HTML fragment.
Thus produce something like:
About the role
Our Cardiac Surgical unit is seeking a dynamic New Grad Nurse to join our team of nursing excellence. Join Aurora St. Luke's a 6 times Magnet designated Medical Center! Be The Nurse Who Redefines Care. At Advocate Health, being a nurse means more than delivering exceptional clinical care—it means leading with purpose, compassion, and boldness. As part of our One Advocate Nurse community, you’ll join a unified team committed to lifting others up, embracing innovation, and creating inclusive spaces where everyone can thrive. You’ll be empowered to think boldly, collaborate with humility, and drive change through fearless curiosity. Whether you're at the bedside, in the community, or advancing care through research and education, you’ll help shape the future of health—because here, we’re redefining care for you, for us, for all. Your feedback matters. Every nurse’s voice is vital in shaping our culture and improving care. We value your insights and experiences because they help us grow stronger together.
Where You Will Work
maybe not allowed. Could incorporate into About the role? But we have a separate location description. Could make a section "About This Location" but not in allowed list. Might be okay to use a heading not in list? The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say you cannot use other headings, but suggests those are typical. Safer to stick to those. So we could merge location description into About the role or Responsibilities? Probably About the role includes location. Thus About the role paragraph can include both intro and location description. Then Responsibilities:
Responsibilities
As a skilled and compassionate RN, you will play a pivotal role in providing and coordinating comprehensive patient care through the nursing process to deliver safe, therapeutic care in accordance with established standards, policies, and procedures. Using evidence-based practice, clinical decision making, compassion, and skills communication while leading efforts to create the safest patient environment and the best patient experience across the continuum.
Then Requirements:Requirements
- Completion of an accredited or approved nursing program
- Registered Nurse license issued by the state in which you practice
- Basic Life Support (BLS) for Healthcare Providers certification issued by the American Heart Association
- New graduates welcome
- Strong interest and passion for cardiac care
- Commitment to teamwork, communication, and continual professional growth
About the role
... (intro + location description + orientation + quality scores + environment encouragement)
Responsibilities
... (What You’ll Do)
Requirements
- Completion of an accredited or approved nursing program
- Registered Nurse license issued by the state in which you practice
- Basic Life Support (BLS) for Healthcare Providers certification issued by the American Heart Association
- New graduates welcome
- Strong interest and passion for cardiac care
- Commitment to teamwork, communication, and continual professional growth
- Must be able to sit, stand, walk, lift, squat, bend, reach above shoulders, and twist frequently throughout the workday.
- Must be able to lift and support the weight of 35 pounds in handling patients, medical equipment, and supplies.
- Must be able to push/pull with 30 lbs. of force and perform a sliding transfer
- . The posting does not have explicit bullet lists; but we could still format as paragraphs.
Physical Requirements And Working Conditions: that is a list of requirements; we could put under Requirements or maybe a separate section like "Physical Requirements". Not in allowed headings; maybe we can incorporate into Requirements as a list.
We must not include boilerplate like EEO etc. Not present.
We must not repeat job title as heading. Not needed.
We must not include Job ID etc.
We must output only HTML fragment.
Thus produce something like: