Senior People Partner- HRBP

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the Role: The posting has "About the Role" heading with paragraphs describing role. - Responsibilities: There is a list of duties: "Serve as a trusted People Partner to Engineering and Product teams in the U.S., with additional support for G&A, translating business priorities into practical people plans. Coach leaders and managers on organizational design, performance, talent development, compensation, employee relations, and team effectiveness. Use employee feedback, engagement insights, and people data to identify themes and partner with leaders on focused, actionable improvements. Partner with People & Culture colleagues to strengthen talent retention, succession, and development approaches that support business needs and employee growth. Collaborate with local People Partners in EMEA and APAC on Engineering and Product initiatives, balancing global consistency with local context. Build strong relationships across the business and People & Culture team, working flexibly across time zones when global collaboration is needed." These are responsibilities. - Requirements: The posting includes "We are looking for you if you have 8-10 years of HR Business Partner or People Partner experience, with a track record of advising leaders in dynamic, evolving organizations; experience partnering with R&D organizations, particularly Engineering and Product, is strongly preferred." Also "Strong business acumen and the ability to connect people priorities to team and company goals while keeping solutions practical and employee-centered." etc. Those are more like qualifications/skills. We need to decide sections: Could have Requirements (experience), Qualifications (skills), Skills (maybe overlapping). But we should avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one? But they ask to use headings for those categories if content exists. We need to decide based on content. We have: - Experience: 8-10 years HRBP, advising leaders, partnering with R&D/Engineering/Product. - Business acumen, ability to connect people priorities to goals. - Experience coaching leaders through performance, talent, organizational change, employee relations, team effectiveness. - Comfort using employee feedback and people data to identify patterns, shape recommendations, support decision-making. - Clear, collaborative communication skills, ability to build trust and influence across levels, functions, geographies, time zones. - Pragmatic, curious, inclusive approach, sound judgment, willingness to roll up sleeves. These could be considered Qualifications/Skills. We could have a "Requirements" section for the experience (8-10 years) and maybe "Qualifications" for the rest. Or combine into "Requirements and Qualifications". But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role, Responsibilities, Requirements (experience), Qualifications (business acumen etc), Skills (maybe communication etc). Could separate but risk thin sections. Better: Combine Requirements and Qualifications into one "Requirements" section that includes experience and qualifications. Then maybe "Skills" for communication etc. But we have overlapping. Given instruction to prefer few substantive sections, we could have: - About the role - Responsibilities - Requirements (covers experience, qualifications, skills) - Benefits - Pay Schedule not mentioned, so omit. Benefits: The posting mentions benefits: "We invest in your success as well as the spaces where our teams come together to work, collaborate, and have fun. We love celebrating our SmartBears; we even encourage our crew to take their birthdays off. We are guided by a People and Culture organization - an important distinction for us. We think about our team holistically – the whole person. We celebrate our differences in experiences, viewpoints, and identities because we know it leads to better outcomes." Also later: "Our compensation philosophy is grounded in market competitiveness, internal equity, and rewarding impact. We encourage candidates to view compensation as part of their total rewards experience at SmartBear. This includes performance-based bonuses for eligible roles, a generous benefits package that supports employees’ health and well-being, and promotes work-life balance through flexible time off and hybrid work options. You can build your career at SmartBear through professional development opportunities, and an inclusive, collaborative culture where everyone can thrive." Thus benefits: performance-based bonuses, generous benefits package (health, well-being), flexible time off, hybrid work options, professional development opportunities, inclusive culture, birthday off, etc. Pay: "Estimated Base Salary Range: $135,000 USD - $162,250 USD". Also mention base salary and may include performance bonus plan. Thus we have Pay. Now we need to output HTML with

for each section heading, and

