Product Marketing Manager, Revenue suite
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. We need to map content to appropriate headings.
We have:
- About the role: maybe "About The Team" and "Who we are About Stripe" could be combined as "About the role"? But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content: "What you’ll do" corresponds to Responsibilities.
"Who you are" maybe Qualifications? Or Skills? Actually "Who you are" includes traits like storyteller, data-driven, organized, passion for technology, ambitious, team player. Those could be Skills or Qualifications. Minimum Requirements is Requirements.
"Hybrid work at Stripe" could be Schedule? Actually schedule refers to work arrangement; could be Schedule (remote/hybrid). We'll put under Schedule.
"Pay and benefits" corresponds to Pay and Benefits sections. We need separate Pay and Benefits headings if content exists. The posting gives salary range and additional benefits. So we can have Pay section with salary range, and Benefits section with list of benefits.
We must not repeat job title as heading. No Job ID.
We must remove boilerplate: EEO, legal, application instructions, etc. The posting includes "We look forward to hearing from you..." and "At Stripe, we're looking for people..." and "Apply now" etc. Those are boilerplate/application instructions; we should remove them. Also "Please find our California applicant personal information notice here." etc. Remove.
We must preserve all substantive information.
Thus we need to output HTML with sections:
About the role
maybe combine "Who we are About Stripe" and "About The Team". Provide paragraphs.
Responsibilities
from "What you’ll do" bullet list? Actually it's a list of traits but not bullet. It's a paragraph with bolded traits? The text: "Be a storyteller. You have deep empathy for users and are able to adapt how you communicate to best reach and engage your audience and differentiate Stripe. You have excellent verbal and written communication skillsLead with data. You like working with data and insights and pair that with your passion for users to generate balanced and thoughtful points of view for how to take our products to marketKeep things organized. You are able to manage highly interdependent, complex projects and keep various work streams on trackHave a passion for technology. You are keen to learn about how things work and are able to explain technical concepts in ways that everyday people can understandBe Ambitious. You are eager to make an impact at Stripe. You thrive in a fast-moving, dynamic, hyper-growth environment and are able to operate fluidly between the 30,000-foot strategy level and the micro-detail to get things rightAct as a team player. Product Marketers collaborate across the Marketing team and with basically every team at Stripe. You are able to work with a range of disciplines to execute on your work"
We need to format as - for any list of duties/requirements/benefits. This is a list of responsibilities; we can make each sentence as
- . However the text is not separated by bullet; we can split by the bolded traits? The original had each trait as a sentence starting with a capitalized trait: "Be a storyteller.", "Lead with data.", "Keep things organized.", "Have a passion for technology.", "Be Ambitious.", "Act as a team player." Each followed by explanation. We could make each trait as a
- containing the full sentence(s). That seems appropriate.
Thus
- Be a storyteller. You have deep empathy for users and are able to adapt how you communicate to best reach and engage your audience and differentiate Stripe.
... etc.
Next Requirements
from Minimum Requirements: list: "7+ years prior product marketing experience", "Bachelor’s degree or equivalent experience", "Excellent verbal and written communication skills, with experience translating technical features into benefits for a technical audience", "Be able to leverage data to proactively identify opportunities and drive impactful results". Also maybe "Hybrid work at Stripe" is schedule not requirement.
We'll put those as - .
Next
Qualifications
maybe we could put "Who you are" traits? But we already used those for responsibilities. Actually "Who you are" is more about qualifications/skills. But we already used them for responsibilities; maybe we should treat "What you’ll do" as responsibilities, and "Who you are" as Qualifications/Skills. However the instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to put "Who you are" under Qualifications (or Skills). Since we already used responsibilities for "What you’ll do", we can put "Who you are" under Qualifications (or Skills). Let's put under Qualifications.
Thus Qualifications
with list of those traits.
But we need to avoid duplication: we already used those traits for responsibilities; we need to decide which is correct. Let's read original: "What you’ll do" includes the list of traits (storyteller, lead with data, keep things organized, passion for technology, be ambitious, act as a team player). Actually those are more like responsibilities/expected behaviors. "Who you are" includes: "We’re looking for someone who meets the minimum requirements to be considered for the role. If you meet these requirements, you are encouraged to apply." Then after that: "Minimum Requirements". So "Who you are" is just a intro before Minimum Requirements, not a list of traits. Wait I need to re-examine the text:
Original snippet:
"What you’ll do Be a storyteller. You have deep empathy for users and are able to adapt how you communicate to best reach and engage your audience and differentiate Stripe. You have excellent verbal and written communication skillsLead with data. You like working with data and insights and pair that with your passion for users to generate balanced and thoughtful points of view for how to take our products to marketKeep things organized. You are able to manage highly interdependent, complex projects and keep various work streams on trackHave a passion for technology. You are keen to learn about how things work and are able to explain technical concepts in ways that everyday people can understandBe Ambitious. You are eager to make an impact at Stripe. You thrive in a fast-moving, dynamic, hyper-growth environment and are able to operate fluidly between the 30,000-foot strategy level and the micro-detail to get things rightAct as a team player. Product Marketers collaborate across the Marketing team and with basically every team at Stripe. You are able to work with a range of disciplines to execute on your work Who you are We’re looking for someone who meets the minimum requirements to be considered for the role. If you meet these requirements, you are encouraged to apply. Minimum Requirements 7+ years prior product marketing experienceBachelor’s degree or equivalent experienceExcellent verbal and written communication skills, with experience translating technical features into benefits for a technical audienceBe able to leverage data to proactively identify opportunities and drive impactful results Hybrid work at Stripe ..."
Thus "What you’ll do" includes the traits list. "Who you are" is just a short sentence encouraging apply. So we should not treat "Who you are" as qualifications; it's just filler. So we have:
- About the role: combine "Who we are About Stripe" and "About The Team".
- Responsibilities: the list from "What you’ll do".
- Requirements: Minimum Requirements list.
- Qualifications: maybe none? Could skip if no specific content beyond requirements. But we could put "Who you are" as a short paragraph? It says "We’re looking for someone who meets the minimum requirements to be considered for the role. If you meet these requirements, you are encouraged to apply." That's not substantive beyond requirements; maybe we can omit Qualifications section because it's not specific. 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 should not include Qualifications if it's just that generic line.
- Skills: maybe we could extract skills from responsibilities? But we already used responsibilities for duties. Skills could be things like "excellent verbal and written communication skills", "data-driven", "project management", "technical explanation", "ambitious", "collaboration". However those are already in responsibilities. To avoid duplication, maybe we can put Skills empty or omit. Better to omit Skills if not distinct.
- Benefits: list from "Additional benefits for this role may include: equity, company bonus or sales commissions/bonuses; 401(k) plan; medical, dental, and vision benefits; and wellness stipends."
- Pay: salary range.
- Schedule: Hybrid work at Stripe description.
We must not include sections with filler like "commensurate with experience". We have concrete content.
Now produce HTML.
We need to wrap each section: Heading
then either for prose or
- for lists.
For About the role: we have two paragraphs: "Who we are About Stripe" and "About The Team". We'll combine into maybe two
elements.
Let's extract those paragraphs:
"Who we are About Stripe Stripe is a financial infrastructure platform for businesses. Millions of companies—from the world’s largest enterprises to the most ambitious startups—use Stripe to accept payments, grow their revenue, and accelerate new business opportunities. Our mission is to increase the GDP of the internet, and we have a staggering amount of work ahead. That means you have an unprecedented opportunity to put the global economy within everyone’s reach while doing the most important work of your career."
"About The Team Our Product Marketing team’s mission is to generate customer insights that inform Stripe’s product strategy, and lead go-to-market for our suite of products. Product Marketing is a highly cross-functional role at Stripe, partnering closely with Product and Engineering, Sales, Partnerships, Demand Generation and Campaigns to name a few. Different from many other Product Marketing teams, our team works across the entire product lifecycle, from helping shape the product, to driving launch and commercialization, to growing product adoption post-launch. We are looking for a Product Marketing Manager for Stripe’s Revenue suite (which includes Billing, Invoicing, Tax, and Revenue Recognition). In this role, you’ll craft the narrative for how our Revenue products deliver value to product and finance leaders, drive demand by partnering with the campaigns team, develop cross-product packages and bundles, and enable our sales team."
We'll put each as
.
Responsibilities: list items.
We need to split the "What you’ll do" text into items. Let's parse:
- Be a storyteller. You have deep empathy for users and are able to adapt how you communicate to best reach and engage your audience and differentiate Stripe.
- Lead with data. You like working with data and insights and pair that with your passion for users to generate balanced and thoughtful points of view for how to take our products to market
- Keep things organized. You are able to manage highly interdependent, complex projects and keep various work streams on track
- Have a passion for technology. You are keen to learn about how things work and are able to explain technical concepts in ways that everyday people can understand
- Be Ambitious. You are eager to make an impact at Stripe. You thrive in a fast-moving, dynamic, hyper-growth environment and are able to operate fluidly between the 30,000-foot strategy level and the micro-detail to get things right
- Act
- Be a storyteller. You have deep empathy for users and are able to adapt how you communicate to best reach and engage your audience and differentiate Stripe. ... etc. Next
- .
Next
Qualifications
maybe we could put "Who you are" traits? But we already used those for responsibilities. Actually "Who you are" is more about qualifications/skills. But we already used them for responsibilities; maybe we should treat "What you’ll do" as responsibilities, and "Who you are" as Qualifications/Skills. However the instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to put "Who you are" under Qualifications (or Skills). Since we already used responsibilities for "What you’ll do", we can put "Who you are" under Qualifications (or Skills). Let's put under Qualifications. ThusQualifications
with list of those traits. But we need to avoid duplication: we already used those traits for responsibilities; we need to decide which is correct. Let's read original: "What you’ll do" includes the list of traits (storyteller, lead with data, keep things organized, passion for technology, be ambitious, act as a team player). Actually those are more like responsibilities/expected behaviors. "Who you are" includes: "We’re looking for someone who meets the minimum requirements to be considered for the role. If you meet these requirements, you are encouraged to apply." Then after that: "Minimum Requirements". So "Who you are" is just a intro before Minimum Requirements, not a list of traits. Wait I need to re-examine the text: Original snippet: "What you’ll do Be a storyteller. You have deep empathy for users and are able to adapt how you communicate to best reach and engage your audience and differentiate Stripe. You have excellent verbal and written communication skillsLead with data. You like working with data and insights and pair that with your passion for users to generate balanced and thoughtful points of view for how to take our products to marketKeep things organized. You are able to manage highly interdependent, complex projects and keep various work streams on trackHave a passion for technology. You are keen to learn about how things work and are able to explain technical concepts in ways that everyday people can understandBe Ambitious. You are eager to make an impact at Stripe. You thrive in a fast-moving, dynamic, hyper-growth environment and are able to operate fluidly between the 30,000-foot strategy level and the micro-detail to get things rightAct as a team player. Product Marketers collaborate across the Marketing team and with basically every team at Stripe. You are able to work with a range of disciplines to execute on your work Who you are We’re looking for someone who meets the minimum requirements to be considered for the role. If you meet these requirements, you are encouraged to apply. Minimum Requirements 7+ years prior product marketing experienceBachelor’s degree or equivalent experienceExcellent verbal and written communication skills, with experience translating technical features into benefits for a technical audienceBe able to leverage data to proactively identify opportunities and drive impactful results Hybrid work at Stripe ..." Thus "What you’ll do" includes the traits list. "Who you are" is just a short sentence encouraging apply. So we should not treat "Who you are" as qualifications; it's just filler. So we have: - About the role: combine "Who we are About Stripe" and "About The Team". - Responsibilities: the list from "What you’ll do". - Requirements: Minimum Requirements list. - Qualifications: maybe none? Could skip if no specific content beyond requirements. But we could put "Who you are" as a short paragraph? It says "We’re looking for someone who meets the minimum requirements to be considered for the role. If you meet these requirements, you are encouraged to apply." That's not substantive beyond requirements; maybe we can omit Qualifications section because it's not specific. 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 should not include Qualifications if it's just that generic line. - Skills: maybe we could extract skills from responsibilities? But we already used responsibilities for duties. Skills could be things like "excellent verbal and written communication skills", "data-driven", "project management", "technical explanation", "ambitious", "collaboration". However those are already in responsibilities. To avoid duplication, maybe we can put Skills empty or omit. Better to omit Skills if not distinct. - Benefits: list from "Additional benefits for this role may include: equity, company bonus or sales commissions/bonuses; 401(k) plan; medical, dental, and vision benefits; and wellness stipends." - Pay: salary range. - Schedule: Hybrid work at Stripe description. We must not include sections with filler like "commensurate with experience". We have concrete content. Now produce HTML. We need to wrap each section:Heading
then eitherfor prose or
- for lists.
For About the role: we have two paragraphs: "Who we are About Stripe" and "About The Team". We'll combine into maybe two
elements. Let's extract those paragraphs: "Who we are About Stripe Stripe is a financial infrastructure platform for businesses. Millions of companies—from the world’s largest enterprises to the most ambitious startups—use Stripe to accept payments, grow their revenue, and accelerate new business opportunities. Our mission is to increase the GDP of the internet, and we have a staggering amount of work ahead. That means you have an unprecedented opportunity to put the global economy within everyone’s reach while doing the most important work of your career." "About The Team Our Product Marketing team’s mission is to generate customer insights that inform Stripe’s product strategy, and lead go-to-market for our suite of products. Product Marketing is a highly cross-functional role at Stripe, partnering closely with Product and Engineering, Sales, Partnerships, Demand Generation and Campaigns to name a few. Different from many other Product Marketing teams, our team works across the entire product lifecycle, from helping shape the product, to driving launch and commercialization, to growing product adoption post-launch. We are looking for a Product Marketing Manager for Stripe’s Revenue suite (which includes Billing, Invoicing, Tax, and Revenue Recognition). In this role, you’ll craft the narrative for how our Revenue products deliver value to product and finance leaders, drive demand by partnering with the campaigns team, develop cross-product packages and bundles, and enable our sales team." We'll put each as
. Responsibilities: list items. We need to split the "What you’ll do" text into items. Let's parse: - Be a storyteller. You have deep empathy for users and are able to adapt how you communicate to best reach and engage your audience and differentiate Stripe. - Lead with data. You like working with data and insights and pair that with your passion for users to generate balanced and thoughtful points of view for how to take our products to market - Keep things organized. You are able to manage highly interdependent, complex projects and keep various work streams on track - Have a passion for technology. You are keen to learn about how things work and are able to explain technical concepts in ways that everyday people can understand - Be Ambitious. You are eager to make an impact at Stripe. You thrive in a fast-moving, dynamic, hyper-growth environment and are able to operate fluidly between the 30,000-foot strategy level and the micro-detail to get things right - Act
- for lists.
For About the role: we have two paragraphs: "Who we are About Stripe" and "About The Team". We'll combine into maybe two