Manager, HR Business Partner
Keurig Dr Pepper Inc. · Burlington, MA · 1 mo ago
Human Resources$97k–$135k/yrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use for each heading. Only include sections where posting has real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: EEO, equal opportunity, scam warning, AI disclosure, etc. Also remove navigation/cookie/legal. Also remove duplicated lines. Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Total Rewards: Salary Range: $96,800- $135,000 and Benefits list. So we can have Pay section (maybe heading "Pay") and Benefits section. Schedule not mentioned, so omit.
We need sections: About the role (Job Overview), Responsibilities (Key Responsibilities), Requirements (Requirements), Qualifications maybe overlapping with Requirements? The posting includes Requirements list and also "HR certification such as SHRM-CP...". Could treat Requirements as qualifications. Could also have Skills section if we extract skills like business acumen, data analytics, project management, etc. But we must not create thin sections. Perhaps combine Requirements and Qualifications into one? But rules say we can use those headings if content exists. We have content for Requirements (bullet list). Also we have "Company Overview" which is not required heading; we could put under About the role? Actually About the role already includes job overview. Company overview could be separate but not in allowed headings list; we could omit or incorporate into About the role? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but says use those for section headings. Probably we should stick to those. Company overview could be omitted as not required; but we must preserve ALL substantive information. If we omit company overview, we lose info. However we could incorporate company overview into About the role section as additional paragraph. That's allowed: About the role can contain job overview plus company overview. So we can merge.
Similarly, "Total Rewards Requirements Company Overview" at end seems duplicate; ignore.
Thus sections:
- About the role: combine Job Overview paragraph and Company Overview paragraph(s). Also maybe include the line about unlawful lie detector test? That's legal boilerplate; should be removed as per instruction: remove legal/EEO/equal-opportunity/scam-warning boilerplate. The lie detector test line is legal; remove.
- Responsibilities: list from Key Responsibilities bullet points.
- Requirements: list from Requirements bullet points.
- Qualifications: maybe we could separate certifications? But we could include under Requirements as part of list; but we have a separate heading Qualifications allowed. Could extract "HR certification such as SHRM-CP, SHRM-SCP, PHR, or SPHR." as qualifications. Also maybe "Bachelor's degree..." is requirement; but we already have that. To avoid duplication, we could put degree and experience under Requirements, and certifications under Qualifications. That seems reasonable.
- Skills: we could extract skills like business acumen, executive presence, influence, strategic thinking, hands-on execution, navigating change, workforce planning, talent discussions, employee relations, data analytics, project management, organizational, prioritization, partnering with leaders, etc. But we must avoid thin sections. Could create Skills section with bullet list of skills derived from responsibilities/requirements. However we must preserve all substantive info; if we put them in Skills, we still keep them. But we risk duplication if also in Requirements. Might be okay but could be considered duplication. Better to keep Requirements as is and not create Skills unless we have distinct skill statements not captured elsewhere. The posting includes "Strong business acumen with the ability to understand commercial, operational, and organizational drivers within a complex business environment." That's a skill. Also "Demonstrated ability to leverage data and analytics to identify trends, solve problems, and influence decisions." Also "Strong project management, organizational, and prioritization skills." Also "Experience partnering with business leaders on organizational design, talent strategy, succession planning, and workforce transformation." Those are more experience than skill. Could still be skills.
Given instruction: Prefer a few substantive sections over many thin ones. So maybe we skip Skills section and keep Requirements covering those. Qualifications for certifications.
Benefits: list from Benefits, subject to election and eligibility.
Pay: Salary range.
Schedule: not present, omit.
Now produce HTML:
inside
for each heading. Only include sections where posting has real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: EEO, equal opportunity, scam warning, AI disclosure, etc. Also remove navigation/cookie/legal. Also remove duplicated lines. Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Total Rewards: Salary Range: $96,800- $135,000 and Benefits list. So we can have Pay section (maybe heading "Pay") and Benefits section. Schedule not mentioned, so omit.
We need sections: About the role (Job Overview), Responsibilities (Key Responsibilities), Requirements (Requirements), Qualifications maybe overlapping with Requirements? The posting includes Requirements list and also "HR certification such as SHRM-CP...". Could treat Requirements as qualifications. Could also have Skills section if we extract skills like business acumen, data analytics, project management, etc. But we must not create thin sections. Perhaps combine Requirements and Qualifications into one? But rules say we can use those headings if content exists. We have content for Requirements (bullet list). Also we have "Company Overview" which is not required heading; we could put under About the role? Actually About the role already includes job overview. Company overview could be separate but not in allowed headings list; we could omit or incorporate into About the role? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but says use those for section headings. Probably we should stick to those. Company overview could be omitted as not required; but we must preserve ALL substantive information. If we omit company overview, we lose info. However we could incorporate company overview into About the role section as additional paragraph. That's allowed: About the role can contain job overview plus company overview. So we can merge.
Similarly, "Total Rewards Requirements Company Overview" at end seems duplicate; ignore.
Thus sections:
- About the role: combine Job Overview paragraph and Company Overview paragraph(s). Also maybe include the line about unlawful lie detector test? That's legal boilerplate; should be removed as per instruction: remove legal/EEO/equal-opportunity/scam-warning boilerplate. The lie detector test line is legal; remove.
- Responsibilities: list from Key Responsibilities bullet points.
- Requirements: list from Requirements bullet points.
- Qualifications: maybe we could separate certifications? But we could include under Requirements as part of list; but we have a separate heading Qualifications allowed. Could extract "HR certification such as SHRM-CP, SHRM-SCP, PHR, or SPHR." as qualifications. Also maybe "Bachelor's degree..." is requirement; but we already have that. To avoid duplication, we could put degree and experience under Requirements, and certifications under Qualifications. That seems reasonable.
- Skills: we could extract skills like business acumen, executive presence, influence, strategic thinking, hands-on execution, navigating change, workforce planning, talent discussions, employee relations, data analytics, project management, organizational, prioritization, partnering with leaders, etc. But we must avoid thin sections. Could create Skills section with bullet list of skills derived from responsibilities/requirements. However we must preserve all substantive info; if we put them in Skills, we still keep them. But we risk duplication if also in Requirements. Might be okay but could be considered duplication. Better to keep Requirements as is and not create Skills unless we have distinct skill statements not captured elsewhere. The posting includes "Strong business acumen with the ability to understand commercial, operational, and organizational drivers within a complex business environment." That's a skill. Also "Demonstrated ability to leverage data and analytics to identify trends, solve problems, and influence decisions." Also "Strong project management, organizational, and prioritization skills." Also "Experience partnering with business leaders on organizational design, talent strategy, succession planning, and workforce transformation." Those are more experience than skill. Could still be skills.
Given instruction: Prefer a few substantive sections over many thin ones. So maybe we skip Skills section and keep Requirements covering those. Qualifications for certifications.
Benefits: list from Benefits, subject to election and eligibility.
Pay: Salary range.
Schedule: not present, omit.
Now produce HTML:
About the role
Job overview paragraph(s) + company overview.
Need to preserve all substantive info from job overview and company overview. Let's extract: Job Overview: "The HR Manager will serve as a strategic business partner and trusted advisor to leaders across the Coffee Business Unit's corporate functions, providing HR expertise and leadership to support the execution of business priorities, organizational effectiveness, and talent strategies. This role will partner closely with Vice Presidents, Directors, and functional leadership teams across key Coffee Business Unit corporate functions, including Finance, Commercial Strategy, Digital & Technology, Human Resources, and other shared services organizations. The HR Business Partner will play a critical role in helping leaders build organizational capability, develop talent, drive engagement, and enable business performance through thoughtful people strategies and practical HR solutions. The successful candidate will possess strong business acumen, executive presence, and the ability to influence across a matrixed organization. This individual will balance strategic thinking with hands-on execution and be comfortable navigating organizational change, leadership transitions, workforce planning, talent discussions, and complex employee relations matters in a fast-paced environment." Company Overview: "Keurig Dr Pepper (Nasdaq: KDP) is a leading beverage company with more than 150 owned, licensed and partner brands that meet a wide range of needs and occasions. Our North American refreshment beverage business holds leadership positions across carbonated soft drinks, water, juice and mixers with a portfolio of iconic brands such as Dr Pepper®, Canada Dry®, Mott’s®, A&W®, Peñafiel®, GHOST®, 7UP®, Snapple®, Clamato® and Core Hydration®. Our global coffee business spans more than 100 markets and includes the leading Keurig® single-serve brewing system in the U.S. and Canada, along with powerhouse brands such as Peet’s, L’OR and Jacobs, and other regional coffee leaders. Our more than 50,000 employees aim to enhance the experience of every beverage and coffee occasion while making a positive impact for people, communities, and the planet. We strive to be an employer of choice, providing culture and opportunities that empower our team to grow and develop. We offer robust benefits to support your health and wellness as well as your personal and financial well-being. We also provide employee programs designed to enhance your professional growth and development, while ensuring you feel valued, inspired and appreciated at work. Whatever your area of expertise, at KDP you can be a part of a team that’s proud of its brands, partnerships, innovation and growth." We should omit the equal opportunity and AI disclosure lines. Also omit "Will you join us?" maybe keep as part of company overview? It's a call to action; could be considered boilerplate? It's not EEO but it's a promotional line. Might keep but it's not substantive? It's fluff. Safer to omit? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Will you join us?" is not exactly those but could be considered promotional fluff. Might keep? I'd keep it as part of company overview because it's part of the description. However it's not essential. I'd keep it to preserve substantive info? It's not substantive but it's part of the posting. The instruction says preserve ALL substantive information; not required to preserve fluff. I'd omit it. Thus About the role paragraph(s) combine the two paragraphs. Now Responsibilities: list each bullet from Key Responsibilities. Let's extract bullet points: - Serve as the primary HR business partner to leaders within assigned Coffee Business Unit corporate functions, ensuring people strategies align with business objectives and organizational priorities. - Partner with functional leadership teams to assess organizational effectiveness, workforce capabilities, talent needs, and succession plans to support current and future business growth. - Provide strategic coaching and consultation to Vice Presidents, Directors, and people leaders on organizational design, talent management, performance, employee engagement, and leadership effectiveness. - Partner with business leaders to identify capability gaps and develop talent strategies that strengthen organizational performance and leadership pipelines. - Support organizational changes, business transformation initiatives, restructuring activities, leadership transitions, and other strategic projects impacting Coffee corporate functions. - Leverage workforce analytics, engagement data, talent metrics, and business insights to identify trends and deliver recommendations that inform leadership decision-making. - Facilitate talent reviews, succession planning, leadership assessments, and development planning across supported functions. - Collaborate with HR Centers of Excellence to deliver integrated talent solutions, including recruiting, onboarding, compensation, learning and development, and performance management. - Drive the successful implementation of enterprise HR programs while ensuring alignment with the unique needs of Coffee Business Unit corporate teams. - Provide guidance and support related to employee relations matters, workplace concerns, policy interpretation, and performance issues while ensuring consistency and compliance. - Partner with leaders to foster an inclusive, high-performing culture characterized by accountability, collaboration, innovation, and employee engagement. - Support annual HR processes including performance management, talent planning, compensation cycles, engagement action planning, and organizational reviews. - Develop executive-ready presentations, analyses, and recommendations related to talent, organization effectiveness, workforce planning, and employee engagement. - Lead and contribute to cross-functional HR and business initiatives that support Coffee Business Unit priorities and transformation efforts. We'll put each as- .
Now Requirements: bullet list from Requirements section:
- Bachelor's degree in Human Resources, Business, or a related field, or equivalent combination of education and experience.
- 5+ years experience supporting corporate, professional, or functional employee populations within Finance, Strategy, Procurement, Marketing, R&D, IT, Commercial, Human Resources, Legal, or other corporate functions.
- Experience supporting senior leaders in a complex, matrixed organization.
- Demonstrated success supporting complex organizations through change, growth, organizational redesign, or transformation initiatives.
- Experience managing employee relations matters and providing coaching and consultation to leaders.
- Strong business acumen with the ability to understand commercial, operational, and organizational drivers within a complex business environment.
- Demonstrated ability to leverage data and analytics to identify trends, solve problems, and influence decisions.
- Strong project management, organizational, and prioritization skills.
- Experience partnering with business leaders on organizational design, talent strategy, succession planning, and workforce transformation.
- Experience within consumer packaged goods, food & beverage, manufacturing, or a similarly fast-paced environment.
- HR certification such as SHRM-CP, SHRM-SCP, PHR, or SPHR.
We could split: put the first 10 items under Requirements, and the certification under Qualifications. But the certification is also a requirement. However we have a Qualifications heading allowed; we can put certification there.
Thus Requirements: list items except the last certification.
Qualifications: list HR certification.
Now Benefits: list from Benefits, subject to election and eligibility: Medical, Dental, Vision, Disability, Paid Time Off (including paid parental leave, vacation, and sick time), 401k with company match, Tuition Reimbursement, and Mileage Reimbursement.
We'll put as
- .
Pay: Salary Range: $96,800- $135,000. Also note "Actual placement within the compensation range may vary depending on experience, skills, and other factors". That's substantive; include.
Thus Pay section:
Salary Range: $96,800- $135,000. Actual placement within the compensation range may vary depending on experience, skills, and other factors.
Schedule: none. Now ensure we don't repeat job title as heading. Not using. Now output HTML fragment only. Let's craft.