Manager, HR Business Partner
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. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to decide which sections to include. The posting includes:
- Position Summary (could be "About the role" or "Position Summary" but they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map Position Summary to "About the role". Provide prose.
- Requirements: list of bullet points (Bachelor's degree..., certification preferred..., Minimum five years..., Minimum three years..., Experience..., Continued pattern..., Consulting Experience). We'll put under
Requirements
with - .
- About Yakima Memorial Hospital: could be "About the role"? No, it's about the hospital. Could be a separate section maybe "About the organization"? Not in list but we can still use
About Yakima Memorial Hospital
? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we can use other headings as needed, but better to stick to those given. However we have substantive content about hospital and community and why MultiCare. Could combine into "About the organization" but not in list. Might be okay to use About the organization
but they didn't list that. Safer to use headings from list: maybe "About the role" for position summary, "Requirements" for requirements, "Benefits" for benefits (Why MultiCare? includes benefits), "Pay" for pay range, maybe "Schedule" for schedule (they gave FTE:1.0, Shift: Day Schedule: M-F). That's schedule info. So we need a Schedule section.
Thus sections: About the role (position summary), Requirements, Benefits, Pay, Schedule. Also maybe "About Yakima Memorial Hospital" and "About The Yakima Community" and "Why MultiCare?" could be merged into Benefits or About the role? But they are substantive. Could create a section "About the organization" but not in list; but instruction says prefer a few substantive sections over many thin ones. Could combine hospital, community, why MultiCare into a single "About the organization" section. However they didn't forbid other headings; they just gave examples. So we can add a heading like "About the organization". That seems okay.
But we must not create sections with filler. All have content.
Thus output:
About the role
Position Summary ...
Requirements
- Bachelor’s degree in related field or four (4) years of experience in lieu of degree will be considered
- Recognized human resources professional certification preferred (PHR, SPHR, etc.)
- Minimum five (5) years of experience in Human Resources
- Minimum three (3) years of experience in a supervisory or lead capacity
- Experience in interpretation of personnel policy and managing a wide range of employee issues
- Continued pattern of learning and growth in career
- Consulting Experience
About the organization
About Yakima Memorial Hospital ...
About The Yakima Community ...
Why MultiCare? ...
But we need to keep the content exactly as given, not summarizing. We'll copy paragraphs.
We need to remove boilerplate like "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." That's part of the posting but is it substantive? It's more of a marketing intro. Could be considered part of About the role? Might be okay to include in About the role paragraph. However they said preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that intro as part of About the role? It's not position summary but it's about the company. Could be placed in About the organization section. But we already have About the organization with hospital, community, why MultiCare. The intro is also about MultiCare. Could merge.
Better to keep sections: About the role (Position Summary), Requirements, Benefits (Why MultiCare? includes benefits), Pay, Schedule. And maybe About the organization (hospital + community). Let's decide.
We need to include schedule: FTE: 1.0 , Shift: Day Schedule: M-F. So schedule section.
Pay: pay scale $104,665.60 - $150,612.80 USD.
Benefits: Why MultiCare? includes bullet points: Rooted in the local community, Growth and education, Well-being and support, Living our values, Belonging for all, Pacific Northwest lifestyle. Also mention comprehensive benefits package, competitive salary, medical, dental and retirement benefits and paid time off. That's in Pay and Benefit Expectations paragraph.
Thus Benefits section can list those.
Let's extract Benefits content:
"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."
Also earlier: "We provide a comprehensive benefits package, including competitive salary, medical, dental and retirement benefits and paid time off."
Thus Benefits section can have a with each benefit line.
Now schedule: FTE: 1.0 , Shift: Day Schedule: M-F. Could be a .
Now About the role: Position Summary paragraph(s). Also the introductory paragraph about MultiCare could be included there? Might be redundant. But we can include it as part of About the role to avoid missing info. The Position Summary paragraph is: "This position assumes the role of embedded HP Manager for their assigned business unit(s). This position partners with business unit executive and leaders to develop and implement HP strategies. This position requires a skilled communicator able to engage at all levels, with strong interpersonal and influencing skills, combined with an ability to coach and provide a high level of service. This position serves a trusted advisor providing broad-based professional human resources expertise and consulting. Providing HP support with the highest level of integrity and professionalism in handling sensitive and confidential information. This advanced professional-level position with within MultiCare’s Human Potential Division. Work situations require strong customer service focus, leadership, effective dispute resolution, critical thinking, initiative, independent judgement in decision making a professional work ethic and effective interpersonal and presentation skills. The role requires a mix of HR, labor relations, finance operations and leadership. Hospital-based leaders may have a dual matrixed reporting structure."
We'll put that in
.
Now Requirements list as above.
Now About the organization: Could combine Yakima Memorial Hospital description, Yakima Community description, and maybe the introductory MultiCare paragraph? But we already used that in About the role? Might duplicate. Let's keep About the organization separate: include Yakima Memorial Hospital description, Yakima Community description, and maybe the "Why MultiCare?"? But Why MultiCare? is benefits. We'll keep benefits separate.
Thus About the organization: two paragraphs: Yakima Memorial Hospital description, Yakima Community description.
Now Benefits: list items.
Now Pay:
The pay scale is $104,665.60 - $150,612.80 USD.
Now Schedule: FTE: 1.0, Shift: Day, Schedule: M‑F
Make sure to use proper hyphen.
Now output only HTML fragment.
Check for any duplicated lines: we should not repeat the introductory MultiCare paragraph if we didn't include it. We omitted it; is that substantive? It's about MultiCare mission etc. Could be considered substantive. But we have similar content in Benefits and About the organization. However the introductory paragraph is distinct: "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 not captured elsewhere. Should we include it? It's about MultiCare culture. Could be placed in About the organization or Benefits? It's more about culture/values. Could be part of About the organization section as an introductory paragraph. Let's add it as first paragraph in About the organization.
Thus About the organization will have three paragraphs: the intro MultiCare paragraph, Yakima Memorial Hospital description, Yakima Community description.
Now ensure we didn't miss any other substantive content: The "About Yakima Memorial Hospital" paragraph includes details about 226-bed, not-for-profit hospital, multispecialty team across 20+ primary and specialty care locations, providing cardiac care, cancer care, pediatric trauma care, hospice and advanced care for children with special health needs. Clinicians here care for a diverse patient population and make a meaningful impact in a collaborative, supportive environment where teams are valued and patients are grateful.
The "About The Yakima Community" paragraph includes sunshine, outdoor activities, lower cost of living, welcoming community.
Now Benefits: we need to list each benefit item as separate - . The benefits described: 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,
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. The posting includes: - Position Summary (could be "About the role" or "Position Summary" but they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map Position Summary to "About the role". Provide prose. - Requirements: list of bullet points (Bachelor's degree..., certification preferred..., Minimum five years..., Minimum three years..., Experience..., Continued pattern..., Consulting Experience). We'll put under
Requirements
with- .
- About Yakima Memorial Hospital: could be "About the role"? No, it's about the hospital. Could be a separate section maybe "About the organization"? Not in list but we can still use
About Yakima Memorial Hospital
? The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we can use other headings as needed, but better to stick to those given. However we have substantive content about hospital and community and why MultiCare. Could combine into "About the organization" but not in list. Might be okay to use
About the organization
but they didn't list that. Safer to use headings from list: maybe "About the role" for position summary, "Requirements" for requirements, "Benefits" for benefits (Why MultiCare? includes benefits), "Pay" for pay range, maybe "Schedule" for schedule (they gave FTE:1.0, Shift: Day Schedule: M-F). That's schedule info. So we need a Schedule section. Thus sections: About the role (position summary), Requirements, Benefits, Pay, Schedule. Also maybe "About Yakima Memorial Hospital" and "About The Yakima Community" and "Why MultiCare?" could be merged into Benefits or About the role? But they are substantive. Could create a section "About the organization" but not in list; but instruction says prefer a few substantive sections over many thin ones. Could combine hospital, community, why MultiCare into a single "About the organization" section. However they didn't forbid other headings; they just gave examples. So we can add a heading like "About the organization". That seems okay. But we must not create sections with filler. All have content. Thus output:About the role
Position Summary ...
Requirements
- Bachelor’s degree in related field or four (4) years of experience in lieu of degree will be considered
- Recognized human resources professional certification preferred (PHR, SPHR, etc.)
- Minimum five (5) years of experience in Human Resources
- Minimum three (3) years of experience in a supervisory or lead capacity
- Experience in interpretation of personnel policy and managing a wide range of employee issues
- Continued pattern of learning and growth in career
- Consulting Experience
About the organization
About Yakima Memorial Hospital ...
About The Yakima Community ...
Why MultiCare? ...
But we need to keep the content exactly as given, not summarizing. We'll copy paragraphs. We need to remove boilerplate like "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." That's part of the posting but is it substantive? It's more of a marketing intro. Could be considered part of About the role? Might be okay to include in About the role paragraph. However they said preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that intro as part of About the role? It's not position summary but it's about the company. Could be placed in About the organization section. But we already have About the organization with hospital, community, why MultiCare. The intro is also about MultiCare. Could merge. Better to keep sections: About the role (Position Summary), Requirements, Benefits (Why MultiCare? includes benefits), Pay, Schedule. And maybe About the organization (hospital + community). Let's decide. We need to include schedule: FTE: 1.0 , Shift: Day Schedule: M-F. So schedule section. Pay: pay scale $104,665.60 - $150,612.80 USD. Benefits: Why MultiCare? includes bullet points: Rooted in the local community, Growth and education, Well-being and support, Living our values, Belonging for all, Pacific Northwest lifestyle. Also mention comprehensive benefits package, competitive salary, medical, dental and retirement benefits and paid time off. That's in Pay and Benefit Expectations paragraph. Thus Benefits section can list those. Let's extract Benefits content: "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." Also earlier: "We provide a comprehensive benefits package, including competitive salary, medical, dental and retirement benefits and paid time off." Thus Benefits section can have a- with each benefit line.
Now schedule: FTE: 1.0 , Shift: Day Schedule: M-F. Could be a
- . The benefits described: 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,
. Now About the role: Position Summary paragraph(s). Also the introductory paragraph about MultiCare could be included there? Might be redundant. But we can include it as part of About the role to avoid missing info. The Position Summary paragraph is: "This position assumes the role of embedded HP Manager for their assigned business unit(s). This position partners with business unit executive and leaders to develop and implement HP strategies. This position requires a skilled communicator able to engage at all levels, with strong interpersonal and influencing skills, combined with an ability to coach and provide a high level of service. This position serves a trusted advisor providing broad-based professional human resources expertise and consulting. Providing HP support with the highest level of integrity and professionalism in handling sensitive and confidential information. This advanced professional-level position with within MultiCare’s Human Potential Division. Work situations require strong customer service focus, leadership, effective dispute resolution, critical thinking, initiative, independent judgement in decision making a professional work ethic and effective interpersonal and presentation skills. The role requires a mix of HR, labor relations, finance operations and leadership. Hospital-based leaders may have a dual matrixed reporting structure." We'll put that in
. Now Requirements list as above. Now About the organization: Could combine Yakima Memorial Hospital description, Yakima Community description, and maybe the introductory MultiCare paragraph? But we already used that in About the role? Might duplicate. Let's keep About the organization separate: include Yakima Memorial Hospital description, Yakima Community description, and maybe the "Why MultiCare?"? But Why MultiCare? is benefits. We'll keep benefits separate. Thus About the organization: two paragraphs: Yakima Memorial Hospital description, Yakima Community description. Now Benefits: list items. Now Pay:
The pay scale is $104,665.60 - $150,612.80 USD.
Now Schedule:FTE: 1.0, Shift: Day, Schedule: M‑F
Make sure to use proper hyphen. Now output only HTML fragment. Check for any duplicated lines: we should not repeat the introductory MultiCare paragraph if we didn't include it. We omitted it; is that substantive? It's about MultiCare mission etc. Could be considered substantive. But we have similar content in Benefits and About the organization. However the introductory paragraph is distinct: "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 not captured elsewhere. Should we include it? It's about MultiCare culture. Could be placed in About the organization or Benefits? It's more about culture/values. Could be part of About the organization section as an introductory paragraph. Let's add it as first paragraph in About the organization. Thus About the organization will have three paragraphs: the intro MultiCare paragraph, Yakima Memorial Hospital description, Yakima Community description. Now ensure we didn't miss any other substantive content: The "About Yakima Memorial Hospital" paragraph includes details about 226-bed, not-for-profit hospital, multispecialty team across 20+ primary and specialty care locations, providing cardiac care, cancer care, pediatric trauma care, hospice and advanced care for children with special health needs. Clinicians here care for a diverse patient population and make a meaningful impact in a collaborative, supportive environment where teams are valued and patients are grateful. The "About The Yakima Community" paragraph includes sunshine, outdoor activities, lower cost of living, welcoming community. Now Benefits: we need to list each benefit item as separate