People Business Partner, GTM (Customer Experience, Implementation & Sales Development)
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes a scam warning at end: "Please be aware, job-seekers may be at risk of targeting by malicious actors looking for personal data. Brex recruiters will only reach out via LinkedIn or email with a brex.com domain. Any outreach claiming to be from Brex via other sources should be ignored." That's boilerplate/scam warning; should be removed.
Also "Brex LLC is a wholly owned subsidiary of Capital One, N.A." maybe not boilerplate but could be considered meta; but it's substantive? It's about company; maybe keep? It's not a heading; could be part of About the role? Might be considered filler but it's factual. I'd keep it in About the role paragraph.
We need sections: About the role (intro), People at Brex (maybe part of About?), What You'll Do, Where you'll work (Schedule), Responsibilities, Requirements, What Success Looks Like, Compensation.
We need to decide headings: "About the role", "People at Brex", "What You’ll Do", "Where you’ll work" (or Schedule), "Responsibilities", "Requirements", "What Success Looks Like", "Compensation". Use
for each.
We must not emit heading with filler. Ensure each has content.
Now format content.
We need to use - for any list of duties/requirements/benefits. So for Responsibilities (list), Requirements (list), maybe What Success Looks Like (list). Also maybe "People at Brex" is prose.
Let's extract content.
Intro "Why join us Brex is the intelligent finance platform..." That's about the company. We'll put under About the role.
People at Brex paragraph: "The People team builds and sustains the culture that powers Brex..." We'll put under People at Brex.
What You’ll Do paragraph: "As a People Business Partner, you'll act as a trusted advisor and coach to senior GTM leaders and managers, helping them navigate org design, workforce planning, and change management while driving a culture of high performance. In this role, you'll also partner closely with Employee Relations, Compensation, and People Operations, and lead org design conversations that keep GTM's structure aligned with business strategy as it grows. This role is designed for someone who thrives operating at the intersection of strategic advisory and hands-on execution, and who wants to deepen their partnership with revenue-adjacent and customer-facing organizations at a fast-scaling fintech company."
Where you'll work: "This role will be based in our New York City office. We are a hybrid environment that combines the energy and connections of being in the office with the benefits and flexibility of working from home. We currently require a minimum of three coordinated days in the office per week, Monday, Wednesday and Thursday. As a perk, we also have up to four weeks per year of fully remote work!"
Responsibilities list: bullet points:
- Act as a trusted advisor and coach to senior leaders and managers across Customer Experience, Implementation, and Sales Development
- Drive a culture of high performance by coaching leaders on setting clear expectations, delivering effective feedback, and applying performance management consistently across their orgs
- Use data and org health metrics to identify trends, diagnose root causes, and recommend proactive interventions to GTM leadership
- Lead org design with GTM leaders, ensuring structure and headcount plans align with business strategy and growth targets
- Partner with Employee Relations on complex, sensitive employee matters, escalating themes and risks as needed while maintaining discretion and sound judgment
- Support bi-annual promotion and performance calibration cycles for your client groups, ensuring rigor, consistency, and fairness in outcomes
- Drive cross-functional People projects in partnership with other People Business Partners and People teams
Requirements list:
- 5-8 years of experience working in People Business Partner, Employee Relations, or other closely related functions
- Demonstrated experience advising senior leaders on org design, workforce planning, and organizational change
- Strong understanding of performance management practices in high-performance cultures (feedback, coaching, calibration, documentation)
- Experience partnering with Employee Relations on sensitive employee matters, with sound judgment on when and how to escalate.
- Proven ability to build trusted, credible relationships with senior leaders and influence outcomes without direct authority
- Comfort using data to tell a story, identify trends, and drive decisions
- Strong organizational skills with the ability to manage multiple client groups and competing priorities
- Clear, concise communicator, both written and verbal
- Ability to handle sensitive and confidential information with discretion
Bonus points (maybe not required but could be included under Requirements? It's extra; we could include as a sub-list under Requirements? But rule: use
- for any list of duties/requirements/benefits. Bonus points is a list; we could include as part of Requirements but maybe separate section "Preferred Qualifications"? Not required to create heading if not present; but we could incorporate as part of Requirements with a note. However we should not invent sections. Could add a
under Requirements with bonus points as items preceded by "Bonus points:"? Might be okay to include as part of Requirements list. But better to keep as part of Requirements but maybe separate heading "Preferred Qualifications"? The instruction: include a section ONLY when the posting has real, specific content for it. Bonus points is specific content; we could make a section "Preferred Qualifications". But they didn't list that heading in allowed headings list; they gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Preferred Qualifications but Qualifications is allowed. So we could use "Qualifications" for the requirements and maybe "Skills" for bonus points? But better to keep Requirements as the main list and include bonus points as part of that list but maybe preceded by a note. However that would mix required and bonus; but it's still factual. I'd include bonus points as a separate under a heading "Preferred Qualifications" (or "Qualifications") but we already have Requirements heading. Could rename to "Requirements & Preferred Qualifications"? Might be okay. But to be safe, I'll keep Requirements heading for the required list, and add another heading "Preferred Qualifications" for bonus points. The allowed headings include Qualifications, Skills. So "Preferred Qualifications" is not explicitly listed but could be considered under Qualifications. However they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That's examples, not exhaustive. So we can use Qualifications. I'll use "Qualifications" for the required list, and maybe "Preferred Qualifications" as a subheading? Might be overkill. I'll just include bonus points under Requirements as a separate list with a preceding note "Bonus points:" but still within same ? That would mix. I'd rather create a separate "Preferred Qualifications". It's specific content, so okay.
What Success Looks Like list:
- GTM leaders and managers see you as a trusted, strategic thought partner
- Performance, promotion, and calibration cycles run smoothly and predictably across your client groups
- Org design and workforce planning decisions are grounded in data and aligned with business strategy
- Risks, trends, and underperformance are surfaced early, with thoughtful escalation to Employee Relations and People leadership
- You're building the scope and credibility to grow into a senior/lead People Business Partner role supporting larger or more complex client groups.
Compensation paragraph: "The expected salary range for this role is $144,640 - $180,800. However, the starting base pay will depend on a number of factors including the candidate’s location, skills, experience, market demands, and internal pay parity. Depending on the position offered, equity and other forms of compensation may be provided as part of a total compensation package."
We also have the note about Brex LLC subsidiary and scam warning; we remove scam warning. Keep subsidiary note maybe as part of About the role? It's a factual statement about Brex. Could include in About the role paragraph.
Now construct HTML.
We'll start with About the role
then
...
Then People at Brex
...
Then What You’ll Do
...
Then Schedule
...
(or Where you'll work). Use Schedule heading as allowed.
Then Responsibilities
- ...
Then Requirements
- ...
Then Preferred Qualifications
- ...
(bonus points)
Then What Success Looks Like
- ...
Then Compensation
...
Make sure to preserve all details exactly.
Check for any duplicated lines: none.
Now write HTML.
Be careful with apostrophes etc. Use proper HTML entities? Not needed.
Let's craft.
About the role paragraph: Combine intro and subsidiary note.
"Why join us Brex is the intelligent finance platform that enables companies to spend smarter and move faster in more than 200 markets. By combining global corporate cards and banking with intuitive spend management, bill pay, and travel software, Brex enables founders and finance teams to accelerate operations, gain real-time visibility, and control spend effortlessly. Brex’s AI-native automation and world-class service eliminate manual expense and accounting tasks for customers so they can focus on what matters most. Tens of thousands of the world's best companies run on Brex, including DoorDash, Coinbase, Robinhood, Zoom, Plaid, Reddit, and SeatGeek. Working at Brex allows you to push your limits, challenge the status quo, and collaborate with some of the brightest minds in the industry. We’re committed to building a diverse team and inclusive culture and believe your potential should only be limited by how big you can dream. We make this a reality by empowering you with the tools, resources, and support you need to grow your career. Brex LLC is a wholly owned subsidiary of Capital One, N.A."
People at Brex paragraph: "The People team builds and sustains the culture that powers Brex. We focus on talent, growth, and the employee experience — creating an environment where high-agency individuals can thrive. From hiring to development, we design systems that grow with scale and challenge people to reach their potential. It’s a team for builders, coaches, and culture-shapers."
What You’ll Do paragraph: as above.
Schedule paragraph: "This role will be based in our New York City office. We are a hybrid environment that combines the energy and connections of being in the
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes a scam warning at end: "Please be aware, job-seekers may be at risk of targeting by malicious actors looking for personal data. Brex recruiters will only reach out via LinkedIn or email with a brex.com domain. Any outreach claiming to be from Brex via other sources should be ignored." That's boilerplate/scam warning; should be removed. Also "Brex LLC is a wholly owned subsidiary of Capital One, N.A." maybe not boilerplate but could be considered meta; but it's substantive? It's about company; maybe keep? It's not a heading; could be part of About the role? Might be considered filler but it's factual. I'd keep it in About the role paragraph. We need sections: About the role (intro), People at Brex (maybe part of About?), What You'll Do, Where you'll work (Schedule), Responsibilities, Requirements, What Success Looks Like, Compensation. We need to decide headings: "About the role", "People at Brex", "What You’ll Do", "Where you’ll work" (or Schedule), "Responsibilities", "Requirements", "What Success Looks Like", "Compensation". Use
for each.
We must not emit heading with filler. Ensure each has content.
Now format content.
We need to use - for any list of duties/requirements/benefits. So for Responsibilities (list), Requirements (list), maybe What Success Looks Like (list). Also maybe "People at Brex" is prose.
Let's extract content.
Intro "Why join us Brex is the intelligent finance platform..." That's about the company. We'll put under About the role.
People at Brex paragraph: "The People team builds and sustains the culture that powers Brex..." We'll put under People at Brex.
What You’ll Do paragraph: "As a People Business Partner, you'll act as a trusted advisor and coach to senior GTM leaders and managers, helping them navigate org design, workforce planning, and change management while driving a culture of high performance. In this role, you'll also partner closely with Employee Relations, Compensation, and People Operations, and lead org design conversations that keep GTM's structure aligned with business strategy as it grows. This role is designed for someone who thrives operating at the intersection of strategic advisory and hands-on execution, and who wants to deepen their partnership with revenue-adjacent and customer-facing organizations at a fast-scaling fintech company."
Where you'll work: "This role will be based in our New York City office. We are a hybrid environment that combines the energy and connections of being in the office with the benefits and flexibility of working from home. We currently require a minimum of three coordinated days in the office per week, Monday, Wednesday and Thursday. As a perk, we also have up to four weeks per year of fully remote work!"
Responsibilities list: bullet points:
- Act as a trusted advisor and coach to senior leaders and managers across Customer Experience, Implementation, and Sales Development
- Drive a culture of high performance by coaching leaders on setting clear expectations, delivering effective feedback, and applying performance management consistently across their orgs
- Use data and org health metrics to identify trends, diagnose root causes, and recommend proactive interventions to GTM leadership
- Lead org design with GTM leaders, ensuring structure and headcount plans align with business strategy and growth targets
- Partner with Employee Relations on complex, sensitive employee matters, escalating themes and risks as needed while maintaining discretion and sound judgment
- Support bi-annual promotion and performance calibration cycles for your client groups, ensuring rigor, consistency, and fairness in outcomes
- Drive cross-functional People projects in partnership with other People Business Partners and People teams
Requirements list:
- 5-8 years of experience working in People Business Partner, Employee Relations, or other closely related functions
- Demonstrated experience advising senior leaders on org design, workforce planning, and organizational change
- Strong understanding of performance management practices in high-performance cultures (feedback, coaching, calibration, documentation)
- Experience partnering with Employee Relations on sensitive employee matters, with sound judgment on when and how to escalate.
- Proven ability to build trusted, credible relationships with senior leaders and influence outcomes without direct authority
- Comfort using data to tell a story, identify trends, and drive decisions
- Strong organizational skills with the ability to manage multiple client groups and competing priorities
- Clear, concise communicator, both written and verbal
- Ability to handle sensitive and confidential information with discretion
Bonus points (maybe not required but could be included under Requirements? It's extra; we could include as a sub-list under Requirements? But rule: use
- for any list of duties/requirements/benefits. Bonus points is a list; we could include as part of Requirements but maybe separate section "Preferred Qualifications"? Not required to create heading if not present; but we could incorporate as part of Requirements with a note. However we should not invent sections. Could add a
under Requirements with bonus points as items preceded by "Bonus points:"? Might be okay to include as part of Requirements list. But better to keep as part of Requirements but maybe separate heading "Preferred Qualifications"? The instruction: include a section ONLY when the posting has real, specific content for it. Bonus points is specific content; we could make a section "Preferred Qualifications". But they didn't list that heading in allowed headings list; they gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Preferred Qualifications but Qualifications is allowed. So we could use "Qualifications" for the requirements and maybe "Skills" for bonus points? But better to keep Requirements as the main list and include bonus points as part of that list but maybe preceded by a note. However that would mix required and bonus; but it's still factual. I'd include bonus points as a separate under a heading "Preferred Qualifications" (or "Qualifications") but we already have Requirements heading. Could rename to "Requirements & Preferred Qualifications"? Might be okay. But to be safe, I'll keep Requirements heading for the required list, and add another heading "Preferred Qualifications" for bonus points. The allowed headings include Qualifications, Skills. So "Preferred Qualifications" is not explicitly listed but could be considered under Qualifications. However they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That's examples, not exhaustive. So we can use Qualifications. I'll use "Qualifications" for the required list, and maybe "Preferred Qualifications" as a subheading? Might be overkill. I'll just include bonus points under Requirements as a separate list with a preceding note "Bonus points:" but still within same ? That would mix. I'd rather create a separate "Preferred Qualifications". It's specific content, so okay.
What Success Looks Like list:
- GTM leaders and managers see you as a trusted, strategic thought partner
- Performance, promotion, and calibration cycles run smoothly and predictably across your client groups
- Org design and workforce planning decisions are grounded in data and aligned with business strategy
- Risks, trends, and underperformance are surfaced early, with thoughtful escalation to Employee Relations and People leadership
- You're building the scope and credibility to grow into a senior/lead People Business Partner role supporting larger or more complex client groups.
Compensation paragraph: "The expected salary range for this role is $144,640 - $180,800. However, the starting base pay will depend on a number of factors including the candidate’s location, skills, experience, market demands, and internal pay parity. Depending on the position offered, equity and other forms of compensation may be provided as part of a total compensation package."
We also have the note about Brex LLC subsidiary and scam warning; we remove scam warning. Keep subsidiary note maybe as part of About the role? It's a factual statement about Brex. Could include in About the role paragraph.
Now construct HTML.
We'll start with About the role
then
...
Then People at Brex
...
Then What You’ll Do
...
Then Schedule
...
(or Where you'll work). Use Schedule heading as allowed.
Then Responsibilities
- ...
Then Requirements
- ...
Then Preferred Qualifications
- ...
(bonus points)
Then What Success Looks Like
- ...
Then Compensation
...
Make sure to preserve all details exactly.
Check for any duplicated lines: none.
Now write HTML.
Be careful with apostrophes etc. Use proper HTML entities? Not needed.
Let's craft.
About the role paragraph: Combine intro and subsidiary note.
"Why join us Brex is the intelligent finance platform that enables companies to spend smarter and move faster in more than 200 markets. By combining global corporate cards and banking with intuitive spend management, bill pay, and travel software, Brex enables founders and finance teams to accelerate operations, gain real-time visibility, and control spend effortlessly. Brex’s AI-native automation and world-class service eliminate manual expense and accounting tasks for customers so they can focus on what matters most. Tens of thousands of the world's best companies run on Brex, including DoorDash, Coinbase, Robinhood, Zoom, Plaid, Reddit, and SeatGeek. Working at Brex allows you to push your limits, challenge the status quo, and collaborate with some of the brightest minds in the industry. We’re committed to building a diverse team and inclusive culture and believe your potential should only be limited by how big you can dream. We make this a reality by empowering you with the tools, resources, and support you need to grow your career. Brex LLC is a wholly owned subsidiary of Capital One, N.A."
People at Brex paragraph: "The People team builds and sustains the culture that powers Brex. We focus on talent, growth, and the employee experience — creating an environment where high-agency individuals can thrive. From hiring to development, we design systems that grow with scale and challenge people to reach their potential. It’s a team for builders, coaches, and culture-shapers."
What You’ll Do paragraph: as above.
Schedule paragraph: "This role will be based in our New York City office. We are a hybrid environment that combines the energy and connections of being in the
- for any list of duties/requirements/benefits. Bonus points is a list; we could include as part of Requirements but maybe separate section "Preferred Qualifications"? Not required to create heading if not present; but we could incorporate as part of Requirements with a note. However we should not invent sections. Could add a
- under Requirements with bonus points as items preceded by "Bonus points:"? Might be okay to include as part of Requirements list. But better to keep as part of Requirements but maybe separate heading "Preferred Qualifications"? The instruction: include a section ONLY when the posting has real, specific content for it. Bonus points is specific content; we could make a section "Preferred Qualifications". But they didn't list that heading in allowed headings list; they gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Preferred Qualifications but Qualifications is allowed. So we could use "Qualifications" for the requirements and maybe "Skills" for bonus points? But better to keep Requirements as the main list and include bonus points as part of that list but maybe preceded by a note. However that would mix required and bonus; but it's still factual. I'd include bonus points as a separate
- ...
- ...
- ...
- ...
- under a heading "Preferred Qualifications" (or "Qualifications") but we already have Requirements heading. Could rename to "Requirements & Preferred Qualifications"? Might be okay. But to be safe, I'll keep Requirements heading for the required list, and add another heading "Preferred Qualifications" for bonus points. The allowed headings include Qualifications, Skills. So "Preferred Qualifications" is not explicitly listed but could be considered under Qualifications. However they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That's examples, not exhaustive. So we can use Qualifications. I'll use "Qualifications" for the required list, and maybe "Preferred Qualifications" as a subheading? Might be overkill. I'll just include bonus points under Requirements as a separate list with a preceding note "Bonus points:" but still within same
- ? That would mix. I'd rather create a separate
"Preferred Qualifications". It's specific content, so okay. What Success Looks Like list: - GTM leaders and managers see you as a trusted, strategic thought partner - Performance, promotion, and calibration cycles run smoothly and predictably across your client groups - Org design and workforce planning decisions are grounded in data and aligned with business strategy - Risks, trends, and underperformance are surfaced early, with thoughtful escalation to Employee Relations and People leadership - You're building the scope and credibility to grow into a senior/lead People Business Partner role supporting larger or more complex client groups. Compensation paragraph: "The expected salary range for this role is $144,640 - $180,800. However, the starting base pay will depend on a number of factors including the candidate’s location, skills, experience, market demands, and internal pay parity. Depending on the position offered, equity and other forms of compensation may be provided as part of a total compensation package." We also have the note about Brex LLC subsidiary and scam warning; we remove scam warning. Keep subsidiary note maybe as part of About the role? It's a factual statement about Brex. Could include in About the role paragraph. Now construct HTML. We'll start with
About the role
then...
ThenPeople at Brex
...
ThenWhat You’ll Do
...
ThenSchedule
...
(or Where you'll work). Use Schedule heading as allowed. ThenResponsibilities
Requirements
Preferred Qualifications
What Success Looks Like
Compensation
...
Make sure to preserve all details exactly. Check for any duplicated lines: none. Now write HTML. Be careful with apostrophes etc. Use proper HTML entities? Not needed. Let's craft. About the role paragraph: Combine intro and subsidiary note. "Why join us Brex is the intelligent finance platform that enables companies to spend smarter and move faster in more than 200 markets. By combining global corporate cards and banking with intuitive spend management, bill pay, and travel software, Brex enables founders and finance teams to accelerate operations, gain real-time visibility, and control spend effortlessly. Brex’s AI-native automation and world-class service eliminate manual expense and accounting tasks for customers so they can focus on what matters most. Tens of thousands of the world's best companies run on Brex, including DoorDash, Coinbase, Robinhood, Zoom, Plaid, Reddit, and SeatGeek. Working at Brex allows you to push your limits, challenge the status quo, and collaborate with some of the brightest minds in the industry. We’re committed to building a diverse team and inclusive culture and believe your potential should only be limited by how big you can dream. We make this a reality by empowering you with the tools, resources, and support you need to grow your career. Brex LLC is a wholly owned subsidiary of Capital One, N.A." People at Brex paragraph: "The People team builds and sustains the culture that powers Brex. We focus on talent, growth, and the employee experience — creating an environment where high-agency individuals can thrive. From hiring to development, we design systems that grow with scale and challenge people to reach their potential. It’s a team for builders, coaches, and culture-shapers." What You’ll Do paragraph: as above. Schedule paragraph: "This role will be based in our New York City office. We are a hybrid environment that combines the energy and connections of being in the