RN - Ortho General Surgical
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading
- Do NOT put Job ID/requisition numbers as headings
- Fold minor metadata into short
or drop it
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/scam-warning)
- Include section ONLY when posting has real, specific content
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Output ONLY HTML fragment, no /, no markdown code fences
Let me structure this:
1. The opening paragraph about MultiCare - this is prose, could be an "About the role" or "About the organization" section. But the rules say use
for section headings like "About the role". The posting starts with "Join a team that shares your calling At MultiCare..." - this seems like an intro/about section.
2. There's metadata: "FTE: 0.6, Shift: Night, Schedule: 2x week, every other weekend." This is schedule info. Should I include a Schedule section? The rules say never create Schedule section unless posting actually states them. It does state schedule info. But also says "fold minor metadata into a short
or drop it". This is specific schedule info, so maybe include in a short
under a Schedule heading? But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule. However, the example headings include "Schedule". I think I should include a Schedule section with this info.
3. Position Summary - this is a section.
4. Responsibilities - list.
5. Requirements - list.
6. About Good Samaritan Hospital - prose.
7. About The Puyallup Community - prose.
8. Why MultiCare? - this has multiple bullet points. Could be a "Benefits" or "Why MultiCare" section. The rules mention "Benefits" as a heading. But the posting has "Why MultiCare?" with sub-points. I'll use "Why MultiCare?" as heading.
9. Pay and Benefit Expectations - includes pay range and benefits mention. This should be a "Pay" section? The rules say "Pay" as heading. It also mentions benefits package. Could be "Pay and Benefits". But the rules say "Pay" and "Benefits" as separate headings. However, the posting combines them. I'll create a "Pay and Benefits" section or separate? The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So Benefits and Pay are separate. But the posting has them together. I'll create a "Pay and Benefits" heading? Or maybe "Pay" and then include benefits in same section? The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states both. I'll create a "Pay and Benefits" section with the content.
But the rules say "Prefer a few substantive sections over many thin ones." So maybe combine.
Let me think about the headings:
- About the role (for the intro paragraph and position summary?)
- Schedule (for the FTE/Shift/Schedule line)
- Responsibilities
- Requirements
- About Good Samaritan Hospital
- About the Puyallup Community
- Why MultiCare?
- Pay and Benefits
But the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "About the role" is a suggested heading. The posting has "Position Summary" which is similar. I'll use "About the role" for the intro and position summary? Or keep "Position Summary" as heading? The rules say use those example headings, but not required to use exactly those words. It says "e.g." So I can use "Position Summary" as heading. But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings. However, to be consistent, maybe use "About the role" for the position summary. But the posting has "Position Summary" as a heading. I'll keep the posting's headings where they are clear.
The user says: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests those are the typical headings, but we can use others if needed. However, the posting has "About Good Samaritan Hospital" and "About The Puyallup Community" and "Why MultiCare?" which are specific. I'll keep them.
Now, the metadata line: "FTE: 0.6, Shift: Night, Schedule: 2x week, every other weekend." This is specific schedule info. I'll create a "Schedule" section with a
containing that.
The pay section: "Pay and Benefit Expectations" with pay range. I'll create a "Pay and Benefits" section.
Now, the "Why MultiCare?" section has bullet points. I'll use
- for those.
The "Requirements" list is already bullet points.
"Responsibilities" list.
"About Good Samaritan Hospital" and "About The Puyallup Community" are prose paragraphs.
The opening paragraph: "Join a team that shares your calling At MultiCare, you’re more than just a job title — you’re part of a team built on trust that cares for each other, our patients and our communities. Belonging here means living our mission and values every day. If your purpose and passions align with ours, you’ll find a place to grow, do meaningful work and build a career you love in a community that feels like home." This is prose. Could be part of "About the role" or "About MultiCare". I'll create an "About the role" section with this paragraph and the position summary.
But the position summary is separate: "Position Summary We’re seeking a staff RN to join our incredible hospital-based team. This is an excellent opportunity to utilize your specialized training, knowledge, and nursing care with a multidisciplinary approach. It’s an exciting time to be a nurse at MultiCare. We are on a journey to become a best-in-class nursing organization. Together, we are creating an environment where nurses are owners in the clinical decision-making process, are well connected, have open communication with their colleagues, feel supported to develop professionally, and understand the future of nursing at MultiCare."
I'll combine the opening paragraph and position summary under "About the role".
Now, let's write the HTML.
I need to output only the HTML fragment, no markdown code fences.
Let's structure:
About the role
Join a team that shares your calling At MultiCare, you’re more than just a job title — you’re part of a team built on trust that cares for each other, our patients and our communities. Belonging here means living our mission and values every day. If your purpose and passions align with ours, you’ll find a place to grow, do meaningful work and build a career you love in a community that feels like home.
We’re seeking a staff RN to join our incredible hospital-based team. This is an excellent opportunity to utilize your specialized training, knowledge, and nursing care with a multidisciplinary approach. It’s an exciting time to be a nurse at MultiCare. We are on a journey to become a best-in-class nursing organization. Together, we are creating an environment where nurses are owners in the clinical decision-making process, are well connected, have open communication with their colleagues, feel supported to develop professionally, and understand the future of nursing at MultiCare.
Schedule
FTE: 0.6, Shift: Night, Schedule: 2x week, every other weekend.
Responsibilities
- You will organize patient care by prioritizing, delegating, delivering and evaluating on an ongoing basis
- You will utilize the knowledge base of nursing education and experience to deliver nursing care using the nursing process according to hospital policies, procedures and protocols
- Collaborate with the nursing team to facilitate overall improvement in quality of care, patient experience and cost reduction
- Foster a learning environment for patients/families, nursing staff and members of the health care team
- Advocate for ethical and holistic care promoting the autonomy, dignity, and health of patients from diverse ethnic and social backgrounds
Requirements
- Current Registered Nurse (RN) license in Washington State or Multistate License endorsement (MLS)
- Bachelor’s degree in nursing (BSN) preferred
- Current BLS Certification required
- ACLS or NALS or PALS or TNCC or NRP certification, as required by facility or department
- Certification in specialty area preferred
- One (1) year of experience in acute care setting preferred
About Good Samaritan Hospital
MultiCare Good Samaritan Hospital is a 388-bed acute-care hub serving Puyallup and East Pierce County. As the area’s only hospital, it features a Family Birth Center, Level III Trauma and Neonatal ICUs, Level I Trauma Rehabilitation Center, Children’s Therapy Unit and a 24-hour Emergency Department. Innovative facilities like the LEED Gold-certified Dally Tower and Pulse Heart Institute make Good Samaritan a dynamic workplace for clinicians eager to advance their careers in a state-of-the-art environment.
About the Puyallup Community
Nestled at the foot of Mount Rainier along the Puyallup River, Puyallup offers a welcoming small-town feel just 10 miles from Tacoma and 35 miles from Seattle. Residents enjoy unique dining, an antique-filled downtown, excellent schools and abundant parks and recreation — all while being close to big-city opportunities.
Why MultiCare?
- Rooted in the local community: Partnering with patients, families and neighbors across the Pacific Northwest for more than 140 years.
- Growth and education: Competitive tuition assistance, award-winning residencies, fellowships and career development to invest in you.
- Well-being and support: Generous PTO, Code Lavender and Employee Assistance Programs to help you maintain balance and feel cared in your work and life.
- Living our values: Respect, integrity, kindness and collaboration guide how we care for patients, communities and each other.
- Belonging for all: Resource Groups and outreach programs help ensure every team member feels safe, seen, heard and valued.
- Pacific Northwest lifestyle: Work and live where natural beauty, adventure and strong community connections are part of everyday life.
Pay and Benefits
We provide a comprehensive benefits package, including competitive salary, medical, dental and retirement benefits and paid time off. As required by various pay transparency laws, we share a
for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings - Fold minor metadata into short
or drop it - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning) - Include section ONLY when posting has real, specific content - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no /, no markdown code fences Let me structure this: 1. The opening paragraph about MultiCare - this is prose, could be an "About the role" or "About the organization" section. But the rules say use
for section headings like "About the role". The posting starts with "Join a team that shares your calling At MultiCare..." - this seems like an intro/about section. 2. There's metadata: "FTE: 0.6, Shift: Night, Schedule: 2x week, every other weekend." This is schedule info. Should I include a Schedule section? The rules say never create Schedule section unless posting actually states them. It does state schedule info. But also says "fold minor metadata into a short
or drop it". This is specific schedule info, so maybe include in a short
under a Schedule heading? But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule. However, the example headings include "Schedule". I think I should include a Schedule section with this info. 3. Position Summary - this is a section. 4. Responsibilities - list. 5. Requirements - list. 6. About Good Samaritan Hospital - prose. 7. About The Puyallup Community - prose. 8. Why MultiCare? - this has multiple bullet points. Could be a "Benefits" or "Why MultiCare" section. The rules mention "Benefits" as a heading. But the posting has "Why MultiCare?" with sub-points. I'll use "Why MultiCare?" as heading. 9. Pay and Benefit Expectations - includes pay range and benefits mention. This should be a "Pay" section? The rules say "Pay" as heading. It also mentions benefits package. Could be "Pay and Benefits". But the rules say "Pay" and "Benefits" as separate headings. However, the posting combines them. I'll create a "Pay and Benefits" section or separate? The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So Benefits and Pay are separate. But the posting has them together. I'll create a "Pay and Benefits" heading? Or maybe "Pay" and then include benefits in same section? The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states both. I'll create a "Pay and Benefits" section with the content.
But the rules say "Prefer a few substantive sections over many thin ones." So maybe combine.
Let me think about the headings:
- About the role (for the intro paragraph and position summary?)
- Schedule (for the FTE/Shift/Schedule line)
- Responsibilities
- Requirements
- About Good Samaritan Hospital
- About the Puyallup Community
- Why MultiCare?
- Pay and Benefits
But the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "About the role" is a suggested heading. The posting has "Position Summary" which is similar. I'll use "About the role" for the intro and position summary? Or keep "Position Summary" as heading? The rules say use those example headings, but not required to use exactly those words. It says "e.g." So I can use "Position Summary" as heading. But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings. However, to be consistent, maybe use "About the role" for the position summary. But the posting has "Position Summary" as a heading. I'll keep the posting's headings where they are clear.
The user says: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests those are the typical headings, but we can use others if needed. However, the posting has "About Good Samaritan Hospital" and "About The Puyallup Community" and "Why MultiCare?" which are specific. I'll keep them.
Now, the metadata line: "FTE: 0.6, Shift: Night, Schedule: 2x week, every other weekend." This is specific schedule info. I'll create a "Schedule" section with a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings. However, to be consistent, maybe use "About the role" for the position summary. But the posting has "Position Summary" as a heading. I'll keep the posting's headings where they are clear.
The user says: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests those are the typical headings, but we can use others if needed. However, the posting has "About Good Samaritan Hospital" and "About The Puyallup Community" and "Why MultiCare?" which are specific. I'll keep them.
Now, the metadata line: "FTE: 0.6, Shift: Night, Schedule: 2x week, every other weekend." This is specific schedule info. I'll create a "Schedule" section with a
containing that. The pay section: "Pay and Benefit Expectations" with pay range. I'll create a "Pay and Benefits" section. Now, the "Why MultiCare?" section has bullet points. I'll use
- for those.
The "Requirements" list is already bullet points.
"Responsibilities" list.
"About Good Samaritan Hospital" and "About The Puyallup Community" are prose paragraphs.
The opening paragraph: "Join a team that shares your calling At MultiCare, you’re more than just a job title — you’re part of a team built on trust that cares for each other, our patients and our communities. Belonging here means living our mission and values every day. If your purpose and passions align with ours, you’ll find a place to grow, do meaningful work and build a career you love in a community that feels like home." This is prose. Could be part of "About the role" or "About MultiCare". I'll create an "About the role" section with this paragraph and the position summary.
But the position summary is separate: "Position Summary We’re seeking a staff RN to join our incredible hospital-based team. This is an excellent opportunity to utilize your specialized training, knowledge, and nursing care with a multidisciplinary approach. It’s an exciting time to be a nurse at MultiCare. We are on a journey to become a best-in-class nursing organization. Together, we are creating an environment where nurses are owners in the clinical decision-making process, are well connected, have open communication with their colleagues, feel supported to develop professionally, and understand the future of nursing at MultiCare."
I'll combine the opening paragraph and position summary under "About the role".
Now, let's write the HTML.
I need to output only the HTML fragment, no markdown code fences.
Let's structure:
About the role
Join a team that shares your calling At MultiCare, you’re more than just a job title — you’re part of a team built on trust that cares for each other, our patients and our communities. Belonging here means living our mission and values every day. If your purpose and passions align with ours, you’ll find a place to grow, do meaningful work and build a career you love in a community that feels like home.
We’re seeking a staff RN to join our incredible hospital-based team. This is an excellent opportunity to utilize your specialized training, knowledge, and nursing care with a multidisciplinary approach. It’s an exciting time to be a nurse at MultiCare. We are on a journey to become a best-in-class nursing organization. Together, we are creating an environment where nurses are owners in the clinical decision-making process, are well connected, have open communication with their colleagues, feel supported to develop professionally, and understand the future of nursing at MultiCare.
Schedule
FTE: 0.6, Shift: Night, Schedule: 2x week, every other weekend.
Responsibilities
- You will organize patient care by prioritizing, delegating, delivering and evaluating on an ongoing basis
- You will utilize the knowledge base of nursing education and experience to deliver nursing care using the nursing process according to hospital policies, procedures and protocols
- Collaborate with the nursing team to facilitate overall improvement in quality of care, patient experience and cost reduction
- Foster a learning environment for patients/families, nursing staff and members of the health care team
- Advocate for ethical and holistic care promoting the autonomy, dignity, and health of patients from diverse ethnic and social backgrounds
Requirements
- Current Registered Nurse (RN) license in Washington State or Multistate License endorsement (MLS)
- Bachelor’s degree in nursing (BSN) preferred
- Current BLS Certification required
- ACLS or NALS or PALS or TNCC or NRP certification, as required by facility or department
- Certification in specialty area preferred
- One (1) year of experience in acute care setting preferred
About Good Samaritan Hospital
MultiCare Good Samaritan Hospital is a 388-bed acute-care hub serving Puyallup and East Pierce County. As the area’s only hospital, it features a Family Birth Center, Level III Trauma and Neonatal ICUs, Level I Trauma Rehabilitation Center, Children’s Therapy Unit and a 24-hour Emergency Department. Innovative facilities like the LEED Gold-certified Dally Tower and Pulse Heart Institute make Good Samaritan a dynamic workplace for clinicians eager to advance their careers in a state-of-the-art environment.
About the Puyallup Community
Nestled at the foot of Mount Rainier along the Puyallup River, Puyallup offers a welcoming small-town feel just 10 miles from Tacoma and 35 miles from Seattle. Residents enjoy unique dining, an antique-filled downtown, excellent schools and abundant parks and recreation — all while being close to big-city opportunities.
Why MultiCare?
- Rooted in the local community: Partnering with patients, families and neighbors across the Pacific Northwest for more than 140 years.
- Growth and education: Competitive tuition assistance, award-winning residencies, fellowships and career development to invest in you.
- Well-being and support: Generous PTO, Code Lavender and Employee Assistance Programs to help you maintain balance and feel cared in your work and life.
- Living our values: Respect, integrity, kindness and collaboration guide how we care for patients, communities and each other.
- Belonging for all: Resource Groups and outreach programs help ensure every team member feels safe, seen, heard and valued.
- Pacific Northwest lifestyle: Work and live where natural beauty, adventure and strong community connections are part of everyday life.
Pay and Benefits
We provide a comprehensive benefits package, including competitive salary, medical, dental and retirement benefits and paid time off. As required by various pay transparency laws, we share a