Sr. HR Business Partner
Vertiv · Westerville, OH · 4 wk ago
Human ResourcesFull-time
We need to output HTML fragment with sections: About the role? Actually the job description includes "Job Description" then description. We need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. The posting includes: Job Description (intro paragraph), Responsibilities (list), Qualifications (list), Additional / Preferred Qualifications N/A (skip), Physical & Environmental Requirements N/A (skip), Time Travel Needed N/A (skip), About Us (some content), Work Authorization (some content), Equal Opportunity Employer (boilerplate to remove). Also there is "About Vertiv" etc. We need to preserve substantive info, remove boilerplate/legal/EEO etc. Also remove duplicated lines, navigation, cookie etc. Not present.
We need to decide sections: Possibly "About the role" (intro paragraph), "Responsibilities", "Qualifications", "About Us" maybe as "About the company"? But headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also add "About the company" not in list but maybe we can use "About the role" for intro, and "About Us" could be considered "About the role"? Not exactly. The instruction: use
.
Qualifications list: extract each bullet:
"Bachelor's degree in Human Resources, Business Administration, Organizational Development, or related discipline
8+ years of progressive HR Business Partner experience, with demonstrated success supporting large, complex, and geographically dispersed organizations
Proven experience partnering with senior and executive leadership on strategic workforce initiatives
Working knowledge of multiple human resource disciplines, including compensation practices, organizational diagnosis, employee relations, diversity, performance management, and employment laws
Expertise in organizational design, change management, and workforce planning within field services, operations, or similarly decentralized business models
Strong attention to detail. Attentive to detail and accuracy, performs quality work, continuously looks for improvements, owns/acts on problems, and seeks opportunities to increase effectiveness and efficiency.
Strong track record managing employee relations matters and conducting thorough investigations
Strong global & cultural Awareness.
HR Expertise in talent acquisition, total rewards, learning and development, employee relations and communication
Demonstrated ability to develop and execute talent strategies that address high-volume, technical, or hard-to-fill workforce segments
Strong analytical capabilities with experience leveraging HR data and metrics to drive business decisions"
Note some lines have extra sentences; we keep as is.
Now we need to output only HTML fragment, no markdown.
Let's craft:
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. The posting includes: Job Description (intro paragraph), Responsibilities (list), Qualifications (list), Additional / Preferred Qualifications N/A (skip), Physical & Environmental Requirements N/A (skip), Time Travel Needed N/A (skip), About Us (some content), Work Authorization (some content), Equal Opportunity Employer (boilerplate to remove). Also there is "About Vertiv" etc. We need to preserve substantive info, remove boilerplate/legal/EEO etc. Also remove duplicated lines, navigation, cookie etc. Not present.
We need to decide sections: Possibly "About the role" (intro paragraph), "Responsibilities", "Qualifications", "About Us" maybe as "About the company"? But headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also add "About the company" not in list but maybe we can use "About the role" for intro, and "About Us" could be considered "About the role"? Not exactly. The instruction: use 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 stick to those headings when appropriate. We can also add other headings if needed? It 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: Intro paragraph about role: "The Sr. HR Business Partner (HRBP) position is responsible for aligning business objectives with employees and management in designated business units. The position serves as a consultant to management on human resource-related issues and acts as a strategic business partner, change agent, employee champion and HR process/policy expert to support business strategy and objectives." That fits About the role.
Responsibilities: list of duties.
Qualifications: list of qualifications (Bachelor's degree, 8+ years, etc). Also Additional / Preferred Qualifications N/A skip.
Skills: maybe we could extract skills from qualifications? But we have no explicit skills section. Could we create Skills from qualifications like "Strong attention to detail", "Strong track record managing employee relations", etc? Those are more qualifications. Might be better to not create Skills if no explicit content. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills? But we need to follow headings. If we don't have specific content for Skills, we should omit that section.
Requirements: maybe we could treat Qualifications as Requirements? But they are separate headings. The posting has Qualifications section; we could map that to Qualifications heading. Requirements maybe not present. Could we treat "Additional / Preferred Qualifications N/A" as Requirements? It's N/A, so skip.
Benefits, Pay, Schedule: not present, so omit.
About Us: we have content about Vertiv core principles, strategic priorities, About Vertiv, Work Authorization (legal). The "About Us" could be considered "About the role"? Not exactly. But we have a section "About Us" with substantive content (core principles, strategic priorities, About Vertiv). We could map that to "About the role"? No. Perhaps we could treat "About Us" as "About the role"? Not ideal. However the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It does not forbid using headings not in the list, but they gave examples. Safer to stick to the list. But we have substantive content about the company that doesn't fit any of the headings. Could we put it under "About the role"? Might be a stretch but maybe acceptable as it's about the role's context. However the intro already covers role description; adding company info might be okay under "About the role" as additional context. But we must not invent or summarize away detail. We can include that content as a paragraph under About the role after the intro.
Alternatively we could create a section "About the company" but not in list; risk of being considered not following instruction. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we could use other headings like "About Us". I think it's safe to use "About Us" as a heading because it's present in the posting and has substantive content. The instruction didn't forbid other headings; just gave examples. So we can include About Us.
Similarly we have "Work Authorization" which is substantive (no sponsorship). Could be its own section? Not in examples but could be included. However it's more like a requirement; maybe we could fold into Qualifications or Requirements. But it's about work authorization, not a qualification. Could be a separate section "Work Authorization". But we need to decide.
We also have Equal Opportunity Employer boilerplate to remove.
Thus final HTML: sections:
About the role
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: Intro paragraph about role: "The Sr. HR Business Partner (HRBP) position is responsible for aligning business objectives with employees and management in designated business units. The position serves as a consultant to management on human resource-related issues and acts as a strategic business partner, change agent, employee champion and HR process/policy expert to support business strategy and objectives." That fits About the role.
Responsibilities: list of duties.
Qualifications: list of qualifications (Bachelor's degree, 8+ years, etc). Also Additional / Preferred Qualifications N/A skip.
Skills: maybe we could extract skills from qualifications? But we have no explicit skills section. Could we create Skills from qualifications like "Strong attention to detail", "Strong track record managing employee relations", etc? Those are more qualifications. Might be better to not create Skills if no explicit content. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills? But we need to follow headings. If we don't have specific content for Skills, we should omit that section.
Requirements: maybe we could treat Qualifications as Requirements? But they are separate headings. The posting has Qualifications section; we could map that to Qualifications heading. Requirements maybe not present. Could we treat "Additional / Preferred Qualifications N/A" as Requirements? It's N/A, so skip.
Benefits, Pay, Schedule: not present, so omit.
About Us: we have content about Vertiv core principles, strategic priorities, About Vertiv, Work Authorization (legal). The "About Us" could be considered "About the role"? Not exactly. But we have a section "About Us" with substantive content (core principles, strategic priorities, About Vertiv). We could map that to "About the role"? No. Perhaps we could treat "About Us" as "About the role"? Not ideal. However the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It does not forbid using headings not in the list, but they gave examples. Safer to stick to the list. But we have substantive content about the company that doesn't fit any of the headings. Could we put it under "About the role"? Might be a stretch but maybe acceptable as it's about the role's context. However the intro already covers role description; adding company info might be okay under "About the role" as additional context. But we must not invent or summarize away detail. We can include that content as a paragraph under About the role after the intro.
Alternatively we could create a section "About the company" but not in list; risk of being considered not following instruction. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we could use other headings like "About Us". I think it's safe to use "About Us" as a heading because it's present in the posting and has substantive content. The instruction didn't forbid other headings; just gave examples. So we can include About Us.
Similarly we have "Work Authorization" which is substantive (no sponsorship). Could be its own section? Not in examples but could be included. However it's more like a requirement; maybe we could fold into Qualifications or Requirements. But it's about work authorization, not a qualification. Could be a separate section "Work Authorization". But we need to decide.
We also have Equal Opportunity Employer boilerplate to remove.
Thus final HTML: sections:
About the role
About the role
Intro paragraph.
About Us content (core principles, strategic priorities, About Vertiv).
Responsibilities
- ...
Qualifications
- ...
Work Authorization
with paragraph. But we need to avoid duplication: The About Us content includes "The successful candidate will embrace Vertiv’s Core Principles & Behaviors..." etc. That's substantive. Let's extract: About Us paragraph: "The successful candidate will embrace Vertiv’s Core Principles & Behaviors to help execute our Strategic Priorities. OUR CORE PRINCIPLES: Safety. Integrity. Respect. Teamwork. Inclusion. OUR STRATEGIC PRIORITIES High-Performance Culture Customer Focus Operational Excellence Innovation Financial Strength VERTIV BEHAVIORS Own it Act with urgency Foster a customer-first mindset Think big and execute Lead by example Drive continuous improvement Learn and seek out development Promote transparent & open communication About Vertiv Vertiv (NYSE: VRT) brings together hardware, software, analytics and ongoing services to enable its customers’ vital applications to run continuously, perform optimally and grow with their business needs. Vertiv solves the most important challenges facing today’s data centers, communication networks, and commercial and industrial facilities with a portfolio of power, cooling and IT infrastructure solutions and services that extend from the cloud to the edge of the network. Headquartered in Westerville, Ohio, USA, Vertiv employs around 34,000 people and does business in more than 130 countries. Visit Vertiv.com to learn more." Work Authorization: "Work Authorization No calls or agencies please. Vertiv will only employ those who are legally authorized to work in the United States. This is not a position for which sponsorship will be provided. Individuals with temporary visas such as E, F-1, H-1, H-2, L, B, J, or TN or who need sponsorship for work authorization now or in the future, are not eligible for hire." We should keep that as a section maybe "Work Authorization". It's substantive. Now Responsibilities list: need to extract each bullet from the responsibilities paragraph. The responsibilities are a long sentence with multiple acts separated by line breaks? In the posting they are separated by line breaks? Let's parse: "Acts as a single point of the contact for the employees and managers in the business unit As a strategic partner to assigned business, identify HR needs required by the business and develop executive HR strategies to support the business strategy Acts as thought partner and coach to business leaders to enhance employee engagement and drive a high performing culture Identify team development gaps and facilitate team development activities to improve collaboration and team performance Assess the organizational needs of the business units and work with the business leaders to change and improve the organizational structure, process, systems, rewards necessary to achieve the desired culture and business objectives Acts as change agent in managing organizational changes to ensure achievement of desired business results Acts as employee champion in promoting employee value proposition and drive employee engagement and communication to be the employer of choice Acts as HR policy and process expert and proactively work with COEs in workforce planning, talent acquisition, total rewards, performance management, learning and development, HRIS to ensure delivery of high impact HR services and programs Conducts weekly meetings with respective business units. Consults with line management, providing HR guidance when appropriate. Analyzes trends and metrics in partnership with the HR group to develop solutions, programs and policies. Manages and resolves complex employee relations issues. Conducts effective, thorough and objective investigations. Maintains in-depth knowledge of legal requirements related to day-to-day management of employees, reducing legal risks and ensuring regulatory compliance. Partners with the legal department as needed/required." We'll make each line aAbout the role
The Sr. HR Business Partner (HRBP) position is responsible for aligning business objectives with employees and management in designated business units. The position serves as a consultant to management on human resource-related issues and acts as a strategic business partner, change agent, employee champion and HR process/policy expert to support business strategy and objectives.
The successful candidate will embrace Vertiv’s Core Principles & Behaviors to help execute our Strategic Priorities. OUR CORE PRINCIPLES: Safety. Integrity. Respect. Teamwork. Inclusion. OUR STRATEGIC PRIORITIES High-Performance Culture Customer Focus Operational Excellence Innovation Financial Strength VERTIV BEHAVIORS Own it Act with urgency Foster a customer-first mindset Think big and execute Lead by example Drive continuous improvement Learn and seek out development Promote transparent & open communication About Vertiv Vertiv (NYSE: VRT) brings together hardware, software, analytics and ongoing services to enable its customers’ vital applications to run continuously, perform optimally and grow with their business needs. Vertiv solves the most important challenges facing today’s data centers, communication networks, and commercial and industrial facilities with a portfolio of power, cooling and IT infrastructure solutions and services that extend from the cloud to the edge of the network. Headquartered in Westerville, Ohio, USA, Vertiv employs around 34,000 people and does business in more than 130 countries. Visit Vertiv.com to learn more.
Responsibilities
- Acts