Director, People Team Business Partner

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; 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 parse the job posting. Content: - Mission statement (Our Mission...). This is not a specific section heading but could be part of "About the role"? Actually it's about company mission. Could be part of "About the role" or maybe we can include a short paragraph under a heading like "About the role" or "Company Overview". The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose headings that match content. We have: - Who We Are (mission, values, AI, collaboration, office model). This could be "About the role" or "Company Overview". But we need to decide. - Job Summary: description of role. - Key Responsibilities: bullet list (though it's a paragraph with periods separating responsibilities). We need to turn into

• . - Qualifications: Required Qualifications and Preferred Qualifications. Could be under "Requirements" or "Qualifications". The instruction includes "Requirements" and "Qualifications" as possible headings. We can combine required and preferred under "Qualifications". Or separate "Required Qualifications" and "Preferred Qualifications" as subheadings? But only allowed headings are those listed; we can still use

  for those headings; we could have "Required Qualifications" and "Preferred Qualifications" as separate h3s? The list includes "Qualifications". It didn't forbid other headings, but says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where appropriate. Probably we should use "Responsibilities", "Qualifications". Could also have "About the role" for mission and who we are. Could have "Pay" for compensation disclosure. Could have "Benefits" if benefits described (they mention "A description of our employee benefits may be found here." but not actual benefits list). So we should not create Benefits section because no specific benefits listed. Pay: they give salary range $212,000 - $290,850/yr, plus mention restricted stock units and bonus. So we can include Pay section with that info. Schedule: they mention "We believe collaboration thrives in person. That’s why most of our teams work from the office full time, with flexibility when it’s needed." That's schedule info (office full time, flexibility). So we can include Schedule section. We must not include filler like "commensurate with experience". Not present. We must remove boilerplate: EEO, immigration sponsorship, accommodations, equal opportunity, etc. Also remove "Our Commitment" maybe? It includes diversity statement and accommodations. That's boilerplate/EEO. Should remove. Also remove "Is role eligible for Immigration Sponsorship? No." etc. We must preserve all substantive information: mission, who we are, job summary, responsibilities, qualifications (required and preferred), compensation disclosure (salary range, stock, bonus), schedule (office full time with flexibility). Also maybe mention "We weave AI into the fabric of everything we do". That's substantive. We need to format as HTML fragment only, no /, no markdown fences. We need to use

  for section headings. Use

  • for any list of duties/requirements/benefits. Use

    for prose. We need to decide which sections to include. Potential sections: - About the role (or Company Overview): includes mission, who we are, values, AI, office model. - Responsibilities: list of key responsibilities. - Qualifications: required and preferred. - Pay: compensation disclosure. - Schedule: office full time with flexibility. We should not include Benefits because no specific benefits listed. We need to ensure we don't repeat job title as heading. The job title is "Director, People Business Partner". Not to be used as heading. We need to preserve all substantive information. Let's extract. Mission paragraph: "Our Mission At Palo Alto Networks®, we’re united by a shared mission—to protect our digital way of life. We thrive at the intersection of innovation and impact, solving real-world problems with cutting-edge technology and bold thinking. Here, everyone has a voice, and every idea counts. If you’re ready to do the most meaningful work of your career alongside people who are just as passionate as you are, you’re in the right place." Who We Are: "In order to be the cybersecurity partner of choice, we must trailblaze the path and shape the future of our industry. This is something our employees work at each day and is defined by our values: Disruption, Collaboration, Execution, Integrity, and Inclusion. We weave AI into the fabric of everything we do and use it to augment the impact every individual can have. If you are passionate about solving real-world problems and ideating beside the best and the brightest, we invite you to join us! We believe collaboration thrives in person. That’s why most of our teams work from the office full time, with flexibility when it’s needed. This model supports real-time problem-solving, stronger relationships, and the kind of precision that drives great outcomes." Job Summary: "As a Director, People Business Partner, you will be an integral leader driving people and organizational strategies to anticipate challenges and implement impactful solutions across our Finance organization. You will leverage your expertise to enable the business to achieve its objectives while cultivating a workplace environment that attracts and retains top talent. By coaching leaders and teams, you will foster a culture of collaboration, innovation, and high performance. We are seeking a strategic, data-driven HR professional who excels at navigating complex change, delivering creative, effective people solutions and partnering with leaders to drive transformation." Key Responsibilities (list): - Design people strategies and build programs that scale the organization, build high-performing teams, and develop best-in-class leaders. - Partner with a team of People Business Partners to execute people strategies and cross-functional initiatives effectively. - Leverage people analytics to anticipate organizational issues and deliver data-driven solutions that drive measurable business impact. - Protect our unique culture and ensure the company remains a premier destination for top industry talent. - Collaborate with functional HR leaders to design and deliver competitive compensation, benefits, and leadership development programs. - Lead people practices that foster innovation and collaboration within a highly advanced, mission-driven technology organization. Qualifications Required: - Bachelor's degree or equivalent military experience required. - Minimum of 15 years of progressive HR/People experience, preferably within a technology organization or multinational company. - Proven experience supporting a Finance organization or similar complex business unit. - Demonstrated experience managing, mentoring, and developing a small team. - Ability to develop and execute people strategies by analyzing organizational needs and setting impactful goals. - Track record of coaching leaders and advising on sensitive employee relations, performance management, and organizational diagnostics. - Strong analytical skills with the ability to leverage data insights to drive people programs and solutions. Preferred Qualifications: - Exceptional ability to establish strong, trusted relationships at all levels and across functions within a fast-paced environment. - Highly effective listener and persuasive communicator with a proven ability to influence actions and outcomes. - Demonstrated commitment to fostering a 'one team' culture that values diversity, inclusion, and a positive work environment. Compensation Disclosure: "The compensation offered for this position will depend on qualifications, experience, and work location. For candidates who receive an offer at the posted level, the starting base salary (for non-sales roles) or base salary + commission target (for sales/com-missioned roles) is expected to be the annual range listed below. The offered compensation may also include restricted stock units and a bonus. A description of our employee benefits may be found here. $212,000.00 - $290,850.00/yr" We need to preserve that. The sentence about benefits description link is maybe boilerplate but it's part of compensation disclosure; we can keep it as prose. Schedule: from Who We Are: "We believe collaboration thrives in person. That’s why most of our teams work from the office full time, with flexibility when it’s needed. This model supports real-time problem-solving, stronger relationships, and the kind of precision that drives great outcomes." We can put that under Schedule. Now we need to output HTML. We should not include any extraneous whitespace? It's fine. We need to use

    for each section heading. We need to use

    • for lists. We need to use

      for prose. We must not repeat job title as heading. We must not include Job ID/requisition numbers (none present). We must not include boilerplate like EEO, accommodations, immigration sponsorship, equal opportunity, etc. We removed those. Now decide sections: - About the role (or Company Overview): combine Mission and Who We Are? Could be two paragraphs under same heading. - Responsibilities: list. - Qualifications: maybe split into Required and Preferred as subheadings? But we only have allowed headings; we could still use

      for "Required Qualifications" and "Preferred Qualifications". The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should prefer those. However we could also use "Qualifications" as heading and inside have two

      paragraphs: one for Required, one for Preferred. That would be acceptable. - Pay: compensation disclosure. - Schedule: office full time with flexibility. We should not include Benefits. Now we need to ensure we preserve all substantive information. Let's craft. Section About the role: We'll put two

      paragraphs: first mission paragraph, second who we are paragraph (including values, AI, office model). However the office model also belongs to Schedule; but we can keep it in About the role and also mention in Schedule? Might duplicate. Better to split: About the role includes mission, who we are (values, AI, invitation). Schedule includes office full time with flexibility. Thus About the role paragraph(s) will not include the office model sentence; we will move that to Schedule. Let's extract Who Are without the office model sentence: "In order to be the cybersecurity partner of choice, we must trailblaze the path and shape the future of our industry. This is something our employees work at each day and is defined by our values: Disruption, Collaboration, Execution, Integrity, and Inclusion. We weave AI into the fabric of everything we do and use it to augment the impact every individual can have. If you are passionate about solving real-world problems and ideating beside the best and the brightest, we invite you to join us!" That's substantive. Now Schedule: "We believe collaboration thrives in person. That’s why most of our teams work from the office full time, with flexibility when it’s needed. This model supports real-time problem-solving, stronger relationships, and the kind of precision that drives great outcomes." Now Responsibilities: list as

      • . Qualifications: we can have