Product Marketing Manager, Revenue suite

We need to output only HTML fragment, no /, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, "Who we are About Stripe ..." is description of company. Could be "About the role"? Actually "About the role" heading is for description of role. The posting includes "Who we are About Stripe ..." then "About The Team". Then "What you’ll do" (responsibilities). Then "Who you are" (requirements/qualifications). Then "Hybrid work at Stripe" (schedule? location). Then "Pay and benefits". Then other fluff. We need to avoid repeating job title as heading (not present). No Job ID. We need to remove boilerplate: cookie/navigation/legal/EEO etc. At end there is "Please find our California applicant personal information notice here. The application window will remain open for 100 days..." That's boilerplate; remove. Also "At Stripe, we're looking for people with passion, grit, and integrity..." etc. That's also boilerplate? Might be considered generic encouraging to apply; but it's not specific to role. Probably remove. We need to preserve all substantive information. Let's extract sections: - About the role / About the team: Could combine as "About the role" heading with description of Stripe and team mission. We have: "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." That's substantive. Could be under "About the role". We'll output

About the role

then a

with that text (maybe split into paragraphs). We'll keep as one paragraph or multiple? Use

for prose; we can split logically but not required. - Responsibilities: "What you’ll do" bullet list (though not bullet). It lists: Be a storyteller..., Lead with data..., Keep things organized..., Have a passion for technology..., Be Ambitious..., Act as a team player... Each is a sentence with bold? We'll treat as list items. Use

• for each. - Requirements/Qualifications: "Who you are" includes Minimum Requirements: 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/location. We'll treat that as Schedule section? Actually schedule: remote/hybrid expectations. Could be under Schedule. But we also have Pay and benefits section. We need to decide headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role, Responsibilities, Requirements (minimum requirements), Qualifications (maybe same as requirements? Could combine). Skills: maybe the bullet list under "What you’ll do" includes skills like storytelling, data-driven, organized, tech passion, ambitious, team player. Those could be Skills. But we already used those as Responsibilities. Actually "What you’ll do" is responsibilities. The bullet list there are more like expectations/qualities. Could treat as Skills. But instructions: Use
  • for any list of duties/requirements/benefits. So we need to decide which list corresponds to which heading. We have two lists: the "What you’ll do" (responsibilities) and the Minimum Requirements (requirements). Also we have "Hybrid work at Stripe" (schedule). And Pay and benefits. We could map: - About the role: description of Stripe and team. - Responsibilities: the "What you’ll do" list (storyteller, lead with data, etc.) - Requirements: Minimum Requirements (7+ years experience, bachelor's, communication skills, leverage data) - Qualifications: maybe we could also include "Excellent verbal and written communication skills, with experience translating technical features into benefits for a technical audience" but that's already in requirements. Could also include "Be able to leverage data to proactively identify opportunities and drive impactful results". That's also requirement. We might not need separate Qualifications if content overlaps; but we can still include Qualifications heading with same content? Better to avoid duplication. Perhaps we treat Requirements as the bullet list of minimum requirements, and Qualifications as the "Who you are" paragraph that 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." That's boilerplate; we can drop. Thus we may not need Qualifications heading. Skills: maybe we can extract from responsibilities the skills: storytelling, data-driven, project management, technical explanation, ambition, teamwork. Could list as Skills. But we already used those as responsibilities; but we could still list them under Skills as a separate list. However that would duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's present in source? The source lists them under "What you’ll do". If we also list them under Skills, we would be duplicating but not adding new info; still preserving. Might be okay but could be considered redundant. Better to follow typical structure: Responsibilities = duties; Skills = abilities/skills. The source doesn't explicitly label a skills section; but we can infer skills from responsibilities. However we might be adding interpretation (summarizing). Might be considered summarizing away detail? Not exactly; we are rephrasing. Safer to not create Skills section unless explicitly present. The source does not have a separate "Skills" heading. So we should not create Skills section unless there is explicit list of skills. There is not. So we omit Skills. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Check if Benefits and Pay are separate: The source has "Pay and benefits" paragraph with salary range and additional benefits. We could split into Pay and Benefits headings as per allowed headings. The instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have separate Pay and Benefits sections. We need to extract Pay: "The annual US base salary range for this role is $145,000 - $217,600. For sales roles, the range provided is the role’s On Target Earnings ("OTE") range, meaning that the range includes both the sales commissions/sales bonuses target and annual base salary for the role. This salary range may be inclusive of several career levels at Stripe and will be narrowed during the interview process based on a number of factors, including the candidate’s experience, qualifications, and location. Applicants interested in this role and who are not located in the US may request the annual salary range for their location during the interview process." That's pay info. Benefits: "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." We can make Benefits as a list. Schedule: Hybrid work at Stripe section: details about office vs remote expectations. We'll put under Schedule. Now we need to ensure we don't include boilerplate like "We look forward to hearing from you." etc. Also remove "At Stripe, we're looking for people with passion, grit, and integrity..." etc. Also remove "Please find our California applicant personal information notice here. The application window will remain open for 100 days..." etc. Now produce HTML fragment. Structure:

    About the role

    ... (combined description)

    Responsibilities

    • 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 skills
    • 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 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

    Requirements

    • 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

    Pay

    The annual US base salary range for this role is $145,000 - $217,600. For sales roles, the range provided is the role’s On Target Earnings ("OTE") range, meaning that the range includes both the sales commissions/sales bonuses target and annual base salary for the role. This salary range may be inclusive of several career levels at Stripe and will be narrowed during the interview process based on a number of factors, including the candidate’s experience, qualifications, and location. Applicants interested in this role and who are not located in the US may request the annual salary range for their location during the interview process.

    Benefits

    • equity
    • company bonus or sales commissions/bonuses
    • 401(k) plan
    • medical, dental, and vision benefits
    • wellness stipends

    Schedule

    Hybrid work at Stripe: This role is available either in an office or a remote location (35+ miles or 56+ km from a Stripe office). In-office expectations: Office-assigned Stripes spend at least 50% of the time in a given month in their local office or with users. This hits a balance