• for any list of duties/requirements/benefits, and

  for prose. We need to decide what to put in lists. Responsibilities: we have multiple sentences; could be list items. Requirements: we have experience (8-10 years) plus other qualifications; could be list. Benefits: list items. Pay: maybe a paragraph with salary range. We must not include boilerplate like EEO, navigation, etc. We must preserve all substantive information; do not invent or summarize away detail. We need to include all substantive info from the posting. Let's extract all substantive sentences: From intro about SmartBear (company description) - is that substantive? It's about the company, not the role. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Does that include company overview? Likely yes, as it's part of posting. However we are to format job posting into clean HTML. Usually we include company overview maybe as a paragraph before About the role. There's no heading for that; we could put it in a

  before the first heading. The instruction says use

  for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other paragraphs outside headings. So we can include a leading paragraph summarizing SmartBear description. But we must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description is not boilerplate; it's substantive. Thus we will include an opening

  with the SmartBear description (first paragraph up to "Learn more at www.smartbear.com, or follow us on LinkedIn, X, and Reddit.") Actually that includes a call to action (Learn more...). That might be considered navigation? It's a link to website and social media; could be considered boilerplate? It's not EEO but it's a call to action; maybe we should keep it as it's part of the posting. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Learn more at www.smartbear.com, or follow us on LinkedIn, X, and Reddit." is like a navigation/footer; could be considered navigation. Might be safe to remove. However it's not explicitly navigation like menu; but it's a link to external sites. Might be considered promotional. Safer to remove? The instruction says remove navigation boilerplate. That line is basically a call to follow on social media; could be considered navigation. I'd remove it. Also the sentence "At SmartBear, you will be part of a dynamic team solving one of the most critical challenges facing modern businesses: ensuring the integrity of software in an AI-driven world. Whether you are working directly with customers, driving go to market strategies, supporting operations, building products, or enabling teams, your contributions help shape the future of software quality for organizations worldwide. Join us in our mission." This is substantive about the role and mission; keep. Then we have "Senior People Partner (HRBP)" as job title; we should not repeat as heading. It appears before "Partner with Engineering and Product leaders...". That's part of the role summary. We'll include that as a paragraph maybe. Then "About the Role" heading. We need to ensure we don't duplicate content. Let's extract sections: Opening company description (first paragraph up to before "Learn more at..."): "SmartBear delivers application integrity for modern tech stacks, ensuring continuous, measurable assurance that software just works as intended with governance to operate at AI speed and scale. SmartBear offers deep test automation, API lifecycle management, and observability capabilities. With integrations across the SDLC, it sets a new quality standard for application delivery teams. SmartBear is trusted by developers, testers, and software engineers across 32,000 organizations, including 75% of the largest financial institutions and industry leaders such as Adobe, JetBlue, and Microsoft. SmartBear’s open source tools are downloaded more than 100 million times a month and have earned over 30,000 GitHub stars from the developer community. With its best-loved brands, including Swagger, TestComplete, Reflect, QMetry, Zephyr, and more, SmartBear meets customers where they are to make our technology-driven world a better place." Then maybe a sentence: "Learn more at www.smartbear.com, or follow us on LinkedIn, X, and Reddit." Remove. Then: "At SmartBear, you will be part of a dynamic team solving one of the most critical challenges facing modern businesses: ensuring the integrity of software in an AI-driven world. Whether you are working directly with customers, driving go to market strategies, supporting operations, building products, or enabling teams, your contributions help shape the future of software quality for organizations worldwide. Join us in our mission." Then job title line: "Senior People Partner (HRBP) Partner with Engineering and Product leaders in the U.S., while also supporting G&A teams, to connect people priorities with business goals. Coach leaders and managers on organizational effectiveness, talent, performance, engagement, and employee relations across a growing, fast-moving environment. Collaborate with People Partners in EMEA and APAC on global Engineering and Product initiatives, bringing a consistent employee experience across regions." Then "About the Role" heading and its content. Then responsibilities list (the bullet points after About the Role? Actually the content after About the Role includes those responsibilities). We'll treat that as Responsibilities. Then "We are looking for you if you have 8-10 years of HR Business Partner or People Partner experience, with a track record of advising leaders in dynamic, evolving organizations; experience partnering with R&D organizations, particularly Engineering and Product, is strongly preferred." plus following sentences about business acumen, coaching, using feedback, communication skills, pragmatic approach. Then "Why you should join the SmartBear crew" section includes benefits and culture. Then compensation and benefits details. We need to avoid duplication: The "Why you should join..." includes many benefit statements; we should capture them under Benefits. Also the earlier part about "We invest in your success..." is also benefits. We'll combine. Now we need to output HTML. We'll start with a

  for company description. Then a

  for the "At SmartBear, you will be part..." paragraph. Then a

  for the Senior People Partner (HRBP) line? Actually that line is a summary of role; could be part of About the role? But we have an About the role heading later; we could treat that line as part of About the role content. However the About the role heading already has its own content; we might duplicate if we include both. Better to treat the Senior People Partner line as part of About the role content (maybe as first paragraph under that heading). But the About the role heading content currently is: "Serve as a trusted People Partner to Engineering and Product teams in the U.S., with additional support for G&A, translating business priorities into practical people plans. Coach leaders and managers on organizational design, performance, talent development, compensation, employee relations, and team effectiveness.