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 need to parse the posting.
First, "About The Role" paragraph: "Chime is looking for a Principal People Partner to lead multiple functions including our rapidly growing enterprise business. This role will work closely with our VP of People Partners and be located in our NYC office. As a People Partner at Chime, you will help align business objectives with People solutions for different business organizations that you will support. We are looking for someone who can be a strategic thought partner, workforce planner, talent steward, program deployer, and a leadership coach."
That's about the role.
Then later: "The base salary offered for this role and level of experience will begin at $167,000.00 and up to $230,000.00. Full-time employees are also eligible for a bonus, competitive equity package, and benefits. The actual base salary offered may be higher, depending on your location, skills, qualifications, and experience."
So Pay section: salary range.
Benefits: later "What We Offer For Our Full-time, Regular Employees" includes bullet list: in-office work policy, backup child/elder/pet care, subsidized commuter benefits, comprehensive health/financial/wellbeing benefits, generous vacation policy and company-wide paid days off, 1% of your time off to support local community organizations, annual wellness stipend, up to 22 weeks of paid parental leave for birthing parents and 12 weeks for non-birthing parents, access to family planning reimbursement, challenging and fulfilling opportunity... Also mention "We know that great work can’t be done without a diverse team..." but that's more culture.
We need to extract benefits as list.
Responsibilities: The paragraph after "In this role, you can expect to" includes a list of duties: Working alongside business leaders..., Coach managers..., Collaborating..., By partnering..., Collaborate..., Ensure..., Actively participate..., Partner..., etc. Those are responsibilities.
Requirements/Qualifications/Skills: The section "To thrive in this role, you have" includes bullet-like sentences: At least 10+ years of HR business partner experience. Expertise in building trusting relationships..., A data driven outlook..., Sense of empathy..., The ability to strike a balance..., Comfort with interpreting..., A passion for advocating..., A passion for seeing others grow... Those are qualifications/skills.
We need to decide which sections to output. We have About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay. Schedule: The posting mentions in-office work policy: four days a week in office and Fridays from home for those near one of our offices, plus team and company-wide events depending on location. That's schedule info. So we can include Schedule section.
We must not repeat job title as heading. No Job ID.
We must not include boilerplate like EEO, etc.
We must not create sections with filler like "commensurate with experience". We have actual content.
Now produce HTML:
About the role
...
Responsibilities
We need to split responsibilities into list items.
Responsibilities sentences:
- Working alongside business leaders and other people partners, you'll bring together your people expertise with knowledge of our business to deliver people strategies that help grow and develop our talent.
- Coach managers. Leveraging your experience to understand the needs of your business groups and navigating difficult conversations to coach managers and leaders through the full range of the employee lifecycle.
- Collaborating with other People team members to effectively communicate and plan organizational changes by advocating for the needs of your client groups and facilitating communications and training.
- By partnering with People Operations and Senior People Partners, you'll help drive decisions that align our culture with our reward strategies while ensuring internal parity.
- Collaborate with stakeholders to advocate for and nurture the culture within our business teams.
- Ensure that the unique voices, perspectives, and challenges of each team are recognized and addressed working in partnership with people COEs and enablement functions.
- Actively participate in the design, execution, and rollout of company-wide initiatives.
- Partner with the People Centers of Excellence (COEs) to ensure successful implementation.
We can combine some sentences but keep as separate li.
Now Requirements/Qualifications/Skills: We have list:
- At least 10+ years of HR business partner experience.
- Expertise in building trusting relationships with leaders at all levels.
- A data driven outlook and use people metrics to inform decision making.
- Sense of empathy and understanding for the needs of diverse groups of people.
- The ability to strike a balance between strategic partnership-building and getting things done.
- Comfort with interpreting and using people data to tell a story and translating it into actionable strategy.
- A passion for advocating for others, speaking up even when it's difficult, and seeing others accomplish their goals.
- A passion for seeing others grow through coaching, mentoring, and career development.
We could put these under Requirements or Qualifications. The instruction says use headings like Requirements, Qualifications, Skills. We need to decide which to include. Probably combine into one section "Requirements" or "Qualifications". Since they are qualifications/skills, we could have "Qualifications" and maybe "Skills". But we should avoid thin sections. Could combine into one "Qualifications" section containing all.
But we also have Skills maybe overlapping. To keep few substantive sections, we can have "Qualifications" covering all.
Now Benefits: list items:
- In-office work policy: four days a week in the office and Fridays from home for those near one of our offices, plus team and company-wide events depending on location.
- Backup child, elder, and pet care and subsidized commuter benefits for eligible employees.
- Comprehensive health, financial, and wellbeing benefits designed to support you at every stage of life.
- Generous vacation policy and company-wide paid days off.
- 1% of your time off to support local community organizations of your choice.
- Annual wellness stipend to use towards eligible wellness related expenses.
- Up to 22 weeks of paid parental leave for birthing parents and 12 weeks of paid parental leave for non-birthing parents.
- Access to family planning reimbursement.
- A challenging and fulfilling opportunity to join one of the most experienced teams in FinTech and help millions unlock financial progress.
We could also mention "We know that great work can’t be done without a diverse team..." but that's more culture; maybe not needed.
Pay: salary range: base salary $167,000 to $230,000, plus bonus, competitive equity package, benefits. Also mention actual base may be higher depending on location, skills, qualifications, experience.
We'll put in Pay section.
Schedule: The in-office work policy already covered in Benefits; but schedule is separate: "Our in-office work policy is designed to keep you connected - with four days a week in the office and Fridays from home for those near one of our offices, plus team and company-wide events depending on location." That's schedule. However we already used that as a benefit item. Might duplicate. Better to put schedule separately and not duplicate in benefits. But we can keep schedule as separate section and maybe remove from benefits. However benefits list includes many items; we could keep schedule as separate and not duplicate. Let's extract schedule: "Our in-office work policy is designed to keep you connected - with four days a week in the office and Fridays from home for those near one of our offices, plus team and company-wide events depending on location." That's schedule.
Thus Benefits section will exclude that line.
Now Benefits list items (excluding schedule):
- Backup child, elder, and pet care and subsidized commuter benefits for eligible employees.
- Comprehensive health, financial, and wellbeing benefits designed to support you at every stage of life.
- Generous vacation policy and company-wide paid days off.
- 1% of your time off to support local community organizations of your choice.
- Annual wellness stipend to use towards eligible wellness related expenses.
- Up to 22 weeks of paid parental leave for birthing parents and 12 weeks of paid parental leave for non-birthing parents.
- Access to family planning reimbursement.
- A challenging and fulfilling opportunity to join one of the most experienced teams in FinTech and help millions unlock financial progress.
Now we need to ensure we don't include boilerplate like EEO etc.
Now produce HTML.
We'll wrap each section with
and then
or
- .
Make sure to not include extra whitespace? It's fine.
Let's craft.
About the role paragraph: combine the two sentences: "Chime is looking for a Principal People Partner to lead multiple functions including our rapidly growing enterprise business. This role will work closely with our VP of People Partners and be located in our NYC office. As a People Partner at Chime, you will help align business objectives with People solutions for different business organizations that you will support. We are looking for someone who can be a strategic thought partner, workforce planner, talent steward, program deployer, and a leadership coach."
Now Responsibilities ul.
Now Qualifications ul.
Now Benefits ul.
Now Pay p.
Now Schedule p.
Check that we didn't miss any substantive content: The "A Little About Us" section describing Chime mission etc. That's not required to include? It's substantive but not under any of the headings. Could be part of About the role? But it's about company. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include that info somewhere. Where to put? Could be part of About the role? But it's about company, not role. Could add a section "About Chime" but not in allowed headings list. The allowed headings are only those listed; we should not create other headings. However we could incorporate that info into About the role paragraph? That would be mixing role with company description, but maybe acceptable as it's still substantive. The instruction says use headings for those sections; we can still have other content outside headings? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use for section headings (e.g...). It implies we should use those headings for sections. It doesn't say we cannot have other headings, but better to stick to those. However we need to preserve all substantive info; we could put the "A Little About Us" content into a
after About the role heading but before Responsibilities? That would be ambiguous but still part of About the role? Might be okay.
Alternatively we could add a section "About the company" but not in list; risk of violating instruction. Safer to incorporate into About the role paragraph.
Thus About the role paragraph will include both role description and company description.
Let's craft About the role paragraph:
"Chime is looking for a Principal People Partner to lead multiple functions including our rapidly growing enterprise business. This role will work closely with our VP of People Partners and be located in our NYC office. As a People Partner at Chime, you will help align business objectives with People solutions for different business organizations that you will support. We are looking for someone who can be a strategic thought partner, workforce planner, talent steward, program deployer, and a leadership coach. At Chime, we believe that everyone can achieve financial progress. We created Chime—a financial technology company, not a bank*—on the premise that core banking services should be helpful, easy, and free. Through our user-friendly tools and intuitive platforms, we empower our members to take control of their finances and work towards their goals. Whether it's starting a savings account, purchasing a first car or home, launching a business, or pursuing higher education, we're proud to have helped millions unlock their financial potential. We're a team of problem solvers, dreamers, and builders with one shared obsession: our members. From day one, Chimers have worked tirelessly to out-hustle and out-ex