Growth Product Manager New Channels
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and include description of role and maybe about Xe. The description includes "About Xe" and "The Role". So we can combine.
- Responsibilities: There's a section "Position Responsibilities" but it's generic. Also earlier there is "What You Will Own" and "Examples Of What You Might Build". Those are responsibilities. So we can put those under Responsibilities.
- Requirements / Qualifications / Skills: There's "Who You Are" which lists qualifications. Could be split into Requirements, Qualifications, Skills. But we need to decide. The instruction: prefer a few substantive sections over many thin ones. So maybe combine into one "Requirements" or "Qualifications". But we have headings list; we can include only those with real content. We could have "Requirements" and "Qualifications" maybe both have content. However "Who You Are" includes bullet-like statements: built acquisition channel, think in loops, designed incentives, built engagement products, comfortable most channels will not work, can work alongside Marketing. Those are qualifications/skills. Could be under "Qualifications". Could also have "Skills". But to avoid thin sections, maybe just one "Qualifications" heading.
- Benefits: There's "Perks & Benefits" list. So we can have Benefits section.
- Pay: There's "Compensation" with salary range. So we can have Pay section.
- Schedule: There's "Hybrid Work Schedule" mentioned under Perks & Benefits. Also maybe schedule info. Could be under Schedule section. But we already have Hybrid Work Schedule in Benefits. However we could still have a Schedule section with that detail. But we should avoid duplication. The instruction: remove duplicated lines. So we should not repeat same content in multiple sections. If we put Hybrid Work Schedule under Benefits, we shouldn't also put under Schedule unless we have other schedule info. There's no other schedule specifics. So maybe we omit Schedule section because content is already in Benefits. But the instruction says include a section ONLY when the posting has real, specific content for it. If we already used that content under Benefits, we could still have Schedule but would be duplicate. Better to not include Schedule.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay.
We need to use for each heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, except boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also remove "Position Responsibilities" generic lines that are not substantive? The generic lines: "The position responsibilities outlined above are intended to define the general contents and requirements to perform this job. It is not to be taken as a complete statement of responsibilities or requirements. This job description does not restrict the Company’s right to assign or reassign duties and responsibilities to this job as needed." That's boilerplate; remove.
Also remove "Equal Employment Opportunity" etc.
Also remove "We want Xe to be a great place to work..." etc.
Also remove "If you need assistance..." etc.
Also remove "Compensation Xe offers a competitive salary and benefits package..." maybe keep the salary range but remove fluff? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The sentence "Xe offers a competitive salary and benefits package. The reasonable estimated pay for this Salary Exempt or Non-exempt hourly rate role ranges from $140,000 USD to $180,000 USD. Actual compensation is based upon factors such as the candidate’s skills, qualifications, and experience. In addition, Xe offers comprehensive and inclusive employee benefits for this role, including healthcare, dental and vision benefits, a 401(k) plan, Paid Vacation / Sick Leave and more." This contains substantive info: salary range, mention of benefits. We should keep the salary range and maybe mention benefits but we already have Benefits section. We could keep the salary range in Pay section, and maybe note that benefits are described elsewhere. But we should not discard substantive info like "Actual compensation is based upon factors such as the candidate’s skills, qualifications, and experience." That's substantive. So we keep that.
We need to avoid duplication: Benefits section already lists medical, dental, vision, 401K, employee stock purchase plan, paid vacation/sick leave, hybrid work schedule, tuition assistance, growth opportunities, corporate gatherings, Plumm Mental Health, volunteering day. So we can keep that.
Now let's extract content.
About Xe / About the role:
Paragraphs:
"Growth PM, New Channels Turn the audience we already have into customers, without buying media About Xe Xe is a global leader in international money transfer and currency services, helping businesses and individuals move money across borders with speed, transparency and trust. Tens of millions of people use Xe every month to check rates and convert currency, and our B2B arm helps small and medium enterprises streamline global payments, manage FX risk and expand internationally. The Role Marketing runs the channels we already know work, and runs them well. This role does something different. We have an audience most companies our size would have to buy, and more than one thing to sell it. Your job is to connect the two through channels we own rather than channels we pay for — routes to customers that get cheaper as the base grows, not more expensive."
We can combine into a prose
under About the role.
Now Responsibilities: What You Will Own (list) and Examples Of What You Might Build (list). Also maybe "The handover" etc.
Let's list responsibilities:
From "What You Will Own":
- New channels, not new spend. Identify, build and prove routes to customers that we own rather than pay for, including ones that need a product built rather than a budget spent.
- The referral program. Own it end to end — incentive design, tracking, payout, and the abuse controls that decide whether a program survives contact with reality.
- Reasons to come back. Build products that earn a repeat visit and a way to stay in touch.
- Conversion into what we already sell. An engaged user is not the finish line. Own the path from engagement to a first transaction on an existing Xe product.
- A test budget, used as a test budget. You will have spend available to establish whether a channel is real. It is an experiment cost, not a media budget.
- The handover. A channel leaves Growth once it is predictable, repeatable and documented. Marketing runs it from there. Own the transfer and the evidence behind it.
From "Examples Of What You Might Build":
- Turn someone our product already touches into an account holder.
- Build the mechanics that let a third party introduce clients and share in the revenue.
- Give someone a reason to tell us how they want to be reached, and treat that as the moment we learn who they are.
- Use a contained paid test to establish whether a channel is real before anyone scales it.
We should keep these as list items under Responsibilities.
Now Qualifications/Skills: "Who You Are" bullet-like sentences:
- You have built an acquisition channel from nothing to material volume, and you can show the numbers.
- You think in loops and can model one — inputs, conversion at each step, cycle time, and what breaks it at scale.
- You have designed incentives and dealt with the abuse that follows them.
- You have built engagement or identity-capture products, and you know the difference between a signup form and a reason to sign up.
- You are comfortable that most channels you test will not work, and disciplined about stopping them.
- You can work alongside Marketing and regional revenue leaders without needing to own their budgets.
We can put these as list items under Qualifications.
Now Benefits: list from "Perks & Benefits":
- Medical, Dental & Vision Insurance
- 401K Plan with Match
- Employee Stock Purchase Plan
- Paid Vacation / Sick Leave
- Hybrid Work Schedule
- Tuition Assistance
- Growth Opportunities
- Corporate gatherings, team bonding events, and much more!
- Plumm Mental Health and Wellbeing
- Volunteering day for a charity of your choice
We should keep as list.
Now Pay: from Compensation section:
- "Xe offers a competitive salary and benefits package. The reasonable estimated pay for this Salary Exempt or Non-exempt hourly rate role ranges from $140,000 USD to $180,000 USD. Actual compensation is based upon factors such as the candidate’s skills, qualifications, and experience. In addition, Xe offers comprehensive and inclusive employee benefits for this role, including healthcare, dental and vision benefits, a 401(k) plan, Paid Vacation / Sick Leave and more."
We need to preserve substantive info: salary range, actual compensation based on skills, qualifications, experience. Also mention benefits but we already have Benefits section; we could still mention that benefits are offered but maybe we can keep the sentence but avoid duplication? The instruction: remove duplicated lines. The benefits list is duplicated if we repeat same items. The sentence mentions healthcare, dental and vision benefits, a 401(k) plan, Paid Vacation / Sick Leave and more. That's a summary; not exact duplication of list but still mentions benefits. Could keep it as part of Pay section, but we might want to avoid repeating benefit details. However it's not a duplicate of the list; it's a summary. It's okay to keep.
We'll put Pay section with a
containing that paragraph (maybe trimmed to keep substantive). We'll keep the whole paragraph.
Now we need to ensure we don't include boilerplate like "Equal Employment Opportunity", "We want Xe to be a great place to work", etc.
Also remove "Position Responsibilities" generic lines.
Now produce HTML fragment:
About the role
...
Responsibilities
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
Pay
...
We should not include Schedule.
Check that we haven't missed any substantive info: "How We Work" section includes loops over funnels, evidence over opinion, small teams, short cycles, direct line to Product. That's substantive about how they work; could be part of Responsibilities or maybe a separate section like "How we work". But not in the allowed headings list. The allowed headings are limited to those examples; we could still add other headings? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should likely stick to those. However we could add a section like "How we work" if it's substantive, but the instruction says use those as examples; not strictly limited. But to be safe, we could incorporate that content into Responsibilities or About the role. However it's distinct: "How We Work Loops over funnels...". Could be part of Responsibilities or maybe a separate section like "How we work". Since not in the list, maybe we should incorporate into Responsibilities as it's about how they operate. But we already have Responsibilities covering what you will own. Could add a separate section "How we work" but risk
- for any list of duties/requirements/benefits. Use
for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, except boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also remove "Position Responsibilities" generic lines that are not substantive? The generic lines: "The position responsibilities outlined above are intended to define the general contents and requirements to perform this job. It is not to be taken as a complete statement of responsibilities or requirements. This job description does not restrict the Company’s right to assign or reassign duties and responsibilities to this job as needed." That's boilerplate; remove. Also remove "Equal Employment Opportunity" etc. Also remove "We want Xe to be a great place to work..." etc. Also remove "If you need assistance..." etc. Also remove "Compensation Xe offers a competitive salary and benefits package..." maybe keep the salary range but remove fluff? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The sentence "Xe offers a competitive salary and benefits package. The reasonable estimated pay for this Salary Exempt or Non-exempt hourly rate role ranges from $140,000 USD to $180,000 USD. Actual compensation is based upon factors such as the candidate’s skills, qualifications, and experience. In addition, Xe offers comprehensive and inclusive employee benefits for this role, including healthcare, dental and vision benefits, a 401(k) plan, Paid Vacation / Sick Leave and more." This contains substantive info: salary range, mention of benefits. We should keep the salary range and maybe mention benefits but we already have Benefits section. We could keep the salary range in Pay section, and maybe note that benefits are described elsewhere. But we should not discard substantive info like "Actual compensation is based upon factors such as the candidate’s skills, qualifications, and experience." That's substantive. So we keep that. We need to avoid duplication: Benefits section already lists medical, dental, vision, 401K, employee stock purchase plan, paid vacation/sick leave, hybrid work schedule, tuition assistance, growth opportunities, corporate gatherings, Plumm Mental Health, volunteering day. So we can keep that. Now let's extract content. About Xe / About the role: Paragraphs: "Growth PM, New Channels Turn the audience we already have into customers, without buying media About Xe Xe is a global leader in international money transfer and currency services, helping businesses and individuals move money across borders with speed, transparency and trust. Tens of millions of people use Xe every month to check rates and convert currency, and our B2B arm helps small and medium enterprises streamline global payments, manage FX risk and expand internationally. The Role Marketing runs the channels we already know work, and runs them well. This role does something different. We have an audience most companies our size would have to buy, and more than one thing to sell it. Your job is to connect the two through channels we own rather than channels we pay for — routes to customers that get cheaper as the base grows, not more expensive." We can combine into a prose
under About the role. Now Responsibilities: What You Will Own (list) and Examples Of What You Might Build (list). Also maybe "The handover" etc. Let's list responsibilities: From "What You Will Own": - New channels, not new spend. Identify, build and prove routes to customers that we own rather than pay for, including ones that need a product built rather than a budget spent. - The referral program. Own it end to end — incentive design, tracking, payout, and the abuse controls that decide whether a program survives contact with reality. - Reasons to come back. Build products that earn a repeat visit and a way to stay in touch. - Conversion into what we already sell. An engaged user is not the finish line. Own the path from engagement to a first transaction on an existing Xe product. - A test budget, used as a test budget. You will have spend available to establish whether a channel is real. It is an experiment cost, not a media budget. - The handover. A channel leaves Growth once it is predictable, repeatable and documented. Marketing runs it from there. Own the transfer and the evidence behind it. From "Examples Of What You Might Build": - Turn someone our product already touches into an account holder. - Build the mechanics that let a third party introduce clients and share in the revenue. - Give someone a reason to tell us how they want to be reached, and treat that as the moment we learn who they are. - Use a contained paid test to establish whether a channel is real before anyone scales it. We should keep these as list items under Responsibilities. Now Qualifications/Skills: "Who You Are" bullet-like sentences: - You have built an acquisition channel from nothing to material volume, and you can show the numbers. - You think in loops and can model one — inputs, conversion at each step, cycle time, and what breaks it at scale. - You have designed incentives and dealt with the abuse that follows them. - You have built engagement or identity-capture products, and you know the difference between a signup form and a reason to sign up. - You are comfortable that most channels you test will not work, and disciplined about stopping them. - You can work alongside Marketing and regional revenue leaders without needing to own their budgets. We can put these as list items under Qualifications. Now Benefits: list from "Perks & Benefits": - Medical, Dental & Vision Insurance - 401K Plan with Match - Employee Stock Purchase Plan - Paid Vacation / Sick Leave - Hybrid Work Schedule - Tuition Assistance - Growth Opportunities - Corporate gatherings, team bonding events, and much more! - Plumm Mental Health and Wellbeing - Volunteering day for a charity of your choice We should keep as list. Now Pay: from Compensation section: - "Xe offers a competitive salary and benefits package. The reasonable estimated pay for this Salary Exempt or Non-exempt hourly rate role ranges from $140,000 USD to $180,000 USD. Actual compensation is based upon factors such as the candidate’s skills, qualifications, and experience. In addition, Xe offers comprehensive and inclusive employee benefits for this role, including healthcare, dental and vision benefits, a 401(k) plan, Paid Vacation / Sick Leave and more." We need to preserve substantive info: salary range, actual compensation based on skills, qualifications, experience. Also mention benefits but we already have Benefits section; we could still mention that benefits are offered but maybe we can keep the sentence but avoid duplication? The instruction: remove duplicated lines. The benefits list is duplicated if we repeat same items. The sentence mentions healthcare, dental and vision benefits, a 401(k) plan, Paid Vacation / Sick Leave and more. That's a summary; not exact duplication of list but still mentions benefits. Could keep it as part of Pay section, but we might want to avoid repeating benefit details. However it's not a duplicate of the list; it's a summary. It's okay to keep. We'll put Pay section with a
containing that paragraph (maybe trimmed to keep substantive). We'll keep the whole paragraph. Now we need to ensure we don't include boilerplate like "Equal Employment Opportunity", "We want Xe to be a great place to work", etc. Also remove "Position Responsibilities" generic lines. Now produce HTML fragment:
About the role
...
Responsibilities
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
...
We should not include Schedule. Check that we haven't missed any substantive info: "How We Work" section includes loops over funnels, evidence over opinion, small teams, short cycles, direct line to Product. That's substantive about how they work; could be part of Responsibilities or maybe a separate section like "How we work". But not in the allowed headings list. The allowed headings are limited to those examples; we could still add other headings? The instruction: usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should likely stick to those. However we could add a section like "How we work" if it's substantive, but the instruction says use those as examples; not strictly limited. But to be safe, we could incorporate that content into Responsibilities or About the role. However it's distinct: "How We Work Loops over funnels...". Could be part of Responsibilities or maybe a separate section like "How we work". Since not in the list, maybe we should incorporate into Responsibilities as it's about how they operate. But we already have Responsibilities covering what you will own. Could add a separate section "How we work" but risk