Lead Total Rewards Partner
Airwallex · San Francisco, CA · 1 mo ago
HybridBusiness Development$145k–$210k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About Airwallex, Attributes We Value, About The Team, What You'll Do, Responsibilities, Who You Are (with Minimum Qualifications, Preferred Qualifications), Applicant Safety Policy, Equal opportunity, Compensation Range.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to drop Applicant Safety Policy, Equal opportunity (EEO) maybe considered boilerplate. Also drop "About Airwallex" maybe not a section heading? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings if they exist. The posting has sections: About Airwallex (company overview) maybe not needed? It's not a standard heading but could be considered "About the role"? Actually "About the role" is typical. The posting includes "What You'll Do" which is responsibilities. Also "Responsibilities" separate. Also "Who You Are" includes qualifications. Also "Attributes We Value" maybe skills? Could be "Skills". Also "About The Team" maybe not needed but could be omitted if not standard heading. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to decide which sections to include.
We have content for:
- About the role: maybe combine "About Airwallex" and "About The Team" and "Attributes We Value"? But "About the role" is supposed to be a brief description of the role. The posting has "What You'll Do" which describes role. So we could use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings if they exist. The posting has sections: About Airwallex (company overview) maybe not needed? It's not a standard heading but could be considered "About the role"? Actually "About the role" is typical. The posting includes "What You'll Do" which is responsibilities. Also "Responsibilities" separate. Also "Who You Are" includes qualifications. Also "Attributes We Value" maybe skills? Could be "Skills". Also "About The Team" maybe not needed but could be omitted if not standard heading. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to decide which sections to include.
We have content for:
- About the role: maybe combine "About Airwallex" and "About The Team" and "Attributes We Value"? But "About the role" is supposed to be a brief description of the role. The posting has "What You'll Do" which describes role. So we could use About the role
with content from "What You'll Do" paragraph.
- Responsibilities: we have a list under "Responsibilities". Use - .
- Requirements/Qualifications: we have Minimum Qualifications and Preferred Qualifications. Could combine into Requirements section? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have qualifications content. Could put
Qualifications
with two sub-sections? But we cannot add extra headings beyond those? It didn't forbid subheadings, but we should follow the pattern. Could put Minimum Qualifications
but that's not in the list. Better to put Qualifications
and include both minimum and preferred as paragraphs or lists.
- Skills: maybe "Attributes We Value" could be Skills. So Skills
with list.
- Benefits: not explicitly listed besides compensation range. No benefits description. So we should not create Benefits section unless posting actually states them. It does not list benefits besides compensation range. So skip Benefits.
- Pay: we have Compensation Range: $145K - $210K. So we can create Pay
with that info.
- Schedule: not mentioned. Skip.
Also we might include "About the team" as maybe not needed. Could omit.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all substantive info from the posting, except boilerplate removed.
Let's extract substantive content:
- About Airwallex: description of company. Might be considered substantive but not a standard heading. Could we include it under "About the role"? 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 says use those for section headings. It might be okay to include other headings if they match content? But better to stick to those. However we need to preserve all substantive info; if we omit About Airwallex, we lose info. Could we incorporate it into About the role? The role description is about the job, not company. But we could add a paragraph under About the role that includes company overview? Might be okay but could be considered not accurate. However the instruction says "Preserve ALL substantive information". So we need to keep it somewhere. Perhaps we can create a section About the company
but that's not in the list. The instruction says 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 can use other headings as needed, but we should prefer those. It's safer to use a heading like "About Airwallex". But 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, just gives examples. So we can use About Airwallex as heading.
Similarly, "Attributes We Value" could be a heading.
"About The Team" could be heading.
But we should avoid creating sections with filler. Those have real content.
Thus we can output sections:
About Airwallex
with paragraph.
Attributes We Value
with paragraph.
About The Team
with paragraph.
What You'll Do
with paragraph (maybe treat as About the role). But we could rename to About the role. However the content is "What You'll Do". To preserve info, we could keep heading as What You'll Do? But instruction says use for section headings (e.g. About the role, Responsibilities...). It doesn't forbid using What You'll Do as heading, but better to map to About the role. However if we rename, we might lose the exact heading but content remains. The instruction says preserve ALL substantive information; headings are not substantive? Probably not required to keep exact heading. So we can change to About the role.
But we also have a separate Responsibilities section with detailed list. So we could have About the role (summary) and Responsibilities (detailed). That seems fine.
Thus:
About the role
with paragraph from "What You'll Do".
Responsibilities
with ul list.
Qualifications
with maybe two sub-sections: Minimum Qualifications and Preferred Qualifications as paragraphs or lists.
We could also have Minimum Qualifications
and Preferred Qualifications
but those are not in the examples but okay.
But to follow instruction, we could combine under Qualifications.
We need to preserve all details: list each bullet.
Minimum Qualifications bullets:
- 8+ years of experience in total rewards, compensation, or benefits, including significant experience supporting populations based in the Americas.
- Experience building or managing a complete rewards program (compensation, benefits, equity, etc) at a regional or global level
- Experience managing the benefits process end to end, including negotiating with brokers and insurance carriers to evaluate and renew plans.
- Strong compensation data analytics capability: own the annual market review cycle and influence company pay strategy and decisions at executive level.
- Proven ability to build your own models and projections.
- Working knowledge of US stock administration and equity compensation, including RSUs, vesting mechanics, and how to explain them plainly to a non-specialist.
- Experience at a late-stage private or pre-IPO company, or through the transition to public markets, particularly through changes to an equity program.
- Experience leading cross-functional projects with senior stakeholders, and mentoring or managing other rewards professionals.
Preferred Qualifications bullets:
- Multi-region rewards experience, especially where the global framework is set outside your own time zone.
- Familiarity with compensation and equity tooling such as Carta, BambooHR or Workday, and survey sources such as Radford or Compensia.
- Experience standing up a rewards function or team in a new region.
- Comfort operating with high standards, at a fast pace and under pressure, with evolving priorities and a bias toward building the thing rather than waiting for the playbook.
Also there is "Who You Are" intro: "We're looking for people who meet the minimum requirements for this role. The preferred qualifications are great to have, but are not mandatory." That's boilerplate? Might be considered filler but it's substantive? It's basically saying same as above. Could be omitted as it's redundant. But we already have qualifications sections.
Attributes We Value paragraph: "We hire successful builders with founder-like energy who want real impact, accelerated learning, and true ownership. You bring strong role-related expertise and sharp thinking, and you’re motivated by our mission and operating principles. You move fast with good judgment, dig deep with curiosity, and make decisions from first principles, balancing speed and rigor. You're humble and collaborative; turn zero‑to‑one ideas into real products, and you “get stuff done” end-to-end. You use AI to work smarter and solve problems faster. Here, you’ll tackle complex, high‑visibility problems with exceptional teammates and grow your career as we build the future of global banking. If that sounds like you, let’s build what’s next."
That's substantive.
About The Team paragraph: "The People & Talent team at Airwallex is dedicated to attracting and developing the brightest and most ambitious minds to drive our company forward. We are a global, vibrant, and dynamic team with a focus on creating a positive and inclusive work environment that fosters growth and innovation. Through innovative programs, strategic People & Talent initiatives, and a deep understanding of our organization's needs, we cultivate a collaborative and engaging environment that fuels Airwallex's continued growth and success."
That's substantive.
About Airwallex paragraph: long description.
Compensation Range: "$145K - $210K". That's Pay.
We should not include Applicant Safety Policy, Equal opportunity.
Now produce HTML fragment.
We'll structure:
About Airwallex
...
Attributes We Value
...
About The Team
...
About the role
...
(What You'll Do paragraph)
Responsibilities
- ...
...
Qualifications
maybe split:
Minimum Qualifications
...
Preferred Qualifications
...
Pay
$145K - $210K
Check for any duplicated lines: The posting had "What You'll Do" and then "Responsibilities". Ensure we don't duplicate content. The "What You'll Do" paragraph is: "You'll be the first Total Rewards lead based in the Americas, owning our Compensation, Benefits and Equity programs end to end across the US and Canada, Brazil and Mexico. You'll set the regional rewards agenda and lead its execution, while partnering with the global Total Rewards team to shape how our programs are designed and evolve worldwide. Airwallex is actively rebuilding and scaling its rewards programs, so this is a build role. You'll own the Americas compensation and benefits programs and cycles, ensuring our pay ranges and benefits offerings remain market-aligned, and serve as the senior Total Rewards voice for recruiters, managers, People Partners, and business leaders across the region. You'll work as part of a small, global team, partnering closely with colleagues in Singapore and China, with the opportunity to grow a team in the Americas as we scale. This role is based in San Francisco."
That's substantive.
Responsibilities list includes many items; some overlap with What You'll Do but we keep both as they are distinct.
Now ensure we didn't include boilerplate like "If you’re ready to do the most ambitious work of your career, join us." That's in About Airwallex paragraph? Actually that
Qualifications
with two sub-sections? But we cannot add extra headings beyond those? It didn't forbid subheadings, but we should follow the pattern. Could putMinimum Qualifications
but that's not in the list. Better to putQualifications
and include both minimum and preferred as paragraphs or lists. - Skills: maybe "Attributes We Value" could be Skills. SoSkills
with list. - Benefits: not explicitly listed besides compensation range. No benefits description. So we should not create Benefits section unless posting actually states them. It does not list benefits besides compensation range. So skip Benefits. - Pay: we have Compensation Range: $145K - $210K. So we can createPay
with that info. - Schedule: not mentioned. Skip. Also we might include "About the team" as maybe not needed. Could omit. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all substantive info from the posting, except boilerplate removed. Let's extract substantive content: - About Airwallex: description of company. Might be considered substantive but not a standard heading. Could we include it under "About the role"? 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 says use those for section headings. It might be okay to include other headings if they match content? But better to stick to those. However we need to preserve all substantive info; if we omit About Airwallex, we lose info. Could we incorporate it into About the role? The role description is about the job, not company. But we could add a paragraph under About the role that includes company overview? Might be okay but could be considered not accurate. However the instruction says "Preserve ALL substantive information". So we need to keep it somewhere. Perhaps we can create a section About the company
but that's not in the list. The instruction says 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 can use other headings as needed, but we should prefer those. It's safer to use a heading like "About Airwallex". But 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, just gives examples. So we can use About Airwallex as heading.
Similarly, "Attributes We Value" could be a heading.
"About The Team" could be heading.
But we should avoid creating sections with filler. Those have real content.
Thus we can output sections:
About Airwallex
with paragraph.
Attributes We Value
with paragraph.
About The Team
with paragraph.
What You'll Do
with paragraph (maybe treat as About the role). But we could rename to About the role. However the content is "What You'll Do". To preserve info, we could keep heading as What You'll Do? But instruction says use for section headings (e.g. About the role, Responsibilities...). It doesn't forbid using What You'll Do as heading, but better to map to About the role. However if we rename, we might lose the exact heading but content remains. The instruction says preserve ALL substantive information; headings are not substantive? Probably not required to keep exact heading. So we can change to About the role.
But we also have a separate Responsibilities section with detailed list. So we could have About the role (summary) and Responsibilities (detailed). That seems fine.
Thus:
About the role
with paragraph from "What You'll Do".
Responsibilities
with ul list.
Qualifications
with maybe two sub-sections: Minimum Qualifications and Preferred Qualifications as paragraphs or lists.
We could also have Minimum Qualifications
and Preferred Qualifications
but those are not in the examples but okay.
But to follow instruction, we could combine under Qualifications.
We need to preserve all details: list each bullet.
Minimum Qualifications bullets:
- 8+ years of experience in total rewards, compensation, or benefits, including significant experience supporting populations based in the Americas.
- Experience building or managing a complete rewards program (compensation, benefits, equity, etc) at a regional or global level
- Experience managing the benefits process end to end, including negotiating with brokers and insurance carriers to evaluate and renew plans.
- Strong compensation data analytics capability: own the annual market review cycle and influence company pay strategy and decisions at executive level.
- Proven ability to build your own models and projections.
- Working knowledge of US stock administration and equity compensation, including RSUs, vesting mechanics, and how to explain them plainly to a non-specialist.
- Experience at a late-stage private or pre-IPO company, or through the transition to public markets, particularly through changes to an equity program.
- Experience leading cross-functional projects with senior stakeholders, and mentoring or managing other rewards professionals.
Preferred Qualifications bullets:
- Multi-region rewards experience, especially where the global framework is set outside your own time zone.
- Familiarity with compensation and equity tooling such as Carta, BambooHR or Workday, and survey sources such as Radford or Compensia.
- Experience standing up a rewards function or team in a new region.
- Comfort operating with high standards, at a fast pace and under pressure, with evolving priorities and a bias toward building the thing rather than waiting for the playbook.
Also there is "Who You Are" intro: "We're looking for people who meet the minimum requirements for this role. The preferred qualifications are great to have, but are not mandatory." That's boilerplate? Might be considered filler but it's substantive? It's basically saying same as above. Could be omitted as it's redundant. But we already have qualifications sections.
Attributes We Value paragraph: "We hire successful builders with founder-like energy who want real impact, accelerated learning, and true ownership. You bring strong role-related expertise and sharp thinking, and you’re motivated by our mission and operating principles. You move fast with good judgment, dig deep with curiosity, and make decisions from first principles, balancing speed and rigor. You're humble and collaborative; turn zero‑to‑one ideas into real products, and you “get stuff done” end-to-end. You use AI to work smarter and solve problems faster. Here, you’ll tackle complex, high‑visibility problems with exceptional teammates and grow your career as we build the future of global banking. If that sounds like you, let’s build what’s next."
That's substantive.
About The Team paragraph: "The People & Talent team at Airwallex is dedicated to attracting and developing the brightest and most ambitious minds to drive our company forward. We are a global, vibrant, and dynamic team with a focus on creating a positive and inclusive work environment that fosters growth and innovation. Through innovative programs, strategic People & Talent initiatives, and a deep understanding of our organization's needs, we cultivate a collaborative and engaging environment that fuels Airwallex's continued growth and success."
That's substantive.
About Airwallex paragraph: long description.
Compensation Range: "$145K - $210K". That's Pay.
We should not include Applicant Safety Policy, Equal opportunity.
Now produce HTML fragment.
We'll structure:
About Airwallex
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, just gives examples. So we can use About Airwallex as heading.
Similarly, "Attributes We Value" could be a heading.
"About The Team" could be heading.
But we should avoid creating sections with filler. Those have real content.
Thus we can output sections:
About Airwallex
with paragraph.
Attributes We Value
with paragraph.
About The Team
with paragraph.
What You'll Do
with paragraph (maybe treat as About the role). But we could rename to About the role. However the content is "What You'll Do". To preserve info, we could keep heading as What You'll Do? But instruction says use for section headings (e.g. About the role, Responsibilities...). It doesn't forbid using What You'll Do as heading, but better to map to About the role. However if we rename, we might lose the exact heading but content remains. The instruction says preserve ALL substantive information; headings are not substantive? Probably not required to keep exact heading. So we can change to About the role.
But we also have a separate Responsibilities section with detailed list. So we could have About the role (summary) and Responsibilities (detailed). That seems fine.
Thus:
About the role
with paragraph from "What You'll Do".
Responsibilities
with ul list.
Qualifications
with maybe two sub-sections: Minimum Qualifications and Preferred Qualifications as paragraphs or lists.
We could also have Minimum Qualifications
and Preferred Qualifications
but those are not in the examples but okay.
But to follow instruction, we could combine under Qualifications.
We need to preserve all details: list each bullet.
Minimum Qualifications bullets:
- 8+ years of experience in total rewards, compensation, or benefits, including significant experience supporting populations based in the Americas.
- Experience building or managing a complete rewards program (compensation, benefits, equity, etc) at a regional or global level
- Experience managing the benefits process end to end, including negotiating with brokers and insurance carriers to evaluate and renew plans.
- Strong compensation data analytics capability: own the annual market review cycle and influence company pay strategy and decisions at executive level.
- Proven ability to build your own models and projections.
- Working knowledge of US stock administration and equity compensation, including RSUs, vesting mechanics, and how to explain them plainly to a non-specialist.
- Experience at a late-stage private or pre-IPO company, or through the transition to public markets, particularly through changes to an equity program.
- Experience leading cross-functional projects with senior stakeholders, and mentoring or managing other rewards professionals.
Preferred Qualifications bullets:
- Multi-region rewards experience, especially where the global framework is set outside your own time zone.
- Familiarity with compensation and equity tooling such as Carta, BambooHR or Workday, and survey sources such as Radford or Compensia.
- Experience standing up a rewards function or team in a new region.
- Comfort operating with high standards, at a fast pace and under pressure, with evolving priorities and a bias toward building the thing rather than waiting for the playbook.
Also there is "Who You Are" intro: "We're looking for people who meet the minimum requirements for this role. The preferred qualifications are great to have, but are not mandatory." That's boilerplate? Might be considered filler but it's substantive? It's basically saying same as above. Could be omitted as it's redundant. But we already have qualifications sections.
Attributes We Value paragraph: "We hire successful builders with founder-like energy who want real impact, accelerated learning, and true ownership. You bring strong role-related expertise and sharp thinking, and you’re motivated by our mission and operating principles. You move fast with good judgment, dig deep with curiosity, and make decisions from first principles, balancing speed and rigor. You're humble and collaborative; turn zero‑to‑one ideas into real products, and you “get stuff done” end-to-end. You use AI to work smarter and solve problems faster. Here, you’ll tackle complex, high‑visibility problems with exceptional teammates and grow your career as we build the future of global banking. If that sounds like you, let’s build what’s next."
That's substantive.
About The Team paragraph: "The People & Talent team at Airwallex is dedicated to attracting and developing the brightest and most ambitious minds to drive our company forward. We are a global, vibrant, and dynamic team with a focus on creating a positive and inclusive work environment that fosters growth and innovation. Through innovative programs, strategic People & Talent initiatives, and a deep understanding of our organization's needs, we cultivate a collaborative and engaging environment that fuels Airwallex's continued growth and success."
That's substantive.
About Airwallex paragraph: long description.
Compensation Range: "$145K - $210K". That's Pay.
We should not include Applicant Safety Policy, Equal opportunity.
Now produce HTML fragment.
We'll structure:
About Airwallex
About the role
with paragraph from "What You'll Do".Responsibilities
with ul list.Qualifications
with maybe two sub-sections: Minimum Qualifications and Preferred Qualifications as paragraphs or lists. We could also haveMinimum Qualifications
andPreferred Qualifications
but those are not in the examples but okay. But to follow instruction, we could combine under Qualifications. We need to preserve all details: list each bullet. Minimum Qualifications bullets: - 8+ years of experience in total rewards, compensation, or benefits, including significant experience supporting populations based in the Americas. - Experience building or managing a complete rewards program (compensation, benefits, equity, etc) at a regional or global level - Experience managing the benefits process end to end, including negotiating with brokers and insurance carriers to evaluate and renew plans. - Strong compensation data analytics capability: own the annual market review cycle and influence company pay strategy and decisions at executive level. - Proven ability to build your own models and projections. - Working knowledge of US stock administration and equity compensation, including RSUs, vesting mechanics, and how to explain them plainly to a non-specialist. - Experience at a late-stage private or pre-IPO company, or through the transition to public markets, particularly through changes to an equity program. - Experience leading cross-functional projects with senior stakeholders, and mentoring or managing other rewards professionals. Preferred Qualifications bullets: - Multi-region rewards experience, especially where the global framework is set outside your own time zone. - Familiarity with compensation and equity tooling such as Carta, BambooHR or Workday, and survey sources such as Radford or Compensia. - Experience standing up a rewards function or team in a new region. - Comfort operating with high standards, at a fast pace and under pressure, with evolving priorities and a bias toward building the thing rather than waiting for the playbook. Also there is "Who You Are" intro: "We're looking for people who meet the minimum requirements for this role. The preferred qualifications are great to have, but are not mandatory." That's boilerplate? Might be considered filler but it's substantive? It's basically saying same as above. Could be omitted as it's redundant. But we already have qualifications sections. Attributes We Value paragraph: "We hire successful builders with founder-like energy who want real impact, accelerated learning, and true ownership. You bring strong role-related expertise and sharp thinking, and you’re motivated by our mission and operating principles. You move fast with good judgment, dig deep with curiosity, and make decisions from first principles, balancing speed and rigor. You're humble and collaborative; turn zero‑to‑one ideas into real products, and you “get stuff done” end-to-end. You use AI to work smarter and solve problems faster. Here, you’ll tackle complex, high‑visibility problems with exceptional teammates and grow your career as we build the future of global banking. If that sounds like you, let’s build what’s next." That's substantive. About The Team paragraph: "The People & Talent team at Airwallex is dedicated to attracting and developing the brightest and most ambitious minds to drive our company forward. We are a global, vibrant, and dynamic team with a focus on creating a positive and inclusive work environment that fosters growth and innovation. Through innovative programs, strategic People & Talent initiatives, and a deep understanding of our organization's needs, we cultivate a collaborative and engaging environment that fuels Airwallex's continued growth and success." That's substantive. About Airwallex paragraph: long description. Compensation Range: "$145K - $210K". That's Pay. We should not include Applicant Safety Policy, Equal opportunity. Now produce HTML fragment. We'll structure:About Airwallex
...
Attributes We Value
...
About The Team
...
About the role
...
(What You'll Do paragraph)Responsibilities
- ... ...
Qualifications
maybe split:Minimum Qualifications
- ...
Preferred Qualifications
- ...
Pay
$145K - $210K
Check for any duplicated lines: The posting had "What You'll Do" and then "Responsibilities". Ensure we don't duplicate content. The "What You'll Do" paragraph is: "You'll be the first Total Rewards lead based in the Americas, owning our Compensation, Benefits and Equity programs end to end across the US and Canada, Brazil and Mexico. You'll set the regional rewards agenda and lead its execution, while partnering with the global Total Rewards team to shape how our programs are designed and evolve worldwide. Airwallex is actively rebuilding and scaling its rewards programs, so this is a build role. You'll own the Americas compensation and benefits programs and cycles, ensuring our pay ranges and benefits offerings remain market-aligned, and serve as the senior Total Rewards voice for recruiters, managers, People Partners, and business leaders across the region. You'll work as part of a small, global team, partnering closely with colleagues in Singapore and China, with the opportunity to grow a team in the Americas as we scale. This role is based in San Francisco." That's substantive. Responsibilities list includes many items; some overlap with What You'll Do but we keep both as they are distinct. Now ensure we didn't include boilerplate like "If you’re ready to do the most ambitious work of your career, join us." That's in About Airwallex paragraph? Actually that